alt.hn

4/1/2026 at 11:22:57 PM

IPv6 address, as a sentence you can remember

 https://sentence2ipv6.tib3rius.com/

by LorenDB

4/2/2026 at 6:35:36 AM

They should charge a small annual fee and let people reserve a custom word for a given IP. You could even have a small utility on your computer that automatically queries given names to "resolve" to IPs.

by olalonde

4/2/2026 at 7:12:17 AM

they should also charge a reasonably larger annual fee for reserving a short suffix and allow re-selling custom word prefixes..

by thewisenerd

4/2/2026 at 8:26:22 AM

To facilitate client to client communications, they should add a who-does-it-serve (short WHO DIS) system to get contact information of already reserved names.

by YellowTech

4/2/2026 at 8:37:13 AM

And then if they don't like someone they should revoke their word. And they should make it so words with certain endings are delegated to other countries who can also revoke your word if they don't like you.

by gzread

4/2/2026 at 8:00:51 AM

As long as there is a way to inappropriately link the security of my entire enterprise into it!

by themafia

4/2/2026 at 12:45:07 AM

If you're remembering your IPv6 address you're doing IPv6 wrong. In fact, it's good practice to always use a temporary IPv6 address.

https://datatracker.ietf.org/doc/html/rfc8981#name-problem-s...

by 1970-01-01

4/2/2026 at 8:03:18 AM

It's fdac::1. If you're using random 48 bit or 64 bit numbers in your IP address you're doing it wrong.

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.

by themafia

4/2/2026 at 1:34:10 AM

Yet another reason why ipv6 will never happen

by idiotsecant

4/2/2026 at 1:50:29 AM

I think the Matter standard is going to cause IPv6 adoption to increase significantly in the coming years. People will demand it, without even knowing what Matter or IPv6 are. They just want to be able to turn their lights off from their phone without any extra hardware or software.

by sholladay

4/2/2026 at 3:43:49 AM

Matter is only local networking. Essentially everyone has IPv6 on their local network.

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.

by Gigachad

4/2/2026 at 2:19:36 AM

They've had years to demand it, I don't see why it would suddenly change. Most users who buy "smart" appliances are not power users, don't set everything up themselves and just rely on manufacturer's servers anyway and don't need a direct connection - and are okay with it.

by spaqin

4/2/2026 at 1:36:08 AM

it already happened.

also I sure as hell dont remember my ipv4 address

by iknowstuff

4/2/2026 at 4:54:21 AM

I know your ipv4 address, 127.0.0.1. :)

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.

by Den_VR

4/2/2026 at 7:07:11 AM

Scrabble is 250-280k uk edition - wouldn't want to go too much beyond that I suspect. Where'd 10 mil come from?

by interstice

4/2/2026 at 7:18:56 AM

I also know your IPv6 address, ::1

Even easier.

by mrsssnake

4/2/2026 at 2:04:57 AM

I don't remember my ipv4 addresses either, but I recognize them as mine when I see them.

I've never recognized an IPv6 address or prefix used in my networks.

by RulerOf

4/2/2026 at 2:26:06 AM

You can set your ULA to something like "fddd:192:168::/48" and then on your vlan you prefix hint, say, "66". Now, any device on that vlan will be addressable by "fddd:192:168:66::$host". For example, your gateway ('router') for that vlan would be "fddd:192:168:66::1".

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".

by jorvi

4/2/2026 at 3:32:29 AM

> 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.

by yjftsjthsd-h

4/2/2026 at 3:54:52 AM

> On your lan, you really want to be doing ".local" / ".lan" / ".home".

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.
[1]: https://datatracker.ietf.org/doc/html/rfc8375

by alwillis

4/2/2026 at 4:43:50 AM

It may be the most officially-recommended for home use, but .internal is also officially endorsed for "private-use applications" (deciding the semantics of these is left as an exercise to the reader): https://en.wikipedia.org/wiki/.internal

by yjftsjthsd-h

4/2/2026 at 5:21:11 AM

That is a classical "design by committee" thing.

".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.

by jorvi

4/2/2026 at 4:18:32 AM

I do it by abusing the static slaac address. I have a set of wierd vms where they are cloned from a reference image, so no fixed config allowed. I should have probably just have used dhcp6 but I started by trying slaac and the static address were stable enough for my purposes so it stuck.

by somat

4/2/2026 at 5:17:44 AM

How does that work? I initially assumed you meant you just statically assigned machines to addresses, which I think would work courtesy of collision avoidance (and the massive address space), but I can't see how that would work for VMs. Are you just letting VMs pick an IP at random and then having them never change it, at which point you manually add them to DNS?

by yjftsjthsd-h

4/2/2026 at 5:43:19 AM

