References from draft-ietf-oauth-pop-architecture

This is an experimental product. 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 132 Guidance for Authentication, Authorization, and Accounting (AAA) Key Management
Refs Ref'd by
Best Current Practice informatively references
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
BCP 195 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Refs Ref'd by
Best Current Practice normatively references
draft-hardjono-oauth-kerberos OAuth 2.0 support for the Kerberos V5 Authentication Protocol
Refs Ref'd by
informatively references
draft-ietf-oauth-pop-key-distribution OAuth 2.0 Proof-of-Possession: Authorization Server to Client Key Distribution
Refs Ref'd by
Proposed Standard normatively references
draft-ietf-oauth-proof-of-possession Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)
Refs Ref'd by
Proposed Standard normatively references
draft-ietf-oauth-signed-http-request A Method for Signing HTTP Requests for OAuth
Refs Ref'd by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 4120 The Kerberos Network Authentication Service (V5)
Refs Ref'd by
Proposed Standard informatively references
RFC 4279 Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)
Refs Ref'd by
Proposed Standard informatively references
RFC 4347 Datagram Transport Layer Security
Refs Ref'd by
Proposed Standard informatively references
RFC 4962 Guidance for Authentication, Authorization, and Accounting (AAA) Key Management
Refs Ref'd by
Best Current Practice informatively references
RFC 5056 On the Use of Channel Bindings to Secure Channels
Refs Ref'd by
Proposed Standard informatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
Refs Ref'd by
Proposed Standard normatively references
RFC 5849 The OAuth 1.0 Protocol
Refs Ref'd by
Informational informatively references
RFC 6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
Refs Ref'd by
Proposed Standard informatively references
RFC 6749 The OAuth 2.0 Authorization Framework
Refs Ref'd by
Proposed Standard normatively references
RFC 6750 The OAuth 2.0 Authorization Framework: Bearer Token Usage
Refs Ref'd by
Proposed Standard informatively references
RFC 6819 OAuth 2.0 Threat Model and Security Considerations
Refs Ref'd by
Informational informatively references
RFC 7252 The Constrained Application Protocol (CoAP)
Refs Ref'd by
Proposed Standard informatively references
RFC 7519 JSON Web Token (JWT)
Refs Ref'd by
Proposed Standard normatively references
RFC 7525 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Refs Ref'd by
Best Current Practice normatively references
RFC 7662 OAuth 2.0 Token Introspection
Refs Ref'd by
Proposed Standard normatively references