0
TextText
#ICANN50
Universal Acceptance
25 June 2014
Francisco Arias, Director, Technical Services
Edward Lewis, Senior Man...
TextText
#ICANN50
TextText
#ICANN50
Agenda
• Introduction
• Recent Activity
• The Plan
• Call to Action
TextText
#ICANN50
Universal Acceptance
TextText
#ICANN50
A Changing World of
Identifiers
TextText
#ICANN50
At the Dawn of the TLD Space
• “com/net/org” and the ISO 3166 two-letter codes
o  All but one [arpa.] th...
TextText
#ICANN50
Initial TLD Expansions
• Expansion approved in 2000 and again 2003
o  Set of gTLDs in 2000
o  Set of sTL...
TextText
#ICANN50
IDN ccTLDs Arrive
• Expansion into IDN ccTLDs
o  First encoding of operating non-ASCII TLDs
§  IDN test...
TextText
#ICANN50
2012 gTLD Program
• Hundreds of new gTLDs were proposed
o  First of these TLDs delegated in October 2013...
TextText
#ICANN50
Internationalized Email
• Email names extended from ASCII to UTF8
o  IDN TLDs enabled only this
§  mist...
TextText
#ICANN50
Bumps In the Road
TextText
Browsers Not Recognizing TLDs
www.nic.global.
www.nic.global.
www.nic.global.
Global Result Example
Search
www.gl...
TextText
Browsers Not Rendering Correct Script
www.nic.测试.
www.nic.xn--0zwm56d.
TextText
Internationalized Email Not Accepted
X
Message
From:
To:
Cc:
Subject: Urgent! New project for you
Send
Francisco
...
TextText
#ICANN50
Road Ahead
TextText
#ICANN50
Universal Acceptance Challenges
• Applications and services must
o  Enable use of whatever TLD is delega...
TextText
#ICANN50
ICANN 49
• Much has been said, time to move forward
o  Develop a roadmap based on community input
• ICAN...
TextText
#ICANN50
Recent Activity
TextText
#ICANN50
External Discussions
TextText
#ICANN50
APTLD Member Meeting
• Session dedicated to Universal Acceptance
o  Presentations and panel, including I...
TextText
#ICANN50
CENTR Tech Member Meeting
• Presentation on Universal Acceptance
o  Rising focus in region
• Lessons
o  ...
TextText
#ICANN50
Developing A Plan
• Based on ICANN 49 panel session
o  Spoke with registries, software/service/solutions...
TextText
#ICANN50
The Plan
TextText
#ICANN50
Formalize the Problem
Statement
TextText
#ICANN50
TLD Problem Statement
• Domain names in a TLD must be useable in
applications regardless of the written ...
TextText
#ICANN50
How Does Internationalized Email Fit?
• Internationalized email is a driver for IDN TLD
adoption
o  Cult...
TextText
#ICANN50
Identify Stakeholder Groups
TextText
#ICANN50
Domain Name Industry & Associations
• ICANN
• Registries
• Registrars
• DNS Hosting Vendors
• Trade Asso...
TextText
#ICANN50
User Communities
• Language specific
• Societies relying on communication media
TextText
#ICANN50
Application Developers/Service Providers
• Distributors of software
o  Closed and open source applicatio...
TextText
#ICANN50
Protocol and Operational Standards
• Protocol defining bodies
o  IETF
o  W3C
o  Unicode Consortium
• Ope...
TextText
#ICANN50
System and Network Operators
• IT Departments
o  End-user system administrators
o  Email administrators
...
TextText
#ICANN50
Security Practitioners
• Security Protocol and Operations Engineers
• Security Policy (or Firewall) Admi...
TextText
#ICANN50
Facilitation
TextText
#ICANN50
Motivate Activity
• Listening to stakeholders to gain insight
o  To grow the Internet, have to look to n...
TextText
#ICANN50
Foster Communications
• Connect stakeholders
o  Introduce when needed, help navigate
• Provide on-line c...
TextText
#ICANN50
Support Common Context
• Need for commonality in solution approaches
o  Novel solutions work against int...
TextText
#ICANN50
Areas of Attention
TextText
#ICANN50
Domain Name Industry Focus
• Enablers
o  If registration and DNS hosting don’t work, nothing else
can be...
TextText
#ICANN50
Broader Horizon
• Covers social media sites, webmail, browsers, etc.
o  List is unstructured to avoid se...
TextText
Establishing a Reporting Mechanism
Report Form
Report
This
doesn’t
work
Summary of
Reports
Protocol &
Operational...
TextText
#ICANN50
Call to Action
TextText
#ICANN50
What’s In It for Me?
TextText
#ICANN50
Domain Name Industry & Association
• Some of the challenges ahead
o  Open nameserver names (IDN) and con...
TextText
#ICANN50
User Community
• Some of the challenges ahead
o  Define what constitutes “usable”
o  Provide locale and ...
TextText
#ICANN50
App Vendors/Service Providers
• Some of the challenges ahead
o  Improve timeliness and accuracy in recog...
TextText
#ICANN50
Protocol and Operations Standards
• Some of the challenges ahead
o  Generate transition plans
o  Documen...
TextText
#ICANN50
System and Network Operators
• Some of the challenges ahead
o  Selecting and deploying tools that remove...
TextText
#ICANN50
Security Practitioners
• Some of the challenges ahead
o  Develop safe protocols for non-ASCII identifier...
TextText
#ICANN50
Next Steps
• Draft roadmap is now open for public comment
•  https://www.icann.org/public-comments/tld-a...
TextText
#ICANN50
Questions & Answers
• Draft Roadmap Public Comment
o  https://www.icann.org/public-comments/tld-
accepta...
TextText
#ICANN50
Upcoming Global Domains Division Sessions
•  25 June 2014
o  Whiteboarding Session with IRTP - C IRT
o  ...
Upcoming SlideShare
Loading in...5
×

