Bidirectional Forwarding Detection (BFD) Directed Return Path
draft-mirsky-mpls-bfd-directed-04

Document Type Replaced Internet-Draft (mpls WG)
Last updated 2015-10-14 (latest revision 2015-08-07)
Replaced by draft-ietf-mpls-bfd-directed
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd Ross Callon
IESG IESG state Replaced by draft-ietf-mpls-bfd-directed
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

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-mirsky-mpls-bfd-directed-04.txt

Abstract

Bidirectional Forwarding Detection (BFD) is expected to monitor bi- directional paths. When a BFD session monitors in its forward direction an explicitly routed path there is a need to be able to direct egress BFD peer to use specific path as reverse direction of the BFD session.

Authors

Gregory Mirsky (gregory.mirsky@ericsson.com)
Jeff Tantsura (jeff.tantsura@ericsson.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.)