Bidirectional Forwarding Detection (BFD) Directed Return Path

The information below is for an old version of the document
Document Type Expired Internet-Draft (mpls WG)
Authors Greg Mirsky  , Jeff Tantsura  , Ilya Varlashkin  , Mach Chen 
Last updated 2019-04-01 (latest revision 2018-09-28)
Replaces draft-mirsky-mpls-bfd-directed
Stream IETF
Intended RFC status Proposed Standard
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd Nicolai Leymann
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Martin Vigoureux" <>,, "Nicolai Leymann" <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Bidirectional Forwarding Detection (BFD) is expected to be able to monitor a wide variety of encapsulations of paths between systems. When a BFD session monitors an explicitly routed unidirectional path there may be a need to direct egress BFD peer to use a specific path for the reverse direction of the BFD session.


Greg Mirsky (
Jeff Tantsura (
Ilya Varlashkin (
Mach Chen (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)