July 2019 - council - lists.icann.org

Re: [council] Final Proposed Agenda GNSO Council Meeting - 18 July 2019 at 21:00 UTC
by Steve Chan 16 Jul '19

16 Jul '19

Dear Councilors, In relation to agenda item 6, in order to make the conversation with the PDP leadership as productive as possible, Councilors may want to review the “asks” of Council raised during the pre-ICANN65 webinar [gnso.icann.org] (see pages 7, 13, and 20) and be prepared to provide response as appropriate. Best, Steve From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Tuesday, July 9, 2019 at 1:25 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Final Proposed Agenda GNSO Council Meeting - 18 July 2019 at 21:00 UTC Dear all, Please below find the final proposed agenda for the GNSO Council Meeting on 18 July 2019 at 21:00 UTC Final GNSO Council Agenda 18 July 2019 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/haOjBg This agenda was established according to the GNSO Operating Procedures [gnso.icann.org] v3.3, updated on 30 January 2018 For convenience: An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting held at 21:00 UTC Coordinated Universal Time: 21:00 UTC: https://tinyurl.com/y35nu9lu [tinyurl.com] 14:00 Los Angeles; 17:00 Washington; 21:00 London; (+1 day) 02:00 Islamabad; 06:00 Tokyo; 07:00 Melbourne GNSO Council Meeting Audio Cast To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream02 Listen in application such as iTunes: http://stream.icann.org:8000/stream02.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1: Administrative Matters (10 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes [gnso.icann.org] of the extraordinary GNSO Council meeting on the 28th May 2019 were posted on the 13th June 2019 Minutes [link to be added when available] of the GNSO Council meeting on the 26 June 2019 will be posted on the 13 July 2019 Item 2: Opening Remarks / Review of Projects & Action List (15 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]and Action Item List Item 3: Consent Agenda (10 minutes) Motion to adopt the GNSO Council response [Link to be added when available] to the GAC Marrakech Communique [gac.icann.org] Item 4: COUNCIL DISCUSSION - GNSO Council Letter on Status of Consultation in Relation to Non-Adopted EPDP Phase 1 Parts of Recommendations (purpose 2 and recommendation #12) (15 minutes) On 15 May, the ICANN Board informed [gnso.icann.org] the GNSO Council of the Board’s action in relation to the GNSO’s EPDP Phase 1policy recommendations. The Board did not adopt two of the recommendations in full, where the Board has identified that portions of those recommendations are not in the best interests of the ICANN Community or ICANN and is initiating the consultation process between the Board and the GNSO Council. This concerns recommendation #1, purpose 2 and recommendation #12, deletion of data in the Organization field. As required under the ICANN Bylaws at Annex A-1,Section 6.b, a Board Statement is attached as Annex A to the letter, articulating the reasons for the Board’s non-adoption of these two items. As per the Bylaw requirements (Annex A-1, Section 6.c), “the Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement.” During the Council’s Extraordinary Meeting on 28 May 2019, it reviewed the Board Statement and conducted a lengthy discussion on the best path forward. On 30 May 2019, Keith Drazek, the GNSO Chair provided an update to the EPDP Team on the expected next steps in relation to the ICANN Board’s action on Phase 1 recommendations and requested that the EPDP Team provide input to identify any questions, comments or concerns in relation to ICANN Board’s action on the EPDP Phase 1 Recommendations. Subsequently, on 9 June 2019, Janis Karklins, Chair of the EPDP, informed the GNSO Chair of the following preliminary input noting that there was not sufficient time to formalize and agree on an EPDP Team response: “• In relation to purpose 2, there is a general understanding for why the Board decided to not adopt this purpose and the EPDP Team confirms that it considers it firmly within its scope for phase 2 to further review this purpose in the context of the System for Standardized Access / Disclosure (SSAD); • For recommendation #12, some additional context has been provided that may help explain the thinking behind the EPDP Team’s original recommendation. However, there is no agreement at this stage on whether or not the Board’s non-adoption should be supported.” During the Council’s June 2019 meeting, it continued to consider the next steps, taking into account a discussion with the ICANN Board at ICANN65. The reasoning and intent of the deletion part of recommendation #12 was explained to the Board, as well as the intent of purpose 2 and it was agreed that a letter should be drafted and sent to the ICANN Board as well as the EPDP Team to provide an update on the current thinking of the GNSO Council and likely next steps. Here, the Council will review the draft letter to be sent to the ICANN Board and the EPDP Team. See also Annex A-1, Section 6. Board Approval Process below for further details. Section 6. Board Approval Processes The Board will meet to discuss the EPDP recommendation(s) as soon as feasible, but preferably not later than the second meeting after receipt of the Recommendations Report from the Staff Manager. Board deliberation on the EPDP Recommendations contained within the Recommendations Report shall proceed as follows: a. Any EPDP Recommendations approved by a GNSO Supermajority Vote shall be adopted by the Board unless, by a vote of more than two-thirds (2/3) of the Board, the Board determines that such policy is not in the best interests of the ICANN community or ICANN. If the GNSO Council recommendation was approved by less than a GNSO Supermajority Vote, a majority vote of the Board will be sufficient to determine that such policy is not in the best interests of the ICANN community or ICANN. b. In the event that the Board determines, in accordance with paragraph a above, that the proposed EPDP Recommendations are not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council. c. The Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement. The Board shall determine the method (e.g., by teleconference, email, or otherwise) by which the Council and Board will discuss the Board Statement. At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board, including an explanation for the then-current recommendation. In the event that the Council is able to reach a GNSO Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than two-thirds (2/3) of the Board determines that such guidance is not in the interests of the ICANN community or ICANN. For any Supplemental Recommendation approved by less than a GNSO Supermajority Vote, a majority vote of the Board shall be sufficient to determine that the guidance in the Supplemental Recommendation is not in the best interest of the ICANN community or ICANN. 4.1 – Introduction of topic (Council leadership) 4.2 – Council discussion 4.3 – Next steps Item 5: COUNCIL DISCUSSION – ICANN Org’s Request for Clarification on Data Accuracy and Phase-2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data (15 minutes) On 21 June 2019, the GNSO Council received a letter [gnso.icann.org] from ICANN Org, which was seeking a better understanding of the Expedited Policy Development Process (EPDP) Team’s plans “to consider the subject of "data accuracy" as it relates to gTLD registration data and related services, such as the WHOIS Accuracy Reporting System (ARS) [whois.icann.org].” Further, “ICANN org notes that footnote #6 on page 7 of the EPDP Phase 1 Final Report states: “The topic of accuracy as related to GDPR compliance is expected to be considered further as well as the WHOIS Accuracy Reporting System.” However, it is not clear who would consider this topic and when. Therefore, ICANN org seeks the GNSO Council’s clarification on whether the Phase 2 EPDP Team will be considering the subject of data accuracy, including projects that utilize gTLD registration data, such as WHOIS ARS.” On 8 July 2019, GNSO Council Liaison to the EPDP Team, Rafik Dammak forwarded the letter to the EPDP Team seeking their input to better inform the Council in its preparation for a response to ICANN org. Here, the Council will take into consideration the questions and concerns from ICANN Org and input from the EPDP Team (if any) and seek to agree in principle on how to respond. 5.1 – Introduction of topic (Council leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION – PDP Updates on ICANN65 Activity (30 minutes) The GNSO Council, as the manager of the GNSO PDP, is seeking to ensure that it is staying current on the operations of the PDPs currently underway and to the extent that any assistance is needed from the Council, that it is considered in a timely manner. With ICANN65 recently concluded and all of the PDPs (1. PDP Review of All Rights Protection Mechanisms in All gTLDs; 2. PDP New gTLD Subsequent Procedures; and 3. Temporary Specification for gTLD Registration Data Expedited Policy Development Process Team, Phase 2) having held a number of sessions during the course of the meeting, the Council is seeking an update on each of the groups’ activities at ICANN65. Here, the Council, subject to availability, will receive an update from the respective leadership teams of the PDPs on the activities conducted at ICANN65. In addition, the Council and PDP leadership teams will have an opportunity to have a dialogue on the “asks” of Council raised during the pre-ICANN65 webinar [gnso.icann.org] (see pages 7, 13, and 20). 6.1 – Introduction of topic (PDP Leadership Teams) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - Evolution of the Multistakeholder Model of Governance (15 minutes) At ICANN63, the ICANN Board asked the community, “How should ICANN’s multistakeholder model of governance and policy development process evolve to balance the increasing need for inclusivity, accountability and transparency, with the imperative of getting our work done and our policies developed in a more effective and timely manner, and with the efficient utilization of ICANN’s resources?” Based on community input to that question, as well as other input that resulted in the inclusion of Strategic Objective 2 in the Draft ICANN Strategic Plan for FY 2021-2025, “Improve the effectiveness of ICANN’s multistakeholder model of governance,” the ICANN Board organized a session at ICANN64, led by Brian Cute as an independent facilitator, to continue the conversation with the community. At ICANN65, the dialogue was continued, where the identified issues were consolidated and the work pivoted to developing a work plan. Here, recognizing the similar objectives within the Council’s own PDP 3.0, the Council would like to avoid duplicative or conflicting work, yet also seek to work together where synergies exist. 7.1 – Introduction of topic (Council leadership, Brian Cute) 7.2 – Council discussion 7.3 – Next steps Item 8: ANY OTHER BUSINESS (5 minutes) 8.1 - Public comment on the Fundamental Bylaw amendment [icann.org] and expected next steps for the GNSO as a member of the Empowered Community. 8.2 - Opportunity to ask any follow up questions after the webinar [icann.zoom.us] on the Nominating Committee (NomCom) Review Implementation Planning Team (IPT). _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11 [icann.org]. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… [gnso.icann.org] References for Coordinated Universal Time of 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRT) UTC-3 18:00 London, United Kingdom (GMT) UTC+1 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Paris, France (CET) UTC+2 23:00 Moscow, Russia (MSK) UTC +3 (+1 day) 00:00 Islamabad, Pakistan (PKT) UTC+5 (+1 day) 02:00 Singapore (SGT) UTC+8 (+1 day) 05:00 Tokyo, Japan (JST) UTC+9 (+1 day) 06:00 Melbourne, Australia (AEDT) UTC+11 (+1 day) 07:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 27 of October 2019, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 03 of November 2019 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com] and https://tinyurl.com/y35nu9lu [tinyurl.com]

