|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
It is used as a reference in the Recommendation ITU-T Q.1912.5
|
|
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=4040
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of the referred RFC is "Standards Track".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of the referred RFC is "Standards Track".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
See item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[1] Handley, M. and C. Perkins, "Guidelines for Writers of RTP/
Payload Format Specifications", BCP 36, RFC 2736, December 1999./
/
[2] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part One: Format of Internet Message Bodies",/
RFC 2045, November 1996./
/
[3] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet/
Mail Extensions (MIME) Part Four: Registration Procedures", BCP/
13, RFC 2048, November 1996./
/
[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. and V. Jacobson, "SDP: Session Description/
Protocol", RFC 2327, April 1998./
/
[7] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with/
Session Description Protocol (SDP)", RFC 3264, June 2002./
/
[8] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[9] Sjoberg, J., Westerlund, M., Lakaniemi, A., and Q. Xie, "Real-/
Time Transport Protocol (RTP) Payload Format and File Storage/
Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate/
Wideband (AMR-WB) Audio Codecs", RFC 3267, June 2002./
/
Informative References/
[10] Ong, L., Rytina, I., Garcia, M., Schwarzbauer, H., Coene, L.,/
Lin, H., Juhasz, I., Holdrege, M., and C. Sharp, "Framework/
Architecture for Signaling Transport", RFC 2719, October 1999./
/
[11] 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):
|
|
|
All RFCs are 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.
|
|
