References from RFC 4940
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 | ||
BCP 26 |
References Referenced by |
normatively references | ||
BCP 78 |
References Referenced by |
informatively references | ||
BCP 82 |
References Referenced by |
normatively references | ||
RFC 1584 |
Multicast Extensions to OSPF
References Referenced by |
Historic | normatively references | |
RFC 1793 |
Extending OSPF to Support Demand Circuits
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 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 2740 |
OSPF for IPv6
References Referenced by |
Proposed Standard | normatively references | |
RFC 3101 |
The OSPF Not-So-Stubby Area (NSSA) Option
References Referenced by |
Proposed Standard | normatively references | |
RFC 3623 |
Graceful OSPF Restart
References Referenced by |
Proposed Standard | normatively references | |
RFC 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by |
Proposed Standard | normatively references | |
RFC 3692 |
Assigning Experimental and Testing Numbers Considered Useful
References Referenced by |
Best Current Practice | normatively references |