|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
G.719 Annex C defines the use of G.719 with H.245 based systems. RFC 3984 describes an RTP Payload format for the G.719 codec. The RTP payload format allows packetization of G.719 audio frames.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=5404
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 5404 is a Proposed Standard. This document has been reviewed extensively in IETF.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state. Current standards status of this document can be found at http://www.rfc-editor.org/rfcxx00.html
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
G.719 Annex C defines procedures for use of G.719 in H.245 based systems.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[1] Recommendation ITU-T G.719 extension for 20 kHz fullband audio", April 2008./
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[3] Rosenberg, J. and Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, June 2002. /
[4] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003./
[5] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video Conferences with Minimal Control", STD 65, RFC 3551, July 2003./
[6] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006./
[7] Crocker,D., and P. Overell, “Augmented BNF for Syntax Specifications: ABNF”, STD 68, RFC 5234, January 2008./
[8] Eggert, L. and G. Fairhurst, “Unicast UDP Usage Guidelines for Application Designers”, BCP 145, RFC 5405, November 2008./
Informative References/
[9] Perkings, C., Kouvelas, I., Hodson, O., Hardman, V., Handley, M., Bolot, J., Vega-Garcia, A., and S. Fosse-Parisis, “RTP Payload for Redundant Audio Data”, RFC 2198, September 1997. /
[10] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998./
[11] Handley, M., Perkins, C., and E. Whelan, "Session Announcement Protocol", RFC 2974, October 2000./
[12] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, "The Secure Real-time Transport Protocol (SRTP)", RFC 3711, March 2004./
[13] Castagno, R. and D. Singer, "MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files", RFC 3839, July 2004./
[14] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005. /
[15] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005./
[16] Y Lim and D. Singer, "MIME Type Registration for MPEG-4", RFC 4337, March 2006./
[17] Casner, S., "Media Type Registration of RTP Payload Formats", RFC 4855, February 2007./
[18] Li, A., "RTP Payload Format for Generic Forward Error Correction", RFC 5109, December 2007./
[19] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
RFC 5404 defines the RTP payload for ITU-T G.719 audio. The RTP payload format allows for packetization of G.719 audio frames and transmission over IP networks.
|
|
