References from draft-ietf-mpls-bfd-directed
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 | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 5880 |
Bidirectional Forwarding Detection (BFD) References Referenced by |
Proposed Standard | normatively references | |
RFC 5881 |
Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop) References Referenced by |
Proposed Standard | normatively references | |
RFC 5883 |
Bidirectional Forwarding Detection (BFD) for Multihop Paths References Referenced by |
Proposed Standard | normatively references | |
RFC 5884 |
Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs) References Referenced by |
Proposed Standard | normatively references | |
RFC 7110 |
Return Path Specified Label Switched Path (LSP) Ping References Referenced by |
Proposed Standard | normatively references | |
RFC 7726 |
Clarifying Procedures for Establishing BFD Sessions for MPLS Label Switched Paths (LSPs) References Referenced by |
Proposed Standard | normatively references | |
RFC 8029 |
Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures 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 |