August 2019 - council - lists.icann.org

Fwd: Draft Council Response Acknowledging Receipt of ICANN's Whois Accuracy/ARS Letter
by Marie Pattullo Aug. 21, 2019

Aug. 21, 2019

Apologies - I didn’t copy the entire list. Sorry! Sent from my iPhone Begin forwarded message: From: Marie Pattullo <marie.pattullo(a)aim.be<mailto:marie.pattullo@aim.be>> Date: 21 August 2019 at 19:31:25 GMT+2 To: "Drazek, Keith" <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: RE: Draft Council Response Acknowledging Receipt of ICANN's Whois Accuracy/ARS Letter Keith, all, Again, many thanks for the work here. For my own understanding, do we know if ICANN anticipates developing an update to the ARS for cases where ICANN itself is asserting its own purposes for processing data which is non-public and disclosed upon request? Of course we know that a lawful solution for ARS has to be found, so it would be interesting to know if there has been any preparatory work on this. As the Phase 1 Report implied in Rec 4 that ARS won’t be changed, although footnote 6 said that it will be “considered”, the BC would certainly support Council confirming that the ARS is included as part of the EPDP’s Phase 2 work. Thanks, Marie From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Drazek, Keith via council Sent: Thursday, August 15, 2019 7:16 PM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] Draft Council Response Acknowledging Receipt of ICANN's Whois Accuracy/ARS Letter Hi all, In preparation for our 22 August Council meeting, and further discussion of the topic, attached is a draft letter acknowledging receipt of Goran’s 21 June letter on WHOIS Accuracy and ARS. This is not a substantive response, so it should be fairly straightforward. Here’s the link to the original letter from Goran: https://www.icann.org/en/system/files/correspondence/marby-to-drazek-21jun1… Please let me know if you have any comments. Thanks, Keith

1 0

FW: [Ext] Re: ATRT3 - Survey
by Marika Konings Aug. 20, 2019

Aug. 20, 2019

Forwarding on behalf of Keith FYI, please see below. Note that this item will be added to the agenda under AOB for Thursday’s Council meeting to find volunteers to develop a proposed Council response to the survey. Best regards, Marika From: Bernard Turcotte <turcotte.bernard(a)gmail.com> Date: Tuesday, August 20, 2019 at 07:44 To: "Drazek, Keith" <kdrazek(a)verisign.com>, Marika Konings <marika.konings(a)icann.org> Subject: [Ext] Re: ATRT3 - Survey All, A few corrections to the original posting: · The individual survey is at http://input.icann.org/go?iv=eupcis2ldyww [input.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__input.icann.org_go-3Fiv…> · The survey tool will save incomplete forms which you can return to later IF you allow COOKIES and only when you click NEXT on the form. Apologies for any inconvenience. Bernard Turcotte ICANN Support to the ATRT3 On Mon, Aug 19, 2019 at 11:10 AM Bernard Turcotte <turcotte.bernard(a)gmail.com<mailto:turcotte.bernard@gmail.com>> wrote: Keith, The third Accountability and Transparency Review Team (ATRT3) has published a survey for SO/AC, including GNSO constituent bodies and RALOs, (Community Structures) input. You can find the Community Structures survey here (via Clicktools): http://input.icann.org/go?iv=3j46tfx0r5yzt<https://urldefense.proofpoint.com/v2/url?u=http-3A__input.icann.org_go-3Fiv…> (one survey per individual Community Structure please). The aim of this survey is to collect input from ICANN Community Structures on ICANN’s accountability and transparency and help the ATRT3 Review Team to identify areas which require improvement and could benefit from recommendations. The ATRT Review is one of the few mechanisms which can directly impact ICANN’s accountability and transparency. We need your input to ensure our recommendations can address your issues in these areas. Please note that if you leave the survey prior to completing it you will lose your input. To assist with this we are including printout versions of the survey with this email. You will note that not all questions are numbered - questions without numbers are dependent on the answer to the previous questions. The survey contains approximately 50 basic questions of which about 30 include the possibility of additional text input. The ATRT3 Review Team has published a separate survey for individuals, which can be found here: http://input.icann.org/app/survey/response.jsp<https://urldefense.proofpoint.com/v2/url?u=http-3A__input.icann.org_app_sur…>. We would ask that you promote and encourage your Structure's members to complete the individual version of this survey. The survey for Community Structures is essentially the same survey that is proposed to individuals but with the possibility to input text comments on a number of questions. Both surveys will close on 13 September 2019 at 23:59 UTC. The ATRT3 Review Team will evaluate responses as input to its draft final report. ATRT3 Co-Chairs Cheryl Langdon-Orr, Pat Kane Background The Accountability and Transparency Review is mandated by ICANN's Bylaws (Article 4, Section 4.6 icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__icann.org&d=DwMFaQ&c=Fm…>) to review "ICANN's execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community." Learn more about the ATRT3 Review here icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__icann.org&d=DwMFaQ&c=Fm…>

