21 April 2016 – Presentation at the CSAsummit2016 about Universal Acceptance and why it is important for Brands, ISPs & ESPs. Lars Steffen Member Services, eco – Association of the Internet Industry Jean-Jacques Sahel Vice President Europe, ICANN Terry Zink Program Manager, Microsoft Corporation

1. Universal Acceptance
Lars Steffen / Terry Zink / Jean-Jacques Sahel
#CSASUMMIT2016 / 21 April 2016
Universal Acceptance –
Evolving Email to fit the Expansion of the DNS

2. 2

3. 3

4. 4
Definition
Universal Acceptance (UA) is the state where
all valid domain names and email addresses are
accepted, validated, stored, processed and displayed
correctly and consistently by all Internet-enabled
applications, devices and systems.

5. Universal Acceptance Steering Group

6. 6
Who is involved…
…and many more

7. 7
Review Popular Websites, Dev Frameworks, Browsers, OS
Build Use Cases, Test Environments, EAI Community
Outreach Live Workshops, Panel Discussions, Presentations
UASG Activities
Writing Knowledge Databases, Whitepapers, Quick Guides

8. Why should you care?

9. 9
© FotoMaximum

10. 10
Brands should care...
...because Universal Acceptance is important for
any Online Service operating with Customer Accounts
that require email addresses for identification.

11. 11
© Yongyuan Dai

12. 12
Internet Service Providers should care...
...because any Mailbox worldwide has to be
Universal Acceptance ready to ensure
global and seamless communication.

13. 13
© zanskar

14. 14
Email Service Providers should care...
...because international Brands will request
Universal Acceptance for regional email campaigns
based on IDNs and new TLDs.

15. How to get
Universal Acceptance ready?

16. 16
Universal Acceptance ready
* Accept, Support, Use and Show Unicode.
* Store Information in UTF-8.
* Accept Strings up to 256 characters.
* Validate as little as possible.
* Verify TLDs against authoritative table.
* Query domain name against DNS.

17. 17
Universal Acceptance ready
* When developing app / service, or operating
a registry, consider languages supported.
* Perform code reviews.
* Check code points that were not defined
when application / service was created.

18. 18
Universal Acceptance ready
* Consider mixed-script addresses become more
common.
* Convert non-Unicode to Unicode before display.
* Use Unicode IDNA Compatibility Processing
to match user expectations.
* End user should see “everyone.みんな” vs.
“everyone.xn--q9jyb4c.”

19. Universal Acceptance
in the wild

20. 20

21. 21

22. 22
Further information
* Visit uasg.tech
* Visit bit.ly/icannUA
* Visit github.com/icann
* Get your Universal Acceptance
Quick Guide at the booth!

23. Thank you!