|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC (July 2006).
|
|
3.
|
Justification for the specific reference:
|
|
|
It is used as a reference in the Recommendation ITU-T Q.30xx_VoLTE_Interconnection_FW
|
|
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=4566
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since July 2006. Obsoletes: RFC 2327, 3266
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4566 was published in July, 2006. It is a standards-track document and is currently in the "Proposed standard" state. Obsoletes RFCs 2327, 3266; Errata exist.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 4566 is a basic component of the basic suite of internet protocols and standards and is widely used by the internet community. Obsoletes RFCs 2327, 3266. Errata exist.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, November 1987./
[2] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987./
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[4] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005./
[5] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003./
[6] Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998./
[7] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005./
[8] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998./
[9] Alvestrand, H., "Tags for the Identification of Languages", BCP 47, RFC 3066, January 2001./
[10] Olson, S., Camarillo, G., and A. Roach, "Support for IPv6 in Session Description Protocol (SDP)", RFC 3266, June 2002./
[11] Faltstrom, P., Hoffman, P., and A. Costello, "Internationalizing Domain Names in Applications (IDNA)", RFC 3490, March 2003./
[12] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 3548, July 2003.
|
|
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.
|
|
