Re:I spent a week without IPv4 to understand IPv6 transition...
by hot_gril on Monday March 06, 2023 @04:44PM
(#35048093)
> separates groups of 4 while optionally :: abbreviates a bunch of 0's and leading 0's in groups are optional. The address can be longer, sure, but it's really near identical to dotted decimal beyond the lengths.
Consecutive colons aren't readable or easy to remember.
Re:I spent a week without IPv4 to understand IPv6 transition...
by p1mrx on Tuesday March 07, 2023 @01:02PM
(#35058704)
Do you think we should write addresses like 0000:0000:0000:0000:0000:0000:0000:0001, or what else would you propose?
Re:I spent a week without IPv4 to understand IPv6 transition...
by hot_gril on Tuesday March 07, 2023 @01:43PM
(#35059311)
192.168.1.2.
Re:I spent a week without IPv4 to understand IPv6 transition...
by p1mrx on Tuesday March 07, 2023 @01:51PM
(#35059432)
Error: fewer addresses than humans
Re:I spent a week without IPv4 to understand IPv6 transition...
by hot_gril on Tuesday March 07, 2023 @02:06PM
(#35059669)
There are only a few people on my LAN. For the Internet, use more groups when people need more addresses (like 8.8.8.8.3), and leave the existing addresses like 8.8.8.8 alone. This didn't have to be complicated.
I wouldn't mind a simpler DNS server IP though seeing as it's one of the few locations you need to treat as an address regularly. Sprint/T-Mobile has 2600::, which is not only short but seemingly a phreaking reference, active so why can't something similar be active for DNS. I get not wanting 8888 or whatnot, those blocks aren't assigned and advertising random bits for vanity can be annoying, but there are plenty of short IPv6 addresses that could be in use for the most common DNS servers on the planet. Even I have my personal DNS server running on an XXXX:XXXX:: public IPv6 address!