2013-04-11-gTLDStrings
GAC Advice
2013-04-11-gTLDStrings
N/A
Consensus met
2013-04-11-gTLDStrings
Communication
a. Strings for Further GAC Consideration
In addition to this safeguard advice, that GAC has identified certain gTLD strings where further GAC consideration may be warranted, including at the GAC meetings to be held in Durban.
i. Consequently, the GAC advises the ICANN Board to: not proceed beyond Initial Evaluation with the following strings : .shenzhen (IDN in Chinese), .persiangulf, .guangzhou (IDN in Chinese), .amazon (and IDNs in Japanese and Chinese), .patagonia, .date, .spa, . yun, .thai, .zulu, .wine, .vin
GAC Acknowledgement of Register Entry
GAC: 2 May 2013
Board: 9 May 2013
Next Steps/Required Action
Board Action:
Item | Resp. | Start | Compl. | Status |
---|---|---|---|---|
Publish GAC Communique and notify applicants of 21-day GAC Advice Response Period | Staff | 18 April | Complete | |
Applicants 21-day response period to GAC Advice | Applicants | 19 April | 10 May | Complete |
Publish GAC Communique to solicit input on how the New gTLD Board Committee should address GAC advice regarding safeguards applicable to broad categories of New gTLD Strings | Staff | 23 April | Complete | |
Public Comment period on how Board should address GAC Advice re: Safeguards http://www.icann.org/en/news/public-comment/gac-safeguard-advice-23apr13-en.htm |
Public | 23 April |
Comment: 14 May Reply: 4 June |
Complete |
Collect and summarize applicant responses to GAC Advice | Staff | 11 May | 31 May | Complete |
Summarize and analyze public comments on how Board should address GAC Advice re: Safeguards | Staff | 5 June | 12 June | Complete |
Review and Consider Applicant responses to GAC Advice and Public Comments on how Board should respond to GAC Advice re: Safeguards | New gTLD Program Committee | 13 June | 20 June | Not Started |
The NGPC is also developing a GAC Scorecard similar to the one used during the GAC and the Board meetings in Brussels on 28 February and 1 March 2011.
Each scorecard item will be noted with a '1A' '1B' or '2'
1A: Indicates that the NGPC's proposed position is consistent with GAC Advice as described in the Scorecard.
1B: Indicates that the NGPC's proposed position is consistent with GAC Advice as described in the Scorecard in principle, with some revisions to be made.
2: Indicates that the NGPC's current position is not consistent with GAC advice as described in the Scorecard and further discussion with the GAC is required following the relevant procedures in the ICANN Bylaws.
Updates: http://www.icann.org/en/news/announcements/announcement-14jun13-en.htm
Board Scorecard:
Summary of GAC Advice | NGPC Response | |
---|---|---|
In addition to this safeguard advice the GAC has identified certain gTLD strings where further GAC consideration may be warranted, including at the GAC meetings to be held in Durban. Consequently the GAC advises the ICANN Board to not proceed beyond Initial Evaluation with the following strings: .shenzhen (IDN in Chinese), .persiangulf, .guangzhou (IDN in Chinese), .amazon (and IDNs in Japanese and Chinese), .patagonia, .date, .spa, . yun, .thai, .zulu, .wine, .vin | 1A |
The NGPC accepts this advice. The AGB provides that 'GAC advice will not toll the processing of any applications (i.e an application will not be suspended but will continue through the stages of the application process)' (AGB § 3.1). At this time, ICANN will not proceed beyond initial evaluation of these identified strings. In other words, ICANN will allow evaluation and dispute resolution processes to go forward, but will not enter into any registry agreements with the applicants for the identified strings for now. (Note: community objections have been filed with the International Centre for Expertise of the ICC against .PERSIANGULF, .AMAZON, and .PATAGONIA. The application for .ZULU was withdrawn. |
Responsible Party
Board/Staff
Current Status/Communications Log
10 May 2013 - Letter from the ICANN Board re: Progress in Addressing GAC Beijing Advice
6 June 2013: NGPC Scorecard
Board Action (Accept/Disagree)
- ICANN has allowed evaluation and dispute resolution processes to go forward, but will not enter into registry agreements with applicants for the identified strings for now.
- NGPC expects GAC to consider these applications further in Durban.
See http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-04jun13-en.htm and http://www.icann.org/en/groups/board/documents/new-gtld-resolution-annex-1-04jun13-en.pdf.