|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved as IETF document
|
|
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
(http://trustee.ietf.org/license-info)
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Approved May 2015 as Standard Track
|
|
6.
|
The degree of stability or maturity of the 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).
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ECMAScript]/
Ecma International, "ECMAScript Language Specification,/
5.1 Edition", ECMA Standard 262, June 2011,/
http://www.ecma-international.org/ecma-262/5.1//
ECMA-262.pdf./
/
[IANA.MediaTypes]/
Internet Assigned Numbers Authority (IANA), "Media Types",/
http://www.iana.org/assignments/media-types./
/
[ITU.X690.1994]/
International Telecommunications Union, "Information/
Technology - ASN.1 encoding rules: Specification of Basic/
Encoding Rules (BER), Canonical Encoding Rules (CER) and/
Distinguished Encoding Rules (DER)", ITU-T Recommendation/
X.690, 1994./
[JWA] Jones, M., "JSON Web Algorithms (JWA)", RFC 7518,/
DOI 10.17487/RFC7518, May 2015,/
http://www.rfc-editor.org/info/rfc7518./
/
[JWE] Jones, M. and J. Hildebrand, "JSON Web Encryption (JWE)",/
RFC 7516, DOI 10.17487/RFC7516, May 2015,/
http://www.rfc-editor.org/info/rfc7516./
/
[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web/
Signature (JWS)", RFC 7515, DOI 10.17487/RFC7515, May/
2015, http://www.rfc-editor.org/info/rfc7515./
/
[RFC20] Cerf, V., "ASCII format for Network Interchange", STD 80,/
RFC 20, DOI 10.17487/RFC0020, October 1969,/
http://www.rfc-editor.org/info/rfc20./
/
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part Two: Media Types", RFC 2046,/
DOI 10.17487/RFC2046, November 1996,/
http://www.rfc-editor.org/info/rfc2046./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
http://www.rfc-editor.org/info/rfc2119./
/
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,/
DOI 10.17487/RFC2818, May 2000,/
http://www.rfc-editor.org/info/rfc2818./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November/
2003, http://www.rfc-editor.org/info/rfc3629./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, DOI 10.17487/RFC3986, January 2005,/
http://www.rfc-editor.org/info/rfc3986./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,/
http://www.rfc-editor.org/info/rfc4648./
/
[RFC4945] Korver, B., "The Internet IP Security PKI Profile of/
IKEv1/ISAKMP, IKEv2, and PKIX", RFC 4945,/
DOI 10.17487/RFC4945, August 2007,/
http://www.rfc-editor.org/info/rfc4945./
[RFC4949] Shirey, R., "Internet Security Glossary, Version 2",/
FYI 36, RFC 4949, DOI 10.17487/RFC4949, August 2007,/
http://www.rfc-editor.org/info/rfc4949./
/
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security/
(TLS) Protocol Version 1.2", RFC 5246,/
DOI 10.17487/RFC5246, August 2008,/
http://www.rfc-editor.org/info/rfc5246./
/
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,/
Housley, R., and W. Polk, "Internet X.509 Public Key/
Infrastructure Certificate and Certificate Revocation List/
(CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008,/
http://www.rfc-editor.org/info/rfc5280./
/
[RFC6125] Saint-Andre, P. and J. Hodges, "Representation and/
Verification of Domain-Based Application Service Identity/
within Internet Public Key Infrastructure Using X.509/
(PKIX) Certificates in the Context of Transport Layer/
Security (TLS)", RFC 6125, DOI 10.17487/RFC6125, March/
2011, http://www.rfc-editor.org/info/rfc6125./
/
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data/
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March/
2014, http://www.rfc-editor.org/info/rfc7159./
/
[UNICODE] The Unicode Consortium, "The Unicode Standard",/
http://www.unicode.org/versions/latest/./
/
|
|
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.
|
|
