GNSO IDN Working Group Meetings 3-4 Teleconference 30 January 2007 Contacts:

Slides:



Advertisements
Similar presentations
ICANN Report Presented by: Dr Paul Twomey CEO and President LACNIC, Montevideo 31 March 2004.
Advertisements

1 Update on New gTLD PDP Joint GAC/GNSO meeting Avri Doria Chair, GSNO Council San Juan, Puerto Rico.
GNSO IDN Working Group Outcomes Report Lisbon, Portugal March 25, 2007 Contacts: (Ram Mohan - Chair)
Internationalizing WHOIS Preliminary Approaches for Discussion Internationalized Registration Data Working Group ICANN Meeting, Brussels, Belgium Jeremy.
GNSO Working Session on the Vertical Integration PDP 4 December 2010.
Draft Roadmap to Implement SAC 051 Steve Sheng, ICANN 1.
Internationalization Status and Directions: IETF, JET, and ICANN John C Klensin October 2002 © 2002 John C Klensin.
Governmental Advisory Committee New gTLD Program Briefing 19 June 2010.
Internationalized Domain Names Status Report Prepared for: ICANN Meeting, Lisbon 29 March, 2007 Tina Dam IDN Program Director ICANN
Cairo 2 November Agenda  Guidebook overview  Supporting and explanatory materials  Guidebook Module detail  Probable timelines 2.
Glen de Saint Géry ICANN GNSO Secretariat for Theresa Swinehart Counsel for International Legal Affairs Domain Day Milan.
New gTLD Basics. 2  Overview about domain names, gTLD timeline and the New gTLD Program  Why is ICANN doing this; potential impact of this initiative.
Introduction to ICANN’s new gTLD program. A practical example: the Dot Deloitte case. Jan Corstens, Partner, Deloitte WIPO Moscow, 9 Dec 2011.
1 Revised: April 29, What is a Web Domain?  A HOSTNAME that identifies one or more IP addresses (web servers)  IP address (Internet Protocol)
#ICANN51 1 Translation and Transliteration of Contact Information PDP Working Group Activities Update ICANN Los Angeles Meeting October 2014 Chris Dillon.
IDN over EPP (IDNPROV) IETF BOF, Washington DC November 2004.
Internationalized Domain Names: Overview of ICANN Activities Masanobu Katoh, Chair, IDN Committee Director, ICANN Board CDNC-CNSG-MINC IDN Joint Meeting.
Launching IDN & IDN TLDs: A gTLD Registry Perspective APNIC, Beijing
An Over View of current IDN Developments Eng.Mohamed El Bashir Ahmed Chairman – Sudan Internet Society “SIS” ICANN ccNSO Council Member ICANN IDN Committee.
Internationalized Domain Names (IDNs) Yale A2K2 Conference New Haven, USA April 27, 2007 Ram Mohan Building a Sustainable Framework.
CcTLD IDN TF Report ccTLD Meeting, Rio de Janero Mar. 25, 2003 Young-Eum Chair, ccTLD IDN TF.
1 Updated as of 1 July 2014 Issues of the day at ICANN WHOIS KISA-ICANN Language Localisation Project Module 2.3.
Internationalized Domain Names: Legal Issues and Potential Abuses Michael YAKUSHEV cctld.ru.
GNSO Public Forum Dr Bruce Tonkin Chair, new gTLD Committee Lisbon, 26 March 2007.
Consumer Trust, Consumer Choice & Competition Presenter: Steve DelBianco Chair: Rosemary Sinclair.
Registration of IDN Language Tables John L. Crain Bangkok, CcTLD Training 2004 John L. Crain Bangkok, CcTLD Training 2004.
CcNSO Update for APTLD New Delhi February 2012 Keith Davidson, ccNSO Councillor.
In Dec-2010 ICANN Board requested advice from ALAC, GAC, GNSO and ccNSO on definition, measures, and 3- year targets, for competition, consumer trust,
Michael Yakushev, cctld.ru Board Member.  WHOIS existed before ICANN (1982-)  Review of WHOIS Policy is prescribed by AoC (2009)  Review Team was formed.
1 IDN TLD Progress Veni Markovski Manager, Regional Relations ccTLD Meeting, Slovenia – 7-8 Sept 2009.
JIG (Joint ccNSO-GNSO IDN Group) Update APTLD | New Delhi Feb 23, 2012.
1 IDNs go live under.eu Conference for ccTLD registries and registrars of CIS Bled, Slovenia – 7 September 2009 Joke Braeken, Deputy Manager External Relations.
New gTLD Basics. 2  Overview about domain names, gTLD timeline and the New gTLD Program  Why is ICANN doing this; potential impact of this initiative.
Opportunities and Threats of new Top Level Domain Launches Bart Lieben Domainer Meeting, Paris 19 June 2008.
Internationalized Domain Names “IDN” Eng.Mohamed El Bashir Ahmed Chairman – Sudan Internet Society “SIS” ICANN ccNSO Council Member ICANN IDN Committee.
GNSO Public Forum Dr Bruce Tonkin Chair, GNSO Council Lisbon, 29 March 2007.
© Copyright 2003, JPRS 1.JP IDN Implementation June 24, 2003 Hiro Hotta JPRS (Japan Registry Service) 日本レジストリサービス.jp/
Community Readiness for IDN Variant TLDs Arabic Script Case Sarmad Hussain Center for Language Engineering Al-Khawarizmi Institute of Computer.
ccTLD IDN Report ccTLD Meeting, Montreol June 24, 2003 Young-Eum
1 1 The Why & How of IDN Generic Domain Names Presented by: Chuck Gomes Date: 13 May 2010.
IRTP Part D PDP WG Items for Review. Items for Review Policy Development Process WG Charter GNSO WG Guidelines.
1 Updated as of 1 July 2014 Issues of the day at ICANN Universal Acceptance of All TLDs KISA-ICANN Language Localisation Project Module 2.2.
Proposals for Improvements to the RAA June 22, 2010.
1 1 The GNSO Role in Internet Governance Presented by: Chuck Gomes Date: 13 May 2010.
IDN UPDATE Tina Dam ICANN Chief gTLD Registry Liaison Public Forum, Wellington 30 March 2006.
#ICANN50 Translation and Transliteration of Contact Information PDP Working Group Activities Update ICANN London Meeting June 2014 Chris Dillon and Rudi.
ICANN Regional Outreach Meeting, Dubai 1–3 April Toward a Global Internet Paul Twomey President and CEO 1 April 2008 ICANN Regional Meeting 1–3.
GNSO IDN work Dr Bruce Tonkin Chair, GNSO Council IDN Workshop São Paulo, Brazil.
POLICY: Application rules Moderator John Berryhill – John Berryhill LLC Panelists Thomas Barrett - EnCirca Mike Rodenbaugh – Rodenbaugh Law Nick Wood –
Review of CCWG-Acct 3 rd Proposal and ALAC Issues Alan Greenberg 04 December 2015.
Fast-Track IDN ccTLD Draft Implementation Plan An Overview APTLD Manila 2009 meeting 23 February 2009.
1 New gTLD Program What kind of Internet do you want? Speakers: Olof Nordling and Karla Valente Date: June 11, 2008.
Update on Consumer Choice, Competition and Innovation (CCI) WG Rosemary Sinclair.
Text #ICANN49 Joint ccNSO-GNSO IDN Working Group (JIG) Update.
IDN issues ITU-T SG16-Q7 26 July Objective Provide a set of examples why IDN study at ITU-T could be considered Demonstrate the need of ITU recommendation.
GNSO IDN work Dr Bruce Tonkin Chair, GNSO Council IDN Workshop Marrakech, June 25, 2006.
1 Internationalized Domain Names Paul Twomey 7 April 2008.
18 January 2006 Copenhagen ERO - TISPAN WG4 meeting
New gTLD Rights Protection Mechanisms & RPMs Review
Two different issues ref. country codes
Cyrillic scripts in IDN
Country and Territory Identifiers in New gTLDs
Two different issues ref. country codes
CWG on the use of Country & Territory names as TLDs (CWG UCTN)
ICANN’s Policy Development Activities
CWG on the use of country & territory names as TLDs (CWG UCTN)
IDN Variant TLDs Program Update
One Size Does Not Fit All
Updates about Work Track 5 Geographic Names at the Top-Level
Two different issues ref. country codes
Presentation transcript:

