At 19:02 13/12/00 +0100, Kurt Erik Lindqvist wrote:
I agree with Daniel. It's nothing under the control of the RIPE NCC causing this. It's the community at large. From the routing reports available it's most likely fair to say that the biggest problem is not in the RIPE or ARIN areas anyway.
Likewise I agree, the registries should not be involved in policing the announcements. Definitely a case for industry self control here... One thing that I have on my todo list is to look at the aggregation potential in each registry region. I guess it could take Tony's CIDR report and split it on a per region basis? The biggest problems are from surprising places. Private AS leakage comes mostly from the US, deaggregation comes from every region,... It's usually, but not always limited to newer providers...
Seans suggestion made at the IEPG in San Diego (for those not there it was basically to start charging per announced route) is tempting but most likely not realistic.
I'd be curious to see what happened if someone tried... :-)
However, fact is that it's up to us as a community to let the operators announcing huge amounts of unaggregated or bogus routes that this is wrong and causing a problem. Just as you contact ISP:S abuse contacts or NOC:s for other problems. If enough people show them that we care I am sure they will act (or if you CC their upstream their upstream might care).
I don't think anyone really cares any more. There is enough memory and CPU in the big routers these days, it seems... I could be wrong about both assertions. All this will become a real issue once the number of prefixes being announced becomes a problem for BGP convergence, or storage space on the routers runs out... philip --