Howard, Thanks for the notice on rfc2260. I took a minute to read it and I can see the benefits in that the BGP metrics complied by the Routing Table Analysis(APNIC) shows that 25%(if I'm not mistaken) of the BGP FIB is made up of /24 prefixes. Rfc2270, does fall in line with rfc1930 assumptions of allowing only the provider's existing aggregate to be advertised upstream. the question is still relevant since the filtering by ISPs are based on IRRs information, which is at present not completely reliable. However, I remember reading recently(I can't remember the document), where the preference was to have the more specific route information as the primary whereas when this information no longer exist, then the aggregate prefix would provide NLRI to the desired network prefixes.
For all interested.. here is another really good presentation on Multi-homed BGP. http://www.apnic.net/meetings/10/programme/presentations/4-Multihoming-6up.P DF you just gotta love the Internet and access to information of this kind. Nigel ----- Original Message ----- From: "Howard C. Berkowitz" To: Sent: Sunday, June 02, 2002 3:16 PM Subject: Re: BGP questions Answered.. for the most part [7:45629] > >All, > > I was do some research which led to the following link and I figured > >that some of you might find it useful. > > > >I know on the list "Howard" always tries to define his solutions by > stating.. > >"What is the problem, you're trying to solve?" So I figured this would > >answer some of those questions which in turn may provide the solution. > > > >http://info.connect.com.au/docs/routing/general/multi-faq.shtml > > > >The last bookmark in the TOC on the page links to the sources like RFC2260 > >and > >RFC 2650 among others. > > > >Enjoy! > > > >Nigel > > Good reference! Minor point -- 2270 updates 2260. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=45640&t=45629 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]