References from rfc8362
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 | Possible Reference | |
| draft-ietf-ospf-mt-ospfv3 |
Multi-topology routing in OSPFv3 (MT-OSPFv3)
References Referenced by |
informatively references | ||
| draft-ietf-ospf-ospfv3-segment-routing-extensions |
OSPFv3 Extensions for Segment Routing
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 2154 |
OSPF with Digital Signatures
References Referenced by |
Experimental | informatively references | |
| RFC 3101 |
The OSPF Not-So-Stubby Area (NSSA) Option
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 4291 |
IP Version 6 Addressing Architecture
References Referenced by |
Draft Standard | informatively references | |
| RFC 5340 |
OSPF for IPv6
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5838 |
Support of Address Families in OSPFv3
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7684 |
OSPFv2 Prefix/Link Attribute Advertisement
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 |