Skip to main content

References from draft-ramseyer-grow-peering-api

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
RFC 3912 WHOIS Protocol Specification
References Referenced by
Draft Standard informatively references
RFC 4271 A Border Gateway Protocol 4 (BGP-4)
References Referenced by
Draft Standard informatively references
RFC 5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
References Referenced by
Proposed Standard informatively references
RFC 6480 An Infrastructure to Support Secure Internet Routing
References Referenced by
Informational informatively 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 7454 BGP Operations and Security
References Referenced by
Best Current Practice informatively references
RFC 7515 JSON Web Signature (JWS)
References Referenced by
Proposed Standard normatively references
RFC 7517 JSON Web Key (JWK)
References Referenced by
Proposed Standard informatively references
RFC 7519 JSON Web Token (JWT)
References Referenced by
Proposed Standard normatively references
RFC 7662 OAuth 2.0 Token Introspection
References Referenced by
Proposed Standard informatively references
RFC 8414 OAuth 2.0 Authorization Server Metadata
References Referenced by
Proposed Standard normatively references
RFC 8725 JSON Web Token Best Current Practices
References Referenced by
Best Current Practice normatively references
RFC 9068 JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
References Referenced by
Proposed Standard normatively references
RFC 9092 Finding and Using Geofeed Data
References Referenced by
Proposed Standard informatively references
RFC 9234 Route Leak Prevention and Detection Using Roles in UPDATE and OPEN Messages
References Referenced by
Proposed Standard informatively references
RFC 9323 A Profile for RPKI Signed Checklists (RSCs)
References Referenced by
Proposed Standard normatively references
RFC 9325 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by
Best Current Practice informatively 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