<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-lsr-distoptflood" target="https://datatracker.ietf.org/doc/html/draft-ietf-lsr-distoptflood-13">
   <front>
      <title>IS-IS Distributed Flooding Reduction</title>
      <author initials="R." surname="White" fullname="Russ White">
         <organization>Akamai</organization>
      </author>
      <author initials="S." surname="Hegde" fullname="Shraddha Hegde">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="T." surname="Przygienda" fullname="Tony Przygienda">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="L." surname="Jalil" fullname="Luay Jalil">
         <organization>Verizon</organization>
      </author>
      <author initials="D." surname="Voyer" fullname="Daniel Voyer">
         <organization>Cisco</organization>
      </author>
      <date month="January" day="22" year="2026" />
      <abstract>
	 <t>   In dense topologies (such as data center fabrics based on the Clos
   and butterfly though not limited to those; in fact any large topology
   or one with relatively high degree of connectivity qualifies here)
   IGP flooding mechanisms designed originally for rather sparse
   topologies can &quot;overflood&quot;, or in other words generate too many
   identical copies of same information arriving at a given node from
   other devices.  This normally results in longer convergence times and
   higher resource utilization to process and discard the superfluous
   copies.  Flooding algorithm extensions that restrict the amount of
   flooding performed can be constructed and can reduce resource
   utilization significantly, while improving convergence performance.

   One such flooding modification (based on previous art) optimized for
   operational considerations, described further in Section 2, is
   described in this document.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-lsr-distoptflood-13" />
   
</reference>
