This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg]routing table growth
- Previous message (by thread): [routing-wg]IRR usage arguments
- Next message (by thread): [routing-wg]routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nikolay Datchev
nik at varna.net
Tue Jan 17 16:28:20 CET 2006
Hello group, I want to raise up again the question about world BGP routing table. I don't know what is the result after last discussion (Oct.2005), but maybe peer pressure is not the only way to follow regarding the solution. What a big transit provider can do about customers of it's customer, which politics is "i pay, so i want to do what i want with my AS/prefixes"? I know network administrator, who says "I advertise all my networks as /24's (few /19's...), just because i don't want somebody else to be able to advertise them as more specifics and blackhole me - this is our security policy". There are others, whit PA space, not multihomed, but with own AS number, advertising specific networks just because "it's cool to use my AS number". Or even worse - the combination of the two mentioned above. Also, there are administrators who don't know about aggregating - "I got my 8 class C networks from my LIR, and i advertise them one by one". We have tools like CIDR-repors. Think about this scenario: volunteers spending few hours per week and catching such networks, contacting via email the network administrators, and ask them to aggregate. I have success with this, but only for administrators that i know personally. But i feel inconvenience to contact other people and to say them "Why you don't aggregate your networks? Help for stopping routing table growth!" It sounds sluggish, but it's more than nothing.
- Previous message (by thread): [routing-wg]IRR usage arguments
- Next message (by thread): [routing-wg]routing table growth
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]