References from draft-ietf-ospf-prefix-link-attr
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 100 |
References Referenced by |
informatively references | ||
| draft-francois-rtgwg-segment-routing-ti-lfa |
Abstract
References Referenced by |
informatively references | ||
| draft-ietf-bier-ospf-bier-extensions |
OSPFv2 Extensions for Bit Index Explicit Replication (BIER)
References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-ospf-ospfv3-lsa-extend |
OSPFv3 Link State Advertisement (LSA) Extensibility
References Referenced by |
Proposed Standard | informatively references | |
| draft-ietf-ospf-segment-routing-extensions |
OSPF 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 2328 |
OSPF Version 2
References Referenced by |
Internet Standard | normatively references | |
| RFC 3630 |
Traffic Engineering (TE) Extensions to OSPF Version 2
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5250 |
The OSPF Opaque LSA Option
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6982 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Experimental | Possible Reference | Possible Downref |
| RFC 7120 |
Early IANA Allocation of Standards Track Code Points
References Referenced by |
Best Current Practice | informatively references |