|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4756 (2006)
|
|
Title:
|
Forward Error Correction Grouping Semantics in Session Description Protocol, November 2006
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC
|
|
3.
|
Justification for the specific reference:
|
|
|
V.152 defines SDP usage for SDP configured V.152 gateways. RFC 4756 defines the SDP elements for Forward Error Correction (FEC) method. FEC is supported by V.152
|
|
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=4756
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since November 2006.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4756 was published in November, 2006. It is a standards-track document and is currently in the "Proposed standard" state. Current standards status of this document can be found at http://www.rfc-editor.org/rfcxx00.html.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 4756 is a basic component of the basic suite of internet protocols and standards and is widely used by the internet community.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[2] Camarillo, G., Eriksson, G., Holler, J., and H. Schulzrinne, "Grouping of Media Lines in the Session Description Protocol (SDP)", RFC 3388, December 2002./
[3] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006./
|
|
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.
|
