https://datatracker.ietf.org/doc/html/rfc8981#name-problem-s...
I have zero concerns that the IPv6 namespace for my home network will conflict with another administrative site during a merger. So.. it works great. Also super handy when the DNS resolver for my local network is down because of power outages or other unrelated failures.
That said, I disagree with the parent statement that v6 isn't going to happen. It's already happening at a steady rate. From the Google stats it's steadily rolling out. Some countries are reaching 100% v6 deployment. I wouldn't be surprised if we eventually see some countries with high v6 deployments see services which are v6 only.
World map:
https://www.arcep.fr/cartes-et-donnees/nos-cartes/ipv6/carte...
France is extremely close to 100%:
https://www.arcep.fr/fileadmin/reprise/observatoire/ipv6/Arc...
> some countries with high v6 deployments see services which are v6 only.
IIRC this has already long happened in some countries with smaller IPv4 pools, can't recall where.
also I sure as hell dont remember my ipv4 address
There’s something to be said for human readable addresses. I’m a little nostalgic of how the .hack world was envisioned, where servers had address names like Hidden Forbidden Holy Ground.
If roughly 10 million words exist, then allowing any three words in order creates a space for 10^21 addresses… five words and you’re close to ipv6 address space, six words and there’s more combinations than ipv6 addresses.
I've never recognized an IPv6 address or prefix used in my networks.
If you want to be really wonky you can script DHCPv6 to statically assign ULA IPv6 leases that match the IPv4, and expire them when the IPv4 lease expires, but like said upthread, addressing hosts via IPv6 is the wrong way to go about it. On your lan, you really want to be doing ".local" / ".lan" / ".home".
.local is fine as long as all the daemons work correctly, but AFAIK there's no way to have SLAAC and put hosts in "normal" internal DNS, so .lan/.home/.internal are probably out.
The "official" is home.arpa according to RFC 8375 [1]:
Users and devices within a home network (hereafter referred to as
"homenet") require devices and services to be identified by names
that are unique within the boundaries of the homenet [RFC7368]. The
naming mechanism needs to function without configuration from the
user. While it may be possible for a name to be delegated by an ISP,
homenets must also function in the absence of such a delegation.
This document reserves the name 'home.arpa.' to serve as the default
name for this purpose, with a scope limited to each individual
homenet.
".home" and ".lan" along with a bunch of other historic tlds are on the reserved list and cannot be registered.
Call techy people pathologically lazy but no one is going to switch to typing ".home.arpa" or ".internal". They should have stuck with the original proposal of making ".home" official, instead of sticking ".arpa" behind it. That immediately doomed the RFC.
But the point is that is the address you would put in dns if you also wanted to use slaac. Most of the time however you will just set a manual address. And this was with obsd, where when slaac is setup you get the slaac address and a temporary address. I don't really know what linux does. Might have to try now.
Wow. That's so amazingly unpopular. Why anyone bothers talking about something untold millions of people use every day is beyond me.
You have to take into account seasonal trends. The summer is always higher, so yes, we’re currently below last summer, but we are above last April 1st, and this summer will be higher than last summer.
But I'm not sure that "How morally the enviable assistances categorize the insistent iodine beyond new time where new systems stalk" has the same memorable quality as "correct horse battery staple" does.
Not because of the encryption element, but the part about representing a 64 bit integer as a six word sequence for usability.
(https://en.wikipedia.org/wiki/S/KEY#Usability).
Also used outside of that for quickly/easily recognising hash fingerprints.
(It's easier to recognise that your fingerprint is "GAFF WAIT SKID GIG SKY EYED" than "87FE C776 8B73 CCF9").
(It also slips some parity in there for good measure).
So then I need to use DNS. At which point it could be IPv6.
I have 56 host entries in my dnsmasq.conf.
The reason I'm an IPv4 advocate in the IPv4/IPv6 war is that the problem was "we're out of address", not "your thermostat should be natively routable from every single smartphone on the planet by default and inbound firewalls should become everyone's responsibility to configure for every device they own".
CGNAT is a feature, not a bug. Blending in with the crowd with a dynamic WAN IP is a helpful boost to privacy, even if not a one-stop solution. IPv6 giving everyone a globally unique, stable address by default is a regression in everyone's default privacy, and effectively a death sentence for the privacy of non-technical users who aren't capable of configuring privacy extensions. It's a wet dream for shady data brokers, intelligence agencies, organized crime, and script kiddies alike - all adversaries / attackers in threat modelling scenarios.
IPv6 adds configuration surface I don't want. Privacy extensions, temporary addresses, RA flags, NDP, DHCPv6 vs SLAAC — these are problems I don't have with IPv4. More features means more opportunities to footgun with misconfigurations, being forced to waste my time learning and understanding the nuances of each (in again, what amounts to system I want nothing to do with).
"Reaching your own stuff" is already a solved problem, too. Tailscale/Headscale gives you authenticated, encrypted, NAT-traversing connectivity. It's better than being globally routable. It's also opt-in for anyone who wants it, and not forced on anyone, unlike the IPv6 transition.
I don't have to rely on extra commercial entities to be able to reach my network.
I did have a problem with hosting my own shit because my ISP by default does cgnat. That cost me an hour of my life to convince a party to give what used to be normal, end to end connectivity.
IPv6 predates those by decades.
Highly disagree. Middleboxes are a huge problem on global scale and have frozen any innovation below application layer. TCP and UDP even that they are on software not hardware layer cannot be updated or changed, see MPTCP efforts or QUIC giving up and building on top of UDP.
If this is so much privacy problem, IPv6 is there for many years reaching 50%+ deployments in some countries, I bet there should be concrete examples of such breaches and papers written.
> Reaching your own stuff is already a solved problem, too. Tailscale/Headscale
No address to receive communication - no problem install an app that would proxy it through someone who has the address. Tailscale/Headscale is great, using it daily, but they are not solution to the huge already build global network created to connect devices not connecting devices because lack of digits. Global is key here.
They advertise it as being useful for search/rescue as you can provide a precise location over an unclear voice channel. They conveniently ignore that speaking numbers is clearer than speaking random words.
I'm sure there's more I'm unaware of.
They are missing feature of some codes that can have variable length for variable precision.
Yes
> search and rescue teams are actively against people using it.
Sadly no
I’d really love to see things like this generate little jingles along with the sentence. :)
At least for me, part of the reason I can still sing the countries of the world is because the original Animaniacs song was set to a tune that was already familiar: “Jarabe Tapatío” (aka the Mexican Hat Dance).
Or more concisely, localhost.
Hard to forget a sentence like that!
Now, if only those people who designed IPv6 were smarter.. Hex aint that bad, LONG hex addresses are pain to use.
Now, lets say you have LAN like this [::1:0:0/56]. So, ::1:0:24 is easy to remember right? Managable? right?.. Also, bonus for :: shortening is, you immediatly know what are you dealing with, ::1 is loopback, ::1:1 is LL, ::1:0:1 is LAN.. everything else is Internet.
The truth is, IPv6 is really 64bit, the other 64bit part is just randomish node address...
The rationale being you are more likely to remember grammatical cogent sentence, than a random string of alphanumeric characters. Although I will agree that the generated sentences don't seem easy to remember. So I doubt it's utility.
And I don't think I ever typed manually any IPv6 address other than `::1`.
> How now the smart flies take the new time beyond new time where new times come.
..Nice idea, but it may need some more thought. (Even more so as 2001:db8::1 is much easier to remember than that!) (I wrote that parenthetical from memory on edit, vs. had to copy-paste the sentence when it was my intention to comment on it within seconds.)
All that being said, I think it's a neat idea and a cool tool!
In your typical home environment, just set your ULA to fd00::12 instead of 192.168.0.12, or fd00:16:34 instead of 192.168.16.34
Yes you'll run into issues if you were to later want to merge your private IPs with someone else, and you should use fd12:3456:7890::12 instead, remembering those extra 10 digits, but its not a problem at home, and no more of a problem with business mergers than ipv4 clashes anyway.
It's about as easy to remember as 81.187.123.45//192.168.0.53
Almost all ipv6 addresses I encounter start with 2001, so I just need to remember my home prefix is 8b0:abcd, which is about the same length as my home public IP of 81.187.123.45
::53 means subnet zero host 53, which is easier to remember than which rfc1918 range I used (and basically is the equivalent of remembering the 2001:: prefix)
If I have an internal server I'd have on 192.168.4.12 I could address it with 2001:8b0:abcd:4::12 just as easily, with the "4.12" translating to "4::12", and the "81.187.123.45>192.168.x.y" translating to "2001:8b0:abcd:x::y"
Just because slacc gives you an extra 64 bits of randomness doesn't mean you need to use them.
[…] thaw the new case beyond pure mass where flagrant toys fucken.
despite being an ipv6 skeptic, i’ve been thinking to try using ipv6 for our new company network, but make the addresses purely readable
How could we determine which device on mobile network is a faceless cellphone and which is a proper device needing real sweet Internet connection? And won't that make things more complicated than just v6 deployment?
Can argue that NAT, which interrupt layers ment for end device do basically the same as popular user hostinle unchangable mobile OSes, but I don't think latter is good either.