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]/
[ipv6-wg] Have we failed as IPv6 Working Group?
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Sat Oct 5 13:33:49 CEST 2019
Michel Py wrote on 04/10/2019 23:51: > And I suppose you are aware that there were several attempts before, > including the last one submitted by APNIC, and that they all have > been torpedoed by the IPv6 zealots. The cost of making 240/4 usable is to update every device on the planet, including legacy ipv4 stacks. 240/4 is 16x/8. Before ARIN reached exhaustion, this would have constituted a little more than 1 year of RIR consumption. Bringing 240/4 into production won't change the principle that ipv4 address exhaustion is going to happen: the only thing it does is to move the date a couple of months down the road. There are plenty of people who are not ipv6 zealots, but who view this this as not worth it. Nothing fundamental is going to change, and the cost is very high. Nick
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]