1 / 24

Universal Acceptance

Explore the challenges and solutions of Universal Acceptance (UA) for domain names, email addresses, and internet usage. Learn about the efforts of the Universal Acceptance Steering Group (UASG) supported by ICANN. Discover the impact, progress, and how you can contribute to achieving UA inclusivity online.

chebert
Download Presentation

Universal Acceptance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Universal Acceptance Monday, 22 June 2015

  2. Agenda for the Day • What is Universal Acceptance • Who’s doing something about it • What have they done • What are they going to do • Q&A & Comments

  3. Agenda • What is Universal Acceptance • How is it seen • Who’s Doing something about it • What are they doing • How you can help

  4. What is Universal Acceptance? • All Domain names operate equally: • IDNs, EAIs, IRIs, • Long ASCII • Recently added gTLDs

  5. Validation on Entry • Not all domain names are accepted in all applications • E-mail addresses may be rejected at validation • Browsers interpret a valid domain name as a search term • Non-ASCII, “long names”, “new names”

  6. Storage • Domain Addresses could be stored as 8-bit UTF-8 characters (Unicode) instead of the standard 7-bit ASCII. • Domains Addresses could be stored as Puny Code (xn--…) instead of Unicode. • There is no standard nor convention • URL vs IRLs – what’s to the Right of the “/” – and how is that stored? • Transformation may need to be done on the way in and on the way out

  7. Processing • There are probably some network devices that have firewalls hardcoded for TLD validation. • Browsers need to learn when an address is an address and when it is a search term • Other devices need to know that there are new TLDs being added every day and that addresses are no longer all in ASCII. [Think about your clever photocopier that will e-mail your scanned document. Can it cope with an non-ASCII address?]

  8. Display • Software needs to determine what it will display and under what circumstances. • Unicode or Punycode? • What if the device can’t display the characters? • What if a Unicode script is not installed?

  9. E-mail • How are addresses treated? • Are all Mail Servers compliant? Clients? • What happens when mail encounters a non-compliant server or client? • What happens when a list of addresses included EAIs and ASCII addresses? • What happens when scripts are mixed? Particularly Arabic or Hebrew (Right to Left scripts) 

  10. So, who’s doing something about it?

  11. UASG:Universal Acceptance Steering Group • Community initiative supported by ICANN • Four Groups • Topline & Technical Issues • International • Measurement & Monitoring • Community Outreach

  12. Overview of UASG • Recent History • Structure • Achievements • Going Forward

  13. “Recent” History • January 2015 – Flash Panel – DC • February 2015 – ICANN Singapore • March 2015 - Charter Development • April – Project Coordinators • May – Project Activations

  14. Structure • Chair – Ram Mohan • Vice-Chairs: • Edmon Chung • Rich Merdinger • Christian Dawson • Project Coordinators • T&T: Brent London • International: Dennis Tan & DusanStojičević • Community Outreach: Rich Merdinger & Christian Dawson • Measurement & Montioring: Mark MacFadden • Helper/Nagger/Facilitator/Worrier: Don Hollander

  15. Principles • A Community Group supported by ICANN • Global Solution • Broadbased solution • Not a Policy Development Group

  16. Achievements • UA Readiness • Acceptance & Validation • Storage • Processing • Displaying • Technical Specification & Good Practices Guide – in second draft • Knowledge Base for re-directing complaints started • Catalogue of relevant RFCs built • Testing/Piloting of EAI compliant systems interaction • Engaged with IGFs – Global & APRIGF & EuroDIG • Working on national engagement models (NZ & Thailand) • Working on organisational engagement model (ICANN IT Pilot) • Lots of thinking!

  17. UASG Workshop Resutls

  18. Topline & Technology

  19. International

  20. Measurement

  21. Community Outreach

  22. QUESTIONS/COMMENTS?

  23. Summary • UA is not yet achieved • Big Project – generally requiring effort by those outside the traditional ICANN community • UASG running to help facilitate and encourage

More Related