Bidirectional Forwarding Detection (BFD) Directed Return Path
draft-ietf-mpls-bfd-directed-13
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Greg Mirsky , Jeff Tantsura , Ilya Varlashkin , Mach Chen | ||
Last updated | 2020-06-21 (Latest revision 2019-12-19) | ||
Replaces | draft-mirsky-mpls-bfd-directed | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | Nicolai Leymann | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
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 is available in these formats:
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
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.)