GNSO IDN Working Group Meetings 3-4 Teleconference 30 January 2007 Contacts: (Ram Mohan - Chair) (Olof Nordling - ICANN Staff) (Glen de Saint Géry – GNSO Secretariat)

GNSO IDN Working Group2 Agenda 1.Launch of IDN Wiki – procedures to access 2.Recap of major discussion points from January 23, 2007 call 3.Major topics on issues list 4.Prioritize all major headings 5.IDN impact on New gTLD recommendations 6.Review of ICANN Staff Issues report 7.Preparation for Feb 06 meeting

GNSO IDN Working Group3 Topics Left To Discuss Existing gTLD Strings Geo-Political Details Privacy & Whois Details Legal Details

GNSO IDN Working Group4 Topics … Existing gTLD strings –Allocation –Representation of strings –Should there be a policy recommendation regarding backwards compatibility of existing IDNs when IDN protocols change? Geo-Political Details –What are countries' role in IDN gTLDs? –What is the WG opinion on countries asserting "sovereign right" over scripts/languages? –What are ccTLD's role in IDN gTLDs? –What about geopolitical names in IDN gTLDs?

GNSO IDN Working Group5 Topics … Privacy & Whois Details –Do existing Whois policies for gTLDs adequately cover IDNs? If not, what is lacking? –Should there be a requirement that Whois information be available in a "link language" (such as English) in addition to the local script representation? Legal Details –What is the impact on UDRP when IDNs and IDN TLDs become common-place?

