ICANN 50: Universal Acceptance
-
Upload
icann -
Category
Technology
-
view
551 -
download
0
description
Transcript of ICANN 50: Universal Acceptance
![Page 1: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/1.jpg)
Text Text
#ICANN50
Universal Acceptance
25 June 2014
Francisco Arias, Director, Technical Services Edward Lewis, Senior Manager, Technical Services
![Page 2: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/2.jpg)
Text Text
#ICANN50
![Page 3: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/3.jpg)
Text Text
#ICANN50
Agenda
• Introduction
• Recent Activity
• The Plan
• Call to Action
![Page 4: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/4.jpg)
Text Text
#ICANN50
Universal Acceptance
![Page 5: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/5.jpg)
Text Text
#ICANN50
A Changing World of Identifiers
![Page 6: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/6.jpg)
Text Text
#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
![Page 7: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/7.jpg)
Text Text
#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
![Page 8: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/8.jpg)
Text Text
#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
![Page 9: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/9.jpg)
Text Text
#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
![Page 10: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/10.jpg)
Text Text
#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
![Page 11: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/11.jpg)
Text Text
#ICANN50
Bumps In the Road
![Page 12: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/12.jpg)
Text Text 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
![Page 13: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/13.jpg)
Text Text Browsers Not Rendering Correct Script
www.nic.测试.
www.nic.xn--0zwm56d.
![Page 14: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/14.jpg)
Text Text Internationalized Email Not Accepted
X
Message
From:
To:
Cc:
Subject: Urgent! New project for you
Send
Francisco
? 麻烦先生@导航.中国
![Page 15: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/15.jpg)
Text Text
#ICANN50
Road Ahead
![Page 16: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/16.jpg)
Text Text
#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
![Page 17: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/17.jpg)
Text Text
#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
![Page 18: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/18.jpg)
Text Text
#ICANN50
Recent Activity
![Page 19: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/19.jpg)
Text Text
#ICANN50
External Discussions
![Page 20: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/20.jpg)
Text Text
#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
![Page 21: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/21.jpg)
Text Text
#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
![Page 22: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/22.jpg)
Text Text
#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
![Page 23: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/23.jpg)
Text Text
#ICANN50
The Plan
![Page 24: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/24.jpg)
Text Text
#ICANN50
Formalize the Problem Statement
![Page 25: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/25.jpg)
Text Text
#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
![Page 26: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/26.jpg)
Text Text
#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
![Page 27: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/27.jpg)
Text Text
#ICANN50
Identify Stakeholder Groups
![Page 28: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/28.jpg)
Text Text
#ICANN50
Domain Name Industry & Associations
• ICANN
• Registries
• Registrars
• DNS Hosting Vendors
• Trade Associations
![Page 29: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/29.jpg)
Text Text
#ICANN50
User Communities
• Language specific
• Societies relying on communication media
![Page 30: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/30.jpg)
Text Text
#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
![Page 31: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/31.jpg)
Text Text
#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
![Page 32: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/32.jpg)
Text Text
#ICANN50
System and Network Operators
• IT Departments o End-user system administrators
o Email administrators
o Network administrators
• Internet Service Providers
![Page 33: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/33.jpg)
Text Text
#ICANN50
Security Practitioners
• Security Protocol and Operations Engineers
• Security Policy (or Firewall) Administrators
• Threat Advisors
![Page 34: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/34.jpg)
Text Text
#ICANN50
Facilitation
![Page 35: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/35.jpg)
Text Text
#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
![Page 36: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/36.jpg)
Text Text
#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
![Page 37: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/37.jpg)
Text Text
#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
![Page 38: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/38.jpg)
Text Text
#ICANN50
Areas of Attention
![Page 39: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/39.jpg)
Text Text
#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
![Page 40: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/40.jpg)
Text Text
#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
![Page 41: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/41.jpg)
Text Text 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
![Page 42: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/42.jpg)
Text Text
#ICANN50
Call to Action
![Page 43: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/43.jpg)
Text Text
#ICANN50
What’s In It for Me?
![Page 44: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/44.jpg)
Text Text
#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
![Page 45: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/45.jpg)
Text Text
#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
![Page 46: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/46.jpg)
Text Text
#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)
![Page 47: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/47.jpg)
Text Text
#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
![Page 48: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/48.jpg)
Text Text
#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
![Page 49: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/49.jpg)
Text Text
#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
![Page 50: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/50.jpg)
Text Text
#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)
![Page 51: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/51.jpg)
Text Text
#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
ICANNnews Social Media
![Page 52: ICANN 50: Universal Acceptance](https://reader034.fdocuments.in/reader034/viewer/2022052619/55695cccd8b42ad3278b522f/html5/thumbnails/52.jpg)
Text Text
#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