References from rfc8362

This is an experimental product. 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.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice Possible Reference
draft-ietf-ospf-mt-ospfv3 Multi-topology routing in OSPFv3 (MT-OSPFv3)
Refs Ref'd by
informatively references
draft-ietf-ospf-ospfv3-segment-routing-extensions OSPFv3 Extensions for Segment Routing
Refs Ref'd by
Proposed Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2154 OSPF with Digital Signatures
Refs Ref'd by
Experimental informatively references
RFC 3101 The OSPF Not-So-Stubby Area (NSSA) Option
Refs Ref'd by
Proposed Standard normatively references
RFC 3630 Traffic Engineering (TE) Extensions to OSPF Version 2
Refs Ref'd by
Proposed Standard normatively references
RFC 4291 IP Version 6 Addressing Architecture
Refs Ref'd by
Draft Standard informatively references
RFC 5340 OSPF for IPv6
Refs Ref'd by
Proposed Standard normatively references
RFC 5838 Support of Address Families in OSPFv3
Refs Ref'd by
Proposed Standard normatively references
RFC 7684 OSPFv2 Prefix/Link Attribute Advertisement
Refs Ref'd by
Proposed Standard informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references