|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved as IETF document
|
|
3.
|
Justification for the specific reference:
|
|
|
Needed to secure the access to all services
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
https://datatracker.ietf.org/ipr/search/
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standards track RFC approved May 2015.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards track RFC approved May 2015.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
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]/
IANA, "Media Types",/
http://www.iana.org/assignments/media-types./
/
[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/RFC, 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./
/
[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./
/
[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./
/
[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/./
[CanvasApp]/
Facebook, "Canvas Applications", 2010,/
http://developers.facebook.com/docs/authentication//
canvas./
/
[JSS] Bradley, J. and N. Sakimura (editor), "JSON Simple Sign",/
September 2010, http://jsonenc.info/jss/1.0/./
[MagicSignatures]/
Panzer, J., Ed., Laurie, B., and D. Balfanz, "Magic/
Signatures", January 2011,/
http://salmon-protocol.googlecode.com/svn//
trunk/draft-panzer-magicsig-01.html./
/
[OASIS.saml-core-2.0-os]/
Cantor, S., Kemp, J., Philpott, R., and E. Maler,/
"Assertions and Protocols for the OASIS Security Assertion/
Markup Language (SAML) V2.0", OASIS Standard/
saml-core-2.0-os, March 2005,/
http://docs.oasis-open.org/security/saml/v2.0//
saml-core-2.0-os.pdf./
/
[POSIX.1] IEEE, "The Open Group Base Specifications Issue 7", IEEE/
Std 1003.1, 2013 Edition, 2013,/
http://pubs.opengroup.org/onlinepubs/9699919799//
basedefs/V1_chap04.html#tag_04_15./
/
[RFC3275] Eastlake 3rd, D., Reagle, J., and D. Solo, "(Extensible/
Markup Language) XML-Signature Syntax and Processing",/
RFC 3275, DOI 10.17487/RFC3275, March 2002,/
http://www.rfc-editor.org/info/rfc3275./
/
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:/
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,/
http://www.rfc-editor.org/info/rfc3339./
/
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally/
Unique IDentifier (UUID) URN Namespace", RFC 4122,/
DOI 10.17487/RFC4122, July 2005,/
http://www.rfc-editor.org/info/rfc4122./
/
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 5226,/
DOI 10.17487/RFC5226, May 2008,/
http://www.rfc-editor.org/info/rfc5226./
/
[RFC6755] Campbell, B. and H. Tschofenig, "An IETF URN Sub-Namespace/
for OAuth", RFC 6755, DOI 10.17487/RFC6755, October 2012,/
http://www.rfc-editor.org/info/rfc6755./
/
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type/
Specifications and Registration Procedures", BCP 13,/
RFC 6838, DOI 10.17487/RFC6838, January 2013,/
http://www.rfc-editor.org/info/rfc6838./
[SWT] Hardt, D. and Y. Goland, "Simple Web Token (SWT)", Version/
0.9.5.1, November 2009, http://msdn.microsoft.com/en-us//
library/windowsazure/hh781551.aspx./
/
[W3C.CR-xml11-20060816]/
Cowan, J., "Extensible Markup Language (XML) 1.1 (Second/
Edition)", World Wide Web Consortium Recommendation/
REC-xml11-20060816, August 2006,/
http://www.w3.org/TR/2006/REC-xml11-20060816./
/
[W3C.REC-xml-c14n-20010315]/
Boyer, J., "Canonical XML Version 1.0", World Wide Web/
Consortium Recommendation REC-xml-c14n-20010315, March/
2001, http://www.w3.org/TR/2001/REC-xml-c14n-20010315.
|
|
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.
|
|
