Multiplexed Internet Domain Names
Multiplexed domain names introduce a hierarchy within second level names. This extra level supports multiple use of 'the same' name without ambiguity. Examples could include name.com, name*1.com, name*2.com, etc.
Improvement is needed most in the legacy .com TLD and country code TLDs, but could be applied equally to all Top Level Domains.
Problems solved by multiplexed names include:
Domain names work when normal users are willing
to type them as address or follow them as links.
Domain names were introduced in 1983. The only major improvement since then was the introduction of Internationalized Domain Names that support characters and scripts outside standard ASCII English. Internationalized Domain Names were introduced in 2003!
ICANN's new generic Top Level Domains are not an improvement, they don't support normal users. When US Department of Commerce created ICANN their primary concern was: "... widespread dissatisfaction about the absence of competition in domain name registration."
Commerce never mentioned customer benefit or user demand. ICANN was built on supply side push - Internet users were never asked if they wanted thousands of new Top Level Domains. The results show they didn't.
The DoC also runs the US Patent and Trademark Office. They could have said: "compete by inventing a better system" but instead ICANN was founded and populated by groups that supported launching new TLDs.
More than 1900 ngTLD applications were submitted and over 1200 new TLDs have been delegated (made active) since October, 2013, but users don't want them. They don't solve user problems.
The legacy .com TLD continues to grow. The number of registered .com names is now at 144.4 million (http://research.domaintools.com/statistics/tld-counts/) and continues to grow.
The 266 county code TLDs together account for another 158.7 million registrations.
How have ICANN's 1,200 new generic Top Level Domains worked out? Not very well.- The total number of ngTLD registrations peaked at over 29.4 million in April, 2017; the count today is 2.5 million fewer (https://ntldstats.com/tld). Legacy .com has grown by over 14 million names in the same period.
- Only the top 11 ngTLDs register more than half a million names each, and the top 10 account for 60% of all ngTLD registrations.
- Top ngTLDs can gain or lose thousands of registrations in a day - gains are based on intensive marketing and losses on non-renewals.
- Failing to see value materialize, numerous organizations have withdrawn their ngTLD applications.
Unfortunately most domain names aren't actually used. The last count by ntldstats.com showed 72% of ngTLD registrations don't provide unique content - they are parked, redirect, or suffer from HTTP errors.
If ngTLDs don't resolve domain name problems, what does ICANN propose to do? Oh, they're talking about opening yet another round of ngTLD applications!
Isn't it a better idea to provide users with what they want, instead of what ngTLD merchants want them to want?
The Internet Domain Name System was never designed to provide universal naming, and that caused a number of problems now so ingrained that most people accepted them as inevitable. Things as common as domain name disputes, name warehousing and auctions, and the drive to market unwanted new TLDs are consequences of the system not being designed to provide universal naming.
The basic problem: most people, companies and trademark holders can't use their own name under their preferred Top Level Domain.
The DNS is a technical system written to a technical specification. Problems can be resolved by extending the specification. This was done when Internationalized Domain Names made it possible to use 'foreign' characters and scripts in domain names.
Since the domain name system is hierarchical, multiplexed names add a hierarchical level within second level names. It's like adding street numbers to street names within a city. This makes the name space under any Top Level Domain virtually unlimited.
We need a new token character to identify/generate a hierarchy. We suggest the asterisk (*) as a token, together with a number.
Compare it to the accepted character that designates email addresses - MaratSade.fr could be seen as a domain name, but write it Mar@Sade.fr and you recognize it instantly as an email address. The same can apply to domain names, where the asterisk is a character indicating multiple use of the same name.
Technically, names are registered in a set format and translated by a simple edge application to include the multiplexing token. This is similar to, but not the same as, the system used to generate foreign characters and scripts in Internationalized Domain Names.
Aren't domain names ICANN's responsibility?
Can't you just add numbers, or edit the software already
used to translate foreign characters?
Multiplexed domain names are a technical step toward Universalized Domain Names. Multiplexed names nested with Internationalized Names make Universalized names available to anyone, anywhere, in any language or script, under their country code, legacy, or preferred new generic TLD.
Is Internet access a human right? In that case registering your own name, under your preferred TLD, is also your right. Otherwise you argue that a privileged minority should enjoy name ownership to the exclusion of the majority.
own domain name isn't a problem when Everyone
can be a Star. (Updated May 1, 2019)
Multiplexed names are not offered as a supported product; we want to demonstrate how the Internet domain name system can evolve to eliminate unnecessary naming restrictions and provide relevant names for everyone.
The combined URL address line/search field in modern browsers already supports the multiplexed name concept.
Multiplexed domain names as tested follow all applicable Internet standards, but the translation format used in our tests is not standardized.
Last updated November 2, 2019