<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-rfd-usable" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfd-usable-04">
   <front>
      <title>Making Route Flap Damping Usable</title>
      <author initials="C." surname="Pelsser" fullname="Cristel Pelsser">
         <organization>Internet Initiative Japan</organization>
      </author>
      <author initials="R." surname="Bush" fullname="Randy Bush">
         <organization>Internet Initiative Japan</organization>
      </author>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Mohapatra" fullname="Prodosh Mohapatra">
         <organization>Sproute Networks</organization>
      </author>
      <author initials="O." surname="Maennel" fullname="Olaf Maennel">
         <organization>Loughborough University</organization>
      </author>
      <date month="October" day="10" year="2013" />
      <abstract>
	 <t>Route Flap Damping (RFD) was first proposed to reduce BGP churn in routers.  Unfortunately, RFD was found to severely penalize sites for being well connected because topological richness amplifies the number of update messages exchanged.  Many operators have turned RFD off.  Based on experimental measurement, this document recommends adjusting a few RFD algorithmic constants and limits in order to reduce the high risks with RFD.  The result is damping a non-trivial amount of long-term churn without penalizing well-behaved prefixes&#x27; normal convergence process.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-rfd-usable-04" />
   
</reference>
