References from draft-ietf-ospf-xaf-te
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 | ||
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 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by |
Proposed Standard | normatively references | |
RFC 3906 |
Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels
References Referenced by |
Informational | informatively references | |
RFC 4461 |
Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)
References Referenced by |
Informational | informatively references | |
RFC 5329 |
Traffic Engineering Extensions to OSPF Version 3
References Referenced by |
Proposed Standard | normatively references | |
RFC 5340 |
OSPF for IPv6
References Referenced by |
Proposed Standard | informatively references | |
RFC 5786 |
Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions
References Referenced by |
Proposed Standard | normatively references | |
RFC 5838 |
Support of Address Families in OSPFv3
References Referenced by |
Proposed Standard | informatively references | |
RFC 6827 |
Automatically Switched Optical Network (ASON) Routing for OSPFv2 Protocols
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 | normatively references |