|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
RFC 5391 defines the RTP payload for ITU-T G.711.1. The RTP payload format allows for packetization of one or more Network Abstraction Layer Units, produced by a G.711.1 audio encoder, in each RTP payload.
|
|
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=5391
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 5391 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.711.1 Annex B defines procedures for use of G.711.1 in H.245 based systems.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative references/
[1] Recommendation ITU-T G.711.1, "Wideband embedded extension for G.711 pulse code modulation", March 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] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005./
[7] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006./
[8] Casner, S., "Media Type Registration of RTP Payload Formats", RFC 4855, February 2007./
Informative References/
[8] Recommendation ITU-T G.711, "Pulse code modulation (PCM) of voice frequencies, , November 1988./
[9] Zopf, R., " Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)", RFC 3389, September 2002./
[10] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, "The Secure Real-time Transport Protocol (SRTP)", RFC 3711, March 2004.
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
