RFC 5880: Bidirectional Forwarding Detection (BFD)
This document describes a protocol intended to detect faults in the bidirectional path between two forwarding engines, including interfaces, data link(s), and…
Read RFC 5880 on the RFC Editor
Outgoing relationships (4 related RFCs)
Incoming relationships (70 related RFCs)
Showing 50 of 70 related RFCs.
- Updated by — RFC 7880: Seamless Bidirectional Forwarding Detection (S-BFD)
- Updated by — RFC 8562: Bidirectional Forwarding Detection (BFD) for Multipoint Networks
- Updated by — RFC 7419: Common Interval Support in Bidirectional Forwarding Detection
- Updated by — RFC 9747: Unaffiliated Bidirectional Forwarding Detection (BFD) Echo
- Normatively referenced by — RFC 5881: Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)
- Normatively referenced by — RFC 5884: Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)
- Normatively referenced by — RFC 5883: Bidirectional Forwarding Detection (BFD) for Multihop Paths
- Normatively referenced by — RFC 5885: Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)
- Normatively referenced by — RFC 6428: Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile
- Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
- Normatively referenced by — RFC 9314: YANG Data Model for Bidirectional Forwarding Detection (BFD)
- Normatively referenced by — RFC 6213: IS-IS BFD-Enabled TLV
- Normatively referenced by — RFC 6669: An Overview of the Operations, Administration, and Maintenance (OAM) Toolset for MPLS-Based Transport Networks
- Normatively referenced by — RFC 8532: Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
- Normatively referenced by — RFC 7130: Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces
- Normatively referenced by — RFC 7175: Transparent Interconnection of Lots of Links (TRILL): Bidirectional Forwarding Detection (BFD) Support
- Normatively referenced by — RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
- Normatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
- Normatively referenced by — RFC 7269: NAT64 Deployment Options and Experience
- Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
- Normatively referenced by — RFC 9780: Bidirectional Forwarding Detection (BFD) for Multipoint Networks over Point-to-Multipoint MPLS Label Switched Paths (LSPs)
- Normatively referenced by — RFC 8706: Restart Signaling for IS-IS
- Normatively referenced by — RFC 9127: YANG Data Model for Bidirectional Forwarding Detection (BFD)
- Normatively referenced by — RFC 6674: Gateway-Initiated Dual-Stack Lite Deployment
- Normatively referenced by — RFC 7330: Definitions of Textual Conventions (TCs) for Bidirectional Forwarding Detection (BFD) Management
- Normatively referenced by — RFC 7487: Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TE
- Normatively referenced by — RFC 8971: Bidirectional Forwarding Detection (BFD) for Virtual eXtensible Local Area Network (VXLAN)
- Normatively referenced by — RFC 9026: Multicast VPN Fast Upstream Failover
- Normatively referenced by — RFC 9521: Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve)
- Normatively referenced by — RFC 5994: Application of Ethernet Pseudowires to MPLS Transport Networks
- Normatively referenced by — RFC 7189: Virtual Circuit Connectivity Verification (VCCV) Capability Advertisement for MPLS Transport Profile (MPLS-TP)
- Normatively referenced by — RFC 7331: Bidirectional Forwarding Detection (BFD) Management Information Base
- Normatively referenced by — RFC 7492: Analysis of Bidirectional Forwarding Detection (BFD) Security According to the Keying and Authentication for Routing Protocols (KARP) Design Guidelines
- Normatively referenced by — RFC 9062: Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)
- Normatively referenced by — RFC 9186: Fast Failover in Protocol Independent Multicast - Sparse Mode (PIM-SM) Using Bidirectional Forwarding Detection (BFD) for Multipoint Networks
- Normatively referenced by — RFC 9468: Unsolicited Bidirectional Forwarding Detection (BFD) for Sessionless Applications
- Normatively referenced by — RFC 9612: Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)
- Normatively referenced by — RFC 9764: Bidirectional Forwarding Detection (BFD) Encapsulated in Large Packets
- Normatively referenced by — RFC 9978: Bidirectional Forwarding Detection (BFD) Stability
- Informatively referenced by — RFC 8294: Common YANG Data Types for the Routing Area
- Informatively referenced by — RFC 8177: YANG Data Model for Key Chains
- Informatively referenced by — RFC 7276: An Overview of Operations, Administration, and Maintenance (OAM) Tools
- Informatively referenced by — RFC 6039: Issues with Existing Cryptographic Protection Methods for Routing Protocols
- Informatively referenced by — RFC 7178: Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support
- Informatively referenced by — RFC 7426: Software-Defined Networking (SDN): Layers and Architecture Terminology
- Informatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
- Informatively referenced by — RFC 6518: Keying and Authentication for Routing Protocols (KARP) Design Guidelines
- Informatively referenced by — RFC 9291: A YANG Network Data Model for Layer 2 VPNs
- Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards
- Informatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs