September 2019 - council - lists.icann.org

Reminder input needed: ICANN org's preparation toward implementation of a new round of gTLDs
by Nathalie Peregrine Sept. 10, 2019

Sept. 10, 2019

Dear councilors, A reminder that an action item from the GNSO Council meeting held on the 22 August 2019 was: “Council to consider if they would like to provide a written response to ICANN Org, to be delivered by the end of September. Councilors to inform their respective SG/Cs of the timeline for providing input.” Please find the Assumptions Paper attached for your review. Kind regards, Nathalie From: council <council-bounces(a)gnso.icann.org> on behalf of "council(a)gnso.icann.org" <council(a)gnso.icann.org> Reply-To: "kdrazek(a)verisign.com" <kdrazek(a)verisign.com> Date: Monday, June 17, 2019 at 8:53 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] FW: ICANN org's preparation toward implementation of a new round of gTLDs FYI From: Cyrus Namazi <cyrus.namazi(a)icann.org> Sent: Monday, June 17, 2019 1:29 PM To: Drazek, Keith <kdrazek(a)verisign.com> Cc: Marika Konings <marika.konings(a)icann.org>; David Olive <david.olive(a)icann.org>; Trang Nguyen <trang.nguyen(a)icann.org>; Steve Chan <steve.chan(a)icann.org> Subject: [EXTERNAL] ICANN org's preparation toward implementation of a new round of gTLDs Dear Keith; As you likely recall, 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. We understand that 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. I have shared these assumptions with the ICANN Board, and am now sharing them with all ICANN constituencies in the briefing document attached. We plan to meet face-to-face with the Subsequent Procedures PDP Working Group in Marrakech to further discuss these assumptions. If the GNSO Council members are also interested in further engagement and providing feedback and perspective on these assumptions please let me know and we will be happy to arrange a mutually convenient time for a discussion. For your information, this information will also be included in the ICANN Community Digest which is planned to be issued later this week. Sincerely, Cyrus Namazi Senior Vice President | Global Domains Division Internet Corporation for Assigned Names and Numbers (ICANN) 801 17th St NW, Suite 400 | Washington, DC 20006 USA Office +1 202 249 7543 | Mobile +1 408 421 6894 Skype : cnamazi www.icann.org<http://www.icann.org>

1 0

Reminder: EPDP-Phase 2 Project Management and Work Plan Package
by Nathalie Peregrine Sept. 10, 2019

Sept. 10, 2019

