Live data from Hacker News

Ask HN: What will IPV6 migration actually look like?

news.ycombinator.com

11–20 of 48 posts

Re: Ask HN: What will IPV6 migration actually look like?

#11
post #6

Anyone know what's the biggest hold up of IPv6 on AWS side? They must be working on this for years, but never heard of any push or beta program at all.

.. or they haven't .. VPC gives you your own entire rfc1918 space per region, which tho can be a pain to deal with overlap if you have site-to-site VPN, is enough for basically anyone.

Well, public services are not. ELB for example. If AWS continues to grow, I think they will eventually exhaust their IPv4 blocks and this is an issue they can't ignore.

Re: Ask HN: What will IPV6 migration actually look like?

#12
I don't know the percentages, but several of the big home broadband ISPs are supporting native IPv6 via dual-stacking all the way to the customer premises. If you have a DOCSIS 3.0 modem, I believe that Cox and Comcast will both give you a IPv6 address via DHCPv6, at least in most areas. (I know that both of them do in Northern VA, it may not be universal particularly for Comcast.)

Many users aren't even aware of this, though, because the number of consumer-grade routers that support IPv6 is very small. I think that the Apple Airport may be one of the few, along with a few higher-end Linksys/Cisco ones (although lots of $100+ Linksys units don't, and they seem to be in absolutely no hurry to implement it via firmware updates -- I'm sure they see it as an opportunity to sell new hardware in a few years).

Consumers don't know to look for "IPv6" as a feature when they're buying a router, and so as a result Linksys et al don't bother to include it, and so even though a user might have a fully IPv6-capable uplink, there's no way to use it short of plugging their computer directly into their modem.

Re: Ask HN: What will IPV6 migration actually look like?

#16
post #14

Google currently gets 9% of their traffic over IPv6: https://www.google.com/intl/en/ipv6/statistics.html IPv6 adoption is already at the point where it is relevant to your security checks. If IPv6 clients are exempt from your security, that is a problem right now.

I'm running the site over AWS EC2, so apparently nobody could connect to me via IPv6 at the moment anyways.

Re: Ask HN: What will IPV6 migration actually look like?

#17
post #11

Earlier quoted context omitted.

.. or they haven't .. VPC gives you your own entire rfc1918 space per region, which tho can be a pain to deal with overlap if you have site-to-site VPN, is enough for basically anyone.

Well, public services are not. ELB for example. If AWS continues to grow, I think they will eventually exhaust their IPv4 blocks and this is an issue they can't ignore.

ELBs in EC2 Classic support IPv6, but not ELBs in VPCs, as of now at least. You may already have known this but I figured I'd point it out for others: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel...

Re: Ask HN: What will IPV6 migration actually look like?

#18

Would IPv6 addresses mean scraping would be easier?

I don't think it will. Even though most providers offer IPv6 addresses in /64 blocks, the services you might want to scrape will consider any request coming from the same /64 IPv6 block as coming from the same user.

Re: Ask HN: What will IPV6 migration actually look like?

#20
A lot like today. Half-in, half-out at most.

Applications are the key driver. I could see this if IOT really takes off - autoconfiguration and unique addressing are the attributes that would make IPv6 the only compelling choice. That said, IOT still has a ton of challenges.

Post reply on HN