Bidirectional Forwarding Detection (BFD) Directed Return Path
draft-ietf-mpls-bfd-directed-10

The information below is for an old version of the document
Document Type Expired Internet-Draft (mpls WG)
Last updated 2019-04-01 (latest revision 2018-09-28)
Replaces draft-mirsky-mpls-bfd-directed
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html bibtex
Reviews
Additional URLs
- 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" <martin.vigoureux@nokia.com>, loa@pi.nu, "Nicolai Leymann" <n.leymann@telekom.de>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-mpls-bfd-directed-10.txt

Abstract

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.

Authors

Gregory Mirsky (gregimirsky@gmail.com)
Jeff Tantsura (jefftant.ietf@gmail.com)
Ilya Varlashkin (ilya@nobulus.com)
Mach Chen (mach.chen@huawei.com)

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