References from draft-gazitt-oauth-authzen-claims
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| draft-gazitt-oauth-authzen-issuance |
AuthZEN Profile for OAuth 2.0 Token Issuance
References Referenced by |
normatively references | ||
| draft-gazitt-oauth-authzen-token-exchange |
AuthZEN Binding for OAuth 2.0 Token Exchange
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6749 |
The OAuth 2.0 Authorization Framework
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7515 |
JSON Web Signature (JWS)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7519 |
JSON Web Token (JWT)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7643 |
System for Cross-domain Identity Management: Core Schema
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8707 |
Resource Indicators for OAuth 2.0
References Referenced by |
Proposed Standard | informatively references | |
| RFC 9068 |
JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
References Referenced by |
Proposed Standard | normatively references |