nanog mailing list archives
Re: V6 still widely supported (was Re: CC: s to Non List Members,
From: David Conrad <drc () virtualized org>
Date: Fri, 11 Mar 2022 12:57:22 -0800
On Mar 11, 2022, at 12:20 PM, John Levine <johnl () iecc com> wrote:
It appears that Joe Maimon <jmaimon () jmaimon com> said:higher penetration of native v6, I would restate that a bit more conservatively as Google's statistics are likely a fair barometer for USA usage in the large content provider arena which have a strong mobile representation.AT&T, Comcast, and Charter/Spectrum, the three largest cable companies, have IPv6 support.
As do (so I hear) mobile providers, which is increasingly how people around the world get access to the Internet. However, this discussion has drifted a bit — it wasn’t (supposed to be) a discussion about IPv6 deployment per se, but rather network operations reality as they impact IPv6 deployment. There was an assertion (that I am not questioning) that there are various kit vendors who claim IPv6 support, but when network operators attempt to deploy that kit, the IPv6 support is found to be show-stoppingly buggy, lacking in required features, or otherwise causing said network operators frustration/irritation/etc and/or to give up on deploying IPv6 “until it is more mature” (or “more/any customers demand it”). For whatever reason, there appears to be a reluctance to name names in such cases. My question was whether it might be helpful in encouraging IPv6 deployment (or at least reducing the amount of disappointment) for network operators to be more public when reality does not match vendor claims, just as “timed full disclosure” has helped in addressing (some) security-related issues. Regards, -drc
Attachment:
signature.asc
Description: Message signed with OpenPGP
Current thread:
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Abraham Y. Chen (Mar 11)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Ca By (Mar 11)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Joe Maimon (Mar 11)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Grant Taylor via NANOG (Mar 11)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Joe Maimon (Mar 11)
- Re: V6 still widely supported (was Re: CC: s to Non List Members, John Levine (Mar 11)
- Re: V6 still widely supported (was Re: CC: s to Non List Members, David Conrad (Mar 11)
- Re: V6 still widely supported (was Re: CC: s to Non List Members, John Covici (Mar 11)
- Re: V6 still widely supported (was Re: CC: s to Non List Members, Josh Luthman (Mar 11)
- Re: V6 still widely supported (was Re: CC: s to Non List Members, Christopher Morrow (Mar 13)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Joe Maimon (Mar 11)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Ca By (Mar 11)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Fred Baker (Mar 13)
- Re: V6 still not supported (was Re: CC: s to Non List Members, (was Re: 202203080924.AYC Re: 202203071610.AYC Re: Making Use of 240/4, NetBlock)) Daniel Karrenberg (Mar 14)