<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-bgp-bfd-strict-mode" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-bfd-strict-mode-19">
   <front>
      <title>BGP BFD Strict-Mode</title>
      <author initials="M." surname="Zheng" fullname="Mercia Zheng">
         <organization>Ciena</organization>
      </author>
      <author initials="A." surname="Lindem" fullname="Acee Lindem">
         <organization>Arrcus, Inc</organization>
      </author>
      <author initials="J." surname="Haas" fullname="Jeff Haas">
         <organization>HPE</organization>
      </author>
      <author initials="A." surname="Fu" fullname="Albert Fu">
         <organization>Bloomberg L.P.</organization>
      </author>
      <date month="August" day="26" year="2026" />
      <abstract>
	 <t>   This document specifies extensions to RFC4271 BGP-4 that enable a BGP
   speaker to negotiate additional Bidirectional Forwarding Detection
   (BFD) extensions using a BGP capability.  This BFD Strict-Mode
   Capability enables a BGP speaker to prevent a BGP session from being
   established until a BFD session is established.  This is referred to
   as BFD &quot;strict-mode&quot;.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-bfd-strict-mode-19" />
   
</reference>
