Two different issues ref. country codes

Slides:



Advertisements
Similar presentations
Prepared by Corporate Affairs September ICANN Update AfriNIC9 26 November 2008 Pointe aux Piments, Mauritius Anne-Rachel Inné ICANN.
Advertisements

1 Update on New gTLD PDP Joint GAC/GNSO meeting Avri Doria Chair, GSNO Council San Juan, Puerto Rico.
Protection of Intl Organization Names in new gTLDs ALAC Presentation Brian Peck.
Text #ICANN51 GNSO PDP Improvements Status Update.
#ICANN51 1 Translation and Transliteration of Contact Information PDP Working Group Activities Update ICANN Los Angeles Meeting October 2014 Chris Dillon.
PDP Improvements Update & Discussion. | 2 Background  Ten proposed improvements aimed to streamline and enhance the GNSO PDP Ten proposed improvements.
Consumer Trust, Consumer Choice & Competition Presenter: Steve DelBianco Chair: Rosemary Sinclair.
CcNSO Update for APTLD New Delhi February 2012 Keith Davidson, ccNSO Councillor.
GAC-GNSO Consultation Group On GAC Early Engagement in GNSO PDP London Progress Report 22/06/2014.
ICANN Costa Rica March 2012 FOIWG. Presentation outline Scope of Framework Of Interpretation Process Topics for interpretation Activities since ICANN.
GNSO Public Forum Dr Bruce Tonkin Chair, GNSO Council Lisbon, 29 March 2007.
1 1 The Why & How of IDN Generic Domain Names Presented by: Chuck Gomes Date: 13 May 2010.
Text #ICANN51 GAC / GNSO Joint Meeting 12 October 2014.
New gTLD Subsequent Procedures Steve Chan | APRALO-APAC Hub Webinar | 28 September 2015.
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.
Text #ICANN50 Strategic Discussion. Text What does success look like in one year? Successful working relationship with the GAC Demonstrate efficiency.
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.
GNSO IDN work Dr Bruce Tonkin Chair, GNSO Council IDN Workshop São Paulo, Brazil.
Standing Committee on Improvement Implementation Anne Aikman-Scalese, SCI Chair | ICANN-52 | February 2015.
GAC Community Session Protection of geographic names in new gTLDs 11 February 2015 Woking group Protection of Geographic Names.
ICANN Public Forum 27 March 2014 Work on protecting International Governmental Organization (IGO) and International Non-Governmental Organizations (INGO)
ICANN update APTLD Meeting Moscow, Russia Veni Markovski ICANN 21 June 2012.
GNSO IDN Working Group Meetings 3-4 Teleconference 30 January 2007 Contacts:
Joint GAC ccNSO Meeting ICANN Singapore 22 June 2011.
Text #ICANN50 Cross Community Working Group (CWG) on Framework of CWG Operating Principles Update to the GNSO 21 June 2014.
Text #ICANN49 Joint ccNSO-GNSO IDN Working Group (JIG) Update.
GNSO Costa Rica Report Stéphane Van Gelder, GNSO Council Chair 16 March 2011.
GNSO IDN work Dr Bruce Tonkin Chair, GNSO Council IDN Workshop Marrakech, June 25, 2006.
1 Internationalized Domain Names Paul Twomey 7 April 2008.
Update on New gTLD Auction Proceeds 17 October 2015.
Joint GAC – GNSO Meeting Wednesday 29 June – 9.30 –
GAC SESSION 7: PSWG Update. PUBLIC SAFETY WORKING GROUP (PSWG) – UPDATE TO THE GAC Agenda Item 7 | ICANN 56 | 28 June 2016.
LACRALO- Quick View ICANN 55 – Marrakech Vanda Scartezini 28/March/2016.
APTLD Busan, August 2011 Keith Davidson, ccNSO Councillor.
Vice Chair, UK Representative, Governmental Advisory Committee (GAC)
ccNSO PDP(s) on retirement of ccTLDs and Review mechanism
Country and Territory Identifiers in New gTLDs
New gTLD Subsequent Procedures F2F
ICANN57 F2F Meeting Slides
New gTLD Auction Proceeds CCWG Status Update
GAC in Nomcom Working Group ICANN56 Helsinki , June 2016
GAC Working Group on Protection of Geographic Names in new gTLDs
Two different issues ref. country codes
IANA Stewardship Transition Coordination Group (ICG)
Geographic protections
Community Session - Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS
CWG on the use of Country & Territory names as TLDs (CWG UCTN)
Partnership of Governments, Businesses and Civil Society: the ICANN example in coordinating resources and policy making Dr. Olivier MJ Crépin-Leblond
CWG on the use of country & territory names as TLDs (CWG UCTN)
IDN Variant TLDs Program Update
GAC WG to Examine the Protection of Geographic Names in Any Future Expansion of New gTLDs Update on WT Track 5 Activities Geographic Names at the Top.
ICANN62 GAC Capacity Building
Action Request (Advice) Registry
An Introduction by Dr. Olivier MJ Crépin-Leblond EURALO Chair
Work Track 5 Overview and Update
Guidelines Review Committee
Insert title here (75 characters maximum)
Preparation for Meeting with the Board
GAC Meeting with the GNSO
One Size Does Not Fit All
Updates about Work Track 5 Geographic Names at the Top-Level
1/17/2019.
GAC Joint Meeting with the ICANN Board
Welcome to Your First GAC Meeting
GAC Standards and Work Processes Overview
Two different issues ref. country codes
CCWG Accountability Recommendations
GAC Travel Support Rules Update
CCWG-Accountability ICANN56 26 June 2016
Presentation transcript:

GAC Agenda Item 10: Three-Character Country Codes as Top-Level Domains in Future Rounds

Two different issues ref. country codes THIS SESSION! Three-character country codes at the top-level in future rounds e.g. domainname.CCC Policy Development Process (PDP) First round forbade country names or codes at top-level

Background The joint ccNSO and GNSO working group on use of country and territory names at top level domains (CWG-UCTN) is looking at the possibility of lifting the current restrictions on 3-letter codes as well as country names. They sent out a questionnaire on Sept. 2015 > The GAC provided its initial input on Dec. 2015. Questions covered all 3-character combinations, in ASCII and IDN characters. On ISO 3-letter codes, the GAC noted their strong association with countries and territories > High risk of confusion with ccTLDs. Significant support for maintaining current protections. Less than 2% (300) of the 3-character ASCII letter-letter-letter combinations (17,576) are country codes (ISO 3166-1 Alpha-3). The joint ccNSO and GNSO working group (CWG-UTCN) has divided its work into three work streams and is at an early stage in its policy development process on 3-letter codes. It is starting to look at the treatment of 3-character codes and gathering early input into the PDP from the GAC and others for the future, but does not have proposals at this stage. It is posing questions that correspond to rough scenarios, should the GAC wish to offer early views on some or all of them.

What is the issue? The CWG-UCTN released “straw woman paper” at ICANN 55 Marrakech = possible policy approach to make three-character ISO-3166-1 alpha-3 country codes eligible as gTLDs in future. GAC Geonames WG has prepared a reasoned response to the “straw woman proposal” to uphold current protections. The response is submitted to the GAC for endorsement following Guidelines for GAC WGs. The joint ccNSO and GNSO working group (CWG-UTCN) has divided its work into three work streams and is at an early stage in its policy development process on 3-letter codes. It is starting to look at the treatment of 3-character codes and gathering early input into the PDP from the GAC and others for the future, but does not have proposals at this stage. It is posing questions that correspond to rough scenarios, should the GAC wish to offer early views on some or all of them.

GAC options - Country and territory names as SLDs Review and comment on the proposed response put forward by the GAC WG on geonames to the straw man paper and submit to the CCWG-UTCN. Pose questions to the CWG-UCTN Co-Chairs at ICANN56 in Helsinki. Cross Community session: country and other geographic names Forum (Wednesday 15:15 h.) Additional GAC members could engage in the activities of the CWG-UCTN. The RA sets review by the GAC as a condition to release CTNs. The RA does not specify what GAC review means and ccTLD manager for two-character codes

Thank you ! Questions? Ideas?