<?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-00">
   <front>
      <title>Basic BGP Convergence Benchmarking Methodology for Data Plane Convergence</title>
      <author initials="R." surname="Papneja" fullname="Rajiv Papneja">
         </author>
      <author initials="B." surname="Parise" fullname="Bhavani Parise">
         </author>
      <author initials="S." surname="Hares" fullname="Susan Hares">
         </author>
      <author initials="D." surname="Lee" fullname="Dean Lee">
         </author>
      <author initials="I." surname="Varlashkin" fullname="Ilya Varlashkin">
         </author>
      <date month="July" day="2" year="2013" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bmwg-bgp-basic-convergence-00" />
   
</reference>
