An Introduction to Universal Acceptance

1. An Introduction to Universal Acceptance Presenter Name / Event Name / DD Month YYYY

2. UA in a Nutshell People from around the world can effectively use any domain name and any email address in any application for their personal and business use.

3. The Internet Has Evolved 2006 2016 Country Code (Nearly 300 total) Generic (22 total) Country Code (Over 200 total) Generic (Over 1,200 total) .com .edu .uk .jp .com .edu .org .uk .jp .net .aero .info .org .net .de .fr .de .cn .bank .bar .club .in .br .cn .in .aero .asia .car .global .london .br .mx .mobi .travel .рф .台灣 .vote .rio .sky .한국 .ଭାରତ .info .संगठन .在线 .ابوظبي .ストア .닷넷 . дети

4. What’s Changed • More Top-Level Domains (TLDs) available • No longer just two or three characters • No longer just in ASCII • List of TLDs is no longer static. Names added and deleted frequently. • Mailbox names also no longer just in ASCII .amex .accountant .asia ‎ ‏.كوم‎ .aaa .ファッション ‏.קום .公益 .ভারত .москва

5. But… It Doesn’t All Work Together http://soap.organic http://tokyo.ストア http://bank.com Bank X X 测试@普遍.世界 Email X Not a valid email address. In 2017, only 8% of the top websites could handle our sample set of non-English email addresses and top-level domains longer than the traditional two or three English characters. Only one of the top browsers met all our evaluation criteria.

6. The Role of Universal Acceptance UA-ready http://soap.organic http://tokyo.ストア http://bank.com Welcome to organic TOKYO Bank 当社の製品を購入します 测试@普遍.世界 SOAP Email Email validated. Account created. We make the best soap in the world. It’s 100% organic. Notready http://soap.organic http://tokyo.ストア http://bank.com Bank X X 测试@普遍.世界 Email X Not a valid email address.

7. Let’s See… Try to send an email to: kōrero@ngāpukapuka.nz (On an iPhone or Mac, hold down the ‘o’ to choose ō and hold down the ‘a’ key to choose ā) Test your own email address - https://uasg.tech/eai-check/

8. Anatomy of an email address username@example.com 测试5@普遍接受-测试.世界 • Username/ 测试5 • Mailbox name • Can be in ASCII or Unicode • Second and lower-level domain names (example/ 普遍接受-测试) • Can be ASCII or Unicode • Unicode can be represented as Unicode U-label or ASCII A-label • Top-Level Domain name (.com/.世界) • Can be ASCII or Unicode • Unicode can be represented as U-label or A-label • Can be 2 to 63 characters long • Validate from the DNS, not obsolete static lists

9. Universal Acceptance | Real World Benefits

10. Economic and Internet Accessibility Benefits of UA • There is a combined USD 9.8 billion annual opportunity coming from software systems working in harmony with the common Internet infrastructure. This is a conservative estimate. • Support for IDNs, which allow domain names in all of the world’s languages, could bring 17 million additional new users online. These include users whose lack of local language services was previously a barrier to a complete online experience.

11. UA Benefits • If left unaddressed, businesses and organizations face the potential of lost revenue, lost customer satisfaction and more. Ensuring readiness to accommodate the use of new domains and writing systems will: • Connect the next billion Internet users • Bring better accessibility to the world via internationalization of the Internet • Enable culture, society and economics • Deliver a better UX, resulting in customer satisfaction and retention • Responsibility to comply with standards • Provide uninterrupted support for users of new domain names • Reduce customer support burden

12. Why Bother • Allows people to use their preferred identity through the new TLDs • Seamless acceptance of all domain names and all email addresses – reduced support costs • Better cultural connection – particularly to non-English speaking communities • Responsibility to comply with standards • Remediation is not onerous • From Analysys Mason White Paper - https://uasg.tech/whitepaper/

13. Key Organizations Engaged with UA

14. UA Progress and What’s Ahead Reference documents and resources Use and test cases Industry events and university course slides Social media and email software & services evaluation and programming language remediation Influencer outreach and encouraging email providers to adopt current standards

15. Better UA = Better user experience • Better support for non-English speakers • Better support for screen readers (accessibility issues)URL: https://www.naturalreaders.com/online/ [naturalreaders.com]Test String 1: You may reach me at info@mysite.москваTest String 2: You may reach me at info@mysite.xn—80adxhks

16. Five Verbs to UA Readiness Store Validate Accept Process Display

17. About UASG Universal Acceptance Steering Group • Founded in February 2015 • Tasked with undertaking activities that will effectively promote the Universal Acceptance of all valid domain names and email addresses • Comprised of more than 170 companies (including Afilias, Apple, CNNIC, Go Daddy, Google, Microsoft, THNIC and others), governments and community groups

18. Enabling Universal Acceptance Doers • Developers • Systems Architects Directors • CIOs • Senior IT Management Influencers • C* Suite Officers • Thought Leaders • Government Ministers and Officials

19. Inventory of Material

20. Moving forward • Test your own email address • Secure an EAI address • Use DataMail or Install DataMail App • Use CoreMail • Get your own systems evaluated and fixed • Use UASG Blueprint for CIOs as a guide • Get your tendering and contracts to include UA Readiness Clauses • Use UASG Quick Guide to Tendering clauses • Report UA problems with other applications • UASG Issue Logging • Participate in the UASG Discussions • Join the UA Discuss Mailing List

21. Principles of Universal Acceptance

