|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 8414
|
|
Title:
|
RFC 8414: OAuth 2.0 Authorization Server Metadata, IETF, June 2018
|
|
|
2.
|
Status of approval:
|
|
|
RFC 8414 was published as an IETF Proposed Standard in June 2018. Finalized IETF document.
|
|
3.
|
Justification for the specific reference:
|
|
|
RFC 8414 defines the authorization server metadata discovery mechanism (well-known URI, issuer identifier). X.f2sp contains multiple shall requirements referencing RFC 8414: authorization servers "shall distribute discovery metadata via the metadata document as specified in [RFC8414]"; clients "shall only use authorization server metadata retrieved from the metadata document as specified in [RFC8414]"; and the issuer identifier concept used throughout X.f2sp is defined in RFC 8414. Incorporation of the full text is inappropriate as the full metadata discovery specification is not being reproduced. Freely available. No ITU-T or ISO/IEC equivalent.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known patent claims. Freely available.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Published June 2018. Widely implemented in authorization server products as the standard discovery mechanism. Freely available at https://www.rfc-editor.org/rfc/rfc8414.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Stable, finalized IETF Proposed Standard. Not revised since June 2018.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Referenced by OpenID Connect Discovery (which extends it) and by numerous OAuth 2.0 profiles. No ITU-T/ISO/IEC equivalent.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative references within RFC 8414: RFC 2119, RFC 3986, RFC 5785, RFC 7159, RFC 7517, RFC 7591, RFC 8126. All IETF documents; IETF is qualified under Annex B.
|
|
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):
|
|
|
|
