RFC 9247: BGP - Link State (BGP-LS) Extensions for Seamless Bidirectional Forwarding Detection (S-BFD)
In plain English — editorial summary, not part of the RFC
Seamless Bidirectional Forwarding Detection (S-BFD) defines a simplified mechanism to use Bidirectional Forwarding Detection (BFD) with large portions of negotiation aspects eliminated, thus providing benefits such as quick provisioning as well as improved control and flexibility to network nodes initiating the path monitoring. The link-state routing protocols (IS-IS and OSPF) have been extended to advertise the S-BFD Discriminators. This document defines extensions to the BGP - Link State (BGP-LS) address family to carry the S-BFD Discriminators' information via BGP.
Document record
- Document ID
- RFC9247
- Published
- June 2022
- Authors
- Z. Li; S. Zhuang; K. Talaulikar; S. Aldrin; J. Tantsura; G. Mirsky
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9294Application-Specific Link Attributes Advertisement Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2022
- RFC 9351Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm AdvertisementCurrent
February 2023
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 9314YANG Data Model for Bidirectional Forwarding Detection (BFD)Current
September 2022
- RFC 9127YANG Data Model for Bidirectional Forwarding Detection (BFD)Updated
October 2021
- RFC 9513OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 9655Egress Validation in Label Switched Path Ping and Traceroute MechanismsCurrent
November 2024
- RFC 8541Impact of Shortest Path First (SPF) Trigger and Delay Strategies on IGP Micro-loopsCurrent
March 2019
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?