|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6776 (2012)
|
|
Title:
|
Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC.
|
|
3.
|
Justification for the specific reference:
|
|
|
This RTCP information element is used by ITU-T H.248.87 as part of monitoring RTP traffic.
|
|
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=6776
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 6776 is a Proposed Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 6776 was extensively discussed and is in the meanwhile one years available.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 6776 belongs to the framework of RTCP extension reports, based on RFC 3611, which defines a packet type carried by the RTCP protocol specified in RFC 3550.
|
|
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./
/
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V./
Jacobson, "RTP: A Transport Protocol for Real-Time/
Applications", STD 64, RFC 3550, July 2003./
/
[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,/
"RTP Control Protocol Extended Reports (RTCP XR)",/
RFC 3611, November 2003./
/
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,/
"Network Time Protocol Version 4: Protocol and Algorithms/
Specification", RFC 5905, June 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):
|
|
|
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.
|
