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/ipv6-wg@ripe.net/
[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 ]
S.P.Zeidler
spz at serpens.de
Sun Oct 6 18:13:03 CEST 2019
Thus wrote Mikael Abrahamsson (swmike at swm.pp.se): > I don't think IPv6 has failed, I just think it's going to take a long time, > and especially the last 10% is going to take a really really long time. > Decades. At some point in time IPv4 code will rot, and see too little testing to be still useful, and around then v4 will die pretty quickly. Given we'll have enterprise walled gardens with v4 inside for a long time, that indeed will take decades. If you plan projects that span more than one decade, making sure it's IPv6 capable will at least save you money in the long run, because enterprise-only features come at a premium. regards, spz -- spz at serpens.de (S.P.Zeidler)
- 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 ]