ICANN 50: Universal Acceptance

562

Published on

Based on practical operational experience, not all systems (e.g. browsers, spam filters, registration databases, user profiles, ISPs, etc.) work seamlessly when new TLDs are added. Users may experience failures in resolution or other issues with newer TLDs, which in turn impacts consumer trust on the DNS. The issue of the Universal Acceptance of TLDs (Top-Level Domains) is critically related to the introduction of new gTLDs, as well as the introduction of IDN ccTLDs.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
562
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "ICANN 50: Universal Acceptance"

  1. 1. TextText #ICANN50 Universal Acceptance 25 June 2014 Francisco Arias, Director, Technical Services Edward Lewis, Senior Manager, Technical Services
  2. 2. TextText #ICANN50
  3. 3. TextText #ICANN50 Agenda • Introduction • Recent Activity • The Plan • Call to Action
  4. 4. TextText #ICANN50 Universal Acceptance
  5. 5. TextText #ICANN50 A Changing World of Identifiers
  6. 6. TextText #ICANN50 At the Dawn of the TLD Space • “com/net/org” and the ISO 3166 two-letter codes o  All but one [arpa.] three letters or shorter o  All in “plain” ASCII o  No changes to DNS root beyond new ISO 3166 codes • Email addresses (mailbox names) were ASCII • Assumptions were made, “burned in” o  User interfaces would list valid TLDs o  Security rules were built according to the list
  7. 7. TextText #ICANN50 Initial TLD Expansions • Expansion approved in 2000 and again 2003 o  Set of gTLDs in 2000 o  Set of sTLDs in 2003 o  First non-ccTLD changes since 1988 o  Some names were longer (4 letters and more) • Broke assumptions about valid TLDs, name length
  8. 8. TextText #ICANN50 IDN ccTLDs Arrive • Expansion into IDN ccTLDs o  First encoding of operating non-ASCII TLDs §  IDN test TLDs were not operational (little impact) o  Names were much longer (more letters) than earlier sets o  Right-to-left scripts challenged user interfaces • Broke assumptions regarding ASCII in TLD names
  9. 9. TextText #ICANN50 2012 gTLD Program • Hundreds of new gTLDs were proposed o  First of these TLDs delegated in October 2013 §  More long ASCII names §  More IDN (non-ASCII) names o  Many delegated every week • Broke assumptions of “no/few changes” to the root
  10. 10. TextText #ICANN50 Internationalized Email • Email names extended from ASCII to UTF8 o  IDN TLDs enabled only this §  mistertrouble@东西.测试. o  Internationalized email (RFC 6530) enables this §  麻烦先生@东西.测试. • Broke assumptions in email systems and viewers
  11. 11. TextText #ICANN50 Bumps In the Road
  12. 12. TextText Browsers Not Recognizing TLDs www.nic.global. www.nic.global. www.nic.global. Global Result Example Search www.global.example Buy this product or service. We are an example company that handles an
  13. 13. TextText Browsers Not Rendering Correct Script www.nic.测试. www.nic.xn--0zwm56d.
  14. 14. TextText Internationalized Email Not Accepted X Message From: To: Cc: Subject: Urgent! New project for you Send Francisco ? 麻烦先生@导航.中国 mistertrouble@navigation.china
  15. 15. TextText #ICANN50 Road Ahead
  16. 16. TextText #ICANN50 Universal Acceptance Challenges • Applications and services must o  Enable use of whatever TLD is delegated o  Display domain and email names correctly o  Work correctly for any name o  Implement appropriate levels of security
  17. 17. TextText #ICANN50 ICANN 49 • Much has been said, time to move forward o  Develop a roadmap based on community input • ICANN to play a facilitator role o  Motivate parties to participate o  Foster communications o  Support a common context
  18. 18. TextText #ICANN50 Recent Activity
  19. 19. TextText #ICANN50 External Discussions
  20. 20. TextText #ICANN50 APTLD Member Meeting • Session dedicated to Universal Acceptance o  Presentations and panel, including ICANN o  Wide spread interest in topic, different perspectives • Lessons o  Vendor willingness and challenges o  Legacy code base delaying progress o  User community refining requirements
  21. 21. TextText #ICANN50 CENTR Tech Member Meeting • Presentation on Universal Acceptance o  Rising focus in region • Lessons o  Appropriate scope is TLDs, domain and email addresses o  Realistic view of challenges for registries o  Enhancing usability of Internet is a goal
  22. 22. TextText #ICANN50 Developing A Plan • Based on ICANN 49 panel session o  Spoke with registries, software/service/solutions providers • Participated in a few real cases of problems o  Real reports, used as trials of plan, build connections • Discussed at APTLD and CENTR meetings • Drafted a plan for ICANN activity o  Document is currently open for public comment
  23. 23. TextText #ICANN50 The Plan
  24. 24. TextText #ICANN50 Formalize the Problem Statement
  25. 25. TextText #ICANN50 TLD Problem Statement • Domain names in a TLD must be useable in applications regardless of the written script, and length or newness of the TLD o  This captures the troubles due to broken assumptions, we now have §  Non-ASCII/IDN TLDs §  Longer TLD names §  Rapid introduction of TLDs o  Useable is an open term, to be defined by context
  26. 26. TextText #ICANN50 How Does Internationalized Email Fit? • Internationalized email is a driver for IDN TLD adoption o  Cultures that benefit from IDN want to benefit from email o  A “killer app” even though not a technological enabler • Referring to “useable” o  Define domain names to be useable when email addresses of the same script are fully functional
  27. 27. TextText #ICANN50 Identify Stakeholder Groups
  28. 28. TextText #ICANN50 Domain Name Industry & Associations • ICANN • Registries • Registrars • DNS Hosting Vendors • Trade Associations
  29. 29. TextText #ICANN50 User Communities • Language specific • Societies relying on communication media
  30. 30. TextText #ICANN50 Application Developers/Service Providers • Distributors of software o  Closed and open source applications o  Mobile device apps • Service providers o  Social media sites o  Webmail providers
  31. 31. TextText #ICANN50 Protocol and Operational Standards • Protocol defining bodies o  IETF o  W3C o  Unicode Consortium • Operations best practice bodies o  DNS-related o  Network services
  32. 32. TextText #ICANN50 System and Network Operators • IT Departments o  End-user system administrators o  Email administrators o  Network administrators • Internet Service Providers
  33. 33. TextText #ICANN50 Security Practitioners • Security Protocol and Operations Engineers • Security Policy (or Firewall) Administrators • Threat Advisors
  34. 34. TextText #ICANN50 Facilitation
  35. 35. TextText #ICANN50 Motivate Activity • Listening to stakeholders to gain insight o  To grow the Internet, have to look to new sources for inspiration • Educating audiences when needed o  ASCII and Internet history go hand in hand, need to break old habits • Identify gaps in energy, activity, focus
  36. 36. TextText #ICANN50 Foster Communications • Connect stakeholders o  Introduce when needed, help navigate • Provide on-line collaboration o  Remove the time and distance barrier o  Open, transparent review of approaches • Arrange forum discussions
  37. 37. TextText #ICANN50 Support Common Context • Need for commonality in solution approaches o  Novel solutions work against interoperability • Encourage an open and transparent approach to solutions • Document lessons learned
  38. 38. TextText #ICANN50 Areas of Attention
  39. 39. TextText #ICANN50 Domain Name Industry Focus • Enablers o  If registration and DNS hosting don’t work, nothing else can be built • Familiarity o  ICANN has existing relationships to rely upon
  40. 40. TextText #ICANN50 Broader Horizon • Covers social media sites, webmail, browsers, etc. o  List is unstructured to avoid setting incorrect priorities • Work is progressing here o  Want to tap in to learn o  Perhaps even get ahead and help
  41. 41. TextText Establishing a Reporting Mechanism Report Form Report This doesn’t work Summary of Reports Protocol & Operational Standards Bodies Application Vendors & Service Providers User Communities ICANN
  42. 42. TextText #ICANN50 Call to Action
  43. 43. TextText #ICANN50 What’s In It for Me?
  44. 44. TextText #ICANN50 Domain Name Industry & Association • Some of the challenges ahead o  Open nameserver names (IDN) and contact information (email) to all scripts o  Provide native-script tools for testing IDN • The payoff o  Foster user choice – more avenues for registration o  Build consumer confidence – work in their script o  Competition – permit registrants flexibility in naming
  45. 45. TextText #ICANN50 User Community • Some of the challenges ahead o  Define what constitutes “usable” o  Provide locale and cultural or business use detail o  Determine way to measure progress towards goal • The payoff o  Get the Internet you want
  46. 46. TextText #ICANN50 App Vendors/Service Providers • Some of the challenges ahead o  Improve timeliness and accuracy in recognizing TLDs o  Upgrade user interfaces, many improvements possible o  Keep mobile applications on par • The payoff o  Wider use through growth of the Internet population o  Expand access via new devices (mobile, tablet)
  47. 47. TextText #ICANN50 Protocol and Operations Standards • Some of the challenges ahead o  Generate transition plans o  Document testing criteria • The payoff o  Raising the population of users o  Improving the network o  Enabling further innovation
  48. 48. TextText #ICANN50 System and Network Operators • Some of the challenges ahead o  Selecting and deploying tools that remove barriers o  Testing, trialing configurations • The payoff o  Fewer trouble tickets o  More productive troubleshooting
  49. 49. TextText #ICANN50 Security Practitioners • Some of the challenges ahead o  Develop safe protocols for non-ASCII identifiers o  Develop rules to avoid “confusingly similar” names o  Build understandable, auditable (firewall) rules o  Limit false positive alarms • The payoff o  Safer Internet
  50. 50. TextText #ICANN50 Next Steps • Draft roadmap is now open for public comment •  https://www.icann.org/public-comments/tld-acceptance- initiative-2014-06-18-en • Publish final roadmap o  Include public comments • Follow the roadmap o  Perform the facilitation role (or as advised by the community)
  51. 51. TextText #ICANN50 Questions & Answers • Draft Roadmap Public Comment o  https://www.icann.org/public-comments/tld- acceptance-initiative-2014-06-18-en o  Other resources listed on that page @ICANN ICANNorg ICANN ICANN ICANNnewsSocial Media
  52. 52. TextText #ICANN50 Upcoming Global Domains Division Sessions •  25 June 2014 o  Whiteboarding Session with IRTP - C IRT o  IDN Root Zone LGR Generation Panels Workshop o  ICANN’s Security, Stability & Resiliency Team Outreach Session o  New gTLD Registry Operator Engagement o  User Workshop for GDD Portal Check schedule for times & locations: http://london50.icann.org/schedule
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×