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/address-policy-wg@ripe.net/
[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 ]
Nick Hilliard
nick at inex.ie
Tue May 9 17:22:06 CEST 2006
> each ISP announces, in average, about 8 blocks, which is the small > constant factor. Yes, but in an ipv6 world, i don't really see why the average would be much more than 2 or 3. Most AS's will announce just one. > > 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; > > So, you have found the problem. We all know that the two problems are routing table size and churn. But the two are not particularly related. A large routing table does not necessarily mean extra churn. Nick
- 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 ]