References from RFC 9319
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 |
---|---|---|---|---|
RFC 1918 |
Address Allocation for Private Internets
References Referenced by |
Best Current Practice | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 4271 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | normatively references | |
RFC 5737 |
IPv4 Address Blocks Reserved for Documentation
References Referenced by |
Informational | informatively references | |
RFC 6480 |
An Infrastructure to Support Secure Internet Routing
References Referenced by |
Informational | normatively references | Downref |
RFC 6482 |
A Profile for Route Origin Authorizations (ROAs)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6811 |
BGP Prefix Origin Validation
References Referenced by |
Proposed Standard | normatively references | |
RFC 6907 |
Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying Parties
References Referenced by |
Informational | informatively references | |
RFC 7115 |
Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)
References Referenced by |
Best Current Practice | normatively references | |
RFC 7999 |
BLACKHOLE Community
References Referenced by |
Informational | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8205 |
BGPsec Protocol Specification
References Referenced by |
Proposed Standard | informatively references |