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...
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 of
Hi, NANOGers.
] Next topic: multiple origin ASNs ..
Ooo, one of our faves. :) For a simple view:
http://www.cymru.com/BGP/incon01.html
http://www.cymru.com/BGP/incon01-list.html
Thanks,
Rob, for Team Cymru.
--
Rob Thomas
http://www.cymru.com
ASSERT(coffee != empty);
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:
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 looking
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 clearly
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
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 not
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
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
10 matches
Mail list logo