|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5104 (2008)
|
|
Title:
|
Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF).
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
This Recommendation allows the remote pausing of RTP streams using RTP feedback messages. RFC 5104 defines the codec control messaging framework which is used to achieve this.
|
|
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=5104
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 5104 has been in existence since 2008. Although new it arises from draft-ietf-avt-avpf-ccm.txt, which 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 ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 5104 defines specifies a few extensions to the messages defined in the Audio-Visual Profile with Feedback (AVPF).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[RFC4585] 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./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V./
Jacobson, "RTP: A Transport Protocol for Real-Time/
Applications", STD 64, RFC 3550, July 2003./
/
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session/
Description Protocol", RFC 4566, July 2006./
/
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model/
with Session Description Protocol (SDP)", RFC 3264, June/
2002./
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 2434,/
October 1998./
/
[RFC4234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", RFC 4234, October 2005./
/
Informative References/
/
[Basso] Basso, A., Levin, O., and N. Ismail, "Requirements for/
transport of video control commands", Work in Progress,/
October 2004./
/
[AVC] Joint Video Team of ITU-T and ISO/IEC JTC 1, Draft ITU-T/
Recommendation and Final Draft International Standard of/
Joint Video Specification (ITU-T Rec. H.264 | ISO/IEC/
14496-10 AVC), Joint Video Team (JVT) of ISO/IEC MPEG and/
ITU-T VCEG, JVT-G050, March 2003./
/
[H245] ITU-T Rec. H.245, "Control protocol for multimedia/
communication", May 2006./
/
[NEWPRED] S. Fukunaga, T. Nakai, and H. Inoue, "Error Resilient/
Video Coding by Dynamic Replacing of Reference Pictures",/
in Proc. Globcom'96, vol. 3, pp. 1503 - 1508, 1996./
/
[SRTP] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K./
Norrman, "The Secure Real-time Transport Protocol/
(SRTP)", RFC 3711, March 2004./
/
[RFC2032] Turletti, T. and C. Huitema, "RTP Payload Format for/
H.261 Video Streams", RFC 2032, October 1996./
/
[SAVPF] Ott, J. and E. Carrara, "Extended Secure RTP Profile for/
RTCP-based Feedback (RTP/SAVPF)", Work in Progress,/
November 2007./
/
[RFC3525] Groves, C., Pantaleo, M., Anderson, T., and T. Taylor,/
"Gateway Control Protocol Version 1", RFC 3525, June/
2003./
/
[RFC3448] Handley, M., Floyd, S., Padhye, J., and J. Widmer, "TCP/
Friendly Rate Control (TFRC): Protocol Specification",/
RFC 3448, January 2003./
/
[H.271] ITU-T Rec. H.271, "Video Back Channel Messages", June/
2006./
/
/
[RFC3890] Westerlund, M., "A Transport Independent Bandwidth/
Modifier for the Session Description Protocol (SDP)", RFC/
3890, September 2004./
/
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram/
Congestion Control Protocol (DCCP)", RFC 4340, March/
2006./
/
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,/
A., Peterson, J., Sparks, R., Handley, M., and E./
Schooler, "SIP: Session Initiation Protocol", RFC 3261,/
June 2002./
/
[RFC2198] Perkins, 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./
/
[RFC4587] Even, R., "RTP Payload Format for H.261 Video Streams",/
RFC 4587, August 2006./
/
[RFC5117] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 5117,/
January 2008./
/
[XML-MC] Levin, O., Even, R., and P. Hagendorf, "XML Schema for/
Media Control", Work in Progress, November 2007./
/
|
|
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.
|
|
