Hacker News Reader

Comment by woleium | Hacker News Reader

I first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.

I’ve often wondered if ipv6s less human readable addresses is the primary cause. I dread using and interacting with ipv6, compared to ipv4. Sure ipv6 solves a lot of scaling challenges, but it is so much harder to grock at first glance.

It's a silly bikeshed, but I wish they'd gone for hyphens as separators rather than colons. There's something about

    [abcd-ef12-3456-7890-abcd-ef12-3456-7890]

that's nicer to read than

    [abcd:ef12:3456:7890:abcd:ef12:3456:7890]

It's probably not like that because then you could have something be both a valid hostname and a valid ip address

Yeah, I realized that just after I posted my reply. As usr1106 mentioned, the solution would be to always use square brackets. It would take up more space, but I think it would still be better for at least two reasons:

• Even with the brackets, it always takes the same or fewer keypresses (no need to press shift).

• It's easier to tell when the address starts and ends. This is helpful when you get into odd addresses like "xxxx::xxxx.192.168.123.234", or "::1", or "::". The versions [xxxx--xxxx.192.168.123.234], [--1], and [--] look nicer and more obvious, at least to me.

But of course this is all silly to go over now, decades after the decision. We'll save these changes for IPv8! :-P

Not if you always use the square brackets. Which is of course slightly awkward to type every single time.

it's absolutely not bikeshedding.

anecdote: a few years ago there was a quiz at one of the ripe-conferences where participants were asked to pick the one invalid ipv6 address out of four. iirc the success rate was even below what would result from a random-pick

Many of the "IPv6-isms" come from the fact that renumbering networks is a big PITA and so IPv6 was built with the pipe dream of "change the config on the router and the entire network renumbers itself", like the flick of a switch. It was optimised for the least used case. IMO they should have just increased the address bit size to 128 and be done with it.

One of my own annoyances is the fact that local subnets have to be /64's (you can make smaller subnets but it breaks certain things) and ISP's are supposed to deliver a /48 or /56 to subscribers but some ISP's will only hand one /64. So if you want to create 2 separate networks in your home you're screwed.

It’s even worse - many home routers will simply disable ipv6 if the ISP gives /64.

Address abbreviation helps a bunch. IPv6 (not an expert, but I’m in a class right now!) suffers from severe 2nd system syndrome: it overhauls DHCP in a totally convoluted way, overhauls so much of how the IP layer works, etc. It really is a mess.

I think it would have been better to label everything that DHCPv6 covers with an entirely new name. Its functionality is fine for what it’s tasked to do, and much of the confusion I’d argue stems from those who (think they) know IPv4 trying to map their understanding to IPv6 unmodified.

So did 64 bit CPU adoption get delayed because addresses are hard to read compared to 32 bit addresses? Maybe not so much...

But the argument might still hold. If 80% of average network admins decide to hate IPv6 because they can no longer remember IP addresses of several machines and subnets by heart that might hinder adoption. Most of them are not daily affected by the fact that the world has run out of IPv4 addresses. And NAT works well enough for most of them, many are even convinced it gives them security.

Remembering your own machines really isn't the problem people think it is.

If I ask you what 192.168.1.1 is, you're probably going to guess it's a router/gateway. There is absolutely no reason for it to be, it's merely an accepted convention that the lowest-numbered host is the gateway.

There's absolutely nothing stopping you doing the same in ipv6. If you need to be able to remember where your gateway is, put it on 2001:db8::1. The problem isn't that they're long, it's that for some reason we assume we have to remember dynamically assigned addresses. Any address you have to memorise shouldn't be dynamically assigned, whether it's v4 or v6.

> put it on 2001:db8::1

Except my prefix is a hell of a lot longer than that...

And it's not my choice that it changes every now and then (at least once a month).

That said, I use DynDNS for IPv4 too, but it's easier since I only need to configure it for the router, but for IPv6 each machine I want to access needs it's own record.

For all of it's faults Port Address Translation (NAT) sure has a way of making the address size more manageable.

we managed to connect a few billion devices using about 200mio addresses and a protocol that was designed for a few thousand hosts.

successfull technology indeed.

Close to 90% mobile phones in USA/Canada have IPv6 connectivity for about 5 years.

My home ISP gives me an IPv6 address as well. Much of the internal infra that I use at work has AAAA records in our local DNS.

I feel comfortable saying IPv6 is here.

I wish Verizon would start offering IPV6 across their wireline footprint.

They are. I was part of the test rollout of IPv6 when I lived in Richmond, VA last year. It worked flawlessly so I'd assume they should be set for a greater rollout sooner rather than later.

When was that? It's been "coming soon" on Verizon's own FAQ[1] for almost half a decade now. I'm in one of the major MSAs along the eastern megalopolis, and there's no IPv6 here.

[1]: https://web.archive.org/web/20171220092540/https://www.veriz...

Last year. I got it at the beginning of 2020 IIRC and I moved from VA to another state in sept 2020.

Over 30% global adoption for google users, to the extent of having a public ipv6 address and using ipv6 preferentially:

https://www.google.com/intl/en/ipv6/statistics.html

If you watch the graph in smaller time scale you see adoption is higher on weekends than on weekdays. I guess that means consumers using Google and similar from their mobile phones have a high rate of adoption. They did not do it themselves. While the average medium (and why not big) company IT department has not started to do anything and is IPv4 only. Seen in the graph when people work Monday to Friday and especially around Christmas.

I have had native IPv6 from my ISP for 11 years now.

Meanwhile, entire countries missing it today...

and there are those having ipv6 access from the isp but disabling it in the router because it caused some (badly timed) fuckups in the past.

Reply on news.ycombinator.com