<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.grow-bounded-longest-match" target="https://datatracker.ietf.org/doc/html/draft-grow-bounded-longest-match-00">
   <front>
      <title>Bounding Longest Match Considered</title>
      <author initials="R." surname="White" fullname="Russ White">
         </author>
      <author initials="T." surname="Hardie" fullname="Ted Hardie">
         </author>
      <date month="June" day="3" year="2003" />
      <abstract>
	 <t>Some ASes currently use length-based filters to manage the size of
the routing table they use and propagate.  This draft explores an
alternative to length-based filters which allows for more automatic
configuration and which provides for better redundancy.
Rather than use a filter, this draft proposes a method of modifying
the BGP longest match algorithm by setting a bound on the prefix
lengths eligible for preference.  A bound would operate on long
prefixes when covering route announcements are available; in certain
circumstances it would cause a router to prefer an aggregate over a
more specific route announcement.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-grow-bounded-longest-match-00" />
   
</reference>
