March 2017 - council - lists.icann.org

Board Resolution -IRTP-C Follow Up
by James M. Bladel 20 Mar '17

20 Mar '17

Councilors – Please note that the Board adopted the following resolution during its meeting in Copenhagen: “Approval of GNSO Council Request for CEO & Registrar Stakeholder Group to evaluate alternatives for the implementation of Inter-Registrar Transfer Policy Part C (IRTP-C) Whereas, the Generic Names Supporting Organization (GNSO) Council sent a letter<https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf> [PDF, 109 KB] to the ICANN Board on 1 December 2016 ("GNSO Council Letter") regarding implementation concerns with the Inter-Registrar Transfer Policy ("Transfer Policy") – Part C. Whereas, the GNSO Council Letter requested the Board to instruct ICANN Org to work with the Registrar Stakeholder Group and other interested parties to evaluate alternatives for the implementation concerns related to Transfer Policy Part C. Resolved (2017.03.16.05), the Board instructs the ICANN President and CEO, or his designee(s), to work with the Registrar Stakeholder Group and other interested parties to evaluate alternatives for the implementation concerns related to Transfer Policy Part C and to report back to the GNSO Council with the results of the discussion.” https://www.icann.org/resources/board-material/resolutions-2017-03-16-en#1.e I will work with GDD Staff to set up dates & times to meet and discuss, and share all additional information as it becomes available. Thank you, J. ------------------ James Bladel GNSO Chair

1 0

Board Resolution - GNSO Amendment/Modification of protections for Red Cross names
by James M. Bladel 20 Mar '17

20 Mar '17

