Hacker News new | comments | show | ask | jobs | submit login

Shaming an ISP is one thing. Like pommi said, the end user might not be very interested in the fact that its connection to a web site is using IPv4 or IPv6. The end user just wants to see the content instead of an error.

The maintainer of the web site that the end user is visiting must make sure his website is reachable over either IPv4 and IPv6, so the content can be viewed by users who have an IPv4 only connection, a dual stack connection, or even an IPv6 only connection.

Doing so just requires to enable IPv4 and IPv6 on the entry point (loadbalancer / front facing web server) of the place where the web site is hosted.

What I'd like to get shamed, is the poor adoption of IPv6 in all major "cloud" systems. Where's the IPv6 address on the VM I can start at amazon[1], where's proper IPv6 support in OpenStack [2], CloudStack [3], CloudFoundry [4] etc. etc...

[1] http://blog.iphoting.com/blog/2012/06/02/ipv6-on-amazon-aws-... [2] https://wiki.openstack.org/wiki/Neutron/IPv6 [3] http://docs.cloudstack.apache.org/en/latest/networking/ipv6.... [4] cannot even find a sensible page to quote here when I google it

IPv6 is not only about the fact that you can put some address on an external facing loadbalancer. The applications I want to run on my IaaS, PaaS or WhateverAas are also clients who connect to the internet, just like a web browser.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact