7 ms·
What is the rational reason, if any, for gripes like these? The time to have this discussion would have been in like 1993 or so. Now, IPv6 is what we have, and
by teddyh 11y ago
What is the rational reason, if any, for gripes 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.
Also, the double-click argument is crap for two reasons: Firstly, it can be fixed by configuring your local software, and secondly, IPv4 addresses also had this so-called problem.
> IPv6 is still in the early stages of adoption
It really, really isn’t. It might look that way to you, in the US, at your home endpoint, but move to the backbone or outside the US and you get a very different picture. ARIN in the US just happened to be the last of the RIRs (except AFRINIC in Africa) to run out of IPv4 addresses, so the US was able to put off switching for longer than most, and the whole of the US is now consequently behind the curve.
- pas 11y agoSo, why not fix these problems? Go through the RFC process, if it doesn't collide with anything, it'll make it into the standard, IPv6.1 or whatever, and eventually things will support it. Sure, it might take ~10 years for all freezers and forgotten L3 switches to support it, but why not start at all? We can chance these things easier than our visual pattern matching engine. (Not that we can't train it to perform better, but that just means we'll still make more mistakes and will be less efficient than with this small change.) Fixed width fonts and indentation are good things, the majority of programmers use it for some reason, why not go for sane ergonomics in network related stuff?
- teddyh 11y ago> Sure, it might take ~10 years for all freezers and forgotten L3 switches to support it, but why not start at all? I seriously doubt that any change in notation would be beneficial enough to be worth the 10 years of work, incompatibilities and bugs. You don’t see people making this kind of fuss about MAC addresses; that’s because people know that they aren’t supposed to memorize them, and we treat them accordingly. That’s the thing about IPv6 - you have to realize that you have to let go of the notion of memorizing IP addresses, just as it would never occur to you to know your MAC address by heart. Use the DNS; eliminating the need to memorize IP addresses is what the DNS is meant for.
- toast0 11y agoMAC addresses are actually worse, some software displays uses colons to separate, and some uses dashes. IPv6 addresses are ungainly, and have two forms (canonical short, and canonical full), but you can usually put either form wherever you need an address, and there's good library support. I guess that's a benefit of a multiple decades adoption; by the time I get to use it, everything works already. :)
- jsz0 11y ago> So, why not fix these problems? They're individual preferences not problems. We can't realistically have a bunch of different notation standards to make everyone happy.
- prewett 11y agoTrue, so why not make a good notational standard so that everyone is at least not unhappy?
- jsz0 11y agoI'm a network engineer and I work with IPv6 often these days. I think it's a good notational standard. I don't care about the difference between dots and colons. That's much more of a programmers fetish type of thing. As a general rule I think network engineers, who actually have to work with this stuff, just want consistency. If IPv8 wants to replace colons with middle finger emojis sure OK. Whatever I don't care. Just let me know. I'll figure it out.
- uxcn 11y agoThe majority of people will use IPv6 transparently through DNS. I'm not sure why typing an address into a browser or even a terminal seems like the more common use case.
- xaduha 11y agoHear, hear. The fact that IPv6 addresses are so unruly is a blessing in disguise. Use DNS, /etc/hosts, bonjour, .ssh/config, whatever. Use names, stop using addresses directly, even with IPv4.
- colejohnson66 11y agoSadly, it's a lot easier to have my router always always assign my NAS 192.168.0.2 than it is to configure DNS
- merlincorey 11y agoMake a homelab and setup local DNS. It's not that complicated if you don't want to get fancy. You can also team it up with DHCP using tools like dnsmasq which is lightweight and works on everything from raspberry pis and routers with flashed firmware to a whole computer or VM on a larger host. You can do it. You should do it. Why haven't you done it yet?
- pmarreck 11y agoBecause it is work, and then it will require administration. Which is more work. Computers are smart enough to handle this, why can't everything on a subnet just have (for example) zeroconf?
- colejohnson66 11y agoNot saying what I'm doing is right, but giving my NAS a static IP works on any device connected to the network. My router doesn't support manual DNS entries and I don't want to go through the trouble of flashing OpenWRT just to do something. You can name off tools that make it easier all you want, but how is the average user supposed to know that? When I set up my NAS, I wanted it to be accessible from the same address no matter what. I knew (at the time) about static IPs and manual DNS entries. So I went to my router's configuration and it didn't support manual DNS entries. So I opted for a static IP, and it worked. Sure, it's a kludge and not future proof, but I don't care. That's the problem. The "solutions" only work if you both know about them and care enough to do it the right (instead of the easy) way
- brongondwana 11y ago> What is the rational reason, if any, for gripes 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 rational reason is that despite tons of "we have to adopt IPv6 or the world will end", people aren't learning it. Trying to understand the underlying reasons is worthwhile. The shittyness of the representation is one of those reasons. (I agree with the people who say "making the parsing namespace even more complex won't help anyone" though)
- teddyh 11y agoIt no longer matters if some people want to learn IPv6 or not. The world at large has adopted IPv6, by necessity. Those who refuse to follow with the times will, sooner or later, be replaced by those who are happy to learn new things. It’s not like the world will suddenly one day decide to give up and go back to IPv4. Adapt or die.
- Bud 11y agoYou seem to be confusing the difficulty of "learning" something which is trivially easy with the difficulty of using something that is designed in an obfuscated way that makes it hard to use. This situation is the latter. That's the argument of the article.
- Dylan16807 11y agoThe article is rather against the use of a colon at all, and that is not obfuscation.
- elktea 11y agoHardly. IPv6 is straight forward for any network engineer with experience with existing networks. It's IPv4 but you get to design address space to logically suit your infrastructure and needs.
- bigbugbag 11y agoYou seem to be confusing the difficulty of "learning" something with the difficulty of "unlearning" something to learn something new. I don't see any actual argument in the article, just narrow minded rant failing to see farther than it's own nose.
- toast0 11y ago>> IPv6 is still in the early stages of adoption > It really, really isn’t. It might look that way to you, in the US, at your home endpoint, but move to the backbone or outside the US and you get a very different picture. ARIN in the US just happened to be the last of the RIRs (except AFRINIC in Africa) to run out of IPv4 addresses, so the US was able to put off switching for longer than most, and the whole of the US is now consequently behind the curve. The US may have been slow to start, but is probably ahead of the curve now. AT&T (6rd, but still) and Comcast have a large amount of residential users that are IPv6 enabled; T-Mobile, Verizon, AT&T and Sprint all support it on wireless too (subject to apns and access technology).
- belorn 11y agoI suspect it's more about mind share in the IT profession rather than IPv6 support by ISPs, as they started to roll out when all new equipment had IPv6 support by default and a subset of customers were asking for it. In Europe for example, the IT profession has been bombarded with news on how IPv4 was running out, then it ran out, and then all problems because it ran out. Network courses have been teaching IPv6 for a long time, government has issued mandates to use it (and governments are not known to be fast on those issues...), and IT conferences used to talk about it to the point where it's such old news that it is no longer worth talking about.
- emmelaich 11y agoMost IT operations people within corporate networks use ips instead of names. And unix admins only trust ips in their host firewalls. So many things rely on the ip address that people get to know that 10.1.0.0 is headquarters and 10.1.3.0 is marketing and 10.4.0.0 is Seattle .. etc etc. I'm not saying that is a good thing or not, I'm just saying it IS. It would be a pain to use ipv6 internally.
- mulmen 11y agoI know that some network configurations will still have to use actual IPv6 addresses but for the most part you could save yourself a lot of pain by just using DNS and hostnames.
- emmelaich 11y agoWhen I speak to our network guys to get a firewall entry they don't want to hear about names. Their network diagrams don't have names. Using names to them is unnecessary cognitive load.
- belorn 11y agoWhat would happen if your current ISP got problems and you had to switch to a different ISP with a new range of addresses (assuming you don't have operator independent addresses and not using BGP)?
- p1mrx 11y agoIn theory, a change to the text representation would be significantly easier to deploy than IPv6 itself, because it doesn't require a change to the wire format. An end user could tweak the text representation for their own tools, while continuing to exchange packets with the rest of the Internet.
- conkrete 11y agoIf user access to Google via IPv6 is considered a good tool of measurement, then The US actually has the highest rate of IPv6 adoption. https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption&tab=per-country-ipv6-adoption https://www.google.com/intl/en/ipv6/statistics.html#tab=per-... Globally (again using user access to google as measurement) the adoption rate is still less than 10%, One could argue this could be considered still early stages of adoption.
- alternize 11y ago> then The US actually has the highest rate of IPv6 adoption. actually, according to these statistics, the adoption rate in belgium is much higher: 40.39%