Re: Sprint BGP filters in 207.x.x.x?

["Daniel M. Barton" <dmbarton () mci net>]

MCI aggregates all its customer's routes into /19's.  We have just 
received our first block of address space from the 207.x.x.x range.  If 
you continue to filter at /18's for the 207.x.x.x range, you won't be 
able to reach all of MCI's customers.

Needless to say MCI would appreciate it if you'd change your policy to be 
/19's, and I'm sure Sprint's customers would appreciate it as well.

Regards, Daniel


---------------------------------------------------------------
|  Daniel M. Barton              Internet:  dmbarton () mci net  |
|  MCI Internet Services         World Wide Web:              |
|  Cary, North Carolina, USA        http://infopage.mci.net   |
---------------------------------------------------------------

On Wed, 13 Dec 1995, Sean Doran wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
>
> > > > > > "Avi" == Avi Freedman <freedman () netaxs com> writes:
>
>     Avi> What's the smallest CIDR block Sprint will listen
>     Avi> to from an external source in the
>     Avi> 207.x.x.x-208.x.x.x range?  Is it different than
>     Avi> the filters on > /19s in 206.x.x.x-207.x.x.x
>     Avi> range?
>
> - From non-customer BGP peerings we listen to /19s in 206/8.  
>
> We listen to /18s in 207/8 to the top of the IPv4 unicast space.
>
> The nanog email archive should have lots more detail for you.
>
>       Sean.