Re:The world in which IPv6 was a good design (2017)
by Mauricebranagh on Tuesday December 29, 2020 @09:11AM
(#25569839)
Not as much, you could learn the basics on ipv4 in two to three 4 hour classes of study - assuming you know how to convert between binary octal and decimal.
[ Parent
| on HN ]
Re:The world in which IPv6 was a good design (2017)
by welterde on Tuesday December 29, 2020 @09:20AM
(#25569923)
The same is true of IPv6? There is really nothing deeply magical there that takes forever to understand.
Maybe be a bit more concrete about what's so much more complicated about IPv6 than IPv4..
Re:The world in which IPv6 was a good design (2017)
by sixothree on Tuesday December 29, 2020 @11:41AM
(#25571618)
What I am seeing here mostly is the biggest problem is that you can't hold an IPv6 address in your head. Ever.
I can look at an v4 address then 15 seconds later look at another address and know they are different. That's not possible with v6.
So I think people are conflating "difficult to wield" as "more complicated".
Re:The world in which IPv6 was a good design (2017)
by welterde on Tuesday December 29, 2020 @11:58AM
(#25571819)
If you only use autoconfiguration perhaps, but for manually assigned addresses it's really not too bad since one can structure them in a logical way (which would be extremely expensive to do in the IPv4 case).
If you are a company you can get your own IPv6 space and can structure things hierarchically: <company prefix>:<site>:<vlan>::<hostnumber>.
And in fact I can remember more IPv6 addresses for hosts than IPv4 addresses for the same hosts right now.. so there is that.
Re:The world in which IPv6 was a good design (2017)
by oarsinsync on Tuesday December 29, 2020 @01:31PM
(#25573071)
And yet I have fe80:: in my head and 2001:db8:: in my head (as well as my own /32). I don’t have the documentation prefix (if one even exists) for IPv4 in my head.
It’s harder, but “can’t... ever” and “not possible” are not true for everyone.