[7811] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: BGP announcements and small providers

daemon@ATHENA.MIT.EDU (Paul Ferguson)
Tue Feb 25 10:57:53 1997

Date: Tue, 25 Feb 1997 10:50:44 -0500
To: David Papp <david@oanet.com>
From: Paul Ferguson <pferguso@cisco.com>
Cc: Avi Freedman <freedman@netaxs.com>, jgonz@ibernet.es, nanog@merit.edu

Well, without naming names, the prefix-length based filtering is
done on non-customer routes. A byproduct of this is it grudgingly
encourages aggregation.

- paul

At 08:32 AM 2/25/97 -0700, David Papp wrote:

>Isn't it true though that some upstream providers (such as Sprint) filter
>out anything smaller than /19 and will not carry those routes? Therefore
>in this example, Sprint clients would not be able to see these smaller
>providers and vice versa unless he agregates them to /19 or higher and
>then announces the routes himself?
>
>...David
>
>*  David Papp         |    4907-99 Street     |      Ph: +1.403.430.0811  *
>*  Manager            |   Edmonton, Alberta   |     Fax: +1.403.436.9963  *
>*  OA Internet Inc.   |    Canada, T6E 4Y1    |   Email: david@oanet.com  *
>
>On Tue, 25 Feb 1997, Paul Ferguson wrote:
>> If the downstream customers are not multihomed, there's no reason
>> to run BGP with them; a simple default/static will work just fine.
>> Also, if you suballocate addresses to them from within your address
>> space, you can aggregate them.
>> 
>> This is generally considered a Good Thing.
>> 
>> - paul
>
>
>

home help back first fref pref prev next nref lref last post