GNSO IDN Working Group6 Prioritization Introduction of New gTLDs Techno-Policy Details Existing Domain Name Holders Existing gTLD strings Geo-Political Details Privacy & Whois Details Legal Details

GNSO IDN Working Group7 New gTLD Recommendations – applicability of IDNs Selection Criteria –String –Applicant –Process conditions (ICANN) Allocation Methods Policies for Contractual Conditions

GNSO IDN Working Group8 ICANN Staff Issues Report Review document sent separately

GNSO IDN Working Group9 Plan for Feb 06 meeting Review WG thinking on –new gTLD Recommendations & –ICANN Staff Issues Report Review IAB Document Review Lab Test Begin crafting basic WG statements on the top priority topics

End of Jan 30 discussion

GNSO IDN Working Group11 Appendix Background material follows

GNSO IDN Working Group12 GNSO IDN WG Purpose To identify and specify –any policy issues that should be considered by the GNSO via a policy development process (PDP) that have not already been considered within PDP-Dec05 Our Job –Review New gTLD draft recommendations Laboratory test outcomes ICANN Staff Issues report RFC 4690 (IAB document) –Research Policy implications for IDN gTLDs –Report (due March 21, 2007) Policy matters shared/conflicted with ccNSO Policy issues that merit a new PDP

GNSO IDN Working Group13 Plan of Operation 18 meetings (9 pairs, every Tuesday) Each pair of meetings focused on specific agenda topics Calendar: –Complete review process by Feb 6 –Create draft review outcome by Feb 13 –Research policy implications & arrive at draft conclusions by Mar 6 –Review draft Lisbon report Mar 13 –Finalize Lisbon report Mar 20 –Issue Lisbon report Mar 21

GNSO IDN Working Group14 Issues from Sao Paulo I 1. Should transliterations of existing gTLD strings be addressed? - Translations of gTLDs already covered in the New gTLD work, - Transliterations relate to “confusingly similar” concept in New gTLDs - Complex, as transliterations cannot be defined for some scripts/languages 2. Should the next round for new gTLDs wait for the inclusion of IDN gTLDs? - Community expectations that IDN gTLD be launched soon, preferably within a year - Support in the New gTLD work to at least enable reservation of IDN strings - Risks for ASCII cybersquatting identified (e.g.espana vs.españa) - New gTLDs should not be delayed by waiting for a decision on IDN gTLDs. - IDN gTLD timing depends on outcome of both technical and policy work 3. Would aliasing be a preferred option, an open option or an option to discourage? - Aliasing maps the whole sub-domain tree to an additional TLD string - To be discussed without specific reference to any technical solution - Not an IDN issue per se, although prompting much interest in relation to IDNs - In the New gTLD recommendations, each application for a string is regarded as applying for a separate TLD. - There is no need for defensive registrations in an “alias” string - Aliasing could improve or deteriorate user experience, depending on the case - Aliasing of existing TLDs may invoke competition concerns