Dear councilors, A reminder to please submit input on the EPDP Phase 2 Project Management and Work Plan Package at your earliest convenience. Kind regards, Nathalie From: council <council-bounces(a)gnso.icann.org> on behalf of "rafik.dammak(a)gmail.com" <rafik.dammak(a)gmail.com> Date: Wednesday, August 14, 2019 at 1:51 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] EPDP-Phase 2 Project Management and Work Plan Package Dear GNSO Council Members, Please find attach the EPDP-Phase 2 project and work plan package that outlines the group’s key deliverables and milestones. Apologies up front for the large number of documents contained in the package, but each one plays a distinct role in managing and communicating the status and condition of this project. Below is brief highlight of each of the work products contained within the package. The full substance of project plan can be found on page 4. In short, the EPDP-P2 team targets early December 2019 to deliver an Initial Report for public comment, and shortly after ICANN67 (Cancun) the group plans to deliver its Final Report. This package was reviewed 13 August with the EPDP and if you prefer an in-depth briefing, the recording is now available<https://community.icann.org/display/EOTSFGRD/2019-08-13+EPDP-+Phase+2+call+…>. While the GNSO Council, as normal procedure, adopts a group’s charter before initiating policy deliberations, to our knowledge, this is the first time the GNSO Council will approve a detailed plan like what is attached here for the EPDP. This is largely due to the fact that this is also the first policy development process executed that is funded separately from ICANN’s Contingency fund and therefore the extra procedures and attention. The Council’s adoption of this plan is a crucial step by which the GNSO Council can request additional dedicated resources required to complete the Phase 2 effort. Very much like Phase 1, the Phase 2 EPDP will request additional resources to complete the formal request from the ICANN Board. You will recall two such interim requests made in April and June of 2019. Shortly after the Council’s approval of this plan, the resource request to the Board will be initiated and details of that request will be supplied at that time. We are targeting the 22 Aug 2019 Council meeting to obtain approval of the plan. It should be noted however, that the EPDP-P2 leadership team will reassess the project plan based on outcomes of the Los Angeles face-to-face in early September. One final thing to consider when reviewing the plan at a high-level and as communicated in Marrakech, an aspirational target was set for Dec 2019 to launch an Initial Report for public comment. You’ll see this represented in the work products that make up this package. Berry would like to reinforce the notion that this plan attempts to allocate tasks based on the number of hours it takes for the group to deliberate the policy topics and agree on some sort of outcome. While the project plan is represented on a 5 business day work week, in reality that only translates to 4 or 6 hours of conference calls per week. So, it is important to think of tasks being resourced in those terms instead of being driven only by calendar dates. As an example and assuming we do not take any breaks, considering plenary calls are 2 hours and secondary/legal calls are 1.5 hours, and finally considering total hours for the face-to-face in LA, it only equates to a total of 38 hours to deliberate topics verbally through 11 September 2019. That’s less than one business week assuming that it could be condensed into a single week. EPDP-P2 Project and Work Plan Package: * The general intent is this will be compiled and reviewed once per month in preparation for EPDP planning/progress, but also to prepare for updates required by the GNSO Council. Individual work products will be updated more frequently and as necessary by the EPDP leadership team to meet the project communication and planning requirements. * Page 1 - a high-level, simple Gantt view of key deliverable dates for the primary phases of the project including engagement opportunities such as ICANN meetings or dedicated face-to-face sessions. The summary timeline will typically be presented on a rolling twelve months and updated monthly. * Page 2- this Fact Sheet work product is primarily used for projects with dedicated funds and acts as an overall communications vehicle. It displays the status, activities, milestone completion, and a summary of the financial resources. The project leadership team, as well as the Project Cost Support Team will manage and update the Fact Sheet with the assistance of staff. The milestones section, such as the % complete, will be derived from the four primary phases of the project plan Gantt chart. * Page 3 – Project SitRep, this work product is a copy of the project document presented in the GNSO Council’s Project List to enhance status reporting consistency to broader GNSO. It contains the project summary, scope, composition, summary, and deliverables/milestones. The lower section describes in more detail the current, planned, and completed tasks. The Status and Condition codes are the primary feature, and it’s complemented by an escalation process (described later) where At-Risk or In-Trouble projects can be properly managed. * Page 4 – Collapsed version of the Gantt Project Plan; a full expanded version of the plan can be found on the EPDP’s wiki page<https://community.icann.org/x/6BdIBg>. The Gantt is a detailed view of the project’s tasks and deliverables from beginning to end. The project typically begins with the adoption of a group’s charter that contains all detailed tasks to be accomplished in between major milestones in a manner that also identifies dependencies and duration of each task. The Gantt chart is an effective tool to demonstrate impacts should key deliverable dates be missed that may impact the critical path and downstream tasks or deliverables. * Page 5 – is screen print of the work plan and action items. this work product presents a tactical view of the tasks and deliverables for the group. Unlike the Gantt, it takes a simple form of a table listing the task, who is assigned, when it was assigned, due dates, and notes related to the task. In most cases, this should only contain those activities that occur the next several weeks and no longer than two months as to maintain focus on the current tasks. It will be updated each week with the tasks from the project plan. This work product now resides on Google Sheets [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spread…>. Enjoy the review of the project package and staff is happy to answer any questions over the list in the meantime. Thank you. Best Regards, Rafik Dammak

1 0

