Thanks for testing,
in year 2026, still IPv6 is not fully well utilized homes, corporates especially it is worse at clouds (AWS, GCP) if you not limit north to south, they are not good for east-to-west compared to telco providers.
For example, GCP uses IP forwarding for IPv6 real IP address is not allocated at machine. At some of the components which is EKS is not support every case at IPv6.
So IPv8 can be available around year 2300 I guess :) (i have not inspected v8 RFC yet)
Imo the insistence on 'no NAT' has killed IPv6, as it made talking to legacy IPv4 nodes very awkward. If it could interop well with v4, then the transition wouldn't be all or nothing.
And it turns out the simplicity of 'no NAT' still buys you nothing. It's very common for modern systems to run multiple network interfaces with connections having to be juggled between them. In that case, connection and session management falls to a higher level protocol, often in the application.
Hrm, but the insistence is more "NAT should not be a practical requirement in a pure IPv6 network", not "No NAT ever for any reason".
NAT-based compatibility strategies are widely deployed in the real world (most cell carriers and Google's IPv6-mostly corporate network use NAT to allow communication with the IPv4 world from IPv6 only devices).
NAT is accepted for transition purposes; for example NAT64 makes it trivial to connect from v6-only clients to v4 servers, and is used by some large ISPs (e.g. T-Mobile in the US) to avoid running v4 inside their access network.
Because it wasn’t implemented transparently at the OS. I can’t plug in to my ip6 only network and reach an ip4 address because end user OSes don’t implement clat transparently, even today in 2026, let alone 20 years ago.
Yes you can able to see IPv6 at your browser, but actualy there is always middlewhere sofware level (NLB, ALB, NAT) to reach real backend server, which creates bottle neck.
For large scale enterprises this creates issue, even for cloudproviders, I have encountered bottle neck at some Major cloudprovider which causes snowball impact to whole cluster retry mechanisms and 4 hours outage for us and some other customers :D
if the 2 enterpise has machine to machine IPv6 connectivity, this is will not happend.
I'd argue it has, but that's not the point. IPv4 is pretty much mandatory for most users of the internet. Yes, individual users probably neither know nor core whether they're on IPv4 or IPv6, but it's so difficult to run IPv6-only that you just wouldn't bother.
Trying to teach someone about how to use ULA vs. GUA only leads to headaches. In fact, I'd go so far as to say the reason why the internet became so ubiquitous was because of NAT -- static internal addressing is pretty much fundamental to an easy-to-use experience. Having multiple addresses on a host only makes things far more confusing, so people don't bother, because IPv4 justworks.
If IPv6 were wholeheartedly "adopted" then I and most consumers would not require "dual-stack" at home. Dual-stack is a terrible curse and a hack. IPv4 NAT is likewise a curse and a hack. We are left with these legacy curses only because the world can't seem to adopt IPv6. You don't need to abolish IPv4 to do it, you just need to get AAAA records and support the protocol! If you run a server or a public network, and you're not reachable by IPv6 in 2026, you're part of the problem.
I would not need "a home LAN" at home; I would not need "Private IP address space"; I would not need NATing router technology; my router software and configuration would be far, far simpler if my devices were able to single-stack. I believe the source of a lot of connectivity errors and difficult Heisenbugs involve dual-stack problems.
My devices don't need lateral connectivity on the LAN except for the printer. I attempted shutting off IPv4 on the printer and it dropped off entirely. I can't understand that. It doesn't need to reach the outside world for any reason. My Chromebook and Android don't speak to each other, except for Quick Share, which shouldn't require IPv4 addressing.
Has anyone devised a protocol or scheme by which an IPv6-only device can seamlessly access IPv4-only devices through their ISP and not local support? In other words, opportunistically intercept connection attempts and interpose a tunnel? It seems like this would be a final component to just killing off IPv4, en masse, in people's homes.
> If IPv6 were wholeheartedly "adopted" then I and most consumers would not require "dual-stack" at home.
Nah. We're not going to shut down IPv4 service for many, many decades. IPv6 is primarily an global-address-space-pressure-relief mechanism. In the next five, ten, fifteen years, enough end-user sites will have IPv6 GUA service that putting every end-user behind an IPv4 CGN and reducing the IPv4 GUA to end-user ratio to 50:1 or more will be a quite reasonable thing to do.
Any complaints you have about what you believe to be added complexity are mooted by one or more of the following:
1) End-users typically plug the magic internet router into the ISP-provided magic internet cable or box. They then magically get internet access in their house. They typically have no understanding of how any of this works.
2) Because the firewalls provided by Windows and OSX primarily care about which application is doing the network traffic, they're inherently IP version agnostic. I know that on the Linux side of things, nftables has been available for a decade and -by default- gives zero shits about the IP version of the traffic it's inspecting. So, for the three major consumer OSs it's easy to write firewall rules exactly once and have them apply regardless of what version of IP carries the traffic.
3) The major IP implementations were written years ago. That work's already been done. Removing one of those stacks is even more work.
It is unclear whether this requires cooperation or knowledge on the IPv6-only side. It says it can be deployed to service providers. Do my IPv6 clients need to be NAT64 aware to participate? Or can this be transparently implemented to furnish IPv4 connectivity where normally it would just be an error? That's the sort of model I'm thinking of.
NAT64 is transparent and requires no support on the client side. The client does need a CLAT to use 464 for apps that connect to IPv4 addresses without using DNS.
Is the IPX + IP dual stack a terrible curse and a hack? [0]
IP + Ethernet? [1]
[0] If you think this isn't real, you're not old enough.
[1] Given that your focus is home networks, other than "legacy baggage" there's zero reason that switches and IP implementations couldn't eliminate Ethernet addresses and use IP as their lowest logical layer. Switches already have to maintain a "MAC address -> switch port" lookup table. Converting that to an "IP address -> switch port" lookup table is easy. With the removal of Ethernet addresses, the need for ARP is eliminated, so there's no need for hosts to remember MAC addresses. Things are much simpler without all that legacy baggage, don't you agree?
Eliminating MAC addresses is a novel idea. I have not seen it credibly suggested before. Surely some functionality would be lost? Surely you'd at least need to redesign all Ethernet controllers around it?
Anyway, IPX, and Ethernet MAC, are different protocols with unique aims. I guess IPX was routable. But it was proprietary; it was Novell's baby, and it was serving a particular purpose for their software and network architecture. There was no sin in running it parallel to IP stacks.
The sin in dual-stack IPv4 + IPv6 is that they're the same protocol. There is nothing different in their aims, their reach, their utility or their transit networks. They're all serving the same Internet purposes, and the same protocols are both on top and below them, layer-wise. Same old TCP, UDP, QUIC, etc.
So, the only reason 4 and 6 coexist is transitional support. The only reason 4 still needs support and dual-stacking is because of a lack of 6 support. When/if IPv6 is wholeheartedly embraced, then dual-stacking is obsolete.
I'd like to reiterate that dual-stacking is an administrative pain and possibly the source of some really crazy connectivity bugs. A dual-stack system is unnecessarily complex. Eliminating Ethernet and MAC addresses is a revolutionary idea that would simplify things. But today, it is realistic to eliminate IPv4 just by widening support for v6. And that's something we should be working towards.
When/if IPv6 is wholeheartedly embraced, then dual-stacking is obsolete. ...dual-stacking is an administrative pain and possibly the source of some really crazy connectivity bugs. A dual-stack system is unnecessarily complex.
I don't think anybody really disagrees with this but it's kind of pointless to mention because there is no alternative. IPv8 would also require a period of dual-stacking.
T-Mobile is already running 99% single-stack IPv6-only so I would say the transition works; it's just a matter of doing it.
> I'd like to reiterate that dual-stacking is an administrative pain...
This professional administrator disagrees.
> The sin in dual-stack IPv4 + IPv6 is that they're the same protocol. There is nothing different in their aims, their reach, their utility or their transit networks.
That same commentary applies to IP + IPX. Your understanding of IPX is poor. This was about the depth of analysis I was expecting. Pity.
> Eliminating MAC addresses is a novel idea. I have not seen it credibly suggested before. Surely some functionality would be lost?
No more than eliminating IPv4 addresses in the far future, and far less if that elimination was done today. Go read up. It'll probably take you a few weeks to get up to speed.
> But today, it is realistic to eliminate IPv4 just by widening support for v6.
So IPv8 can be available around year 2300 I guess :) (i have not inspected v8 RFC yet)