References from RFC 4456
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 | informatively references | ||
| BCP 78 | References Referenced by | informatively references | ||
| RFC 1863 | A BGP/IDRP Route Server alternative to a full mesh routing References Referenced by | Historic | informatively references | |
| RFC 1966 | BGP Route Reflection An alternative to full mesh IBGP References Referenced by | Experimental | informatively references | |
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | Possible Reference | |
| RFC 2385 | Protection of BGP Sessions via the TCP MD5 Signature Option References Referenced by | Proposed Standard | informatively references | |
| RFC 2796 | BGP Route Reflection - An Alternative to Full Mesh IBGP References Referenced by | Proposed Standard | informatively references | |
| RFC 3065 | Autonomous System Confederations for BGP References Referenced by | Proposed Standard | informatively references | |
| RFC 4271 | A Border Gateway Protocol 4 (BGP-4) References Referenced by | Draft Standard | normatively references | |
| STD 1 | References Referenced by | Possible Reference |