July 13, 2026
ARPageddon now
A Farewell to ARPs: IPv4 Service on IPv6-Only Networks
Internet engineers want to kill old network clutter, but the comments are already fighting
TLDR: An internet standards proposal wants to let old IPv4 services run on modern IPv6-only networks without hauling around extra legacy setup. Commenters were split between “finally fix this mess,” “this only matters at huge scale,” and one very blunt “this reads like AI slop” critique.
A new proposal making the rounds at the internet standards world is basically trying to do something network operators have dreamed about for years: keep modern networks IPv6-only underneath, while still giving older apps their precious IPv4 addresses on top. In plain English, the pitch is: stop dragging around old-school local network baggage like ARP, the ancient “who has this address?” shout-across-the-room system that can turn into chaos at scale. The article says this could cut waste, reduce maintenance headaches, and avoid the weird patchwork tricks already used by big hosting companies.
But the real fireworks are in the reactions. One camp is giving exhausted-parent energy. “It’s all so tiresome,” sighed one commenter, perfectly capturing the mood of people who hear “new network fix” and immediately picture five more compatibility hacks. Another commenter pushed back with a cooler, more practical take: ARP isn’t some universal villain, they argued — it’s mostly a problem when networks get huge, and there are already ways to shrink the damage zone before you declare total war on the old system.
Then came the sharpest jab: one reader dismissed the piece as “LLMslop,” a brutal accusation that the article itself felt AI-generated and overhyped — a spicy side quest that turned a standards discussion into a mini credibility fight. So yes, the proposal is serious, and it may matter a lot to companies running giant networks. But in the comments, the vibe was less “finally, the future” and more “do we really need another complicated fix for a problem half the internet still has to support?”
Key Points
- •The article describes an IETF Internet-Draft that would allow IPv4 to be delivered over IPv6-only infrastructure without translation or tunnelling.
- •The proposal originated from a lightning talk at RIPE 91 in Bucharest and the draft is now in its third version before the IETF IntArea working group.
- •The article argues that many IPv6-only networks still retain IPv4 subnets, gateway addresses, and ARP because legacy applications and devices still require IPv4.
- •It identifies ARP, IPv4 address consumption, subnet administration, and dual-stack operational overhead as key problems with current approaches.
- •The article says providers such as Hetzner, OVHcloud, and Scaleway already implement similar IPv4 /32 service models in production, but through non-standard, provider-specific configurations.