|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
December 2011 as Standards Track
|
|
3.
|
Justification for the specific reference:
|
|
|
The referenced document constitutes provisions of this Recommendation
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG).
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6454
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC20] Cerf, V., "ASCII format for network interchange", RFC 20,/
October 1969./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,/
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext/
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999./
/
[RFC3864] Klyne, G., Nottingham, M., and J. Mogul, "Registration/
Procedures for Message Header Fields", BCP 90, RFC 3864,/
September 2004./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, January 2005./
/
[RFC4790] Newman, C., Duerst, M., and A. Gulbrandsen, "Internet/
Application Protocol Collation Registry", RFC 4790,/
March 2007./
/
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for/
Syntax Specifications: ABNF", STD 68, RFC 5234,/
January 2008./
/
[RFC5890] Klensin, J., "Internationalized Domain Names for/
Applications (IDNA): Definitions and Document Framework",/
RFC 5890, August 2010. /
[RFC5891] Klensin, J., "Internationalized Domain Names in/
Applications (IDNA): Protocol", RFC 5891, August 2010./
/
[Unicode6] The Unicode Consortium, "The Unicode Standard, Version/
6.0.0", 2011,/
http://www.unicode.org/versions/Unicode6.0.0/.
|
|
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):
|
|
|
None.
|
|
