[members-discuss] Re

Hi,

> The problem is in equipment.  How many IPv6 devices users actually have?

Every PC, mobile phone and tablet that still gets firmware and OS updates. Most printers as well. And for provisioning those devices with IPv6: take a look at https://www.google.com/intl/en/ipv6/statistics.html. Google shows that 12.5% of all users world-wide not only have devices that support IPv6 but also an ISP that provides them with IPv6. Take a look at http://www.worldipv6launch.org/measurements/, it shows how major networks in the world (Comcast, AT&T, KDDI, Verizon Wireless, Time Warner Cable, SoftBank, Deutsche Telecom, Sky, T-Mobile USA etc etc etc) are providing IPv6 to their users.

> Why is it still allowed to produce IPv4 equipment, like IP cameras?

Because supporting multiple network protocols in parallel is to everyone's benefit. And yes: all my IP cameras support IPv6 as well. Everybody who invests in IPv4-only equipment these days is not making a very smart buying decision. There are no laws against stupidity...

> Who in RIPE is responsible for coordinating with manufactures? Why does he fail?

Every RIPE member (which includes you) should talk to vendors about IPv6 support. And the RIPE NCC (of which you apparently also a member as you are on the members-discuss mailing list) just agreed to help fund the IETF where internet standards are developed and all major vendors are involved. It's not RIPE NCC's job to coordinate with manufacturers, it's yours. Talk to your vendors, talk to your upstreams and peers, vote with your wallet. The RIPE community and RIPE NCC have been telling all stakeholders that they need to invest in IPv6 for years. Those that didn't listen are responsible for their own problems...

Cheers,
Sander

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160722/80eaed1a/attachment.sig>