Reminder: For Review: Initial draft of Proposed GNSO Council Response to CCT-RT Recommendations Passed Through to GNSO
by Nathalie Peregrine Sept. 10, 2019

Sept. 10, 2019

Dear councilors, A reminder that the closing date for input on the initial draft of the proposed GNSO Council response to CCT-RT Recommendations is this coming Friday, 13 September 2019. Kind regards, Nathalie From: council <council-bounces(a)gnso.icann.org> on behalf of PAMELALITTLE <pam.little(a)alibaba-inc.com> Reply-To: PAMELALITTLE <pam.little(a)alibaba-inc.com> Date: Friday, August 30, 2019 at 5:45 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, Flip Petillion <fpetillion(a)petillion.law> Cc: "carlosraulg(a)gmail.com" <carlosraulg(a)gmail.com> Subject: Re: [council] For Review: Initial draft of Proposed GNSO Council Response to CCT-RT Recommendations Passed Through to GNSO Hi Flip - Thank you for taking the time to review the draft. Dear Councilors, This item was on 22 August Council meeting agenda but was deferred to our next monthly meeting on 19 September. There are 5 recommendations under consideration and the small team's proposed response is as follows: #10 (initiating a PDP to create a privacy baseline across all registries) - No action at this time #16 (abuse and Domain Abuse Activity Reporting (DAAR)) - Redirect to ICANN org #27 & #28 - Refer to the RPM WG #29 be - Refer to Sub-pro WG It would be greatly appreciated if you could take a moment to review the draft (attached again) and, if appropriate, seek input from your respective group by 13 September 2019. It would hopefully make our discussion during the Council meeting more efficient. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion(a)petillion.law> Sent At:2019 Aug. 20 (Tue.) 16:47 Recipient:PAMELALITTLE <pam.little(a)alibaba-inc.com>; council(a)gnso.icann.org <council(a)gnso.icann.org>; council <council-bounces(a)gnso.icann.org> Cc:"Carlos Raúl Gutiérrez G." <carlosraulg(a)gmail.com> Subject:Re: [council] For Review: Initial draft of Proposed GNSO Council Response to CCT-RT Recommendations Passed Through to GNSO Thank you Pam I have no comments. Best regards, Flip Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_1247444843][petillion.law]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.petillion.law_&d=Dw…> Attorneys – Advocaten - Avocats From: council <council-bounces(a)gnso.icann.org> on behalf of Pam Little <pam.little(a)alibaba-inc.com> Reply to: Pam Little <pam.little(a)alibaba-inc.com> Date: Tuesday, 20 August 2019 at 02:42 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, council <council-bounces(a)gnso.icann.org> Cc: "Carlos Raúl Gutiérrez G." <carlosraulg(a)gmail.com> Subject: Re: [council] For Review: Initial draft of Proposed GNSO Council Response to CCT-RT Recommendations Passed Through to GNSO Dear Councilors, The small team would like to suggest some changes to the draft that was sent to the Council list late July: #16 on DAAR and DNS abuse - In light of the on-going conversations within the ICANN community, including a Plenary session on DNS Abuse to be held at ICANN66, we've made some suggested edits to the proposed Council response and new language to reflect this. #28 on cost-benefit analysis of TMCH - Staff recently clarified that the RPM WG did not carry out a cost-benefit analysis. While this was one of the specific Charter questions, Analysis Group's Final Report indicates that their data did not provide quantifiable information to include such analysis in its review. In light of this, we are suggesting a change to the proposed Council response: From: The GNSO Council will seek feedback/comment from the RPM WG whether its Phase 1 work has carried out a cost-benefit analysis consistent with the scope described in this Recommendation #28. To: The GNSO Council will refer this recommendation to the RPM WG. A redline version is attached for your review. Please let us know if you have any questions or comments. We look forward to discussing this further at the upcoming Council meeting later this week. Kind regards, Pam ------------------------------------------------------------------ Sender:PAMELALITTLE <pam.little(a)alibaba-inc.com> Sent At:2019 Jul. 23 (Tue.) 16:31 Recipient:council@gnso.icann.org <council(a)gnso.icann.org>; council <council-bounces(a)gnso.icann.org> Cc:"Carlos Raúl Gutiérrez G." <carlosraulg(a)gmail.com>; Carlos Raul Gutierrez <carlosraul(a)gutierrez.se>; Michele Neylon - Blacknight <michele(a)blacknight.com> Subject:For Review: Initial draft of Proposed GNSO Council Response to CCT-RT Recommendations Passed Through to GNSO Dear Councilors, You may recall that the Council discussed this topic during the wrap-up session in Marrakesh and the action item was for a small team (Carlos, Michele and myself) to take a look at the 5 Recommendations that were passed through to GNSO (see the message below from Larisa Gurnick forwarded by Mary to Council). In addition, a number of Recommendations were passed through to gTLD Subsequent Procedures PDP Working Group and/or Rights Protection Mechanisms (RPM) PDP Working Group. In order to have a better picture of where all the Recommendations passed to the GNSO and its PDPs stand, Keith is planning to write to the leadership of the Working Groups seeking their feedback. In the meantime, I attach an initial draft with the small team's proposed GNSO Council response to those 5 Recommendations passed through directly to the GNSO for your review and consideration. It is likely to be included in our August Council meeting agenda so please take some time to consider the proposed responses before the meeting. All feedback/comments/suggested edits are welcome! Kind regards, Pam ------------------------------------------------------------------ Sender:Mary Wong <mary.wong(a)icann.org> Sent At:2019 Jun. 10 (Mon.) 16:43 Recipient:council@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

Reminder: PDP 3.0 Package 1: Final Documents for Improvements 1, 2, 3 & 6
by Nathalie Peregrine Sept. 10, 2019

Sept. 10, 2019

Dear councilors, A reminder that the closing date for input on the PDP3.0 Package 1 is this coming Friday, 13 September 2019. Kind regards, Nathalie From: council <council-bounces(a)gnso.icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Thursday, August 22, 2019 at 5:38 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: Re: [council] PDP 3.0 Package 1: Final Documents for Improvements 1, 2, 3 & 6 Dear GNSO Councilors, Following up on today’s Council meeting, please be so kind to review the Small Team’s conclusions and proposed implementation of Improvements #1, #2, #3, and #6. Please provide your input/feedback for the final documents (links in the email below) directly via this thread on the Council list by COB Friday, 13 September. For your convenience, staff have attached the slides shown during the Council call. The slides provide a high-level overview of each completed improvement, as well as next steps/actions for the Council to consider. In addition, staff also attached an update project list indicating the status of PDP 3.0 project. This project list follows the proposed new format as part of the implementation of Improvements #16 (Criteria for PDP WG Updates), which the Council will review in further detail in the near future. Thank you for your time and input! Best Regards, Ariel From: Ariel Liang <ariel.liang(a)icann.org> Date: Tuesday, August 13, 2019 at 7:30 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: PDP 3.0 Package 1: Final Documents for Improvements 1, 2, 3 & 6 Dear GNSO Councilors, On behalf of the PDP 3.0 Small Team, staff would like to inform you that the Small Team has completed five (5) out of fourteen (14) PDP 3.0 improvements so far. The rest of the nine (9) improvements are all in the pipeline with various levels of progress. In advance of the 22 August Council meeting, the PDP 3.0 Small Team are sending the following documents for four (4) completed PDP 3.0 improvements as the first deliverable to the GNSO Council for review. They are packaged together as they are concerned with the expectations, requirements, and/or participation methods for PDP working groups members and/or leaders. Note that Improvement #14 (Criteria to Evaluate Request for Data Gathering) has also been completed, but it will be delivered in a separate package together with other completed, related improvements prior to future GNSO Council meetings. * Improvement #1: Terms of participation for working group members [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Improvement #2: Consider alternatives to open working group model [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Improvement #3: Criteria for joining of new members after a PDP working group is formed or re-chartered * Main document [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Working Group Member Skills Guide [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> * Improvement #6: Document expectations for working group leaders (Chairs/Co- Chairs/Leads) that outlines role & responsibilities as well as minimum skills / expertise required [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> The Small Team invites the GNSO Council to review these documents and welcomes your questions and feedback. The Small Team looks forward to further discussions with the GNSO Council during the meeting on 22 August. == Background The GNSO Council identified a number of challenges as well as possible improvements related to the Policy Development Process (PDP), as a result of a number of discussions throughout 2018. These efforts started in the form of a staff discussion paper [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_file_…>, shared on 10 January 2018 and discussed at the GNSO Council’s 2018 Strategic Planning Session. In order to engage the broader GNSO community in this discussion, the GNSO Council organized a collaborative session [61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…> involving the members of the PDP Leadership Teams as well as the broader community to summarize key points from the Strategic Planning Session, elaborate on the challenges that PDPs presently face and identified, and begin to brainstorm possible solutions. On 11 May 2018, an updated paper [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> was prepared, taking into account feedback received. The GNSO Council solicited additional feedback from the GNSO Stakeholder Groups and Constituencies, summarizing input received [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>. An updated report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> was prepared as well as an Implementation Plan [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>. On 24 October 2018, the Council resolved [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> to adopt the Final Report and begin implementation, as well as report on progress no less than on a quarterly basis. At the 2019 GNSO Council Strategic Planning Session, the Council discussed early drafts for select implementation areas, ultimately agreeing that a small team of Councilors be convened to support implementation efforts. That small team of Councilors first convened at ICANN64 in Kobe, Japan and met on a bi-weekly basis between April and June 2019. During its informal status meeting at ICANN65 in Marrakech, Morocco, the small team decided to make a few enhancements on its working methods in order to meet its goal of completing implementation of all fourteen (14) PDP 3.0 improvements by ICANN66 Montreal, Canada. These enhancements include: * Increase its meeting frequency to weekly basis; * Designate small team lead who works with GNSO support staff to tackle each improvement; * Track completion status and set target dates for final call and document finalization; * Use google docs for all improvement documents to facilitate collaboration. In addition, the small team has also decided to deliver the final documents of completed improvements in an incremental manner -- selected few improvements, which often have a common theme or relate to each other, are delivered to the GNSO Council in one package. With fewer documents to review each time, the GNSO Council should be able to digest the documents more easily and provide timely input to help the small team improve its future deliverables to the Council. Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org

