References from rfc6793
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 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 1997 |
BGP Communities Attribute
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 4001 |
Textual Conventions for Internet Network Addresses
References Referenced by |
Proposed Standard | informatively references | |
RFC 4271 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | normatively references | |
RFC 4273 |
Definitions of Managed Objects for BGP-4
References Referenced by |
Proposed Standard | informatively references | |
RFC 4893 |
BGP Support for Four-octet AS Number Space
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 5065 |
Autonomous System Confederations for BGP
References Referenced by |
Draft Standard | normatively references | |
RFC 5101 |
Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information
References Referenced by |
Proposed Standard | informatively references | |
RFC 5492 |
Capabilities Advertisement with BGP-4
References Referenced by |
Draft Standard | normatively references | |
RFC 5668 |
4-Octet AS Specific BGP Extended Community
References Referenced by |
Proposed Standard | normatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | Possible Downref |