<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-rs-bfd" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-rs-bfd-09">
   <front>
      <title>Making Route Servers Aware of Data Link Failures at IXPs</title>
      <author initials="R." surname="Bush" fullname="Randy Bush">
         <organization>Internet Initiative Japan</organization>
      </author>
      <author initials="J." surname="Haas" fullname="Jeffrey Haas">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <author initials="J." surname="Scudder" fullname="John Scudder">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <author initials="A." surname="Nipper" fullname="Arnold Nipper">
         <organization>DE-CIX Management GmbH</organization>
      </author>
      <author initials="C." surname="Dietzel" fullname="Christoph Dietzel">
         <organization>DE-CIX Management GmbH</organization>
      </author>
      <date month="September" day="21" year="2020" />
      <abstract>
	 <t>   When BGP route servers are used, the data plane is not congruent with
   the control plane.  Therefore, peers at an Internet exchange can lose
   data connectivity without the control plane being aware of it, and
   packets are lost.  This document proposes the use of a newly defined
   BGP Subsequent Address Family Identifier (SAFI) both to allow the
   route server to request its clients use BFD to track data plane
   connectivity to their peers&#x27; addresses, and for the clients to signal
   that connectivity state back to the route server.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-rs-bfd-09" />
   
</reference>
