|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5576 (2009)
|
|
Title:
|
Source-Specific Media Attributes in the Session Description Protocol (SDP)
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
This Recommendation allows local and remote pausing of RTP streams referenced by their SSRC identifier. RFC 5576 provides SDP attributes that allow source specific information to be set. This provides a means of identifying the relevant streams.
|
|
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=5576
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 5576 has been in existence since 2009.
|
|
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 5576 belongs to the suite of RFCs related to the RTP.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model/
with Session Description Protocol (SDP)", RFC 3264,/
June 2002./
/
[RFC3388] Camarillo, G., Eriksson, G., Holler, J., and H./
Schulzrinne, "Grouping of Media Lines in the Session/
Description Protocol (SDP)", RFC 3388, December 2002./
/
[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./
/
[RFC4756] Li, A., "Forward Error Correction Grouping Semantics in/
Session Description Protocol", RFC 4756, November 2006./
/
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 5226,/
May 2008./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
|
|
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.
|
|
