|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC (Proposed Standard)
|
|
3.
|
Justification for the specific reference:
|
|
|
Revised Recommendation H.248.57 describes the use of RTP transport multiplexing on H.248 controlled media gateways. It uses the "a=rtcp-mux" SDP attribute as defined by IETF RFC 5761 to indicate the use of RTP transport multiplexing.
|
|
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=5761
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since April 2010. It updates RFC 3550 and RFC 3551. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
It is a standards-track document and is currently in the "Proposed Standard" state.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
IETF RFC 5761 is one of a suite of document related to the Real Time Protocol (RTP) [RFC 3550]. Updates RFC 3550, RFC 3551. Errata exist.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References:/
----------------------------/
[1] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,/
"RTP: A Transport Protocol for Real-Time Applications", STD 64,/
RFC 3550, July 2003./
/
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[3] Turletti, T., "RTP Payload Format for H.261 Video Streams",/
RFC 2032, October 1996./
/
[4] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,/
"Extended RTP Profile for Real-time Transport Control Protocol/
(RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July 2006./
/
[5] Friedman, T., Caceres, R., and A. Clark, "RTP Control Protocol/
Extended Reports (RTCP XR)", RFC 3611, November 2003./
/
[6] Ott, J., Chesterfield, J., and E. Schooler, "RTP Control/
Protocol (RTCP) Extensions for Single-Source Multicast Sessions/
with Unicast Feedback", RFC 5760, February 2010./
/
[7] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video/
Conferences with Minimal Control", STD 65, RFC 3551, July 2003./
/
[8] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session/
Description Protocol", RFC 4566, July 2006./
/
[9] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with/
Session Description Protocol (SDP)", RFC 3264, June 2002./
/
[10] Huitema, C., "Real Time Control Protocol (RTCP) attribute in/
Session Description Protocol (SDP)", RFC 3605, October 2003./
/
[11] Westerlund, M., "A Transport Independent Bandwidth Modifier for/
the Session Description Protocol (SDP)", RFC 3890,/
September 2004./
/
[12] Casner, S., "Session Description Protocol (SDP) Bandwidth/
Modifiers for RTP Control Protocol (RTCP) Bandwidth", RFC 3556,/
July 2003./
/
[13] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K./
Norrman, "The Secure Real-time Transport Protocol (SRTP)",/
RFC 3711, March 2004./
/
Informative References/
-----------------------------/
/
[14] Srisuresh, P. and K. Egevang, "Traditional IP Network Address/
Translator (Traditional NAT)", RFC 3022, January 2001./
/
[15] Clark, D. and D. Tennenhouse, "Architectural Considerations for/
a New Generation of Protocols", Proceedings of ACM/
SIGCOMM 1990, September 1990./
/
[16] Casner, S. and S. Deering, "First IETF Internet Audiocast", ACM/
SIGCOMM Computer Communication Review, Volume 22, Number 3,/
July 1992./
/
[17] Even, R., "RTP Payload Format for H.261 Video Streams",/
RFC 4587, August 2006./
/
[18] Johansson, I. and M. Westerlund, "Support for Reduced-Size/
Real-Time Transport Control Protocol (RTCP): Opportunities and/
Consequences", RFC 5506, April 2009./
/
[19] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A/
Protocol for Network Address Translator (NAT) Traversal for/
Offer/Answer Protocols", RFC 5245, April 2010./
/
[20] Casner, S. and V. Jacobson, "Compressing IP/UDP/RTP Headers for/
Low-Speed Serial Links", RFC 2508, February 1999./
/
[21] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H.,/
Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le, K.,/
Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, T.,/
Yoshimura, T., and H. Zheng, "RObust Header Compression (ROHC):/
Framework and four profiles: RTP, UDP, ESP, and uncompressed",/
RFC 3095, July 2001./
/
[22] Sandlund, K., Pelletier, G., and L-E. Jonsson, "The RObust/
Header Compression (ROHC) Framework", RFC 5795, March 2010.
|
|
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):
|
|
|
None.
|
|
