References from draft-ietf-oauth-browser-based-apps
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-ietf-httpbis-rfc6265bis | Cookies: HTTP State Management Mechanism References Referenced by | Proposed Standard | normatively 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 6750 | The OAuth 2.0 Authorization Framework: Bearer Token Usage References Referenced by | Proposed Standard | normatively references | |
| RFC 6819 | OAuth 2.0 Threat Model and Security Considerations References Referenced by | Informational | informatively references | |
| RFC 7636 | Proof Key for Code Exchange by OAuth Public Clients References Referenced by | Proposed Standard | normatively references | |
| RFC 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by | Best Current Practice | normatively references | |
| RFC 8252 | OAuth 2.0 for Native Apps References Referenced by | Best Current Practice | normatively references | |
| RFC 8707 | Resource Indicators for OAuth 2.0 References Referenced by | Proposed Standard | normatively references | |
| RFC 9449 | OAuth 2.0 Demonstrating Proof of Possession (DPoP) References Referenced by | Proposed Standard | normatively references | |
| RFC 9700 | Best Current Practice for OAuth 2.0 Security References Referenced by | Best Current Practice | normatively references |