References from rfc4972
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 | |
BCP 78 |
Rights Contributors Provide to the IETF Trust References Referenced by |
Best Current Practice | informatively references | |
RFC 1195 |
Use of OSI IS-IS for routing in TCP/IP and dual environments 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 2328 |
OSPF Version 2 References Referenced by |
Internet Standard | normatively references | |
RFC 2370 |
The OSPF Opaque LSA Option References Referenced by |
Proposed Standard | normatively references | |
RFC 2740 |
OSPF for IPv6 References Referenced by |
Proposed Standard | normatively references | |
RFC 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2 References Referenced by |
Proposed Standard | informatively references | |
RFC 3784 |
Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE) References Referenced by |
Informational | informatively references | |
RFC 4970 |
Extensions to OSPF for Advertising Optional Router Capabilities References Referenced by |
Proposed Standard | normatively references | |
RFC 4971 |
Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information References Referenced by |
Proposed Standard | normatively references | |
STD 1 |
Internet Official Protocol Standards References Referenced by |
Historic | Possible Reference | Possible Downref |