Applying the Paper Napkin Problem to the DNS system, then I see an alternative.
The unique, unmemorable 32 hex digit in @chrisfostertv initial DNS was this:
He proposed putting a string on top of it. Now my thought is, if a user can be specified as above, why couldn’t a domain name be as well?
There’s no reason to have to remember an unmemorible amount of numbers - only three pseudo random characters have to be remembered - at the end of any domain name, and then the domain name is provably unique.
In order for squatters to have no legitimate claim to a name, it has to reliably map many-to-one. The way I understand the username situation, it provides a many-to-one mapping of the name itself, but it then uses the first three characters of the MPID in place of where (on the existing internet) the TLD is located. So you end up with this:
- google.abc
- google.ubx
- google.ycd
Now I just used the MPID because that’s what the username uses. In reality, we could use any number that is similarly generated and similarly checked by the system for domainname/ID similarity (see @dirvine’s post above.)
P.S. When I read your comment, I thought of:
