Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

> IMHO, I think we should create a route-set obj like call it... RS-DEAGGREGATES and > list all the major irresponsible providers's specific /24's in it... > > So some ASes who wish to not accept deaggregated specifics using RPSL can update > their AS import policy to not import RS-DEAGGREGATES

Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

Yup, Looks like they've started getting things a bit organized since sunday night/ monday early dawn. From my network's pt of view, you can see the sudden slight "sink" in announcements transited thru UUNET which is where bellsouth's prefixes come from on my end: http://www.twdx.net/bgp/graph-1w

Re: BellSouth prefix deaggregation

] Thanks Rob. Noticed one of our routes there that an upstream was also ] originating, for no reason. That's cleared up, so one less inconsistent ] AS... No worries and thank YOU. :) -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty);

Re: BellSouth prefix deaggregation

Rob Thomas wrote: Hi, NANOGers. ] Next topic: multiple origin ASNs .. Ooo, one of our faves. :) For a simple view: Thanks, Rob, for Team Cymru. Thanks Rob. Noticed one of our routes there that an upstr

Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

Hi, NANOGers. ] Next topic: multiple origin ASNs .. Ooo, one of our faves. :) For a simple view: Thanks, Rob, for Team Cymru. -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty);

Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

On Sun, Oct 12, 2003 at 01:18:59AM -0400, Terry Baranski wrote: > More on this - > > Two of BellSouth's AS's (6197 & 6198) have combined to inject around > 1,000 deaggregated prefixes into the global routing tables over the last > few weeks (in addition to their usual load of ~600+ for a total o

Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

The idea is to not filter just /24's. The idea is to work with people who run cidr-report.org (may be.. or other people who are willing to coop), and find an ASNs who advertise a lots of irresponsible deaggregates. As you can see, cidr-report only shows deaggregation for the prefixes that an A

RE: BellSouth prefix deaggregation (was: as6198 aggregation event)

> > IMHO, I think we should create a route-set obj like call > it... RS-DEAGGREGATES and list all the major irresponsible > providers's specific /24's in it... CASE: Business has a /24 from X provider in order to multihome. That /24 is de-aggregated from a /19, with this policy that /24 may n

Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

IMHO, I think we should create a route-set obj like call it... RS-DEAGGREGATES and list all the major irresponsible providers's specific /24's in it... So some ASes who wish to not accept deaggregated specifics using RPSL can update their AS import policy to not import RS-DEAGGREGATES... Just

Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

On Sun, Oct 12, 2003 at 01:02:57PM +, Stephen J. Wilcox wrote: > > > Can anyone from BellSouth comment? What if a few other major ISPs were > > to add a thousand or so deaggregated routes in a few weeks time? Would > > there be a greater impact? > > one word - irresponsible This c

Re: BellSouth prefix deaggregation (was: as6198 aggregation event)

> Can anyone from BellSouth comment? What if a few other major ISPs were > to add a thousand or so deaggregated routes in a few weeks time? Would > there be a greater impact? one word - irresponsible Steve > > (Note: The above numbers are based on data from cidr-report.org. Some > other lo

BellSouth prefix deaggregation (was: as6198 aggregation event)

More on this - Two of BellSouth's AS's (6197 & 6198) have combined to inject around 1,000 deaggregated prefixes into the global routing tables over the last few weeks (in addition to their usual load of ~600+ for a total of ~1,600). This does indeed appear to be having an operational impact o