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

2003-10-18 Thread bdragon
> 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)

2003-10-13 Thread Haesu
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 (was: as6198 aggregation event)

2003-10-13 Thread Rob Thomas
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)

2003-10-13 Thread James Cowie
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)

2003-10-12 Thread Haesu
> > > - Jared > > > > > > > > (Note: The above numbers are based on data from > > cidr-report.org. Some > > > > > other looking glasses were also checked to see if > > cidr-report.org's view > > > > > of these AS&#

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

2003-10-12 Thread McBurnett, Jim
> cidr-report.org. Some > > > > other looking glasses were also checked to see if > cidr-report.org's view > > > > of these AS's is consistent with the Internet as a > whole. This appears > > > > to be the case, but corrections

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

2003-10-12 Thread Haesu
> > > > > > -Terry > > > > > > > -Original Message- > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > > > Behalf Of Terry Baranski > > > > Sent: Sunday, October 05, 2003 3:01 PM > > > > To:

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

2003-10-12 Thread Jared Mauch
ki > > > Sent: Sunday, October 05, 2003 3:01 PM > > > To: 'James Cowie'; [EMAIL PROTECTED] > > > Subject: RE: as6198 aggregation event > > > > > > > > > > > > James Cowie wrote: > > > > >

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

2003-10-12 Thread Stephen J. Wilcox
t; From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Terry Baranski > > Sent: Sunday, October 05, 2003 3:01 PM > > To: 'James Cowie'; [EMAIL PROTECTED] > > Subject: RE: as6198 aggregation event > > > > > > > > James Cowie wrote: &

BellSouth prefix deaggregation (was: as6198 aggregation event)

2003-10-11 Thread Terry Baranski
ry > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Terry Baranski > Sent: Sunday, October 05, 2003 3:01 PM > To: 'James Cowie'; [EMAIL PROTECTED] > Subject: RE: as6198 aggregation event > > > > James Cowie wrote:

RE: as6198 aggregation event

2003-10-05 Thread Terry Baranski
James Cowie wrote: > On Friday, we noted with some interest the appearance of more > than six hundred deaggregated /24s into the global routing > tables. More unusually, they're still in there this morning. > > AS6198 (BellSouth Miami) seems to have been patiently injecting > them over the

as6198 aggregation event

2003-10-05 Thread James Cowie
On Friday, we noted with some interest the appearance of more than six hundred deaggregated /24s into the global routing tables. More unusually, they're still in there this morning. AS6198 (BellSouth Miami) seems to have been patiently injecting them over the course of several hours, betwe