Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence
This is an older version of an Internet-Draft that was ultimately published as RFC 7747.
Expired & archived
|Authors||Rajiv Papneja , Bhavani Parise , Susan Hares , Dean Lee , Ilya Varlashkin|
|Last updated||2014-01-03 (Latest revision 2013-07-02)|
|RFC stream||Internet Engineering Task Force (IETF)|
GENART Last Call review (of -04) Almost Ready
OPSDIR Last Call review (of -04) Has Nits
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
BGP is widely deployed and used by several service providers as the default Inter AS routing protocol. It is of utmost importance to ensure that when a BGP peer or a downstream link of a BGP peer fails, the alternate paths are rapidly used and routes via these alternate paths are installed. This document provides the basic BGP Benchmarking Methodology using existing BGP Convergence Terminology, RFC 4098.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)