Domain Name Basics - Universal Acceptance
10
Domain Name Basics Universal Acceptance a short introduction for newcomers
-
Upload
tobias-sattler -
Category
Internet
-
view
414 -
download
1
Transcript of Domain Name Basics - Universal Acceptance
Domain Name Basics
Universal Acceptancea short introduction for newcomers
Universal Acceptance
2 | Tobias Sattler, CIO www.united-domains.de
Universal Acceptance is the concept that all domain names should be treated
equally.
References to the occurrence of users experiencing browser, email and other
applications issues while using Top-Level Domains (TLDs).
Domains and email addresses must be usable in any applications regardless of the
written script, length or newness of the TLD: example.photography
тест@пример.рф
例 . 佛山 [email protected]ögensberater
At the beginning of the TLD space, everything was based on ISO 3166 two-letter
codes and gTLDs, such as .com, .net and .org.
Wrong Assumptions
3 | Tobias Sattler, CIO www.united-domains.de
All TLDs are three letters or shorter
All TLDs in ‘plain’ American Standard Code for Information Interchange (ASCII)
No changes to DNS root beyond new ISO 3166 two-letter codes
Email addresses are ASCII only
These assumptions resulted in validation rules being hardcoded by software
developers and problems for users.
First Wave of Changes
4 | Tobias Sattler, CIO www.united-domains.de
The introduction of new gTLDs in 2001, such as .info and .museum, broke the
assumption about the length and larger changes to DNS root.
International Domain Names (IDNs) starting of 2003, such as español.com and
müller.de, broke the assumption about ASCII and email addresses.
The first non-ASCII Top-Level Domain (TLD) went live 2010. Russia рф
Egypt صر Saudi Arabia السعودية United Arab Emirates امارات
All the assumptions were wrong, but most people didn’t care.
Second Wave of Changes
5 | Tobias Sattler, CIO www.united-domains.de
In 2012 when ICANN announced the new gTLD program, and more than 1,900
were proposed.
Starting October 2013 the first new TLDs were delegated. More long ASCII names, such as .photography and .barcelona
More IDN (non-ASCII) names, such as .vermögensberater
Many TLDs were delegated every week
Browser, email and other application vendors couldn’t keep up with these changes.
General Slackness
6 | Tobias Sattler, CIO www.united-domains.de
Since 2001 a lot of changes have happened in the Domain Name Space.
Most changes weren’t transparent and weren’t widely public communicated.
Many of these changes hadn’t any impact on the public.
A lot of Software Developers and Managers didn’t care and some are lazy. They
were searching for code snippets and were just using them, regardless if they fully
fix the issue, e.g. search results on ’validate email address code’: +10M Google Search Results
+500 GitHub Repositories
+100 CPAN Modules
Public Suffix List
7 | Tobias Sattler, CIO www.united-domains.de
The Public Suffix List (PSL) is a catalog of Top-Level Domains (TLDs) maintained by
the Mozilla Foundation and used by Firefox, Google Chrome, Safari, Chromium,
Opera and Internet Explorer.
It is available for use in any software, but was originally created to meet the needs
of browser vendors.
PSL contains public Top-Level Domains and private Domains, such as CentralNic
TLDs (ae.org, gb.com, and many more), DynDNS, etc.
PSL helps in finding the highest level at which a domain may be registered for a
particular TLD and is used in many 3rd Party Libraries to support Software
Developers.
You may find more details and toolkits on https://publicsuffix.org
Initiatives
8 | Tobias Sattler, CIO www.united-domains.de
Especially because of the new gTLD program, a lot of awareness was created and
some initiatives arose from that. ICANN https://icann.org/universalacceptance
Universal Acceptance Toolkit (C, C#, Java, Perl, Python) https://github.com/icann
Universal Acceptance Repository http://ua.thedna.org
Universal Acceptance Steering Group (UASG) https://community.icann.org/pages/viewpage.action?
pageId=47255444
Google's Domain Test service https://github.com/google/domaintest
What should be done?
9 | Tobias Sattler, CIO www.united-domains.de
If you run an online business, ask your IT if your customers can use any kind of
email address to sign up or to update their data.
If you are an IT manager, don’t ignore it just because most people have .com email
addresses. Way to many people don’t. Let your developers check and adopt it.
If you are a Software Developer, quick check how your code is validating email
addresses (keyword ’newness of TLDs’) and how your database is storing them
(keyword ‘length’). There is a lot of help out there.
Thank you!
Please get in touch if you have any further questions:
https://tobiassattler.com
tobiassattler
10 | Tobias Sattler, CIO www.united-domains.de
