RFC 5880: Bidirectional Forwarding Detection (BFD)
In plain English — editorial summary, not part of the RFC
This document describes a protocol intended to detect faults in the bidirectional path between two forwarding engines, including interfaces, data link(s), and to the extent possible the forwarding engines themselves, with potentially very low latency. It operates independently of media, data protocols, and routing protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5880
- Published
- June 2010
- Authors
- D. Katz; D. Ward
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 49
- Also known as
- —
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 7419Common Interval Support in Bidirectional Forwarding DetectionCurrent
December 2014
- RFC 7880Seamless Bidirectional Forwarding Detection (S-BFD)Current
July 2016
- RFC 8562Bidirectional Forwarding Detection (BFD) for Multipoint NetworksUpdated
April 2019
- RFC 9747Unaffiliated Bidirectional Forwarding Detection (BFD) EchoCurrent
March 2025
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5881Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)Current
June 2010
- RFC 5882Generic Application of Bidirectional Forwarding Detection (BFD)Current
June 2010
- RFC 5883Bidirectional Forwarding Detection (BFD) for Multihop PathsCurrent
June 2010
- RFC 5884Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)Updated
June 2010
- RFC 5885Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)Updated
June 2010
- RFC 5886A Set of Monitoring Tools for Path Computation Element (PCE)-Based ArchitectureCurrent
June 2010
- RFC 5867Building Automation Routing Requirements in Low-Power and Lossy NetworksCurrent
June 2010
- RFC 5862Path Computation Clients (PCC) - Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TECurrent
June 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?