1 0

FW: Notification of ICANN RFP to select a contractor to perform a study as part of the Name Collision Analysis Project (NCAP)
by Drazek, Keith 16 Jul '19

16 Jul '19

FYI, please see below for a communication from ICANN concerning the NCAP work and the associated RFP. The RFP deadline is set to be extended and ICANN is looking for interested/qualified respondents. Best, Keith From: Matt Larson <matt.larson(a)icann.org> Sent: Tuesday, July 16, 2019 8:13 PM To: Drazek, Keith <kdrazek(a)verisign.com>; Donna.Austin(a)neustar.biz Subject: [EXTERNAL] Notification of ICANN RFP to select a contractor to perform a study as part of the Name Collision Analysis Project (NCAP) Hi, Keith, Donna. David Conrad suggested I reach out to you in your roles as GNSO Council Chair and RySG Chair, respectively. You are probably aware of the SSAC Name Collision Analysis Project (NCAP), undertaken at the request of the Board in late 2017. Briefly, SSAC designed three large studies to answer the Board's questions related to name collisions, but being an all-volunteer group, they are not well suited to do the work. The ICANN org, specifically OCTO, has been tasked to do the studies, but we don't have sufficient resources, either, so we are outsourcing the work. Just this week we just started an RFP process to select a contractor to perform the first of the three studies. It is conceivable that this work on name collisions might somehow affect the next round of new gTLDs (though I must stress that I do not have any direct knowledge to that effect). To the extent that might be the case, it is reasonable to presume that your constituencies would have an interest that the work be done well and in a timely fashion. So far the response to the RFP has been disappointing in terms of the number of firms expressing an intention to bid, despite our letting several organizations we believe might be interested or qualified know about the RFP as soon as it opened. I'm writing to ask if you would be willing to please publicize the RFP to your constituencies. The greater the awareness of the RFP, hopefully the more qualified bids we will receive. More information is available at https://www.icann.org/news/announcement-2019-07-09-en, including a link to a project overview document (https://www.icann.org/en/system/files/files/rfp-ncap-study-1-09jul19-en.pdf) that explains the requirements of the study. As explained in the announcement linked to above, anyone interested in bidding should email NCAP-Study1-RFP(a)icann.org<mailto:NCAP-Study1-RFP@icann.org> to express interest and receive further instructions. Finally, I should add that we intend to extend the RFP timeline to allow more time for responses, so no one should be dissuaded by the apparent lack of time to respond. I would be grateful for your passing on this information, as appropriate, and I would also be happy to receive any names of potential bidders you think might be interested and qualified to do the work so I could give them more information about the RFP. Thanks, Matt -- Matt Larson, VP of Research ICANN Office of the CTO