22. Accept • UASG Recommendations • Input fields should be large enough to accept any valid input. • Applications and services should accept UTF-8 encoded domain names and email addresses. • Software should accept both A-labels and U-labels but convert A-labels to U-labels for display and for any processing that does not require A-labels. • In almost all cases an entered domain name or email address should be converted into Unicode Normalization Form C (NFC) before further processing. Process by which a domain name or an email address is received from a user interface, file, or API (application program interface) to be used by a software application or online service.

23. Validate • UASG Recommendations • All domain names should be validated against the Internationalized Domain Names in Applications standard, currently IDNA2008. • If an input string is expected to be an existing entry in the DNS, validate it with a DNS lookup. • Because the local part of an email address is defined only by the mail system that receives mail, it is generally not possible to validate it. Asking the user to enter the email address twice may detect typing errors. • In most cases, all of the components of a domain name or email address (except the TLD name if it is not an IDN) should be in a single script or closely related scripts. Process to check an email address or domain name for correct syntax and, when appropriate, that a name that is expected to exist in the DNS actually does. Validation techniques may need updating to work with modern domain names and email addresses.

24. Store • UASG Recommendations • Typically, domain names and email addresses should be normalized according to Unicode Normalization Form C (NFC) before storing. • In most applications, domain names and email addresses should be stored in files and databases encoded as UTF-8, the most common and best-supported Unicode encoding. • Within application code, the most appropriate representation of Unicode depends on the programming environment. • Applications should choose a consistent internal representation—either U-labels or A-labels—for IDNs. The temporary or long-term storage of domain names and email addresses, which should be stored in well-defined formats regardless of the expected duration of the storage.

25. Process • UASG Recommendations • As Unicode evolves, upgrade software when practical to use the most recent version of the standard and any available graphics and fonts. • Use APIs that support UTF-8 input or output whenever available. Use standard well-debugged libraries to process and validate IDNs. • Give special consideration for scripts written right-to-left that are used in domain names and email addresses. • When creating registries or other data structures that include script or language information, allow for as many as possible, ideally all that the Unicode Standard supports. Occurs whenever an email address or domain name is used by an application or service to perform an activity or changed into an alternative format. Additional validation may occur during processing.

26. Display • UASG Recommendations • Consider that although modern software and devices can display nearly all Unicode code points, older systems may have limited support, and require that applications manage some of their old fonts. • Display IDNs in their native character form unless there is a specific requirement to display them as A-labels. • Some mixed left-to-right (LTR) or right-to-left (RTL) text makes sense to users, and some does not. Use the Unicode restriction levels criteria to flag potentially misleading strings. • In some cases it may be necessary to design applications separately for different languages or language groups. Occurs whenever an email address or domain name is rendered visually by a user interface.

27. Tools & Resources for Developers Authoritative Tables: • http://www.internic.net/domain/root.zone • http://www.dns.icann.org/services/authoritative-dns/index.html • http://data.iana.org/TLD/tlds-alpha-by-domain.txt • See also SAC070: https://tinyurl.com/sac070 Internationalized Domain Names for Applications: • Framework: https://tools.ietf.org/html/rfc5890 • Protocol: https://tools.ietf.org/html/rfc5891 • Tables: https://tools.ietf.org/html/rfc5892 • Right-to-Left Scripts: https://tools.ietf.org/html/rfc5893 • Rationale: https://tools.ietf.org/html/rfc5894 • Internet Standard RFC 20: https://tools.ietf.org/html/rfc20 • GNU Libidn2 Library: https://www.gnu.org/software/libidn/#libidn2 Unicode: • Security Considerations: http://unicode.org/reports/tr36/ • Security Mechanisms: https://unicode.org/reports/tr39/ • Bidirectional Algorithm: http://unicode.org/reports/tr9 • Normalization Forms: https://www.unicode.org/reports/tr15/tr15-47.html • Supported Scripts: http://unicode.org/standard/supported.html • Universal Acceptance Steering Group info & recent developments: www.uasg.tech

28. Featured Case Studies The Government of the State of Rajasthan,through India’s RajMail project, has provided all its citizens with a free email address in either Hindi or English, using its own secure email platform provided by local company XgenPlus. This is an important step in the state’s eGovernance project. • RajMail: https://uasg.tech/wp-content/uploads/2019/02/UASG013E-en-case-study-rajmail-government-of-rajasthan.pdf The Thai Network Information Center Foundation (THNIC) and the Thai government support the .Thai Internationalized Domain Name (.ไทย)and Email Address Internationalization (EAI) initiatives, which facilitate the use of email addresses using the .ไทย IDN. This is an important step in increasing Thailand’s Internet penetration. • THNIC: https://uasg.tech/wp-content/uploads/2016/11/UASG013A-161031-en-case-study-thnic-digital.pdf See all case studies: https://uasg.tech/case-studies/

29. Next Steps… • Read the documents at https://uasg.tech/information/ • UASG003 – Fact Sheet • UASG005 – Quick Guide • UASG007 – Introduction to Universal Acceptance • UASG011 – FAQs • Subscribe to the UASG Discussion list www.uasg.tech/subscribe • Get your own systems UA Ready • Spread the word…

30. Contact Information • Contact the UASG: https://uasg.tech/contact/ • Meet the people of the UASG: https://uasg.tech/about/people/ • Participate in UASG Discussions: https://uasg.tech/subscribe • Report UA problems with other applications: https://uasg.tech/global-support-centre/

31. Thank You