Councilors – Please be aware of the following resolution was adopted by the ICANN Board during its meeting in Copenhagen (below). I will work with Marika, Mary and the Vice Chairs to develop a draft motion that conforms to our existing PDP Amendment/Modification procedures, and plan to introduce this in time for our next meeting on 20 APR. We have already notified the chair of the previous PDP (Thomas Rickert) that his services may be required again, and he has tentatively agreed to help in this regard. Stay tuned for updates… Thank you, J. ------------------ James Bladel GNSO Chair Protections for Red Cross/Red Crescent Movement Identifiers in gTLDs Whereas, at ICANN57 in Hyderabad the Board proposed that the GAC and the GNSO engage in a facilitated, good faith discussion to attempt to resolve outstanding inconsistencies between GAC public policy advice and GNSO consensus policy recommendations regarding second-level protections in all gTLDs for the identifiers (names and acronyms) of International Governmental Organizations (IGOs) and International Non-Governmental Organizations (INGOs). This includes certain identifiers of the International Red Cross and Red Crescent Movement (referred to as "Scope 2 Identifiers" in the Policy Development Process (PDP) Working Group Final Report on the Protection of IGO and INGO Identifiers in All gTLDs<https://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf> [PDF, 644 KB]). Whereas, the Board acknowledged that any outcome of any dialogue between the affected parties would be conditioned on, and would be reviewed according to, the GAC's and the GNSO's own internal processes. Whereas, representatives from the GAC and the GNSO engaged in a facilitated discussion at ICANN58 in Copenhagen concerning protections for International Red Cross and Red Crescent Movement identifiers (Recommendation 5) in Section 3.1. of the PDP Working Group's Final Report. Whereas, the starting place for the facilitated discussion was a problem statement and briefing materials reviewed by the affected parties (https://community.icann.org/x/hIPRAw). Whereas, during the facilitated discussion, the interested parties discussed the following matters: (1) The GAC's rationale for seeking permanent protections for the identifiers of the International Red Cross and Red Crescent Movement and its respective components (including the 190 National Red Cross and Red Crescent Societies and the Movement's two international organizations – the International Committee of the Red Cross and the International Federation of Red Cross and Red Crescent Societies), is grounded in the protections of the designations "Red Cross", "Red Crescent", "Red Lion and Sun", and "Red Crystal" under the laws in force in multiple national jurisdictions; and the global public policy considerations in the protections of the identifiers of the respective Red Cross and Red Crescent organizations from forms of misuse in the domain name system, including from fraud and embezzlement in times of humanitarian crises. (2) The list of names of the National Red Cross and Red Crescent National Societies submitted for protection is finite and comprises the names of the 190 National Societies recognized within the International Red Cross and Red Crescent Movement – the Movement – both in English and in each National Society's official national language(s) and script(s). The number of National Societies (see the official list of National Societies at http://www.ifrc.org/Docs/ExcelExport/NS_Directory.pdf [PDF, 657 KB]) is limited and only subject to increase further to the future recognition within the Movement of new National Societies (a development that remains subject to a strict process and to strict conditions defined in the Statutes of the Movement). In accordance with the Fundamental Principle of Unity, there can only be one National Red Cross, Red Crescent or Red Crystal Society in any one country. The National Societies' names submitted for protection in the DNS include the official names of the 190 National Societies recognized within the Movement, as well as where these are distinct, their usual names. (3) The respective Red Cross and Red Crescent organizations should preserve the ability to register their names should they require to do so, and there are no other legitimate uses for these names. Whereas, the participants in the facilitated discussion took note that, following the completion of the GNSO PDP, the GAC provided additional guidance as to the specific International Red Cross and Red Crescent Movement identifiers for which protections were being sought (https://gacweb.icann.org/download/attachments/28278854/Final%20Communique%2…, 145 KB]). Whereas, the GAC issued advice to the ICANN Board in the Copenhagen Communique<https://gacweb.icann.org/display/gacweb/Governmental+Advisory+Committee?pre…>[PDF, 190 KB] to "request the GNSO without delay to re-examine its 2013 recommendations pertaining to the protections of Red Cross and Red Crescent names and identifiers (defined as 'Scope 2' names in the GNSO process) which were inconsistent with GAC Advice." Whereas, the Board has considered the outputs from the facilitated discussion and the GAC's advice in the context of ICANN's mission and ICANN's commitment to carry out its mission in conformity with relevant principles of international law and international conventions and applicable local law, as expressed in ICANN's Bylaws. Resolved (2017.03.16.13), the Board requests that the GNSO initiate its process for Amendments or Modifications of Approved Policies, as described in Section 16 of the GNSO PDP Manual, to consider amending Recommendation 5 in Section 3.1. of the PDP Working Group Final Report, as follows: (1) The full names of the 190 Red Cross National Societies and the full names of the International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies are to be placed into Specification 5 of the Base gTLD Registry Agreement, with an exception procedure to be created for cases where the relevant Red Cross Red Crescent Movement organization wishes to apply for their protected string at the second level; (2) In placing the specified identifiers into Specification 5 of the Base gTLD Registry Agreement, this should apply to an exact match of the full name of the relevant National Society recognized by the International Red Cross and Red Crescent Movement (in English and the official languages of its state of origin), the full names International Committee of the Red Cross and International Federation of Red Cross and Red Crescent Societies (in the six official United Nations languages) and a defined limited set of variations of these names; and (3) In considering the Board's request, the Council is requested to duly take into account these factors and the public policy advice to reserve the finite list of names of the Red Cross and Red Crescent National Societies, as recognized within the International Red Cross and Red Crescent Movement, in all gTLDs. Resolved (2017.03.16.14), the Board thanks Dr. Bruce Tonkin for facilitating the GAC-GNSO discussions on this topic, and thanks the GAC and the GNSO representatives who participated in the facilitated discussions for their good faith participation and willingness to work toward a reconciliation of the matter. https://www.icann.org/resources/board-material/resolutions-2017-03-16-en#2.…

1 0

FW: [Soac-infoalert] ICANN Board to NomCom Letter - Important Skills for Board Members
by James M. Bladel 16 Mar '17

16 Mar '17

Councilors – Apologies for not sending this earlier (received while in transit to CPH), but please see attached for a letter from Steve Crocker to the NomCom regarding qualification criteria for Board appointments. Thank you, J. From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Friday, March 10, 2017 at 8:41 Subject: [Soac-infoalert] ICANN Board to NomCom Letter - Important Skills for Board Members Dear Community Leaders. Please find attached an ICANN Board to NomCom Letter on Important Skills for Board Members. Best regards. David

1 0

FW: [Soac-infoalert] Fwd: GAC Communiqué – Copenhagen, Denmark
by James M. Bladel 16 Mar '17

16 Mar '17

Councilors – GAC Copenhagen Communique below. Let’s discuss the formation of our response team during today’s Wrap Up. Thanks— J. From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Thursday, March 16, 2017 at 6:25 Subject: [Soac-infoalert] Fwd: GAC Communiqué – Copenhagen, Denmark GAC Communiqué – Copenhagen, Denmark The Governmental Advisory Committee (GAC) of the Internet Corporation for Assigned Names and Numbers (ICANN) met in Copenhagen, Denmark from 11 to 16 March 2017. 59 GAC Members and 8 Observers attended the meeting. The GAC meeting was conducted as part of ICANN 58. All GAC plenary and Working Group sessions were conducted as open meetings. https://gacweb.icann.org/download/attachments/27132037/GAC%20ICANN%2058%20C…

3 2

GNSO ICANN58 Wrap Up Interview
by Ariel Liang 16 Mar '17

16 Mar '17

Dear Councilors, Happy last day of ICANN58! This is to let you know that the GNSO ICANN58 Wrap Up Interview is now live: https://youtu.be/Ouz3sjRyTQo. It is also featured in today’s newsletter http://campaign.r20.constantcontact.com/render?m=1118638566701&ca=ca16e221-…. Thanks to James, Donna, and Heather for doing the interview! Have a great day! Best regards, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Re: [council] FW: [Soac-infoalert] Fwd: GAC Communiqué – Copenhagen, Denmark
by Marika Konings 16 Mar '17

16 Mar '17

Attached you will find the template for the GNSO Review of the GAC Communique which has been filled out with the CPH Communique information. Best regards, Marika From: <council-bounces(a)gnso.icann.org> on behalf of "James M. Bladel" <jbladel(a)godaddy.com> Date: Thursday, March 16, 2017 at 08:02 To: GNSO Council List <council(a)gnso.icann.org> Subject: [council] FW: [Soac-infoalert] Fwd: GAC Communiqué – Copenhagen, Denmark Councilors – GAC Copenhagen Communique below. Let’s discuss the formation of our response team during today’s Wrap Up. Thanks— J. From: <soac-infoalert-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Thursday, March 16, 2017 at 6:25 Subject: [Soac-infoalert] Fwd: GAC Communiqué – Copenhagen, Denmark GAC Communiqué – Copenhagen, Denmark The Governmental Advisory Committee (GAC) of the Internet Corporation for Assigned Names and Numbers (ICANN) met in Copenhagen, Denmark from 11 to 16 March 2017. 59 GAC Members and 8 Observers attended the meeting. The GAC meeting was conducted as part of ICANN 58. All GAC plenary and Working Group sessions were conducted as open meetings. https://gacweb.icann.org/download/attachments/27132037/GAC%20ICANN%2058%20C…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gacweb.icann.org_downl…>

1 0

Please review: GNSO Council motion and statement 15 March 2017
by Nathalie Peregrine 15 Mar '17

15 Mar '17

Dear Councilors, Ahead of the official minutes, the following resolution was passed by the GNSO Council at its meeting on Wednesday, 15 March 2017. Please review and I will then circulate to the Council list and post to the website<https://gnso.icann.org/en/council/resolutions>. Please also notice the Glen de Saint Gery Statement which was adopted during this same GNSO Council meeting and which will also be posted on the website<https://gnso.icann.org/en/council/correspondence>. Motion – Preliminary Adoption of GNSO Standing Selection Committee (SSC) Charter Proposed: James Bladel Seconded: Susan Kawaguchi, Ed Morris Whereas, 1. The GNSO Council expressed the desire to establish a GNSO Standing Selection Committee to assist with the selection of GNSO representatives to future Review Teams, including for the various reviews mandated by the ICANN Bylaws, and other ICANN structures for which the GNSO will need to appoint, nominate or endorse candidates 2. A small team of Council members developed a set of criteria intended to serve as the basis for a uniform process that would be used by the GNSO Standing Selection Committee to make future selections as required 3. These criteria have been captured in GNSO Standing Selection Committee (SSC) Charter (see https://gnso.icann.org/en/drafts/draft-standing-selection-committee-15mar17…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>) 4. The Council reviewed the charter and agreed that as this is a new entity and approach, it would be desirable to test the process and criteria outlined in the charter to assess whether it is fit-for-purpose. To that end, it is proposed that: 1) the charter be adopted on an interim basis, 2) SSC be formed in accordance with the charter, 3) SSC to apply the charter for a minimum carry out 2 selection / nomination processes, 4) SSC to conduct a review of the selection / nomination process and suggest changes to the Charter if appropriate, 5) Confirm the GNSO SSC Charter as is, or, as modified based on the review. Resolved, 1. The GNSO Council adopts the GNSO Standing Selection Committee (SSC) Charter on an interim basis (see https://gnso.icann.org/en/drafts/draft-standing-selection-committee-15mar17…)<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> and instructs the GNSO Secretariat to launch a call for volunteers per the membership criteria outlined in the SSC Charter as soon as possible with a view to having each member identified by their appointing SG/C by 27 March 2017 and the establishment of the SSC no later than 31 March 2017. 2. The GNSO Council tasks the SSC to carry out the review and selection of GNSO endorsed candidates for the Registration Directory Service Review Team for Council consideration at the latest by its 20 April 2017 meeting. 3. The GNSO Council tasks the SSC to develop the criteria and the process for the selection of the GNSO Representative to the Empowered Community for GNSO Council consideration by its June 2017 meeting, and following the approval by the GNSO Council, carry out the selection process. 4. Following the completion of two selection processes, the GNSO Council requests the SSC to report back to the GNSO Council with its assessment of whether the charter provides sufficient guidance and flexibility to carry out its work, and/or whether any modifications should be considered. Acknowledging that this is a work in progress, the GNSO Council will review this assessment as well as whether any modifications should be considered, as well as any inconsistencies that may need to be addressed as a result of the finalization of the work of the Bylaws Drafting Team. 5. The GNSO Council thanks the small group of volunteers, Susan Kawaguchi, Ed Morris, Valerie Tan and the GNSO Council leadership team, for its work on the charter. Voting results<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> Statement Adopted by the GNSO Council: Glen de Saint Géry Proposed: James Bladel Seconded: All members of the GNSO Council Whereas, Glen de Saint Géry has been involved in the ICANN world before there was an ICANN, and before anybody really understood what ICANN was. Whereas Glen was instrumental in the development of the practices and procedures that have supported the operation and administration of the GNSO since its inception as the DNSO, and which have been adopted beyond the GNSO to support other ICANN supporting organisations and advisory committees. Whereas Glen has been responsible for developing and mentoring not only ICANN staff performing support roles for the GNSO, but also incoming Councilors. Whereas Glen has survived seven GNSO Chairs and too many GNSO Councilors to count. Whereas Glen is the living embodiment of ICANN’s core values of openness, transparency and fairness, having performed her duties without prejudice and with diplomacy, style, grace, humour and warmth that is second to none. Resolved The GNSO Council, from the bottom of our hearts, and on behalf of all of the GNSO Councils that have come before us, sincerely thank Glen for her dedication, warmth and love in supporting the GNSO and the work that we do on behalf of the global internet community. In recognition of the significant contribution Glen has made to ICANN over the past 14 years, the GNSO Council recognizes that for the purposes of ICANN58 Copenhagen, the GNSO be known as the Glen de Saint Géry Names Supporting Organisation Thank you very much for your time and feedback. Nathalie

1 0

FW: [community-finance] FY18 Operating Plan and Budget - Published for Public Comment
by James M. Bladel 15 Mar '17

15 Mar '17

Councilors – Related to Ed’s item of AOB in our meeting today, ICANN has published a corrected version of the FY18 budget, and is open to scheduling a call/webinar to discuss questions and concerns. I think it would make sense for the entire GNSO to schedule a session, rather than holding separate calls for SGs and Cs. Let’s discuss tomorrow in our wrap-up. Thanks— J. From: <community-finance-bounces(a)icann.org> on behalf of Jessica Castillo <jessica.castillo(a)icann.org> Date: Wednesday, March 15, 2017 at 14:59 Subject: [community-finance] FY18 Operating Plan and Budget - Published for Public Comment Dear ICANN Community, ICANN’s Draft FY18 Operating Plan and Budget, and Five-Year Operating Plan Update was published for public comment on 8 March 2017. Please note that on 13 March 2017, revised documents with minor corrections were published along with a summary of the changes. You may find the documents and full announcement on the public comment website at https://www.icann.org/public-comments/fy18-budget-2017-03-08-en . We would like to invite you to schedule a call to discuss your comments on these documents, should it be needed. The calls would be held one to two weeks after public comment closes 28 April 2017. To schedule a placeholder meeting with the Planning Team, please contact me by 31 March 2017. Additionally, if you were unable to attend our Budget Working Group session yesterday evening, you may find the recording online using the link below. Budget Working Group Recording https://participate.icann.org/p7ouanp9ewz/?launcher=false&fcsContent=true&p… (On behalf of the Planning Team – Becky Nash, Taryn Presley, Leo Vegoda, Kirsten Wattson) Jessica Castillo Operations & Project Coordinator ICANN | Human Resources & Finance Departments

1 0

Updated SSC Charter for your review
by Marika Konings 15 Mar '17

15 Mar '17

Dear All, Per today’s discussion, please find attached for your review the updated SSC Charter. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

2 2

Update: Draft Motion on
by James M. Bladel 14 Mar '17

14 Mar '17

Colleagues - Thank you for your work this evening. To reflect Heather's proposals, I have modified the language of the draft motion Resolved 4 to read: 4. Following the completion of two selection processes , the GNSO Council requests the SSC to report back to the GNSO Council with its assessment of whether the charter provides sufficient guidance and flexibility to carry out its work, and/or whether any modifications should be considered. Acknowledging that this is a work in progress, the GNSO Council will review this assessment as well as whether any modifications should be considered, as well as any inconsistencies that may need to be addressed as a result of the finalization of the work of the Bylaws Drafting Team. The original text can be found at: https://community.icann.org/display/gnsocouncilmeetings/Motions+15+March+20… Thanks-- J.

1 1