Bidirectional Forwarding Detection (bfd)

Deleted milestone "Submit BFD encapsulation and usage profile for multi-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", not present in approved charter

Deleted milestone "Submit BFD encapsulation and usage profile for MPLS LSPs to the IESG to be considered as a Proposed Standard", not present in approved charter

Deleted milestone "Submit BFD encapsulation and usage profile for single-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", not present in approved charter

Added milestone "Define a use of the BFD Echo where the local system supports BFD but the adjacent system does not support BFD.", due 2024-12-31, from approved charter

Added milestone "Extend BFD to allow it to detect whether a path between two systems is capable of carrying a payload of a particular size.", due 2024-12-31, from approved charter

Resources changed to tracker https://trac.ietf.org/trac/bfd/report/1 (Issue tracker), wiki https://wiki.ietf.org/group/bfd (Working group wiki), zulip https://zulip.ietf.org/#narrow/stream/143-bfd (Zulip Stream) from tracker https://trac.ietf.org/trac/bfd/report/1 (Issue tracker), wiki https://trac.ietf.org/trac/bfd/wiki (Working group wiki), zulip https://zulip.ietf.org/#narrow/stream/143-bfd (Zulip Stream)

Resources changed to tracker https://trac.ietf.org/trac/bfd/report/1 (Issue tracker), wiki https://trac.ietf.org/trac/bfd/wiki (Working group wiki), zulip https://zulip.ietf.org/#narrow/stream/143-bfd (Zulip Stream) from tracker https://trac.ietf.org/trac/bfd/report/1 (Issue tracker), wiki https://trac.ietf.org/trac/bfd/wiki (Working group wiki)

The BFD Working Group standardizes the Bi-directional Forwarding Detection protocol specified in RFC 5880 and its related documents.  BFD is typically used by "client protocols" in order to provide sub-second continuity verification, typically augmenting much slower protocols.  An example of this is providing sub-second detection of link failures for IGPs (Interior Gateway Protocols).  A "seamless" version of BFD, S-BFD, is specified in RFC 7880 and its extensions to provide for BFD functionality in environments where endpoints are potentially unknown to each other.

New work under consideration for BFD includes:
- Refining client protocol semantics for BFD liveness vs. protocol liveness in BGP and OSPF.
- Considering BFD for the Geneve transport protocol.
- Optimized authentication procedures to permit authentication to be used with high granularity session timers.
- Validation of path MTU over the links utilized by a BFD session.
- Providing RFC 5880/5881 services without explicit IP endpoint configuration.

and finally:
- Considering whether it's time to extend BFD to provide a more general framework for carrying additional information.

The status of the Working Group is always available at https://trac.ietf.org/trac/bfd/wiki

[Last Updated: March 19, 2019]

The BFD Working Group standardizes the Bi-directional Forwarding Detection protocol specified in RFC 5880 and its related documents.  BFD is typically used by "client protocols" in order to provide sub-second continuity verification, typically augmenting much slower protocols.  An example of this is providing sub-second detection of link failures for IGPs (Interior Gateway Protocols).  A "seamless" version of BFD, S-BFD, is specified in RFC 7880 and its extensions to provide for BFD functionality in environments where endpoints are potentially unknown to each other.

New work under consideration for BFD includes:
- Optimized authentication procedures to permit authentication to be used with high granularity session timers.
- Validation of path MTU over the links utilized by a BFD session.
- Operating in demand mode in MPLS environments.
- Providing RFC 5880/5881 services without explicit IP endpoint configuration.

The status of the Working Group is always available at https://trac.ietf.org/trac/bfd/wiki

[Last Updated: November 8, 2018]

Changed milestone "Submit the BFD Seamless IP draft to the IESG to be considered as a Proposed Standard", set due date to December 2015 from March 2015

Changed milestone "Submit the BFD Seamless Base draft to the IESG to be considered as a Proposed Standard", set due date to December 2015 from March 2015

Changed milestone "Submit the the document on BFD point-to-multipoint support to the IESG to be considered as a Proposed Standard", set due date to April 2016 from March 2015

Changed milestone "Submit the BFD MPLS extension MIB to the IESG to be considered as a Proposed Standard", set due date to April 2016 from November 2014

Changed milestone "Submit the BFD Seamless IP draft to the IESG to be considered as a Proposed Standard", set state to active from review, accepting new milestone

Changed milestone "Submit the BFD Seamless Use Case document to the IESG to be considered as a Proposed Standard", set due date to December 2014 from November 2014

Changed milestone "Submit the the document on BFD point-to-multipoint support to the IESG to be considered as a Proposed Standard", set due date to March 2015 from June 2014

Changed milestone "Submit a BFD Yang module to the IESG to be considered as a Proposed Standard", set state to active from review, accepting new milestone

Changed milestone "Submit a BFD Yang module to the IESG to be considered as a Proposed Standard", set due date to December 2016 from December 2015

Changed milestone "Submit the BFD Seamless Base draft to the IESG to be considered as a Proposed Standard", set state to active from review, accepting new milestone

Changed milestone "Submit the BFD Seamless Use Case document to the IESG to be considered as a Proposed Standard", set state to active from review, accepting new milestone

Changed milestone "Submit the BFD Common Intervals document to the IESG to be considered as an Informational RFC", set state to active from review, accepting new milestone

Changed milestone "Submit the BFD MPLS extension MIB to the IESG to be considered as a Proposed Standard", set state to active from review, accepting new milestone

Changed milestone "Submit the BFD over LAG mechanism to the IESG to be considered as a Proposed Standard", set state to active from review, accepting new milestone

Changed milestone "Submit the cryptographic authentication procedures for BFD to the IESG to be considered as a Proposed Standard", set due date to January 2015 from December 2011

Changed milestone "Submit a BFD MIB extension in support of the generic keying document to the IESG to be considered as a Proposed Standard", set due date to January 2015 from December 2011

Changed milestone "Submit the generic keying based cryptographic authentication mechanism to the IESG to be considered as a Proposed Standard", set due date to January 2015 from December 2011

Changed milestone "Submit the the document on BFD point-to-multipoint support to the IESG to be considered as a Proposed Standard", set due date to June 2014 from March 2012

Changed milestone "Submit BFD encapsulation and usage profile for multi-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", resolved as "Done"

Changed milestone "Submit BFD encapsulation and usage profile for single-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard", resolved as "Done"