Making Route Servers Aware of Data Link Failures at IXPs
draft-ymbk-idr-rs-bfd-01
| Document | Type | Replaced Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2015-03-24) | ||
| Replaced by | draft-ietf-idr-rs-bfd | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-idr-rs-bfd | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ymbk-idr-rs-bfd-01.txt
Abstract
When route servers are used, the data plane is not congruent with the control plane. Therefore, the peers on the Internet exchange can lose data connectivity without the control plane being aware of it, and packets are dropped on the floor. This document proposes the use of BFD between the two peering routers to detect a data plane failure, and then uses BGP next hop cost to signal the state of the data link to the route server(s).
Authors
Randy Bush
(randy@psg.com)
Jeffrey Haas
(jhaas@juniper.net)
John Scudder
(jgs@juniper.net)
Arnold Nipper
(arnold.nipper@de-cix.net)
Thomas King
(thomas.king@de-cix.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)