[address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fw at deneb.enyo.de
Tue May 9 21:58:49 CEST 2006
* Nick Hilliard: > Geoff Huston's talk about this at RIPE was rather interesting. Yes, the > routing table will grow. But that's only part of the problem; a bigger > part of the problem is routing churn. > > Take a look at pages 37 and 38 of: > > http://www.ripe.net/ripe/meetings/ripe-52/presentations/ripe52-plenary-bgp-review.pdf Interesting. But -- obviously, it's not a significant problem. Otherwise, there would be peer pressure to fix it. Unlike things like BCP38, it's clear where the unnecessary BGP announcements/withdrawals come from. > You can see that there is a small number of organisations responsible > for massive numbers of updates. I can tell you that If I were supreme > ruler of the universe, these organisations would get a smack on the > face. The number of origin ASNs may be small, but their uplinks and peering partners support this behavior, at least passively.
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]