References from draft-ietf-idr-eag-distribution
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 1195 |
Use of OSI IS-IS for routing in TCP/IP and dual environments 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 2328 |
OSPF Version 2 References Referenced by |
Internet Standard | informatively references | |
| RFC 4271 |
A Border Gateway Protocol 4 (BGP-4) References Referenced by |
Draft Standard | informatively references | |
| RFC 4272 |
BGP Security Vulnerabilities Analysis References Referenced by |
Informational | informatively references | |
| RFC 5340 |
OSPF for IPv6 References Referenced by |
Proposed Standard | informatively references | |
| RFC 6952 |
Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide References Referenced by |
Informational | informatively references | |
| RFC 7308 |
Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE) References Referenced by |
Proposed Standard | normatively references | |
| RFC 7752 |
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP References Referenced by |
Proposed Standard | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by |
Best Current Practice | normatively references |