July 2016 - council - lists.icann.org

Re: [council] FYI and review - Board/GAC call to discuss the GAC Helsinki Communique
by James M. Bladel 21 Jul '16

21 Jul '16

Thanks, Mary. I'll try to listen before our Council call later today. Any idea if there's a transcript coming? J. From: <owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org>> on behalf of Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>> Date: Thursday, July 21, 2016 at 10:41 To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] FYI and review - Board/GAC call to discuss the GAC Helsinki Communique Dear Councilors, Yesterday, the ICANN Board and the GAC held a joint call to discuss the GAC's Helsinki Communique. This is a new initiative and, as far as we can tell, the first time such a meeting has been held with the aim to allow at least some brief follow-up discussion and the opportunity to clarify various points of GAC advice. The call was recorded and the recording has been made available at https://gacweb.icann.org/display/gacweb/Governmental+Advisory+Committee?pre…. In view of the fact that the GNSO's review of the GAC Communique is an item on the Council's agenda today, we thought this information might be helpful even if the call and recording unfortunately took place so close to the Council's meeting time. Thanks and cheers Mary Mary Wong Senior Policy Director Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org<mailto:mary.wong@icann.org> Telephone: +1-603-5744889

1 0

FYI and review - Board/GAC call to discuss the GAC Helsinki Communique
by Mary Wong 21 Jul '16

21 Jul '16

Dear Councilors, Yesterday, the ICANN Board and the GAC held a joint call to discuss the GAC’s Helsinki Communique. This is a new initiative and, as far as we can tell, the first time such a meeting has been held with the aim to allow at least some brief follow-up discussion and the opportunity to clarify various points of GAC advice. The call was recorded and the recording has been made available at https://gacweb.icann.org/display/gacweb/Governmental+Advisory+Committee?pre…. In view of the fact that the GNSO’s review of the GAC Communique is an item on the Council’s agenda today, we thought this information might be helpful even if the call and recording unfortunately took place so close to the Council’s meeting time. Thanks and cheers Mary Mary Wong Senior Policy Director Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org Telephone: +1-603-5744889

1 0

Amended Motion: GNSO CSC Liaison Candidates
by WUKnoben 21 Jul '16

21 Jul '16

Dear Councilors, Please see the attached amended motion for the GNSO CSC Liaison Selection for consideration at the Council meeting on 21 July. As noted in the motion, this process began on 1 June 2016, when ICANN sent a request to the ICANN Supporting Organizations (SOs), Advisory Committees (ACs) and Registry Stakeholder Group (RySG) to initiate their respective organization's processes and appoint candidates to serve as members and liaisons on the CSC. As an ICANN Supporting Organization, the GNSO may appoint a liaison to the CSC, in addition to the two gTLD registry operator members to be selected by the RySG. Liaison candidates are to be confirmed by 22 July 2016, and the final slate of CSC members and liaisons as determined by the ccNSO and GNSO Councils will be sent to ICANN not later than 10 August 2016. On 02 June 2016, the GNSO Council confirmed a Selection Committee -- David Cake, Heather Forrest, Rubens Kuhl, Susan Kawaguchi, and Wolf-Ulrich Knoben -- to evaluate the candidates GNSO liaison. On 20 June 2016, the Selection Committee sent reminders to the GNSO Stakeholder Groups and Constituencies requesting Expressions of Interest from candidates to be submitted by 15 July 2016. Another reminder went out on 11 July. The Selection Committee has completed its evaluation of the single Expression of Interest that it received for the GNSO liaison candidate. We hereby submit the summary of our evaluation of the candidate: James Gannon. Based on our evaluation we recommend James for the role of GNSO Liaison to the CSC. We have amended the motion accordingly. Kind regards, Wolf-Ulrich

5 5