1 0

FW: [Ext] ICANN News Alert -- Join the Webinar on ICANN’s FY21 Annual Operating Plan and Budget and 5-Year Operating and Financial Plan
by Nathalie Peregrine Sept. 10, 2019

Sept. 10, 2019

FYI From: ICANN <no-reply(a)external.icann.org> Reply-To: "no-reply(a)external.icann.org" <no-reply(a)external.icann.org> Date: Tuesday, September 10, 2019 at 12:56 AM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Subject: [Ext] ICANN News Alert -- Join the Webinar on ICANN’s FY21 Annual Operating Plan and Budget and 5-Year Operating and Financial Plan [ICANN Announcement Alerts] Join the Webinar on ICANN’s FY21 Annual Operating Plan and Budget and 5-Year Operating and Financial Plan [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_K…> 09 September 2019 LOS ANGELES – 9 September 2019 – The Internet Corporation for Assigned Names and Numbers (ICANN) invites the ICANN community to participate in a webinar on the planning process for the FY21 Operating Plan and Budget and FY21-FY25 Operating and Financial Plan. There are two options to participate: * 11 September 2019 at 0000 UTC https://icann.zoom.us/j/462178439 [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_j…> * 13 September 2019 at 1600 UTC https://icann.zoom.us/j/826234297 [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_Z…> The ICANN Planning Team will discuss the timeline and process for the FY21 Operating Plan and Budget, and the FY21-FY25 Operating and Financial Plan. There will be an opportunity to ask questions. Community participation in ICANN's planning process is a cornerstone of transparency and accountability to the global multistakeholder community. ICANN thanks all community members who contribute to this important process. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. [shadow] [Twitter][newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_Z…> [Facebook][newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_w…> [Instagram][newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_I…> [Linkedin][newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_L…> [YouTube][newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_q…> [shadow1] Unsubscribe [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_h…> | https://www.icann.org [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_W…> [newsalerts.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__newsalerts.icann.org_E…>

1 0

IRP-IOT Small Team: DRAFT GNSO Input on Questions Relating to the Issues for Considerations Regarding the IRP IOT
by Julie Hedlund Sept. 10, 2019

Sept. 10, 2019

Dear GNSO Councilors, As you may recall, Elsa Saade and Flip Petillion volunteered to be the small team to draft a possible GNSO Council response to the request for the community to respond to the questions relating to the IRP Implementation Oversight Team (IOT) as requested at ICANN65. The original deadline to respond to ICANN Org was 15 April 2019, per the Blog Post from Göran Marby dated 09 March 2019: https://www.icann.org/news/blog/independent-review-process-standing-panel-c… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. In May Samantha Eisner and David McCauley gave a presentation on the IRP-IOT to the GNSO Council. At ICANN65 the Council asked for volunteers to draft possible GNSO Council responses, which Elsa and Flip have now done and it is attach for your consideration after considerable discussion and upon reviewing the comments provided by the GNSO Community. We have confirmed with Samantha Eisner that ICANN Org is still interested in receiving input from the GNSO. This document is on the agenda for discussion for the GNSO Council meeting on Thursday, 19 September. In the meantime, please let us know if you have any questions or comments. Kind regards, Julie Julie Hedlund on behalf of Elsa Saade and Flip Petillion

2 1

FW: [ICANN Community Leaders] 9 September Update
by Julie Bisland Sept. 9, 2019

Sept. 9, 2019

FYI: [http://r20.rs6.net/on.jsp?ca=cc7fb8f1-9e84-4225-8ff6-ab8e43d0d088&a=1122025…] Monday, 9 September 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 Requests · TODAY: NextGen@ICANN Survey · THIS WEEK: Third Accountability and Transparency Review Survey Available for Community Input Information Sharing · NEW: FY21 Planning Process Webinars · THIS WEEK: Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model · REMINDER: Global Public Interest Framework Webinar ICANN66 Planning · THIS WEEK: CROP Deadline for ICANN66 · REMINDER: Publication Support for ICANN66 · SAVE THE DATES: ICANN66 Prep Week · SAVE THE DATE: ICANN66 Community Leadership Reception Public Comment · Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model Requests TODAY: NextGen@ICANN Survey Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders REQUEST 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 2019. 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 post about the NextGen@ICANN Community Consultation [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> THIS WEEK: Third Accountability and Transparency Review Survey Available for Community Input Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders REQUEST The third Accountability and Transparency Review Team (ATRT3) has published a survey for community input. The aim of this survey is to collect opinions from individuals and groups in the ICANN community on ICANN’s accountability and transparency, and to help the ATRT3 Review Team identify areas which require improvement and could benefit from a recommendation. The individual survey is available here: http://input.icann.org/go?iv=eupcis2ldyww The group survey (intended to capture group responses from ICANN community groups) is available here: http://input.icann.org/go?iv=3j46tfx0r5yzt Following the close of both surveys on Friday, 13 September 2019 at 23:59 UTC, the ATRT3 Review Team will evaluate responses as input to its draft final report. Information Sharing NEW: FY21 Planning Process Webinars Executive: Xavier Calvez, Senior Vice President and Chief Financial Officer FOR: All Community Leaders INFORMATION SHARING ICANN’s Planning Team would like to invite you to attend a webinar on the Fiscal Year 2021 (FY21) Planning Process which includes Operating Plans and Budgets for PTI, IANA, and ICANN. We will hold two webinars that will cover the following: · FY21 Operating Plan and Budget · FY21-FY25 Operating and Financial Plan · Timeline · Community Participation Opportunities · Questions Below are the details for the two sessions. If you are unable to participate in one of these sessions, they will be recorded and posted to the ICANN Finance Community Wiki [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> for future viewing and additional questions. It is not necessary to attend both sessions, each session will cover the same material. We are hosting two sessions to better accommodate time zones. Webinar #1 Wednesday, 11 September 2019 00:00-1:00 UTC Remote Participation: https://icann.zoom.us/j/462178439 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Webinar #2 Friday, 13 September 2019 16:00-17:00 UTC Remote Participation: https://icann.zoom.us/j/826234297 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> We look forward to your participation and invite you to share this information with other community members who would like to learn more about ICANN’s Planning Process. THIS WEEK: Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING A Public Comment proceeding [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> seeking input on the “Next Steps to Improve the Effectiveness of ICANN’s Multistakeholder Model [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>” launched on 27 August 2019. The proceeding will provide input for developing a work plan to address issues hampering the effectiveness and efficiency of ICANN’s multistakeholder model. To discuss the proceeding and next steps, the community is invited to participate in a webinar [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> on Wednesday, 11 September 2019 at 23:00 UTC or Thursday, 12 September 2019 at 16:00 UTC. Brian Cute, the facilitator for Evolving ICANN’s Multistakeholder Model, is available to discuss this work with any ICANN community group at its convenience. To contact Brian, please send your request to the mailing list [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. REMINDER: Global Public Interest Framework Webinar Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING You are invited to attend a webinar to learn more about one of the ICANN Board’s operational priorities: the public interest. The webinar is open to all community members. The global public interest is central to many of ICANN’s primary governance documents, and the ICANN Board hopes to play a role in facilitating a bottom-up, community-driven process to develop a framework as a toolkit for the ICANN community to consider the global public interest. These considerations would not change the process by which decisions are made but could instead serve as tools for the community to reinforce the commitment to the public interest and to demonstrate how specific recommendations, advice, and public comments are in the global public interest. This includes the ICANN community guiding the ICANN Board about the public interest determination the latter must make in its decisions. To learn more about the framework, please read the discussion paper (PDF) [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. For more information, visit the wiki [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. The Global Public Interest Framework Webinar has been scheduled for Tuesday, 17 September 2019 at 15:00 UTC. To join the webinar, please visit https://icann.zoom.us/j/288558444 Zoom call details Meeting ID: 288 558 444 Find your local number [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Time zone converter [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> ICANN66 Planning THIS WEEK: CROP Deadline for ICANN66 Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING For eligible groups planning to use Community Regional Outreach Program (CROP) funds to conduct outreach during ICANN66, requests must be submitted no later than Friday, 13 September 2019. No exceptions will be made. When submitting a CROP travel request, please keep in mind the following: · Trip requests must be approved by the respective community leadership team. · For FY20, the trip request must be filled in by the CROP participant via the CROP Wikispace. · In order to access the CROP Wikispace, applicants must first have an account; please let the CROP Coordinator know if an account is needed. · All individuals requesting CROP funding must also review the CROP Guidelines prior to submitting a request: https://community.icann.org/x/046jBg Please contact crop-staff(a)icann.org with any questions. REMINDER: Publication Support for ICANN66 Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Print-Only Deadline If you only need your ICANN66 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 20 September 2019. Please work directly with your Policy support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. SAVE THE DATES: ICANN66 Prep Week Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING ICANN66 Prep Week will take place 14-17 October 2019. This initiative aims to streamline the pre-ICANN Public Meeting experience to improve community preparation and increase awareness of plenary session topics. Stay tuned for an announcement with the full schedule and remote participation details. SAVE THE DATE: ICANN66 Community Leadership Reception Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The ICANN66 Community Leadership Reception with members of the ICANN Board and Executive Team will be held on Friday, 1 November 2019. More details including location and specific time will be shared later. Public Comment Next Steps to Improve the Effectiveness of ICANN's Multistakeholder Model [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 14 October 2019 Volume 1, Issue 48 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 12 September 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

FOR REVIEW: Draft GNSO Council Response to ICANN Board on Thick Whois Deferral Request
by Drazek, Keith Sept. 6, 2019

Sept. 6, 2019

Hi all, For your review and consideration, attached is a draft GNSO Council response to the ICANN Board's letter of 27 August 2019 (also attached) concerning Verisign's request for a deferral of the Thick Whois implementation. Please review the Board's letter, which requested a response shortly after our 19 September Council meeting, and the draft reply. We can discuss this on the list, and we will add it to the agenda for our meeting. Pam, Rafik and I coordinated on this proposed draft, which acknowledges the work ahead of Council on reviewing existing policies and procedures, including the Thick Whois consensus policy, in the context of EPDP Phase One Recommendation 27. It also points out that a single contracted party request for an implementation compliance deferral is not policy, per se, and is therefore the responsibility of ICANN Org and not the GNSO Council. I will note here that I am sensitive to views or concerns around a conflict of interest on this topic, in that Verisign is the contracted party requesting the deferral and is also my employer. As such, Pam, Rafik and I coordinated drafting this proposed response, and they have agreed to take the lead on shepherding the draft to a conclusion, so we can respond to the Board's request in a timely manner. I feel that this draft strikes the right procedural balance and avoids the substantive discussions that will need to take place in the near future as we tackle the issue of reviewing and amending the Thick Whois Consensus Policy in the context of the EPDP's Recommendations 7 and 27. If anyone has feedback for me on this, please let me know. Please respond with any comments on the draft letter so we can finalize and approve it at our next meeting. Best, Keith

1 0

FW: Implementation of Privacy and Proxy Service Provider Accreditation Issues Working Group [ ref:_00D1aY7OU._5001Pqrn9S:ref ]
by Drazek, Keith Sept. 6, 2019

Sept. 6, 2019

Hi all, Please see the attached letter from Cyrus related to PPSAI implementation and the IRTP. Thanks, Keith From: Correspondence <correspondence(a)icann.org> Sent: Thursday, September 05, 2019 11:35 AM To: Drazek, Keith <kdrazek(a)verisign.com>; pam.little(a)alibaba-inc.com; rafik.dammak(a)gmail.com Cc: cyrus.namazi(a)icann.org Subject: [EXTERNAL] Implementation of Privacy and Proxy Service Provider Accreditation Issues Working Group [ ref:_00D1aY7OU._5001Pqrn9S:ref ] Dear Keith Drazek, Pam Little and Rafik Dammak, Thank you for your letter of . Please find attached a response to your letter from Cyrus Namazi, Senior Vice President, Global Domains Division at ICANN. This response will be posted shortly to the ICANN Correspondence page (https://www.icann.org/resources/pages/correspondence) Please submit any questions you may have about this message to correspondence(a)icann.org<mailto:correspondence@icann.org>. Best Regards, Hope Shafer The Correspondence Team Internet Corporation for Assigned Names and Numbers (ICANN) correspondence(a)icann.org www.icann.org ref:_00D1aY7OU._5001Pqrn9S:ref

1 0

Reminder: Document and Motion deadline Monday 9 September 2019 at 23:59 UTC for GNSO Council Meeting 19 September 2019 at 21:00 UTC
by Nathalie Peregrine Sept. 6, 2019

Sept. 6, 2019

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 9 September 2019 at 23:59 UTC) of the GNSO Council Meeting on Thursday 19 September 2019 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/M4-kBg Thank you very much. With kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 2