Pretty much. A given mac address assigned in the vm config maps directly to a static slaac address(the ones they recommend you not use) and those preknown slaac address are in dns, Like I said, I should probably use dhcp6 but it was a personal experiment in cloning a vm for a sandbox execution environment. and those slacc address were stable enough for that. every time it gets cloned to the same mac address it ended up with the same ip6 address. works for me, don't have to faf around with dhcp6, put it in dns. time for a drink.

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.

by somat

4/2/2026 at 10:14:14 AM

Clarification for others: with privacy extensions disabled, SLAAC'd IPv6 addresses are deterministically generated based on MAC addresses. There's also an inbetween (IPv6 are stable per network by hashing).

by jorvi

4/2/2026 at 6:39:27 AM

I run split-horizon DNS on mine. By far my preferred solution.

by stackghost

4/2/2026 at 7:08:38 AM

it will naturally happen when you work with it long term, similar to how it was with v4.

by miyuru

4/2/2026 at 1:39:47 AM

Adoption has been flat under 50% for a year now.

by apitman

4/2/2026 at 2:36:01 AM

A bit less than 50% of the whole Internet.

Wow. That's so amazingly unpopular. Why anyone bothers talking about something untold millions of people use every day is beyond me.

by msla

4/2/2026 at 2:42:50 AM

It’s not flat: https://www.google.com/intl/en/ipv6/statistics.html

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.

by umanwizard

4/2/2026 at 3:44:55 AM

Also just looking at the history it always seems to have flat periods with sudden boosts which never go back down.

by Gigachad

4/2/2026 at 2:40:38 AM

I’m always bemused when I read comments like this. Regardless of whether you think IPv6 is good or bad, it is happening. IPv6 traffic to Google goes up by a few percentage points a year, steadily, and is at around 50% now.

by umanwizard

4/2/2026 at 12:38:10 AM

I tried it. Maybe it's easier to speak than hexadecimal is.

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.

by ssl-3

4/2/2026 at 4:55:24 AM

Reminds me a bit of S/KEY (RFC1760, RFC2289 and others around the 1990's).

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).

by gertrunde

4/2/2026 at 1:43:15 AM

Being essentially impossible to memorize is one of the worst attributes of IPv6. I memorize and manually type IPv4 addresses all the time and it's super useful.

by apitman

4/2/2026 at 4:44:31 AM

I've been memorizing and typing IPv4 addresses too, but I have enough devices on the network now that I can't remember nearly all the IPv4 addresses.

So then I need to use DNS. At which point it could be IPv6.

I have 56 host entries in my dnsmasq.conf.

by BenjiWiebe

4/2/2026 at 4:05:09 AM

It is notable that an IPv4 address expressed as a decimal number has up to 10 digits, the same as a phone number in many countries.

by userbinator

4/2/2026 at 2:43:37 AM

DNS, Avahi are super usefuler.

by RiverCrochet

4/2/2026 at 3:55:21 AM

Good luck when you're trying to troubleshoot and DNS not working is one of the symptoms. 8.8.8.8 and 4.2.2.x are easy to remember.

by userbinator

4/2/2026 at 5:13:25 AM

So is 2620:fe::fe for Quad9 DNS

by flexagoon

4/2/2026 at 7:14:59 AM

DNS should be auto configured and work with multiple redundancy these days.

If it breaks, so much that you cannot do a dig, you need to re think your network.

by miyuru

4/2/2026 at 10:52:42 AM

My DNS "server" is a router which can "add" static entries. Easy with static addresses, won't work with dynamic addresses.

What redundancy, multiple servers? Do you think everybody runs dedicated homelabs to access a raspberry pi.

by whatevaa

4/2/2026 at 8:40:12 AM

Oh yes, that's really convenient for home users. "Install this thing on several computers and keep it in sync or you're not qualified to have a network"

by gzread

4/2/2026 at 2:43:23 AM

What would have been your solution to needing more bits? More information is always going to be harder to remember.

by umanwizard

4/2/2026 at 2:48:54 AM

Adding two extra bits to each octet, making each octet range from a still memorable 0-1023 rather than 0-255, would result in an addressing scheme 256x larger than all of IPv4 combined. The entire internet works fine even when IPv4 was nominally exhausted. NAT and CGNAT are not sins, they're not crimes, and there's no rational reason to be as disgusted with them as IPv6 fans are. Even then, IPv4 exhaustion wasn't really a true technical problem in the first place, it was an allocation problem. There are huge /8 blocks of public IPv4 space that remain almost entirely unused to this day.

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.

by anonym29

4/2/2026 at 5:56:08 AM