1 0

GAC communique
by Johan Helsingius 15 Jul '19

15 Jul '19

The GAC communique is now online at https://gac.icann.org/contentMigrated/icann65-marrakech-communique In my view, nothing that we really need to react on. Julf

4 9

FYI: 15 July Update
by Terri Agnew 15 Jul '19

15 Jul '19

FYI: [Image removed by sender.] Monday, 15 July 2019 ICANN Community Leadership Digest [Image removed by sender.] This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. TABLE OF CONTENTS Information Sharing · NEW: Post-ICANN65 Policy Report Now Available · REMINDER: NextGen@ICANN Survey · REMINDER: Update and Information on IRP IOT Re-Composition · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Public Comment · CLOSING TODAY: Process Proposal for Streamlining Organizational Reviews · CLOSING THIS WEEK: Study on Technical Use of Root Zone Label Generation Rules · CLOSING NEXT WEEK: Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review · CLOSING NEXT WEEK: Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership · CLOSING NEXT WEEK: Proposed IANA SLAs for Publishing LGRs/IDN Tables · Draft Final Report of the Second Country Code Names Supporting Organization Review · Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan · Evolving the Governance of the Root Server System · Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Information Sharing NEW: Post-ICANN65 Policy Report Now Available Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The Post-ICANN65 Policy Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> written by the ICANN Policy Development Support team captures decisions and outcomes from the Supporting Organizations and Advisory Committees. While the report provides an overview of activities held during the Policy Forum, it also looks ahead at the work to come in the upcoming months. Included in the report are various resources to support the ongoing, sustained engagement of the community on several important issues. REMINDER: NextGen@ICANN Survey Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The ICANN organization is initiating a community consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> to identify improvement opportunities for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. The review will start with gathering community input via a survey about several aspects of the NextGen@ICANN Program, including its purpose, goals, processes, and synergies with the ICANN academic community. The survey [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> (PDF with background at the beginning and questionnaire questions at the end) is intended for all ICANN community groups; individuals are encouraged to work with their relevant Supporting Organizations, Advisory Committees, stakeholder groups, and constituencies. Responses are due Monday, 9 September. Based on the input received from the survey, ICANN org will draft a proposal for program improvements that will be published for Public Comment. Once all feedback is received, ICANN org will prepare the final proposal for program improvements. Sally Costerton's blog about the NextGen@ICANN Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> REMINDER: Update and Information on IRP IOT Re-Composition Executive: John Jeffrey, General Counsel FOR: All SO/AC Chairs INFORMATION SHARING As the ICANN Board committee with oversight responsibility of ICANN's accountability mechanisms, the Board Accountability Mechanisms Committee (BAMC) considers the work of the [Independent Review Process (IRP)] Implementation Oversight Team (IOT) to be paramount to ICANN's accountability...we seek your help in finding additional volunteers within the community that meet the qualifications identified in the attached letter, outlining skills and experience requirements, to join the IOT and help to conclude its work in a timely fashion. Read more [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Executive: Cyrus Namazi, Senior Vice President, Global Domains Division FOR: All Community Leaders INFORMATION SHARING In December 2015, the GNSO initiated a Policy Development Process (PDP) to determine if changes to existing policy recommendations are needed before the next round of gTLDs. The PDP Working Group expects to publish its final report with its recommendations by December 2019. These recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. In the course of our preparatory work toward the planning and implementation of the new policy, ICANN org has compiled a number of fundamental operationally focused assumptions to help with the preliminary planning and operational readiness of the organization. These assumptions have been shared with the ICANN Board, and now ICANN org would like to share them with relevant parts of the community. Public Comment Process Proposal for Streamlining Organizational Reviews [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING TODAY: Monday, 15 July 2019 Study on Technical Use of Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING THIS WEEK: Friday, 19 July Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING NEXT WEEK: Friday, 26 July 2019 Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING NEXT WEEK: Friday, 26 July 2019 Proposed IANA SLAs for Publishing LGRs/IDN Tables [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING NEXT WEEK: Friday, 26 July 2019 Draft Final Report of the Second Country Code Names Supporting Organization Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: 4 August 2019 Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 5 August 2019 Evolving the Governance of the Root Server System [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 9 August 2019 Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 12 August 2019 Volume 1, Issue 32 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 18 July 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Image removed by sender. Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

Re: [council] Message regarding CCT-RT recommendations
by Emily Barabas 15 Jul '19

15 Jul '19

Sent on behalf of the GNSO Leadership Team: Dear Larisa, Thank you for your message notifying the GNSO Council of the CCT-RT recommendations that the ICANN Board resolved to pass through to the GNSO for consideration. The GNSO Council is in the process of reviewing these recommendations and will follow up with the Board once it has determined whether the GNSO will take on any additional work in response to the recommendations. If you have any questions or concerns, please do not hesitate to contact us. Kind regards, Keith Drazek, Rafik Dammak, and Pam Little GNSO Leadership Team From: council <council-bounces(a)gnso.icann.org> on behalf of Mary Wong <mary.wong(a)icann.org> Date: Monday, 10 June 2019 at 08:43 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Message regarding CCT-RT recommendations Dear Councilors, I am forwarding the message below on behalf of Larisa Gurnick, Vice-President in ICANN’s Multi-stakeholder Strategy & Strategic Initiatives (MSSI) department. You may recall that the Competition, Consumer Protection & Consumer Trust Review Team’s (CCT-RT) final recommendations included several that were directed at the GNSO Council. This notification should provide you with additional information and context for the ICANN Board’s action in respect of those recommendations. Dear Members of the GNSO Council, The purpose of this note is to highlight the Board resolution passed on 1 March 2019 - see https://www.icann.org/resources/board-material/resolutions-2019-03-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> - that calls for a set of Competition, Consumer Trust, and Consumer Choice Review Team (CCT-RT) Final Recommendations to be passed through to community groups. As articulated in the Board resolution, “recognizing that the Board has the obligation and responsibility to balance the work of ICANN in order to preserve the ability for ICANN org to serve its Mission and the public interest, the Board decided on three categories of action”: * Accepting recommendations, subject to costing and implementation considerations; * Placing recommendations (in whole or in part) in "Pending" status, directing ICANN org to perform specific actions to enable the Board to take further actions; * Passing recommendations (in whole or in part) to community groups the CCT-RT identified for their consideration. The Board noted fourteen such recommendations (9, 10, 12, 16, 19, 20, 25, 27, 28, 29, 32, 33, 34, 35). We invite you to refer to pages 1-4 of the scorecard https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scor… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> which compile pass-through recommendations, including the groups they are addressed to. Accordingly, ICANN org wishes to notify you of the recommendations the ICANN Board resolved to pass through to you, in whole or in part, for your consideration: * Recommendation 10. * Recommendation 16 (in part) Note: this recommendation was also passed through to the New gTLD Subsequent Procedures PDP WG, Registries Stakeholder Group, Registrar Stakeholder Group, Generic Names Supporting Organization, Second Security, Stability & Resiliency of DNS Review Team as suggested by the CCT-RT. In the scorecard, the Board noted that “it is not accepting the policy directives that may be inherent here but rather, passes on such elements of the recommendation to the relevant community groups to consider”. * Recommendation 27. * Recommendation 28. * Recommendation 29. Note: this recommendation was also passed through to the New gTLD Subsequent Procedures PDP WG, as suggested by the CCT-RT. To inform work relating to recommendations 29 and 30, the ICANN Board suggested that the New gTLD Subsequent Procedures PDP WG could take on, “should they choose to do so, defining the term ‘Global South’ or agreeing on another term to describe underserved or underrepresented regions or stakeholders in coordination with ICANN org”. We would like to highlight the following language of the Board resolution: “in passing these recommendations through, the Board is neither accepting, nor rejecting the recommendations. […] Passing recommendations through to community groups is not a directive that the groups identified should formally address any of the issues within those recommendations. It is within the purview of each group to identify whether work will be taken on and the topics that the group will address”. As indicated in the resolution, the Board encourages community groups to be “mindful of any interdependencies with ongoing work and discussions”. Additionally, the Board suggests “to the referenced community groups that the CCT-RT's proposed priority levels be taken into account as the groups decide whether, how and when to address the CCT-RT recommendations that are being passed through […]”. Additionally, we would like to flag the Board suggestion that for transparency purposes, “it would be helpful to have records or reporting made available to the ICANN community on how the community group considered the items coming out of the CCT-RT. The Board encourages any level of reporting that the groups are able to provide as the ICANN org and Board track action on the CCT-RT's recommendations”. Please consider providing updates on your progress in addressing (as appropriate) these recommendations, to be included with ICANN org’s reporting. Background The Competition, Consumer Trust, and Consumer Choice Review Team (CCT-RT) released its Final Report on 8 September 2018 – see https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>. The CCT-RT Final Report contains 35 recommendations and is the culmination of nearly three years of work, reviewing how the expansion of top-level domain names impacted competition, consumer trust and choice. For more information on the CCT Review and Specific Reviews, please read https://www.icann.org/resources/pages/governance/bylaws-en#article4.6 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. The ICANN Board took action on each of the 35 recommendations produced by the CCT-RT - see https://www.icann.org/resources/board-material/resolutions-2019-03-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> - on 1 March 2019 and was informed by public comment input received on the Final report (see https://www.icann.org/public-comments/cct-final-recs-2018-10-08-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>). The Board’s decisions on each recommendation is documented in the scorecard published at https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scor… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>. A blog post on the Board action can be found at https://www.icann.org/news/blog/board-action-on-competition-consumer-trust-… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> for more context. We thank you for your collaboration in considering the CCT-RT output. Please let us know whether you have any questions. Thank you. Best regards. Larisa Gurnick Vice-President, Multi-stakeholder Strategy & Strategic Initiatives, ICANN

1 0

Re: [council] 11 July Update - Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review
by Julie Hedlund 12 Jul '19

12 Jul '19

Dear GNSO Councilors, Staff thought it might be helpful to provide some context concerning this item below in the ICANN Community Leadership Digest: “Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review” and to explain the GNSO’s role as a Decisional Participant in the Empowered Community. The item in the digest references an open public comment forum: https://www.icann.org/public-comments/bylaws-amend-iana-naming-function-201…. The purpose of the forum, which closes on 26 July 2019, is: to obtain community input on a proposed change to Bylaws Section 18.7(b), regarding the IANA Naming Function Review Team's Composition. The proposed amendment was raised by the ccNSO, which has identified a current and ongoing issue with populating the IANA Naming Function Review in accordance with the Bylaws' requirements. The Board, taking on the ccNSO's request, agreed to initiate the Fundament Bylaws amendment process (specified Section 25.2 of the Bylaws) to seek community input on the ccNSO's proposed modifications to the composition requirements. The amendment would remove the requirement for the ccNSO to identify a non-ccNSO member ccTLD representative and instead allow the ccNSO to appoint three representatives to the team, regardless of ccNSO member status. The GNSO’s role in this process as a Decision Participant in the Empowered Community is noted in the public comment forum announcement [emphasis added]: “The ICANN Board will consider public comments received in evaluating the proposed Amendment. If the Board approves a Fundamental Bylaws change, the ICANN Empowered Community will then need to consider whether to approve the amendment as well.” The Empowered Community has a role in approval actions as described in Annex D EC Mechanism, Section 1.1 Approval Actions. There are three actions that require approval: 1. Fundamental Bylaw Amendments, as contemplated by Section 25.2 of the Bylaws; 2. Articles Amendments, as contemplated by Section 25.2 of the Bylaws; and 3. Asset Sales, as contemplated by Article 26 of the Bylaws. As the change requested by the ccNSO is an amendment to the Fundamental Bylaws, it requires consideration by the Empowered Community as to whether to approve the amendment. If the Board decides to approve the Fundamental Bylaws change that will trigger Section 1.3 of Annex D, Approval Action Community Forum. In anticipation of Board approval, an Approval Action Community Forum is tentatively planned for ICANN66 (if requested, the Forum occurs either within 30 days of the Board’s approval, or at the next scheduled ICANN meeting). As you may know, the GNSO Council has re-established a Drafting Team<https://community.icann.org/pages/viewpage.action?pageId=102143482> that is developing guidelines for the GNSO’s roles and obligations as a Decisional Participant in the Empowered Community. According to its timeline<https://community.icann.org/display/GBIDT/DT+Timeline+and+Background+Docume…>, the Drafting Team anticipates providing all guidelines and templates to the GNSO Council to review by October 2019. However, the Drafting Team expects to complete its review of the guidelines and templates for Section 1.3 of the Bylaws, the Approval Action Community Forum, by 24 July 2019. In any case, those guidelines will be available to guide the GNSO’s engagement in the Approval Action Community Forum at ICANN66 and its decision whether or not to approve the Fundamental Bylaws Amendment via a simple majority vote on a motion according to the deadline of 21 days following the end of the Forum. This Approval Action will afford the GNSO Council the first opportunity to act in its role as a Decisional Participant using the guidelines and templates developed by the Drafting Team. If the GNSO Council would like a short briefing on this issue at its meeting on 18 July there is time allotted in the agenda under Any Other Business. In addition, please feel free to direct any questions you may have for staff to this list. Kind regards, Julie Julie Hedlund, Policy Director From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Thursday, July 11, 2019 at 10:01 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] [ICANN Community Leaders] 11 July Update [http://r20.rs6.net/on.jsp?ca=507bdd88-cdb1-40c9-8c70-c3dec8dd2aac&a=1122025…] Thursday, 11 July 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. TABLE OF CONTENTS Information Sharing · NEW: NextGen@ICANN Survey · REMINDER: Update and Information on IRP IOT Re-Composition · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Public Comment · Process Proposal for Streamlining Organizational Reviews · Study on Technical Use of Root Zone Label Generation Rules · Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review · Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership · Proposed IANA SLAs for Publishing LGRs/IDN Tables · Draft Final Report of the Second Country Code Names Supporting Organization Review · Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan · Evolving the Governance of the Root Server System · Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Information Sharing NEW: NextGen@ICANN Survey Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The ICANN organization is initiating a community consultation to identify improvement opportunities for the NextGen@ICANN Program. The review will start with gathering community input about several aspects of the NextGen@ICANN Program, including its purpose, goals, processes, and synergies with the ICANN academic community. The survey is intended for all ICANN community groups; individuals are encouraged to work with their relevant Supporting Organizations, Advisory Committees, stakeholder groups, and constituencies. Based on the input received from the survey, ICANN org will draft a proposal for program improvements that will be published for Public Comment. Once all feedback is received, ICANN org will prepare the final proposal for program improvements. Survey [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> (PDF with background at the beginning and questionnaire questions at the end) Background about the Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Sally Costerton's blog about the NextGen@ICANN Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> NextGen webpage [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> REMINDER: Update and Information on IRP IOT Re-Composition Executive: John Jeffrey, General Counsel FOR: All SO/AC Chairs INFORMATION SHARING As the ICANN Board committee with oversight responsibility of ICANN's accountability mechanisms, the Board Accountability Mechanisms Committee (BAMC) considers the work of the [Independent Review Process (IRP)] Implementation Oversight Team (IOT) to be paramount to ICANN's accountability...we seek your help in finding additional volunteers within the community that meet the qualifications identified in the attached letter, outlining skills and experience requirements, to join the IOT and help to conclude its work in a timely fashion. Read more [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Executive: Cyrus Namazi, Senior Vice President, Global Domains Division FOR: All Community Leaders INFORMATION SHARING In December 2015, the GNSO initiated a Policy Development Process (PDP) to determine if changes to existing policy recommendations are needed before the next round of gTLDs. The PDP Working Group expects to publish its final report with its recommendations by December 2019. These recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. In the course of our preparatory work toward the planning and implementation of the new policy, ICANN org has compiled a number of fundamental operationally focused assumptions to help with the preliminary planning and operational readiness of the organization. These assumptions have been shared with the ICANN Board, and now ICANN org would like to share them with relevant parts of the community. Public Comment Process Proposal for Streamlining Organizational Reviews [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 15 July 2019 Study on Technical Use of Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 19 July Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 26 July 2019 Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 26 July 2019 Proposed IANA SLAs for Publishing LGRs/IDN Tables [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 26 July 2019 Draft Final Report of the Second Country Code Names Supporting Organization Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: 4 August 2019 Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 5 August 2019 Evolving the Governance of the Root Server System [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 9 August 2019 Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 12 August 2019 Volume 1, Issue 31 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 15 July 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

[ICANN Community Leaders] 11 July Update
by Nathalie Peregrine 11 Jul '19

11 Jul '19

[http://r20.rs6.net/on.jsp?ca=507bdd88-cdb1-40c9-8c70-c3dec8dd2aac&a=1122025…] Thursday, 11 July 2019 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. TABLE OF CONTENTS Information Sharing · NEW: NextGen@ICANN Survey · REMINDER: Update and Information on IRP IOT Re-Composition · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Public Comment · Process Proposal for Streamlining Organizational Reviews · Study on Technical Use of Root Zone Label Generation Rules · Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review · Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership · Proposed IANA SLAs for Publishing LGRs/IDN Tables · Draft Final Report of the Second Country Code Names Supporting Organization Review · Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan · Evolving the Governance of the Root Server System · Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Information Sharing NEW: NextGen@ICANN Survey Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The ICANN organization is initiating a community consultation to identify improvement opportunities for the NextGen@ICANN Program. The review will start with gathering community input about several aspects of the NextGen@ICANN Program, including its purpose, goals, processes, and synergies with the ICANN academic community. The survey is intended for all ICANN community groups; individuals are encouraged to work with their relevant Supporting Organizations, Advisory Committees, stakeholder groups, and constituencies. Based on the input received from the survey, ICANN org will draft a proposal for program improvements that will be published for Public Comment. Once all feedback is received, ICANN org will prepare the final proposal for program improvements. Survey [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> (PDF with background at the beginning and questionnaire questions at the end) Background about the Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Sally Costerton's blog about the NextGen@ICANN Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> NextGen webpage [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> REMINDER: Update and Information on IRP IOT Re-Composition Executive: John Jeffrey, General Counsel FOR: All SO/AC Chairs INFORMATION SHARING As the ICANN Board committee with oversight responsibility of ICANN's accountability mechanisms, the Board Accountability Mechanisms Committee (BAMC) considers the work of the [Independent Review Process (IRP)] Implementation Oversight Team (IOT) to be paramount to ICANN's accountability...we seek your help in finding additional volunteers within the community that meet the qualifications identified in the attached letter, outlining skills and experience requirements, to join the IOT and help to conclude its work in a timely fashion. Read more [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Executive: Cyrus Namazi, Senior Vice President, Global Domains Division FOR: All Community Leaders INFORMATION SHARING In December 2015, the GNSO initiated a Policy Development Process (PDP) to determine if changes to existing policy recommendations are needed before the next round of gTLDs. The PDP Working Group expects to publish its final report with its recommendations by December 2019. These recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. In the course of our preparatory work toward the planning and implementation of the new policy, ICANN org has compiled a number of fundamental operationally focused assumptions to help with the preliminary planning and operational readiness of the organization. These assumptions have been shared with the ICANN Board, and now ICANN org would like to share them with relevant parts of the community. Public Comment Process Proposal for Streamlining Organizational Reviews [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 15 July 2019 Study on Technical Use of Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 19 July Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 26 July 2019 Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 26 July 2019 Proposed IANA SLAs for Publishing LGRs/IDN Tables [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 26 July 2019 Draft Final Report of the Second Country Code Names Supporting Organization Review [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: 4 August 2019 Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 5 August 2019 Evolving the Governance of the Root Server System [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 9 August 2019 Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 12 August 2019 Volume 1, Issue 31 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 15 July 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

GNSO Council Abstention Notification Form [#316]
by ICANN 10 Jul '19

10 Jul '19

1 0

Loss of Adobe Connect
by Ayden Férdeline 10 Jul '19

10 Jul '19

Dear all, [ICANN has announced](https://www.icann.org/news/blog/transitioning-icann-s-remote-par… that it will be rapidly transitioning away from the Adobe Connect platform to Zoom. I am not sure if there was consultation with other parts of the community, or if there is support for this decision, but I was hoping to hear from other Councillors as to whether or not they thought this decision would have implications on our work. I have used Zoom before and found the platform's interface to not be particularly intuitive, so I am worried. Perhaps someone could put me at ease that this will not be a consequential change. Thanks. Best wishes, Ayden

5 9

GNSO Council Abstention Notification Form [#315]
by ICANN 10 Jul '19

10 Jul '19

1 0