What's the smallest CIDR block Sprint will listen
> to from an external source in the
> 207.x.x.x-208.x.x.x range? Is it different than
> the filters on > /19s in 206.x.x.x-207.x.x.x
> 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.
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 Barton writes:
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.
Let me clarify something I incorrectly stated earlier. The MCI provider
network (MCI-NETBLKxx) are aggregated into /16s at the borders, not /19s
as my earlier note said. As a result, our new 207.0/14 block will be
reachable to Sprint, since they will hear the /16s.
Regards, Daniel