Bidirectional Forwarding Detection (bfd) Internet Drafts
| Bidirectional Forwarding Detection Management Information Base | |||||||||||||||||
|
This draft defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling Bidirectional Forwarding Detection (BFD) protocol [BFD]. | ||||||||||||||||
| BFD For MPLS LSPs | |||||||||||||||||
|
One desirable application of Bi-directional Forwarding Detection (BFD) is to detect a Multi Protocol Label Switched (MPLS) Label Switched Path (LSP) data plane failure. LSP-Ping is an existing mechanism for detecting MPLS data plane failures and for verifying the MPLS LSP data plane against the control plane. BFD can be used for the former, but not for the latter. However the control plane processing required for BFD control packets is relatively smaller than the processing required for LSP-Ping messages. A combination of LSP-Ping and BFD can be used to provide faster data plane failure detection and/or make it possible to provide such detection on a greater number of LSPs. This document describes the applicability of BFD in relation to LSP-Ping for this application. It also describes procedures for using BFD in this environment. | ||||||||||||||||
| Bidirectional Forwarding Detection | |||||||||||||||||
|
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. Comments on this draft should be directed to rtg-bfd@ietf.org. | ||||||||||||||||
| BFD for Multihop Paths | |||||||||||||||||
|
This document describes the use of the Bidirectional Forwarding Detection protocol (BFD) over multihop paths, including unidirectional links. | ||||||||||||||||
| BFD for IPv4 and IPv6 (Single Hop) | |||||||||||||||||
|
This document describes the use of the Bidirectional Forwarding Detection protocol over IPv4 and IPv6 for single IP hops. Comments on this draft should be directed to rtg-bfd@ietf.org. | ||||||||||||||||
| Generic Application of BFD | |||||||||||||||||
|
This document describes the generic application of the Bidirectional Forwarding Detection (BFD) protocol. Comments on this draft should be directed to rtg-bfd@ietf.org. | ||||||||||||||||
| BFD for Multipoint Networks | |||||||||||||||||
|
This document describes extensions to the Bidirectional Forwarding Detection (BFD) protocol for its use in multipoint and multicast networks. Comments on this draft should be directed to rtg- bfd@ietf.org. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Bidirectional Forwarding Detection (bfd)
Last Modified: 2007-04-02
Additional information is available at tools.ietf.org/wg/bfd
Chair(s):
Routing Area Director(s):
Routing Area Advisor:
Technical Advisor(s):
Mailing Lists:
General Discussion: rtg-bfd@ietf.orgTo Subscribe: rtg-bfd-request@ietf.org
In Body: With a subject line: subscribe
Archive: ftp://ftp.ietf.org/ietf-mail-archive/rtg-bfd/
Description of Working Group:
The BFD Working Group is chartered to specify a protocol forbidirectional forwarding detection (BFD), as well as extensions to be
used within the scope of BFD and IP routing, or protocols such as MPLS
that are based on IP routing, in a way that will encourage multiple,
inter-operable vendor implementations.
BFD is a protocol intended to detect faults in the bidirectional path
between two forwarding engines, including physical interfaces,
subinterfaces, 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. An
additional goal is to provide a single mechanism that can be used for
liveness detection over any media, at any protocol layer, with
a wide range of detection times and overhead, to avoid a proliferation
of different methods.
Important characteristics of BFD include:
- Simple, fixed-field encoding to facilitate implementations in
hardware
- Independence of the data protocol being forwarded between two
systems.
BFD packets are carried as the payload of whatever encapsulating
protocol is appropriate for the medium and network.
- Path independence: BFD can provide failure detection on any kind of
path between systems, including direct physical links, virtual
circuits, tunnels, MPLS LSPs, multihop routed paths, and
unidirectional links (so long as there is some return path, of
course.)
- Ability to be bootstrapped by any other protocol that automatically
forms peer, neighbor or adjacency relationships to seed BFD endpoint
discovery.
At this time the WG is chartered to complete the following work items
(additional items will require rechartering):
1. Develop the base BFD protocol specification and submit it to the
IESG
for publication as a Proposed Standard
2. Document BFD encapsulation and usage profile for single-hop IPv4
and IPv6 adjacencies (e.g, physical links and IP/GRE tunnels for
static routes, IS-IS, OSPFv2, OSPFv3, single-hop BGP) and submit the
specification to the IESG for publication as a Proposed Standard.
3. Document BFD encapsulation and usage profile for MPLS LSPs and
submit
the specification to the IESG for publication as a Proposed
Standard.
4. Develop the MIB module for BFD and submit it to the IESG for
publication as a Proposed Standard.
5. Document BFD encapsulation and usage profile for multi-hop IPv4
and IPv6 adjacencies (e.g. OSPF virtual links and iBGP sessions)
and submit the specification to the IESG for publication as a
Proposed Standard.
Topics for Possible Future Work:
1. Document BFD directly over 802.3 in close collaboration and
synchronization with the IEEE.
Goals and Milestones:
| Aug 2004 | Submit the base protocol specification to the IESG to be considered as a Proposed Standard. | |
| Aug 2004 | Submit BFD encapsulation and usage profile for single-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard | |
| Aug 2004 | Submit BFD encapsulation and usage profile for MPLS LSPs to the IESG to be considered as a Proposed Standard | |
| Nov 2004 | Submit BFD MIB to the IESG to be considered as Proposed Standard. | |
| Feb 2005 | Submit BFD encapsulation and usage profile for multi-hop IPv4 and IPv6 adjacencies to the IESG to be considered as a Proposed Standard |
Internet-Drafts:
Bidirectional Forwarding Detection Management Information Base (53577 bytes)BFD For MPLS LSPs (27838 bytes)
Bidirectional Forwarding Detection (102627 bytes)
BFD for Multihop Paths (12070 bytes)
BFD for IPv4 and IPv6 (Single Hop) (14417 bytes)
Generic Application of BFD (39775 bytes)
BFD for Multipoint Networks (58754 bytes)
No Request For Comments
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