Saying that IPv4 is ok because we have NAT and CGNAT is like saying that spam is not a problem because we have spam filters everywhere.

by teo_zero

4/2/2026 at 6:04:25 AM

I don't have your problems with ipv6, and I'm actively using it.

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.

by hbogert

4/2/2026 at 6:40:28 AM

Wouldn't easy and accessible self-hosting be a major privacy win if that's your primary concern? Sounds much more private to run a Minecraft and Mumble server on an old laptop in a friend group than paying a commercial entity like a hosting provider to know about it and have a back door.

by simonra

4/2/2026 at 3:55:34 AM

>"Reaching your own stuff" is already a solved problem, too. Tailscale/Headscale

IPv6 predates those by decades.

by thfuran

4/2/2026 at 7:36:38 AM

> NAT and CGNAT are not sins

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.

by mrsssnake

4/2/2026 at 1:34:55 AM

It reminds me of what3words, using three words to describe any location on earth. I really hoped that could catch on.

by Gathering6678

4/2/2026 at 2:25:17 AM

Kind of like what3words, except what3words uses three words which you stand a chance of remembering, whereas this produced, for an address similar to mine, "Miniature nerves eulogize gaily inside erect lion yet able stables hiss the conclusive consultation."

by wzdd

4/2/2026 at 2:15:29 AM

what3words Is terrible and search and rescue teams are actively against people using it.

by katbyte

4/2/2026 at 2:27:08 AM

Care to elaborate why? I'm just curious since I didn't know (1) there was actually any kind of serious usage, or (2) there was pushback from rescue team...

by Gathering6678

4/2/2026 at 2:36:45 AM

W3W is very aggressive about protecting their IP, they don't want it to be a standard anyone can use like lat/long.

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.

by ryankrage77

4/2/2026 at 4:05:17 AM

One reason is that there are a lot of similar words in the dictionary. It is easy to mishear the wrong location especially when they are close together. Some of the words are long and complicated. Another is that they are random which means can't navigate from the codes.

They are missing feature of some codes that can have variable length for variable precision.

by ianburrell

4/2/2026 at 12:52:14 AM

Something that I think was probably once obvious to me but I rediscovered recently is just how intensely wired for song the brain is. If you want to memorize anything, doing it as a song makes it far easier.

I’d really love to see things like this generate little jingles along with the sentence. :)

by Waterluvian

4/2/2026 at 7:46:36 AM

As anecdotal evidence, I could never remember all the names of the london tube stations as prose, but after listening to Jay Foreman's Every Tube Station song a few times, I cant help but sing it every time I hear a tube station name, and can almost flawlessly list them all off

https://youtu.be/8jPyg2pK11M

by voidUpdate

4/2/2026 at 1:13:11 AM

There actually was an attempt on HN a little while back to use GenAI to convert facts, flashcards, lists, etc. into automated melodic mnemonics. The biggest issue in that particular case was that it was also generating the motif from scratch.

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).

by vunderba

4/2/2026 at 1:08:34 AM

It's huge when you consider all the data humans have stored and transferred orally over the millennia.

Music, meter, and rhyme are all (among other things) algorithms for indexing and error-correction, tools very suitable to the squishy hardware.

by Terr_

4/2/2026 at 1:40:24 AM

The new times take now beneath the new time while new times take the new year.

Or more concisely, localhost.

by buttocks

4/2/2026 at 2:25:52 AM

Commented with the same without reading through the comments first; now deleted.

That is a lot of words for ::1.

Edit: there was another one below, haha :)

by wowczarek

4/2/2026 at 6:13:02 AM

I’m afraid to ask, but why, and who, tries to or wants/needs to remember IPv6 addresses?

by Brajeshwar

4/2/2026 at 6:03:01 AM

It'd be nice if simpler addresses gave simpler sentences. fe80::1 translates to "Uninhibited times take now inside new time yet new times take the new year."

by traderj0e

4/2/2026 at 4:49:43 AM

"The amazing champions inspire boldly like brilliant genius and incredible legends admire splendid talent."

Hard to forget a sentence like that!

by _air

4/2/2026 at 1:21:47 AM

What is the use-case for this? I’m trying to think of an IPv6 address I would need to remember, and then when I’d have access to this site without having access to a text file where I could have noted the address down. I’m coming up empty.

by al_borland

4/2/2026 at 1:51:36 AM

it may more likely have something to do with the date of April Fools :) seems it got more than a few folks here haha

by boston_clone

4/2/2026 at 6:41:13 AM

http://borg.uu3.net/~borg/?ipv6

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...

by Borg3

4/2/2026 at 7:39:54 AM

> The truth is, IPv6 is really 64bit, the other 64bit part is just randomish node address...

So anyway it gives 128bits in total, 64 for network and 64 for node.

