References from draft-spaghetti-sidrops-avoid-rpki-state-in-bgp
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-sidrops-aspa-profile |
A Profile for Autonomous System Provider Authorization
References Referenced by |
informatively references | ||
RFC 1997 |
BGP Communities Attribute
References Referenced by |
Proposed Standard | informatively 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 | informatively references | |
RFC 6480 |
An Infrastructure to Support Secure Internet Routing
References Referenced by |
Informational | informatively references | |
RFC 6482 |
A Profile for Route Origin Authorizations (ROAs)
References Referenced by |
Proposed Standard | informatively references | |
RFC 6811 |
BGP Prefix Origin Validation
References Referenced by |
Proposed Standard | informatively references | |
RFC 8092 |
BGP Large Communities Attribute
References Referenced by |
Proposed Standard | informatively references | |
RFC 8097 |
BGP Prefix Origin Validation State Extended Community
References Referenced by |
Proposed Standard | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8210 |
The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
References Referenced by |
Proposed Standard | informatively references | |
RFC 9319 |
The Use of maxLength in the Resource Public Key Infrastructure (RPKI)
References Referenced by |
Best Current Practice | informatively references |