Historical Resolution Tracking Feature » Remaining Items from Beijing, Durban, Buenos Aires, Singapore and London GAC Advice: Updates and Actions

Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.

Remaining Items from Beijing, Durban, Buenos Aires, Singapore and London GAC Advice: Updates and Actions


Resolution of the New gTLD Program Committee
Topic: 
GAC Advice
Summary: 

NGPC adopts the scorecard titled "GAC Advice (Beijing, Durban, Buenos Aires, Singapore, and London): Actions and Updates (8 September 2014)

Category: 
gTLDs
Meeting Date: 
Mon, 8 Sep 2014
Resolution Number: 
2014.09.08.NG02
Resolution Text: 

Resolved (2014.09.08.NG02), the NGPC adopts the scorecard titled "GAC Advice (Beijing, Durban, Buenos Aires, Singapore, and London): Actions and Updates (8 September 2014)", attached as Annex 1 [PDF, 429 KB] to this Resolution, in response to open items of Beijing, Durban, Buenos Aires, Singapore and London GAC advice.

Rationale for Resolution: 

Article XI, Section 2.1 of the ICANN Bylaws https://www.icann.org/resources/pages/bylaws-2012-02-25-en - XI permit the GAC to "put issues to the Board directly, either by way of comment or prior advice, or by way of specifically recommending action or new policy development or revision to existing policies." The GAC issued advice to the Board on the New gTLD Program through its Beijing Communiqué dated 11 April 2013, its Durban Communiqué dated 18 July 2013, its Buenos Aires Communiqué dated 20 November 2013, its Singapore Communiqué dated 27 March 2014 (as amended 16 April 2014), and its London Communiqué dated 25 June 2014. The ICANN Bylaws require the Board to take into account the GAC's advice on public policy matters in the formulation and adoption of the polices. If the Board decides to take an action that is not consistent with the GAC advice, it must inform the GAC and state the reasons why it decided not to follow the advice. The Board and the GAC will then try in good faith to find a mutually acceptable solution. If no solution can be found, the Board will state in its final decision why the GAC advice was not followed.

The NGPC has previously addressed items of the GAC's Beijing, Durban, Buenos Aires, and Singapore advice, but there are some items that the NGPC continues to work through. Additionally, the GAC issued new advice in its London Communiqué that relates to the New gTLD Program. The NGPC is being asked to consider accepting some of the remaining open items of the Beijing, Durban, Buenos Aires, and Singapore GAC advice, and new items of advice from London as described in the scorecard [PDF, 429 KB] (dated 8 September 2014).

As part of its consideration of the GAC advice, ICANN posted the GAC advice and officially notified applicants of the advice, triggering the 21-day applicant response period pursuant to the Applicant Guidebook Module 3.1. The Beijing GAC advice was posted on 18 April 2013 ; the Durban GAC advice was posted on 1 August 2013 ; the Buenos Aires GAC advice was posted on 11 December 2013 ; the Singapore advice was posted on 11 April 2014 http://newgtlds.icann.org/en/announcements-and-media/announcement-11apr1... and the London advice was posted on 14 July 2014 . The complete set of applicant responses are provided at: .

In addition, on 23 April 2013, ICANN initiated a public comment forum to solicit input on how the NGPC should address Beijing GAC advice regarding safeguards applicable to broad categories of new gTLD strings . The NGPC has considered the applicant responses in addition to the community feedback on how ICANN could implement the GAC's safeguard advice in the Beijing Communiqué in formulating its response to the remaining items of GAC advice.

As part of its deliberations, the NGPC reviewed various materials, including, but not limited to, the following materials and documents:

GAC Beijing Communiqué: https://gacweb.icann.org/download/attachments/27132037/Final_GAC_Communi... [PDF, 237 KB]

GAC Durban Communiqué: https://gacweb.icann.org/download/attachments/27132037/Final_GAC_Communi... [PDF, 103 KB]

GAC Buenos Aires Communiqué: https://gacweb.icann.org/download/attachments/27132037/FINAL_Buenos_Aire... [PDF, 97 KB]

GAC Singapore Communiqué (as amended): https://gacweb.icann.org/download/attachments/27132037/GAC_Amended_Commu... [PDF, 147 KB]

GAC London Communiqué: https://gacweb.icann.org/download/attachments/27132037/Communique%20Lond... [PDF, 140 KB]

Applicant responses to GAC advice: http://newgtlds.icann.org/en/applicants/gac-advice/

Applicant Guidebook, Module 3: http://newgtlds.icann.org/en/applicants/agb/objection-procedures-04jun12... [PDF, 260 KB]

In adopting its response to remaining items of Beijing, Durban, Buenos Aires, and Singapore GAC advice, and the new London advice, the NGPC considered the applicant comments submitted, the GAC's advice transmitted in the Communiqués, and the procedures established in the AGB and the ICANN Bylaws. The adoption of the GAC advice as provided in the attached scorecard will assist with resolving the GAC advice in manner that permits the greatest number of new gTLD applications to continue to move forward as soon as possible.

There are no foreseen fiscal impacts associated with the adoption of this resolution. Approval of the resolution will not impact security, stability or resiliency issues relating to the DNS.

As part of ICANN's organizational administrative function, ICANN posted the London Communiqué and officially notified applicants of the advice on 14 July 2014. The Singapore Communiqué, the Buenos Aires Communiqué, the Durban Communiqué, and the Beijing Communiqué were posted on 11 April 2014, 11 December 2013, 18 April 2013 and 1 August 2013, respectively. In each case, this triggered the 21-day applicant response period pursuant to the Applicant Guidebook Module 3.1.