References from rfc8476

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
References Referenced by
Best Current Practice normatively references
draft-ietf-idr-bgp-ls-segment-routing-msd Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State
References Referenced by
Proposed Standard informatively references
draft-ietf-isis-segment-routing-msd Signaling Maximum SID Depth (MSD) Using IS-IS
References Referenced by
Proposed Standard normatively references
draft-ietf-ospf-mpls-elc Signaling Entropy Label Capability and Entropy Readable Label Depth Using OSPF
References Referenced by
Proposed Standard informatively references
draft-ietf-pce-segment-routing Path Computation Element Communication Protocol (PCEP) 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 3031 Multiprotocol Label Switching Architecture
References Referenced by
Proposed Standard normatively references
RFC 4552 Authentication/Confidentiality for OSPFv3
References Referenced by
Proposed Standard informatively references
RFC 6863 Analysis of OSPF Security According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
References Referenced by
Informational informatively references
RFC 7166 Supporting Authentication Trailer for OSPFv3
References Referenced by
Proposed Standard informatively references
RFC 7474 Security Extension for OSPFv2 When Using Manual Key Management
References Referenced by
Proposed Standard informatively references
RFC 7684 OSPFv2 Prefix/Link Attribute Advertisement
References Referenced by
Proposed Standard normatively references
RFC 7752 North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
References Referenced by
Proposed Standard informatively references
RFC 7770 Extensions to OSPF for Advertising Optional Router Capabilities
References Referenced by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8362 OSPFv3 Link State Advertisement (LSA) Extensibility
References Referenced by
Proposed Standard normatively references
RFC 8402 Segment Routing Architecture
References Referenced by
Proposed Standard normatively references