Skip to main content

References from draft-richer-oauth-httpsig

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.

Reference type help

Document Title Status Type Downref
BCP 195
References Referenced by
normatively references
draft-ietf-oauth-client-id-metadata-document OAuth Client ID Metadata Document
References Referenced by
informatively references
draft-ietf-oauth-signed-http-request A Method for Signing HTTP Requests for OAuth
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 7235 Hypertext Transfer Protocol (HTTP/1.1): Authentication
References Referenced by
Proposed Standard normatively references
RFC 7517 JSON Web Key (JWK)
References Referenced by
Proposed Standard normatively references
RFC 7518 JSON Web Algorithms (JWA)
References Referenced by
Proposed Standard normatively references
RFC 7591 OAuth 2.0 Dynamic Client Registration Protocol
References Referenced by
Proposed Standard normatively references
RFC 7800 Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)
References Referenced by
Proposed Standard normatively references
RFC 8032 Edwards-Curve Digital Signature Algorithm (EdDSA)
References Referenced by
Informational normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8705 OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
References Referenced by
Proposed Standard normatively references
RFC 8792 Handling Long Lines in Content of Internet-Drafts and RFCs
References Referenced by
Informational normatively references
RFC 9126 OAuth 2.0 Pushed Authorization Requests
References Referenced by
Proposed Standard normatively references
RFC 9421 HTTP Message Signatures
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 9530 Digest Fields
References Referenced by
Proposed Standard normatively references
RFC 9651 Structured Field Values for HTTP
References Referenced by
Proposed Standard normatively references
RFC 9701 JSON Web Token (JWT) Response for OAuth Token Introspection
References Referenced by
Proposed Standard informatively references
RFC 9864 Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)
References Referenced by
Proposed Standard normatively references