But I wish there was a better way to write just the local node part and global part being taken automatically.

by mrsssnake

4/2/2026 at 12:49:50 AM

I don't understand how the mapping works. An address has 8 parts and produces 16 words, so each part consists of 2 words. If we take the example 2a02, that gets encoded to "how atop", but I don't see how that text helps me that "how atop" means 2a02? Am I suppose to memorize both? How does that help?

by RedShift1

4/2/2026 at 1:10:38 AM

You are not supposed worry about the mapping. You trust the website to help decode it. You just remember the sentence. It's a little like what3words for coordinates.

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.

by spprashant

4/2/2026 at 3:21:59 AM

This encoding is so long, that I'm more likely to remember the raw address. :D

And I don't think I ever typed manually any IPv6 address other than `::1`.

by dpc_01234

4/2/2026 at 3:24:44 AM

No need to type `::1` anymore, you can instead just type `The new times take now beneath the new time while new times take the new year.`

by dietr1ch

4/2/2026 at 6:33:19 AM

OK. That's much easier. :D

by dpc_01234

4/2/2026 at 3:43:02 AM

You can make unique local address subnets with simple addresses.

I use a simple one like `fd10::1/128` and `fd10::2/128` and so on

Technically speaking RFC 4193 says you should use random bits. But I don't care.

by kingstnap

4/2/2026 at 12:33:21 AM

The new times take now beneath the new time while new times take the new time.

by Bratmon

4/2/2026 at 12:55:47 AM

So just imagine if there was a service that could translate any words you wanted into the IP address instead of relying on some website to generate jibberish. Wouldn't that be cool to use instead? Some kind of name system? Based around domains of authority?

by vel0city

4/2/2026 at 12:37:56 AM

The first (of two) examples encodes to:

> 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.)

by OJFord

4/2/2026 at 12:34:08 AM

I'm old. I can't remember breakfast.

by Singletail

4/2/2026 at 5:58:42 AM

why is there even a need to remember IPv6 address in the first place?

by vishalvi

4/2/2026 at 12:46:12 AM

Not too sure of the utility of this. It's not an easy sentence to remember, because while grammatical, it's nonsense—it would take some effort. So if I'm trying to memorize a static IP, setting up a DNS name is likely to be easier. And also if I'm going to be using this to memorize IPs I'd like the algorithm to be open source.

All that being said, I think it's a neat idea and a cool tool!

by re

4/2/2026 at 5:25:10 AM

love to get an api for this.

by HariPavan

4/2/2026 at 2:38:48 AM

Ah yes, because "How now the smart flies take the new time beyond new time where new times come." is so much easier to remember than "2001:db8::1".

by amstan

4/2/2026 at 2:00:19 AM

We kind of had the same idea for ECDSA public keys (an imagined solution to zokos triangle -- human readable and decentralized) as well as private keys (BIP39 brain wallets). Honestly it still falls short of truly name-based though.

by Uptrenda

4/2/2026 at 1:07:02 AM

Just proves that 16 bytes was too much, and we should have just gone 8 bytes.

by emilfihlman

4/2/2026 at 1:44:51 AM

I'm fine with 16 but they should have only used the bytes as they were needed, at least for 5 and 6 byte addresses, so those who desire short addresses could buy them.

by apitman

4/2/2026 at 6:06:11 AM

At least on a LAN, you can set up like fe80::3 . I think. Now I'm not sure if I got that right.

by traderj0e

4/2/2026 at 6:17:04 AM

fe80:: is for link local. You'd want to use something starting fc00:: or fd00::

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.

by iso1631

4/2/2026 at 6:07:32 AM

My vrrp address for my dns server at home is 2001:8b0:abcd::53

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.

by iso1631

4/2/2026 at 2:25:30 AM

Mine comes with a swear!

[…] thaw the new case beyond pure mass where flagrant toys fucken.

by blurrybird

4/2/2026 at 1:47:02 AM

ipv6 is for faceless hordes of cellphones, which could just as easily be NAT

despite being an ipv6 skeptic, i’ve been thinking to try using ipv6 for our new company network, but make the addresses purely readable

by paulsutter

4/2/2026 at 4:02:21 AM

If you're assigning addresses, you can make the addresses in a ULA as short as you want. You're supposed to use a random 40 bit network id but if you can accept that you may need to renumber at some point there is no reason you can't use fd12:b:a:d::beef or whatever.

by reincarnate0x14

4/2/2026 at 2:44:53 AM

There's another way to make addresses purely readable that's been around longer than NAT: DNS.

by RiverCrochet

4/2/2026 at 7:50:47 AM

> is for faceless hordes of cellphones

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.

by mrsssnake