<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.gmsm-bess-evpn-bfd" target="https://datatracker.ietf.org/doc/html/draft-gmsm-bess-evpn-bfd-04">
   <front>
      <title>Fault Management for EVPN networks</title>
      <author initials="V. P." surname="Govindan" fullname="Vengada Prasad Govindan">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="M." surname="Mudigonda" fullname="Mallik Mudigonda">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="G." surname="Mirsky" fullname="Greg Mirsky">
         <organization>ZTE</organization>
      </author>
      <author initials="D. E." surname="Eastlake" fullname="Donald E. Eastlake 3rd">
         <organization>Futurewei Technologies</organization>
      </author>
      <date month="January" day="2" year="2020" />
      <abstract>
	 <t>   This document specifies proactive, in-band network OAM mechanisms to
   detect loss of continuity and miss-connection faults that affect
   unicast and multi-destination paths (used by Broadcast, Unknown
   Unicast and Multicast traffic) in an Ethernet VPN (EVPN) network.
   The mechanisms specified in the draft are based on the widely adopted
   Bidirectional Forwarding Detection (BFD) protocol.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-gmsm-bess-evpn-bfd-04" />
   
</reference>
