Live data from Hacker News

Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

seam.cs.umd.edu

11–20 of 60 posts

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#11

Can someone explain to me how about a decade ago we were going to run out of IPv4 addresses in a matter of months and we needed to switch to IPv6 or else , but now we’re still using it fine?

Many users don't even have a dedicated IPv4 anymore (dual stack lite) thanks to carrier grade NAT.

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#12

Can someone explain to me how about a decade ago we were going to run out of IPv4 addresses in a matter of months and we needed to switch to IPv6 or else , but now we’re still using it fine?

I would pretty strongly oppose the notion we're using it "fine". IPv4 address allocation requests are on waiting lists. As of November, almost all requests have stopped fulfilling. We've completely run out of them.

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#13
i have a question, when iphone was introduced in 2007, 3G came AFTER that, then 4g and now 5g. why didn't the mobile revolution help move ipv6 adoption? i mean at the time, why wasn't 3G built on ipv6 instead of basing on ipv4? couldn't apple have forced websites to play nice with ipv6 to get more users from iphone crowd? android would have followed suit?

i get the whole legacy thing but since transitioning to lets say gigabit internet and beyond, that is somewhat fresh tech so why wasn't that stack made ipv6 primarily and not ipv4?

i am truly clueless on this

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#14
post #6

What is the rational reason, if any, for bringing up things like these? The time to have this discussion would have been in like 1993 or so. Now, IPv6 is what we have, and the standards are what they are, flaws and all. The only reason I can think of is psychological: People don’t want to learn new things, so they find reasons to dislike the new thing to be able to pretend they don’t need to learn it.

I think it could be argued that the flaws in IPv6 are significant enough to result in an scenario where IPv4 is never actually retired and therefore IPv6 is never fully adopted.

Its been decades, but still IPv6 is deployed (at best) as a parallel network that effectively doubles management/maintenance overhead. And at worst sites just add an IPv6 reverse proxy.

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#15

i have a question, when iphone was introduced in 2007, 3G came AFTER that, then 4g and now 5g. why didn't the mobile revolution help move ipv6 adoption? i mean at the time, why wasn't 3G built on ipv6 instead of basing on ipv4? couldn't apple have forced websites to play nice with ipv6 to get more users from iphone crowd? android would have followed suit? i get the whole legacy thing but since transitioning to lets s…

Mobile is leading the IPv6 transition, for exactly the reasons you think it is. It just happened bit later than what you expected. I'm pretty sure that vast majority of 5G deployments support IPv6.

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#17
post #6

What is the rational reason, if any, for bringing up things like these? The time to have this discussion would have been in like 1993 or so. Now, IPv6 is what we have, and the standards are what they are, flaws and all. The only reason I can think of is psychological: People don’t want to learn new things, so they find reasons to dislike the new thing to be able to pretend they don’t need to learn it.

I think it could be argued that the flaws in IPv6 are significant enough to result in an scenario where IPv4 is never actually retired and therefore IPv6 is never fully adopted. Its been decades, but still IPv6 is deployed (at best) as a parallel network that effectively doubles management/maintenance overhead. And at worst sites just add an IPv6 reverse proxy.

What's the problem with an IPv6 reverse proxy? If the Internet-exposed endpoint is IPv6, then from my point-of-view of a client, it's effectively that. For what I care about, they could be running fax machines over an analog phone line beneath that point.

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#18

Can someone explain to me how about a decade ago we were going to run out of IPv4 addresses in a matter of months and we needed to switch to IPv6 or else , but now we’re still using it fine?

The price per IP used to be almost nothing, now it's about $5/month and will keep going up; you can see these costs clearly with inexpensive hosting providers like Hetzner.

As a result many home and mobile users only get personal IPv6 addresses with IPv4 connections being tunneled over shared addresses.

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#19
post #6

What is the rational reason, if any, for bringing up things like these? The time to have this discussion would have been in like 1993 or so. Now, IPv6 is what we have, and the standards are what they are, flaws and all. The only reason I can think of is psychological: People don’t want to learn new things, so they find reasons to dislike the new thing to be able to pretend they don’t need to learn it.

I think it could be argued that the flaws in IPv6 are significant enough to result in an scenario where IPv4 is never actually retired and therefore IPv6 is never fully adopted. Its been decades, but still IPv6 is deployed (at best) as a parallel network that effectively doubles management/maintenance overhead. And at worst sites just add an IPv6 reverse proxy.

What do you think are the biggest flaws in IPv6?

Re: Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]

#20
I wrote a proposal back in 1999 or so exploring IPv4-in-IPv4 as an alternative to IPv6. You would have used the outer IP header to traverse the internet backbone, and the inner IP header locally. It completely avoided the need to change any inter-domain infrastructure and, with some DNS-based gatewaying where the gateway to the Interent added/removed the outer IP header, could even be incrementally deployed to unmodified end systems (the idea was you would eventually modify end-systems/applications to add the outer header, as this simplifies applications and avoids the DNS hack).

But in the end, IPv6 is cleaner, and it seemed better not to distract too much from progress there. If I'd known it would have taken another quarter century to make much progress, I might have made a different decision.

There were quite a few "extend IPv4" solutions over the years.

Post reply on HN