poll BLOW-UP THE NAMESPACE?

SpaceshipSpaceship
Watch

eyedomainous

PDFTV.comTop Member
Impact
1,632
As ICANN creates more domain extensions to "expand consumer choice, increase competition, and enhance innovation", character use restrictions in domain names remain based on 1987 rules, from RFC 1035 specifications, designed for 7-bit ASCII systems.

Should ICANN unrestrict some restricted characters in the DNS?

After all, expanding the domain name character set expands consumer choice, increases competition, and enhances innovation by infinite orders of magnitude greater than putting one of 1,500+ extensions after a name. Of course, one could do both... in the age of Large Language Models.

According to AI
"Machine learning models and algorithmic approaches could architect DNS implementations with expanded valid character sets while preserving interoperability and security. Through hybrid encoding strategies, enhanced error handling, and protocol simulation, AI could reduce invalid character errors by 40-60% within 3 to 5 years."

Restricted / 'Invalid' characters in the DNS include:
Comma (,)
Tilde (~)
Colon (:)
Exclamation point (!)
At sign (@)
Number sign (#)
Dollar sign ($)
Percent (%)
Caret (^)
Ampersand (&)
Apostrophe (')
Parentheses (())
Braces ({})
Underscore (_)
White space (blank)
Backslash (/)
Slash (/)
Asterisk (*)
Question mark (?)
Quotation mark (")
Less than sign (<)
Greater than sign (>)
Vertical bar (|)
63 character limit

Note:
Feel free to state a reason for your vote, and how you might use an 'invalid' character in a reg.
 
0
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
GoDaddyGoDaddy
Appraise.net

We're social

Escrow.com
Spaceship
Rexus Domain
CryptoExchange.com
Domain Recover
CatchDoms
DomDB
NameFit
  • The sidebar remains visible by scrolling at a speed relative to the page’s height.
Back