1 0

For Review: Initial draft of Proposed GNSO Council Response to CCT-RT Recommendations Passed Through to GNSO
by Pam Little Aug. 19, 2019

Aug. 19, 2019

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 - 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… 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. 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. 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 - 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) 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…. A blog post on the Board action can be found at https://www.icann.org/news/blog/board-action-on-competition-consumer-trust-… 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

2 2

ICANN 2019 NomCom Selected Nominees
by Nathalie Peregrine Aug. 19, 2019

Aug. 19, 2019

Dear councilors, On behalf of Keith Drazek, please find below the names of the 2019 NomCom selected nominees, and the announcement published here<https://www.icann.org/news/announcement-2019-08-19-en>. Kind regards, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of NomCom Operations Team <nomcom-ops-team(a)icann.org> Date: Monday, August 19, 2019 at 8:23 PM To: "kdrazek(a)verisign.com" <kdrazek(a)verisign.com> Cc: NomCom Operations Team <nomcom-ops-team(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, "dashcraft(a)swlaw.com" <dashcraft(a)swlaw.com> Subject: [gnso-secs] Confidential – ICANN 2019 NomCom Selected Nominees Dear Keith, It is my pleasure to inform you of the 2019 Nominating Committee selected nominees to the Council of the GNSO. We expect to announce the selections shortly. Please keep the appointments confidential until the publication of the announcement. The 2019 Nominating Committee selected nominees are: Generic Names Supporting Organization: 1. Carlton Samuels (Voting Non-Contracted Party House) – Region: LAC 2. Thomas (Tom) Dale (Voting Contracted Party House) – Region: AP Warm regards, Damon Ashcraft Chair, 2019 Nominating Committee

1 0

FYI: 19 August Update
by Michelle DeSmyter Aug. 19, 2019

Aug. 19, 2019

