In my view we cannot reduce the Internet to a infrastructure just to fit the needs for a plain consumer/provider model, where the providers are more and more using CDNs. Beyond that, there are many more functions the Internet is serving. One of these examples is pure transport, where many companies are leveraging the Internet as transport to interconnect their locations scattered around the globe, like SD-WAN. This other major use-case is relying on a decentral and resilient architecture, rather than centralistic.

My opinion why adoption rate is that slow is related to the relationship between established ISPs and companies or enterprises.

IANA pool might be drained but the ISP's are not.

As long as ISPs can provide Internet connectivity with native IPv4, companies will prefer these ISPs. They don't care whether IPv6 or IPv4. Economy acts cost driven. A company would only afford the effort to use IPv6 in their internal network, if a real cost related threat would exist. There is no threat to loose customer reach as long as ISPs can give out IPv4 addresses. There is no need to interconnect sites using IPv6 when ISPs can give out IPv4 addresses. There is no need to deploy IPv6 in internal enterprise networks as long as all relevant destinations can be reached via IPv4.

And on the other hand. if you have a offering only reachable via IPv6, you'll be outbeaten by the competitors who are reachable via IPv4 because of the above said.

Although I'm still persuaded that continuation towards IPv6 is the only and right way, I am really lacking ideas to overcome the above outlined dependency loop. I think w/o commercial pressure, this problem cannot be solved and the IPv6 adoption is left in the hands of the enthusiasts in the network community - like myself.

-- Alex

Dear IPv6 WG list members,

we had a very packed agenda in our last session in Prague. Therefore we 
unfortunately did not have so much time for questions and longer discussions. 
Thanks again to all of the presenters!

More than a week has passed now and I heard very different, opposing opinions 
about one of the presentations.

Geoff Huston was talking about "Why Is This IPv6 Transition Taking So long" 
[1]. Shortly before the RIPE89 meeting Geoff published a related article [2] 
in the APNIC blog.

What do you think about Geoffs presentation? Did the Internet change and do we 
have to adjust our expectations? Do you agree to the fact that we now have "A 
Network of Names" and are using a lot of CDNs to bring content to the End 
Users and therefore perhaps do not need to do more IPv6 migration or do you 
think we all should find a way to somehow speed up the IPv6 migration around 
the world to enable end-to-end communication between all devices again?

[1] https://urldefense.com/v3/__https://ripe89.ripe.net/archives/video/1493/__;!!Eu8ikxSnpXkBCg!b9wGnxt47R_Lh5eWXjlkWzkJQOFC0Do6Tklst8IrSzR4dwD6-dqz8Bwa1qTFMGRva7BhHX6MbamAa283UdOrHGATl5w$
[2] https://urldefense.com/v3/__https://blog.apnic.net/2024/10/22/the-ipv6-transition/__;!!Eu8ikxSnpXkBCg!b9wGnxt47R_Lh5eWXjlkWzkJQOFC0Do6Tklst8IrSzR4dwD6-dqz8Bwa1qTFMGRva7BhHX6MbamAa283UdOrk9I_KJI$

Thanks and kind regards from Berlin

Chris
-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://urldefense.com/v3/__https://mailman.ripe.net/mailman3/lists/ipv6-wg.ripe.net/__;!!Eu8ikxSnpXkBCg!b9wGnxt47R_Lh5eWXjlkWzkJQOFC0Do6Tklst8IrSzR4dwD6-dqz8Bwa1qTFMGRva7BhHX6MbamAa283UdOrBTJa-E0$
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. 
More details at: https://urldefense.com/v3/__https://www.ripe.net/membership/mail/mailman-3-migration/__;!!Eu8ikxSnpXkBCg!b9wGnxt47R_Lh5eWXjlkWzkJQOFC0Do6Tklst8IrSzR4dwD6-dqz8Bwa1qTFMGRva7BhHX6MbamAa283UdOrgRAbuPU$

This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith.

Click merckgroup.com/disclaimer to access the German, French, Spanish, Portuguese, Turkish, Polish and Slovak versions of this disclaimer.