<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bmwg-bgp-basic-convergence" target="https://datatracker.ietf.org/doc/html/draft-ietf-bmwg-bgp-basic-convergence-05">
   <front>
      <title>Basic BGP Convergence Benchmarking Methodology for Data-Plane Convergence</title>
      <author initials="R." surname="Papneja" fullname="Rajiv Papneja">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="B." surname="Parise" fullname="Bhavani Parise">
         <organization>Skyport Systems</organization>
      </author>
      <author initials="S." surname="Hares" fullname="Susan Hares">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="D." surname="Lee" fullname="Dean Lee">
         <organization>IXIA</organization>
      </author>
      <author initials="I." surname="Varlashkin" fullname="Ilya Varlashkin">
         <organization>Google</organization>
      </author>
      <date month="January" day="16" year="2015" />
      <abstract>
	 <t>BGP is widely deployed and used by several service providers as the default inter-AS (Autonomous System) 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 as defined in RFC 4098.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bmwg-bgp-basic-convergence-05" />
   
</reference>
