|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved Standards Track document. Also known as STD 65.
|
|
3.
|
Justification for the specific reference:
|
|
|
H.248.1 Annex E defines an RTP package. Part of this package defines statistics that are based on RTCP packets which are defined in this RFC.
|
|
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=3551
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since 2003. Although new, it obsoletes RFC 1890 which has been in existence since January, 1996 and arises from draft-ietf-avt-profile-new-13.txt, which has been reviewed extensively in IETF. Updated by: 5761, 7007 , Obsoletes: 1890
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 3551 was published in 2003. It is a standards-track document and is currently in the "Proposed Standard" state. Updated by RFC 7007, RFC 5761. Obsoletes RFC 1890.
Obsoletes RFC 1890.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 3551 is a component of the suite of multimedia over packet network protocols and, as a successor to RFC 1890, is widely used.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[1] Schulzrinne, H., S. Casner, R. Frederick, and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications," Work in progress, revision to RFC 1889./
[2] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement Levels," BCP 14, RFC 2119, March 1997./
[3] Apple Computer, "Audio Interchange File Format AIFF-C," August 1991. (Also ftp://ftp.sgi.com/sgi/aiff-c.9.26.91.ps.Z)./
Informative References/
[4] Braden, R., D. Clark, S. Shenker, "Integrated Services in the Internet Architecture: an Overview," RFC 1633, June 1994./
[5] Blake, S., D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss, "An Architecture for Differentiated Service," RFC 2475, December 1998./
[6] Handley, M. and V. Jacobson, "SDP: Session Description Protocol," RFC 2327, April 1998./
[7] Casner, S. and P. Hoschka, "MIME Type Registration of RTP Payload Types," Internet Draft, Internet Engineering Task Force, Work in progress./
[8] Freed, N., J. Klensin, and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures," BCP 13, RFC 2048, November 1996./
[9] Zopf, R., "Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)," RFC 3389, September 2002./
[10] IMA Digital Audio Focus and Technical Working Groups, "Recommended practices for enhancing digital audio compatibility in multimedia systems (version 3.00)," tech. rep., Interactive Multimedia Association, Annapolis, Maryland, October 1992./
[11] Deleam, D. and J.-P. Petit, "Real-time implementations of the recent ITU-T low bit rate speech coders on the TI TMS320C54X DSP: results, methodology, and applications," in Proc. Of International Conference on Signal Processing, Technology, and Applications (ICSPAT) , (Boston, Massachusetts), pp. 1656--1660, October 1996./
[12] Mouly, M. and M.-B. Pautet, The GSM system for mobile communications Lassay-les-Chateaux, France: Europe Media Duplication, 1993./
[13] Degener, J., "Digital Speech Compression," Dr. Dobb's Journal , December 1994./
[14] Redl, S., M. Weber, and M. Oliphant, An Introduction to GSM Boston: Artech House, 1995./
[15] Hoffman, D., G. Fernando, V. Goyal, and M. Civanlar, "RTP Payload Format for MPEG1/MPEG2 Video," RFC 2250, January 1998./
[16] Jayant, N. and P. Noll, Digital Coding of Waveforms—Principles and Applications to Speech and Video Englewood Cliffs, New Jersey: Prentice-Hall, 1984./
[17] McKay, K., "RTP Payload Format for PureVoice(tm) Audio", RFC 2658, August 1999./
[18] Perkins, C., I. Kouvelas, O. Hodson, V. Hardman, M. Handley, J.-C. Bolot, A. Vega-Garcia, and S. Fosse-Parisis, "RTP Payload for Redundant Audio Data," RFC 2198, September 1997./
[19] Speer, M. and D. Hoffman, "RTP Payload Format of Sun's CellB Video Encoding," RFC 2029, October 1996./
[20] Berc, L., W. Fenner, R. Frederick, and S. McCanne, "RTP Payload Format for JPEG-Compressed Video," RFC 2435, October 1996./
[21] Turletti, T. and C. Huitema, "RTP Payload Format for H.261 Video Streams," RFC 2032, October 1996./
[22] Zhu, C., "RTP Payload Format for H.263 Video Streams," RFC 2190, September 1997./
[23] Bormann, C., L. Cline, G. Deisher, T. Gardos, C. Maciocco, D. Newell, J. Ott, G. Sullivan, S. Wenger, C. Zhu, "RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)," RFC 2429, October 1998./
[24] Schulzrinne, H., A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," RFC 2326, April 1998./
[25] Deering, S., "Host Extensions for IP Multicasting," STD 5, RFC 1112, August 1989.
|
|
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.
|
|
