Making Route Servers Aware of Data Link Failures at IXPs
draft-ietf-idr-rs-bfd-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Randy Bush , Jeffrey Haas , John Scudder , Arnold Nipper , Thomas King | ||
| Last updated | 2018-01-04 (Latest revision 2017-07-03) | ||
| Replaces | draft-ymbk-idr-rs-bfd | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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
When BGP route servers are used, the data plane is not congruent with the control plane. Therefore, peers at an Internet exchange can lose data connectivity without the control plane being aware of it, and packets are lost. This document proposes the use of a newly defined BGP Subsequent Address Family Identifier (SAFI) both to allow the route server to request its clients use BFD to track data plane connectivity to their peers' addresses, and for the clients to signal that connectivity state back to the route server.
Authors
Randy Bush
Jeffrey Haas
John Scudder
Arnold Nipper
Thomas King
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)