References from draft-kumari-deprecate-as-set-confed-set
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 |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
BCP 172 |
References Referenced by |
informatively references | ||
BCP 6 |
References Referenced by |
informatively references | ||
RFC 1930 |
Guidelines for creation, selection, and registration of an Autonomous System (AS)
References Referenced by |
Best Current Practice | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3779 |
X.509 Extensions for IP Addresses and AS Identifiers
References Referenced by |
Proposed Standard | informatively references | |
RFC 4271 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | normatively references | |
RFC 5065 |
Autonomous System Confederations for BGP
References Referenced by |
Draft Standard | normatively references | |
RFC 6472 |
Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP
References Referenced by |
Best Current Practice | informatively references | |
RFC 6811 |
BGP Prefix Origin Validation
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 | informatively references | |
RFC 8205 |
BGPsec Protocol Specification
References Referenced by |
Proposed Standard | informatively references |