References from draft-rivadeneyra-no-ibgp-full-mesh
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 1105 |
Border Gateway Protocol (BGP)
References Referenced by |
Experimental | informatively references | |
| RFC 1163 |
Border Gateway Protocol (BGP)
References Referenced by |
Historic | informatively references | |
| RFC 1267 |
Border Gateway Protocol 3 (BGP-3)
References Referenced by |
Historic | informatively references | |
| RFC 1654 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 1771 |
A Border Gateway Protocol 4 (BGP-4)
References Referenced by |
Draft Standard | informatively references | |
| RFC 1958 |
Architectural Principles of the Internet
References Referenced by |
Informational | 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 4456 |
BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
References Referenced by |
Draft Standard | informatively references | |
| RFC 5065 |
Autonomous System Confederations for BGP
References Referenced by |
Draft Standard | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references |