TR: GNSO Council Abstention Notification Form [#209]
by Glen de Saint Géry 21 Jul '16

21 Jul '16

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : jeudi 21 juillet 2016 14:18 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#209] Name of Officer: * Keith Drazek Officer Email Address: * kdrazek(a)verisign.com<mailto:kdrazek@verisign.com> Date Prepared: * Thursday, July 21, 2016 GNSO Organization: * Registries Stakeholder Group Officer Position or Title: * GNSO Councilor Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * I am unable to attend the July 21 GNSO Council meeting and give my proxy to Rubens Kuhl. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * All GNSO council motions and votes on July 21, 2016. Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Saturday, July 23, 2016 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Rubens Kuhl

1 0

FW: GNSO Council Abstention Notification Form [#208]
by Glen de Saint Géry 21 Jul '16

21 Jul '16

Kind regards, FYI Kind regards, Glen From: ICANN [mailto:no-reply@wufoo.com] Sent: jeudi 21 juillet 2016 04:28 To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: GNSO Council Abstention Notification Form [#208] Name of Officer: * Tapani Tarvainen Officer Email Address: * ncsg(a)tapani.tarvainen.info<mailto:ncsg@tapani.tarvainen.info> Date Prepared: * Thursday, July 21, 2016 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * NCSG Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Edward Morris is unable to participate in the council meeting on 21 July 2016. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Marilia Maciel will submit Edward''s vote by proxy for the motions to be approved, and any other matters needing a vote. Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, July 22, 2016 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Marilia Maciel

1 0

FW: GNSO Council Abstention Notification Form [#206]
by Glen de Saint Géry 20 Jul '16

20 Jul '16

FYI Kind regards, Glen From: ICANN [mailto:no-reply@wufoo.com] Sent: mercredi 20 juillet 2016 23:27 To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: GNSO Council Abstention Notification Form [#206] Name of Officer: * Graeme Bunton Officer Email Address: * gbunton(a)tucows.com<mailto:gbunton@tucows.com> Date Prepared: * Monday, July 25, 2016 GNSO Organization: * Registrars Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * We've had TWO(!) councilors have to step down in the past month, and the election process for people to fill those roles has not been completed yet. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * For all votes at the next GNSO meeting: James Bladel is to receive a proxy vote, representing Volker Greiman. Donna Austin is to recieve a proxy vote, representing Jenn Gore Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Monday, August 1, 2016 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * James Bladel

1 0

FW: GNSO Council Abstention Notification Form [#207]
by Glen de Saint Géry 20 Jul '16

20 Jul '16

FYI Kind regards, Glen From: ICANN [mailto:no-reply@wufoo.com] Sent: mercredi 20 juillet 2016 23:42 To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: GNSO Council Abstention Notification Form [#207] Name of Officer: * Graeme Bunton Officer Email Address: * gbunton(a)tucows.com<mailto:gbunton@tucows.com> Date Prepared: * Wednesday, July 20, 2016 GNSO Organization: * Registrars Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * We've had TWO(!) councilors have to step down in the past month, and the election process for people to fill those roles has not been completed yet. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * For all votes at the next GNSO meeting: Donna Austin is to recieve a proxy vote, representing Jenn Gore Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Monday, August 1, 2016 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Donna Austin

1 0

FW: [Soac-infoalert] Tracking gTLD Marketplace Health - ICANN
by James M. Bladel 20 Jul '16

20 Jul '16

Council Colleagues, FYI. Blog Post from Cyrus Namazi (GDD) on the beta gTLD Marketplace Health Index. Thanks- J. From: <soac-infoalert-bounces(a)icann.org<mailto:soac-infoalert-bounces@icann.org>> on behalf of David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>> Date: Wednesday, July 20, 2016 at 2:58 To: "soac-infoalert(a)icann.org<mailto:soac-infoalert@icann.org>" <soac-infoalert(a)icann.org<mailto:soac-infoalert@icann.org>> Cc: Cyrus Namazi <cyrus.namazi(a)icann.org<mailto:cyrus.namazi@icann.org>> Subject: [Soac-infoalert] Tracking gTLD Marketplace Health - ICANN https://www.icann.org/news/blog/tracking-gtld-marketplace-health ICANN Blog Author: Cyrus Namazi Tracking gTLD Marketplace Health Today, ICANN published the gTLD Marketplace Health Index (Beta), which presents statistics and trends related to generic top-level domains (gTLDs). ICANN intends to publish these statistics biannually to track progress against its goal of supporting the evolution of the domain name marketplace. The initial set of metrics was divided into three categories: Robust competition - geographic representation of gTLD registrars and gTLD registry operators, trends in competition among gTLD registrars and gTLD registry operators, expansion in second-level domains (legacy gTLDs, new gTLDs, internationalized gTLDs) Marketplace stability - accreditation and disaccreditation of gTLD registrars Trust - gTLD registrar terminations, WHOIS accuracy rates, and UDRP and URS complaints View the Health Index [PDF, 2.37 MB]. Public Comment Period The gTLD Marketplace Health Index (Beta) includes gTLD data collected by ICANN. There are many other potential sources of data to consider as ICANN and the community work together to develop additional metrics. To this end, we've opened a public comment period on the health index and a set of proposed discussion topics regarding additional metrics is included in the report. I hope that these materials will spark continued community collaboration on the initiative and shape abstract discussions into a more concrete, implementable set of concepts. The deadline for comment is 6 September 2016. Comment Now. Why Create a Marketplace Health Index? ICANN's Strategic Plan, covering fiscal years 2016-2020, charges the Global Domains Division with supporting the evolution of the domain name marketplace to be robust, stable and trusted. We've been consulting with the community for about one year to determine how best to achieve this goal. These consultations led us to create an initial set of metrics for a domain name marketplace health index. ICANN then enlisted Hemant Bhargava, a professor at the University of California-Davis Graduate School of Management, to review the proposed metrics and overall approach from an academic perspective. Read Dr. Bhargava's report [PDF, 351 KB]. Get Involved! We need your feedback! The index will be much more valuable if we build upon this beta version with a more comprehensive set of metrics for the gTLD Marketplace Health Index 1.0. If you're interested in this topic, I encourage you to join the gTLD Marketplace Health Index Advisory Panel, a group of community volunteers convened earlier this year to collaborate with ICANN on the design of the health index. To join, visit https://mm.icann.org/mailman/listinfo/gtldmarketplace and subscribe to the Advisory Panel email list. Following the close of the public comment period, ICANN will begin holding regular meetings with the gTLD Marketplace Health Index Advisory Panel. Our goal will be to finalize a list of additional, refined metrics during this calendar year so that the required data can be collected, analyzed and ready to publish in the gTLD Marketplace Health Index 1.0 in early 2017.

1 0

Reminder Deadline 22 July: Call for Volunteers for GNSO Drafting Team
by Nathalie Peregrine 19 Jul '16

19 Jul '16

Dear GNSO Councilors, Please see the following Call for Volunteers. Kind regards, Nathalie -- Call for Volunteers: GNSO Drafting Team to Further Develop Recommendations to Implement the GNSO’s New Roles and Obligations Under the Revised ICANN Bylaws In Brief Per the motion adopted on 30 June 2016, the Generic Names Supporting Organization (GNSO) Council seeks volunteers for a Drafting Team to further develop recommendations to implement the GNSO’s new roles and obligations under the post-transition ICANN Bylaws. What This Team Will Do The Drafting Team will work with ICANN staff to fully identify all the new or additional rights and responsibilities that the GNSO has under the post-transition Bylaws, including but not limited to participation of the GNSO within the Empowered Community, and to develop new or modified structures and procedures (as necessary) to fully implement these new or additional rights and responsibilities. The Drafting Team shall provide the GNSO Council with an implementation plan, which will have the consensus of the Drafting Team, including any recommendations for needed further changes to ICANN Bylaws and/or GNSO Operating Procedures to enable effective GNSO participation in ICANN activities under the revised ICANN Bylaws, not later than 30 September 2016. As part of the process of its consideration of the implementation plan, intended to be approved by a GNSO supermajority vote, the Council may further request that the Drafting Team work with ICANN staff to develop new, or propose modifications to existing, procedures and structures to implement the revised Bylaws for the GNSO. Any such new, or proposed modifications to existing procedures and structures to implement the revised Bylaws for the GNSO are also intended to be approved by a GNSO supermajority vote. How to Join Volunteers for the Drafting Team will be identified by GNSO Council members. Volunteers should express interests and can demonstrate reasonable knowledge of or experience with the process of revising the ICANN Bylaws or GNSO Operating Procedures. The Drafting Team shall reflect the current composition of the GNSO and as such, the GNSO Council may review the number of volunteers identified by the GNSO Council members. GNSO Councilors are requested to identify volunteers by email to gnso-sec(a)icann.org<mailto:gnso-sec@icann.org> by 22 July 2016. Next steps As noted above, the GNSO Council directed that this call for volunteers be circulated to the GNSO Council and that the volunteers should be identified by GNSO Council members. It is anticipated that the Drafting Team will convene online for the first time in early August 2016. Following that, regular online meetings will be scheduled in accordance with the Drafting Team’s work plan, which it is expected to develop as one of its first tasks. Further information and Preparation For those interested in volunteering for this effort, you are encouraged to review the table at: http://gnso.icann.org/en/drafts/revised-bylaws-notes-comments-procedures-14…. Background On 27 May 2016 the ICANN Board adopted a set of new ICANN Bylaws, as revised on 26 May 2016, that aim to reflect changes needed to implement the IANA Stewardship Transition Proposal and such adoption is contingent on the proposed transition away of remaining United States Government oversight of ICANN. The Generic Names Supporting Organization (GNSO) Council is aware that changes that may need to be made to the GNSO’s current Operating Procedures and related mechanisms and to the ICANN Bylaws in order to give effect to new roles and obligations of the GNSO under the new Bylaws, such as those in this table (http://gnso.icann.org/en/drafts/revised-bylaws-notes-comments-procedures-14…), including but not limited to the GNSO’s participation in the Empowered Community. Per the motion adopted on 30 June 2016, the Generic Names Supporting Organization (GNSO) Council seeks volunteers for a Drafting Team to further develop recommendations to implement the GNSO’s new roles and obligations under the revised ICANN Bylaws.

1 0

Action Items - GNSO Council Public meeting Helsinki
by Glen de Saint Géry 19 Jul '16

19 Jul '16

Dear Councillors, Please find the action items from the GNSO Council Public meeting in Helsinki. Item 4: COUNCIL VOTE – Approval to Permanently Integrate Successful PDP Improvements into the GNSO Policy Development Process Action Item: The GNSO Council directs staff to move ahead with the identified next steps including: integrating the inclusion of the proposed PDP Charter as part of the Preliminary Issue Report; development of draft guidelines for the use and application for face-to-face facilitated PDP WG meetings for Council review and adoption, and; developing a survey to assess the familiarity that the community has with the different newcomer and training tools as well as their perceived usefulness In process Item 5: COUNCIL VOTE - Approval to Form a Drafting Team to Develop an Implementation Plan for New and Additional GNSO Powers and Obligations under the Revised ICANN Bylaws Action Item ICANN staff to issue a call for volunteers for a Drafting Team that will work with ICANN staff to fully identify all the new or additional rights and responsibilities that the GNSO has under the revised Bylaws, including but not limited to participation of the GNSO within the Empowered Community, and to develop new or modified structures and procedures (as necessary) to fully implement these new or additional rights and responsibilities. In process Item 6: COUNCIL VOTE – Temporary Extension of Term of Current GNSO Liaison to the Governmental Advisory Committee Action Item · GNSO Secretariat to inform the GNSO Stakeholder Groups and Constituencies of the extended selection timeline (Nominations Accepted for Candidates - 1 OCT 2016; Council Chairs consider candidates and notify first choice - 20 OCT; Chairs submit motion to Council by 29 OCT for consideration during Council meeting on 8 NOV; GAC Leadership notified of new Liaison by 9 NOV). · Staff to include consideration of a uniform selection process as part of the work associated with implementing the post-transition bylaws In process Item 7: COUNCIL DISCUSSION – Response to ICANN Board Request concerning Expert Working Group Final Report on Internationalized Registration Data Action Items: · Staff to note that GNSO Council will proceed with the Board request. · Staff to draft a letter which will be circulated to the Council list before transmitting to the ICANN Board and to the co-chairs of the Translation and Transliteration PDP Working group and the GNSO PDP on the Next Generation Registration Directory Services to Replace WHOIS Working Group In process Item 8: COMMITTEE UPDATE - Selection of Primary and Alternate Delegates from the GNSO to the New Bylaws-mandated Customer Standing Committee Action item: Schedule precautionary 9 August 2016 Council meeting as vote is required. Completed Item 9: WORKING GROUP PROGRESS REPORT – Activities of the Cross Community Working Group on Internet Governance Action Item: Council be kept apprised of the Cross Community Working Group on Internet Governance Working Group’s (CCWG IG) progress Ongoing Item 10: COUNCIL DISCUSSION – Next Steps relating to Implementation of Recommendations for the GNSO Review Action Item Staff proposed re-drafting the SCI’s charter in order to accommodate the changes. Anne Aikman-Scalese, vice-Chair of the SCI, reminded the Council that the SCI is at their disposal for work projects. In process Please let us know if there anything to be changed or added. Thank you very much. Kind regards, Glen

1 0