GNSO IDN Working Group15 Issues from Sao Paulo II 4. Should an existing domain name holder have a priority right for a corresponding domain in another script? - Issue not discussed at any depth in Sao Paulo - A domain name as such does not confer any intellectual property rights to the domain name holder - There could be particular issues to explore in connection to “aliasing”, see issue 3 above 5. Given a particular script on the top-level, should that script be compulsory on lower levels also? - Not a requirement for current gTLDs – otherwise there would have been no IDN SLDs - The IDN Guidelines state that characters within a string should be from a single script - Should that restriction extend across levels for an IDN gTLD? - Could be limited to the first and second levels only, in order to have an enforceable policy 6. How should countries’ claims to “rights” to scripts be regarded? - Political requirements to prove community support to accept TLDs in a particular script - Korean is a case in point – are there others? 7. How should initial limitations in available IDN scripts for DNS be made? - At first, only a subset of all Unicode scripts will be available for IDN TLDs - Exclusions of scripts/languages may raise political issues - Possible objections from countries/communities for being unfairly treated or left behind 8. Should a country opting for a gTLD be free to set policies for the second level? - ccTLDs have no obligations to follow any external policy-setting mechanisms - In analogy, should a country opting for a gTLD have similar freedom?

GNSO IDN Working Group16 Issues from Sao Paulo III 9. How could “grandfathering” of existing SLDs be achieved when the IDN protocols change? - The IDN protocol revision reduces the number of allowed code points - May affect 2 million IDN second level domains and require “grandfathering” options - Effects of protocol changes on application software may also raise “grandfathering” issues - Design criteria in the protocol revision are said to foresee grandfathering 10. What requirements for change of Whois should be considered? - Multiple solutions already in use today for Whois regarding IDNs - Few complaints on Whois for IDNs yet, may change with increased use, improved browser support etc - Experience that registrants in general wish to supply their names in their own script - Domain names could be output in, for example, UTF-8 or as “xn--” - Not a constraining factor for launch of IDN gTLDs, but standardization would be useful 11. How to handle IDN cases of variants? - This issue was only mentioned, not discussed in Sao Paulo - Variant issues are important for scripts with many symbols, where some can be interchanged - Related to the notion of “confusingly similar” 12. Is there a need to modify the UDRP in view of increased use of IDNs? - Staff has reported on experience of using the UDRP for IDNs. - UDRP applied by WIPO to IDN SLD disputes since Limited number of cases but UDRP said to work well also for IDNs, without obvious modification needs

GNSO IDN Working Group17 Issues from Sao Paulo IV 13. How to handle geopolitical names? - Is there a need for specific rules for gTLD strings with geopolitical names? - The same geopolitical name can relate to more than one location - New gTLD recommendation foresees objection opportunities to strings and a dispute resolution process - Possible additional New gTLD string test, not IDN-specific - Issue to be addressed by GAC and ccNSO as well 14. How could an IDN - ccTLD be defined and deployed? - Main topic for ccNSO IDN WG discussions in Sao Paulo - GAC input important on this matter, also for decisions regarding registry operators and TLD strings - Parallel list to ISO-3166 would be needed, but ISO has expressed reluctance to this approach - Proposal to start with one IDN-ccTLD per country, dedicated to (one of) its official language(s) - The notion of “official language” varies and calls for flexibility in the approach - Official name(s) of each country as TLD strings may be very long, requiring flexibility - Possible UNESCO role in relation to language communities and vetting of language tables For the full text of the Draft Issue List, see