Bidirectional Forwarding Detection (BFD) Directed Return Path
draft-mirsky-mpls-bfd-directed-04
| Document | Type |
Replaced Internet-Draft
(mpls WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Greg Mirsky , Jeff Tantsura , Ilya Varlashkin , Mach Chen | ||
| Last updated | 2015-10-14 (Latest revision 2015-08-07) | ||
| Replaced by | draft-ietf-mpls-bfd-directed | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| 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 | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
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 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
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.)