FYI: [http://r20.rs6.net/on.jsp?ca=0e63e2f4-c1fe-44df-a5da-34c9fd1a5b3e&a=1122025…] Monday, 19 August 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: Third Accountability and Transparency Review Survey Available for Community Input · REMINDER: Submission Deadline for NCAP Study 1 RFP Extended · REMINDER: NextGen@ICANN Survey · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs ICANN66 Planning · DESIGN DEADLINE THIS WEEK: Publication Support for ICANN66 · REMINDER: CROP Deadline for ICANN66 · SAVE THE DATE: ICANN66 Community Leadership Reception Public Comment · CLOSING TOMORROW: GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration Information Sharing NEW: 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 INFORMATION SHARING 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. REMINDER: Submission Deadline for NCAP Study 1 RFP Extended Executive: David Conrad, Chief Technology Officer (CTO) FOR: All Community Leaders INFORMATION SHARING On 9 July 2019, the ICANN org opened an RFP to select a contractor to research and write Study 1 of the Name Collision Analysis Project (NCAP), a project overseen by SSAC at the request of the ICANN Board. Very few organizations indicated their intention to bid on this work, so the ICANN org decided to extend the deadline for proposal submission to Friday, 23 August 2019. More information [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. All community leaders are encouraged to share this information with any organizations they believe might be interested and capable of performing the work. 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 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 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: 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 are working assumptions informed by the current work of the Subsequent Procedures PDP Working Group. Depending on outcome of the PDP Working Group and community input, the assumptions may be updated. These assumptions have been shared with the ICANN Board, as well as the PDP Working Group and other parts of the community. ICANN org has held discussions and/or received input from the Subsequent Procedures PDP Working Group, GAC, ALAC, and RSSAC. ICANN org plans to summarize the community input received on the operational planning assumptions and share with the ICANN Board at its September workshop. Any community input received by Friday, 30 August 2019 will be included in the summary. To submit additional feedback, please contact Trang Nguyen, trang.nguyen(a)icann.org ICANN66 Planning DESIGN DEADLINE THIS WEEK: Publication Support for ICANN66 Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN66 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 23 August 2019. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. Translation Deadline If your ICANN66 publication requires translation, please provide the final material(s) by Friday, 6 September 2019. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. 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. REMINDER: 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. 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 GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING TOMORROW: Tuesday, 20 August 2019 Volume 1, Issue 42 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 22 August 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

ATRT3 Questions for GNSO Council
by Drazek, Keith Aug. 15, 2019

Aug. 15, 2019

Hi all, In trying to wrap up some Council Action Items, this is a reminder. Please work with your respective SGs and Cs to provide any feedback directly to the ATRT3, or to advise the Council if there are comments that would fall within our remit. Here are the questions posed during our session with the ATRT3 in Marrakech: * Are your community members satisfied with their interaction with the GAC? What types of improvements would your community like to see implemented? * What is your perception of transparency within policy development process, including the EPDP? * Do you find the Board's current level and recent efforts towards accountability and transparency improvements satisfactory? * Is there anything else you'd like to share from the perspective of accountability and transparency? Thanks, Keith From: council <council-bounces(a)gnso.icann.org> On Behalf Of Drazek, Keith via council Sent: Wednesday, July 17, 2019 8:40 AM To: council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: [EXTERNAL] [council] ATRT3 Questions for GNSO Council and GNSO Appointment to ATRT3 Hi all, Two items related to ATRT3: 1. A reminder about the questions posed to Council by the ATRT3 team in Marrakech. See the email below. We need to develop a Council response or advise the ATRT3 that we are deferring response/input to our individual SGs and Cs. Regardless, if you haven't done so already, please socialize these questions with your respective groups. 2. One of the GNSO-appointed members of ATRT3, Erica Varlese, has advised that she will be moving to a new job and will therefore resign from the ATRT3. The GNSO Council leadership team discussed this situation and reviewed the history around the current slate of GNSO appointees. In brief, the GNSO Council originally nominated three primary candidates (Wolfgang Kleinwächter, (NCSG), Patrick Kane (RySG) and Osvaldo Novoa (ISPCP)). It also nominated the following four candidates in case additional spaces needed to be filled: Michael Karanicolas (NCSG), Adetola Sogbesan (BC), Erica Varlese (RySG), and Jacques Blanc (RrSG). All seven of the GNSO nominees were seated. There are none who applied but were not selected. Noting that the GNSO has substantial representation in ATRT3, and no backup candidates, the leadership team recommends we *not* undertake a new EOI and candidate replacement process. Please let us know if you have a different view or any follow-up questions. We can discuss further during our call this week. Thanks, Keith From: Drazek, Keith Sent: Monday, June 24, 2019 2:55 PM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: ATRT3 Questions for GNSO Council Hi all, Here are the questions we'll discuss with the ATRT3 team this afternoon: * Are your community members satisfied with their interaction with the GAC? What types of improvements would your community like to see implemented? * What is your perception of transparency within policy development process, including the EPDP? * Do you find the Board's current level and recent efforts towards accountability and transparency improvements satisfactory? * Is there anything else you'd like to share from the perspective of accountability and transparency? Thanks, Keith

1 0

Draft Council Response Acknowledging Receipt of ICANN's Whois Accuracy/ARS Letter
by Drazek, Keith Aug. 15, 2019

Aug. 15, 2019

Hi all, In preparation for our 22 August Council meeting, and further discussion of the topic, attached is a draft letter acknowledging receipt of Goran's 21 June letter on WHOIS Accuracy and ARS. This is not a substantive response, so it should be fairly straightforward. Here's the link to the original letter from Goran: https://www.icann.org/en/system/files/correspondence/marby-to-drazek-21jun1… Please let me know if you have any comments. Thanks, Keith

1 0

FYI: 15 August Update
by Michelle DeSmyter Aug. 15, 2019

Aug. 15, 2019

FYI: [http://r20.rs6.net/on.jsp?ca=7c9af677-2ff2-4539-95d4-91fa40720b0f&a=1122025…] Thursday, 15 August 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 · REMINDER: Submission Deadline for NCAP Study 1 RFP Extended · REMINDER: NextGen@ICANN Survey · REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs ICANN66 Planning · NEW: CROP Deadline for ICANN66 · SAVE THE DATE: ICANN66 Community Leadership Reception · LOOKING AHEAD: Publication Support Deadlines Public Comment · CLOSING NEXT WEEK: GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration Information Sharing REMINDER: Submission Deadline for NCAP Study 1 RFP Extended Executive: David Conrad, Chief Technology Officer (CTO) FOR: All Community Leaders INFORMATION SHARING On 9 July 2019, the ICANN org opened an RFP to select a contractor to research and write Study 1 of the Name Collision Analysis Project (NCAP), a project overseen by SSAC at the request of the ICANN Board. Very few organizations indicated their intention to bid on this work, so the ICANN org decided to extend the deadline for proposal submission to Friday, 23 August 2019. More information [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. All community leaders are encouraged to share this information with any organizations they believe might be interested and capable of performing the work. 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 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 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: 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 are working assumptions informed by the current work of the Subsequent Procedures PDP Working Group. Depending on outcome of the PDP Working Group and community input, the assumptions may be updated. These assumptions have been shared with the ICANN Board, as well as the PDP Working Group and other parts of the community. ICANN org has held discussions and/or received input from the Subsequent Procedures PDP Working Group, GAC, ALAC, and RSSAC. ICANN org plans to summarize the community input received on the operational planning assumptions and share with the ICANN Board at its September workshop. Any community input received by Friday, 30 August 2019 will be included in the summary. To submit additional feedback, please contact Trang Nguyen, trang.nguyen(a)icann.org ICANN66 Planning NEW: 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 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. 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. LOOKING AHEAD: Publication Support Deadlines Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN66 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 23 August 2019. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. Translation Deadline If your ICANN66 publication requires translation, please provide the final material(s) by Friday, 6 September 2019. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. 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. Public Comment GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> CLOSING NEXT WEEK: Tuesday, 20 August 2019 Volume 1, Issue 41 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 19 August 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

Final Proposed Agenda GNSO Council Meeting - 22 August 2019 at 12:00 UTC
by Nathalie Peregrine Aug. 14, 2019

Aug. 14, 2019

Dear all, Please below find the final proposed agenda for the GNSO Council Meeting on 22 August 2019 at 12:00 UTC Final GNSO Council Agenda 22 August 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/Ba_jBg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf> 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 12:00 UTC Coordinated Universal Time: 12:00 UTC: https://tinyurl.com/y2qdox2m 05:00 Los Angeles; 08:00 Washington; 13:00 London; 17:00 Islamabad; 21:00 Tokyo; 22:00 Melbourne GNSO Council Meeting Audio Cast Listen in browser: http://stream.icann.org:8000/stream02 <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream02.m3u <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> 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<https://gnso.icann.org/sites/default/files/policy/2019/minutes/Draft%20minu…> of the GNSO Council meeting on the 26 June 2019 were posted on the 13 July 2019 Minutes<https://gnso.icann.org/sites/default/files/policy/2019/minutes/draft-minute…> of the GNSO Council meeting on the 18 July 2019 were posted on the 02 August 2019 Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (0 minutes) * None 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<https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-t…> 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<https://mm.icann.org/pipermail/council/2019-May/022754.html>, 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. During the Council’s July 2019 meeting, the Council reviewed the draft letter to be sent to the ICANN Board and the EPDP Team. Based on the input received during the call as well as subsequently on the mailing list, Council leadership circulated a revised version for review on [date]. Here, the Council will review the revised letter to be sent to the ICANN Board. 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 – Overview of updates made (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<https://gnso.icann.org/sites/default/files/file/field-file-attach/marby-to-…> 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)<https://whois.icann.org/en/whoisars>.” 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. During its meeting on 18 July 2019, the Council had an initial exchange of views on this topic which continued on the mailing list. Here the Council will take into consideration the input provided and decide how to substantively respond to the questions and concerns from ICANN Org. 5.1 – Introduction of topic (Council leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION – ICANN Board referrals of CCT-RT recommendations to GNSO Council and GNSO PDP WGs (15 minutes) On 10 June 2019, ICANN org communicated to the GNSO Council that the ICANN Board resolution passed on 1 March 2019 – see https://www.icann.org/resources/board-material/resolutions-2019-03-01-en [icann.org]<https://www.icann.org/resources/board-material/resolutions-2019-03-01-en%20…> - 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). The Council was specifically invited to review to pages 1-4 of the scorecard https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scor…<https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scor…> which compile pass-through recommendations, including the groups they are addressed to. The recommendations the ICANN Board resolved to pass through to the GNSO Council, in whole or in part, for its 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”. The Board noted in its resolution that: “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” A small group of Council volunteers reviewed the recommendations passed through to the GNSO Council as well as 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, the GNSO Chair is planning to write to the leadership of the Working Groups seeking their feedback. An initial draft with the small team's proposed GNSO Council response to those 5 Recommendations passed through directly to the GNSO were circulated to the GNSO Council on 23 July for review and consideration [https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-…] Here the Council will consider the initial draft and receive an update on the feedback received from the PDP WGs to which recommendations were also passed through. 6.1 – Introduction of topic (Pam Little) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - ICANN Org assumptions for new round of new gTLDs (15 minutes) 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’s final report and recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. In the course of ICANN org’s 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 were shared with the ICANN Board and on 17 June these were also shared with all ICANN constituencies, including the GNSO Council [https://gnso.icann.org/en/correspondence/pre-engagement-comms-assumptions-p…] ICANN org noted that if the GNSO Council members are also interested in further engagement and providing feedback and perspective on these assumptions GDD would be happy to arrange a mutually convenient time for a discussion. This is an opportunity for the GNSO Council to ask possible clarifying questions, consider the assumptions and determine whether the GNSO Council would want to provide further feedback. 7.1 – Introduction of topic (GDD Cyrus Namazi & Trang Nguyen) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Proposed Amendments to Consensus Policy Implementation Framework (CFIP) (15 minutes) The Consensus Policy Implementation Framework (CPIF) represents ICANN org’s Global Domains Division’s “roadmap” for implementing community-developed and approved consensus policy recommendations. Point H of the Framework mandates that ICANN org “continually review the implementation framework and related materials to encapsulate additional best-practices or to adjust the steps as a result of lessons learned with previous consensus policy projects.” In accordance with this mandate, please find attached an amended version of the CPIF for your consideration. On 12 July 2019, ICANN org shared a proposed set of amendments focusing on establishing standardized processes for post-implementation consensus policy reviews and for amending the CPIF document on an ongoing basis with the GNSO Council [https://gnso.icann.org/sites/default/files/file/field-file-attach/gdd-conse…] In addition to a number of minor language updates, the following sections have been added to or created: 1. Section V, “Support and Review”: Section expanded to reference the proposed post-implementation consensus policy review process added in the new Section VI 2. Section VI, “Post-Implementation Consensus Policy Review Process”: New section added to detail proposed steps for carrying out reviews of implemented consensus policies 3. Section VII, “Consensus Policy Implementation Framework Amendment Process”: New section added to detail proposed steps for amending the CPIF Similar to ICANN org’s effort last year to update the framework and “test” the amendment process, minor updates have been left as redlines throughout the document; more substantive changes are shown as redlines and have “rationale” comments associated with them. The amended version will ultimately be posted to icann.org’s implementation page at https://www.icann.org/policy/implementation [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_policy_i…>. Here the GNSO Council will have an opportunity to review the proposed amendments and provide feedback. 8.1 – Introduction of topic (Brian Aitchison, GDD) 8.2 – Council discussion 8.3 – Next steps Item 9 - PDP 3.0 Small Group Update/Discussion (15 minutes) The PDP 3.0 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 sent 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…> Here the GNSO Council will consider the documents for four (4) completed PDP 3.0 improvements. 9.1 - Introduction of topic (Rafik Dammak) 9.2 - Council discussion 9.3 - Next steps Item 10: ANY OTHER BUSINESS (10 minutes) 10.1 - ICANN66 Draft Schedule Review & travel booking reminder 10.2 - GNSO Strategic Planning Session January 2020 10.3 - Confirmation of volunteers for Council liaisons to PDP/IRTs beginning at the AGM 10.4 - EPDP Phase 2 Work plan package (see https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phas…) _______________________________ 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. 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… 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 05:00 San José, Costa Rica (CST) UTC-6 06:00 New York/Washington DC, USA (EDT) UTC-4 08:00 Buenos Aires, Argentina (ART) UTC-3 09:00 Rio de Janeiro, Brazil (BRT) UTC-3 09:00 London, United Kingdom (GMT) UTC+1 13:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 13:00 Paris, France (CET) UTC+2 14:00 Moscow, Russia (MSK) UTC +3 15:00 Islamabad, Pakistan (PKT) UTC+5 17:00 Singapore (SGT) UTC+8 20:00 Tokyo, Japan (JST) UTC+9 21:00 Melbourne, Australia (AEDT) UTC+11 22: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<http://www.timeanddate.com/> and https://tinyurl.com/y2qdox2m

1 0

EPDP-Phase 2 Project Management and Work Plan Package
by Rafik Dammak Aug. 13, 2019

Aug. 13, 2019

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 <https://docs.google.com/spreadsheets/d/179ocCF6XHK48CJaFF4Rdg9T3atQKFeY51zw…> . 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