From: http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-25jun13-... 25 June 2013 Approved Resolutions | Meeting of the New gTLD Program Committee (note I have removed the rationales to make it easier to see the decisions - but refer to the link above for the full explanation of why the Board has chosen a particular outcome) 1. Consent Agenda: a. Approval of NGPC Meeting Minutes Resolved (2013.06.25.NG01), the Board approves the minutes of the 4 June 2013 New gTLD Program Committee Meeting. 2. Main Agenda: a. ALAC Statement on TMCH/Variants No resolution taken. b. Safeguards Applicable to all New gTLDs Whereas, the GAC met during the ICANN 46 meeting in Beijing and issued a Communiqué on 11 April 2013 ("Beijing Communiqué"); Whereas, the Beijing Communiqué included six (6) elements of safeguard advice applicable to all new gTLDs, which are identified in the GAC Register of Advice as: (a) 2013-04-11-Safeguards-1, (b) 2013-04-11-Safeguards-2, (c) 2013-04-11-Safeguards-3, (d) 2013-04-11-Safeguards-4, (e) 2013-04-11-Safeguards-5, and (f) 2013-04-11-Safeguards-6 (collectively, the "Safeguards Applicable to All Strings"); Whereas, on 23 April 2013, ICANN initiated a public comment forum to solicit the community's input on how the NGPC should address GAC advice regarding safeguards applicable to broad categories of New gTLD strings http://www.icann.org/en/news/public-comment/gac-safeguard-advice-23apr13-en.... ; Whereas, the NGPC met on 8 and 18 May and 4, 11 and 18 June 2013 to consider a plan for responding to the GAC's advice on the New gTLD Program, including the Safeguards Applicable to All Strings; Whereas, the NGPC met on 25 June 2013 to further discuss and consider its plan for responding the GAC's advice in the Beijing Communiqué on the New gTLD Program; Whereas, the NGPC has considered the public comments submitted during the public comment forum, and has determined that its position, as presented in Annex I attached to this Resolution, is consistent with the GAC's advice regarding Safeguards Applicable to All Strings; Whereas, the NGPC proposes revisions to the final draft of the New gTLD Registry Agreement http://www.icann.org/en/news/public-comment/base-agreement-29apr13-en.htm as presented in Annex II attached to this Resolution to implement certain elements of the GAC advice regarding Safeguards Applicable to All Strings; and Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2013.06.25.NG02), the NGPC adopts the "NGPC Proposal for Implementation of GAC Safeguards Applicable to All New gTLDs" (19 June 2013), attached as Annex I to this Resolution, to accept the GAC's advice regarding Safeguards Applicable to All Strings. Resolved (2013.06.25.NG03), the NGPC directs staff to make appropriate changes to the final draft of the New gTLD Registry Agreement, as presented in Annex II attached to this Resolution, to implement certain elements of the GAC advice regarding Safeguards Applicable to All Strings. c. Category 2 Safeguard Advice re Restricted and Exclusive Registry Access Whereas, the GAC met during the ICANN 46 meeting in Beijing and issued a Communiqué on 11 April 2013 ("Beijing Communiqué"); Whereas, the Beijing Communiqué included Category 2 safeguard advice, which is identified in the GAC Register of Advice as 2013-04-11-Safeguards-Categories-2 (the "Category 2 Safeguard Advice"); Whereas, on 23 April 2013, ICANN initiated a public comment forum to solicit the community's input on how the NGPC should address GAC advice regarding safeguards applicable to broad categories of New gTLD strings < http://www.icann.org/en/news/public-comment/gac-safeguard-advice-23apr13-en.... >; Whereas, the NGPC met on 8 and 18 May and 4, 11 and 18 June 2013 to consider a plan for responding to the GAC's advice on the New gTLD Program, including the Category 2 Safeguard Advice; Whereas, the NGPC met on 25 June 2013 to further discuss and consider its plan for responding the GAC's advice in the Beijing Communiqué on the New gTLD Program; Whereas, the NGPC has considered the public comments submitted during the public comment forum, and proposes revisions to the final draft of the New gTLD Registry Agreement <http://www.icann.org/en/news/public-comment/base-agreement-29apr13-en.htm> as presented in Annex I attached to this Resolution to implement the Category 2 Safeguard Advice for applicants not seeking to impose exclusive registry access; and Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2013.06.25.NG04), the NGPC adopts the "Proposed PIC Spec Implementation of GAC Category 2 Safeguards" (20 June 2013), attached as Annex I to this Resolution, to accept and implement the GAC's Category 2 Safeguard Advice for applicants not seeking to impose exclusive registry access. Resolved (2013.06.25.NG05), the NGPC directs staff to make appropriate changes to the final draft of the New gTLD Registry Agreement, as presented in Annex I attached to this Resolution, to implement the GAC's Category 2 Safeguard Advice for applicants not seeking to impose exclusive registry access. Resolved (2013.06.25.NG06), the NGPC directs staff to defer moving forward with the contracting process for applicants seeking to impose exclusive registry access for "generic strings" to a single person or entity and/or that person's or entity's Affiliates (as defined in Section 2.9(c) of the Registry Agreement), pending a dialogue with the GAC. d. Singular & Plural Versions of the Same String as a TLD Whereas, the GAC met during the ICANN 46 meeting in Beijing and issued a Communiqué on 11 April 2013 ("Beijing Communiqué"); Whereas, the NGPC met on 8 and 18 May and 4 and 11 June 2013, to consider a plan for responding to the GAC's advice on the New gTLD Program, transmitted to the Board through its Beijing Communiqué; Whereas, on 4 June 2013, the NGPC took action accepting GAC advice identified in the GAC Register of Advice as "2013-04-11-PluralStrings" and agreed to consider whether to allow singular and plural versions of the same string; Whereas, the NGPC met on 11 June 2013 to consider the GAC Beijing advice regarding singular and plural versions of the same string; and Whereas, after careful consideration of the issues, review of the comments raised by the community, the process documents of the expert review panels, and deliberations by the NGPC, the NGPC has determined that no changes to the ABG are needed to address potential consumer confusion specifically resulting from allowing singular and plural versions of the same strings; Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2013.06.25.NG07), the NGPC has determined that no changes are needed to the existing mechanisms in the Applicant Guidebook to address potential consumer confusion resulting from allowing singular and plural versions of the same string. e. IGO Protection No resolution taken. f. AOB No resolution taken.