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 ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Wed May 10 02:26:04 CEST 2006
Florian Weimer wrote: >>I also don't understand the whole decision circling back, endlessly, to >>restrictive policies when nobody actually seems to want IPv6 (assuming >>this is still what we're talking about) > The majority of those who post on the RIPE mailing lists deeply fear > that there is a real demand for IPv6, so much that their routers are > overloaded. I don't know why. My understanding is that the IPv4 Internet failed to limit the size of DFZ that BGP convergence is taking prphibitively long time for mission critical applications. Moreover, considering bandwidth requirement for the next 5 or 10 years, I don't think backbone routers can have huge routing tables. Masataka Ohta
- 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 ]