March 2021 - council - lists.icann.org

Confirmation of GNSO Representative on the Empowered Community Administration
by Nathalie Peregrine 20 Oct '22

20 Oct '22

Dear John, Please find the attached a letter with the motion passed at the GNSO Council meeting on 29 November 2018. The Council confirmed the appointment of the GNSO Chair, currently Keith Drazek, representing the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN66. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. 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 taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 4

Letter to ICANN Secretary re interim appointment of the GNSO representative to the Empowered Community Administration
by Nathalie Peregrine 27 Oct '21

27 Oct '21

Dear all, Please find attached the letter informing John Jeffrey and the Empowered Community administration of the interim appointment of Philippe Fouquart as GNSO representative to the Empowered Community administration. The letter will be posted on the Correspondence page[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…> of the GNSO website. 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 taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 1

Motions from Standing Selection Committee for January 2021 GNSO Council Meeting
by Carlton Samuels 20 Oct '21

20 Oct '21

Dear Councilors: I am submitting three motions to be considered in the 21 January 2021 meeting: 1. Appointment of a GNSO Non-Registry Liaison to the Customer Standing Committee; 2. Nomination of a Mentor for the ICANN Fellowship Program; 3. Appointment of a GNSO Representative to the Community Representatives Group that will nominate the Independent Review Process (IRP) Standing Panel. Kind regards, Carlton Samuels ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

6 9

Fwd: ICANN70 GAC Communique.pdf
by Jeff Neuman 05 Apr '21

05 Apr '21

Dear Councilors, Please find enclosed the ICANN70 GAC Communique. This is the first communique in over a year that has GAC Consensus Advice. It also includes follow up on previous GAC Advice. The Advice centers around ePDP Phase 2 and follows up on advice regarding SubPro and IGOs. I would also like to remind the Council of several statements from the ICANN Board at ICANN70 acknowledging that the non-consensus advice is also deemed important by the Board and that they hold intersessional meetings to discuss even the things not designated as GAC Advice. Therefore, we may as a Council, want to consider responding to those items as well (even though we have not done so in the past). I would like to ask for some volunteers that want to assist me on drafting the first response to the Communique. Once that small team is finished with the draft, we can then circulate to the full Council. Sincerely, Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC Jeff(a)JJNSolutions.com +1.202.549.5079 Http://www.jjnsolutions.com ________________________________ From: Jorge.Cancio(a)bakom.admin.ch <Jorge.Cancio(a)bakom.admin.ch> Sent: Monday, March 29, 2021 4:51 AM To: Jeff Neuman Cc: philippe.fouquart(a)orange.com; manal(a)tra.gov.eg Subject: ICANN70 GAC Communique.pdf Dear Jeff Please find attached the finalized GAC Communique for ICANN 70 kindly Jorge

4 3

Re: [council] Fwd: ICANN70 GAC Communique.pdf
by Steve Chan 02 Apr '21

02 Apr '21

Dear Councilors, Thanks Jeff. To assist you and other volunteers in your review of the ICANN70 GAC Communique, staff has put the GAC Consensus Advice to the ICANN Board and Follow-up on Previous Advice into the standard template that the Council has used in the past: https://docs.google.com/document/d/1VRQvT-9lYXsROUaUDnZ9vRq-M1EZeHHeh9EAnsZ…. As Jeff notes, the Council has in the past only elected to provide a response to GAC Advice. For Councilors that may be new to this process, the Council’s review and response in regards to the communique is delivered to the ICANN Board, for the Board to have available when considering the GAC Advice. The Council generally aims to adopt the review of the communique at the subsequent Council meeting, which in this case is the 22 April 2021 meeting (with a 12 April motion and documents deadline). Best, Steve From: council <council-bounces(a)gnso.icann.org> on behalf of Jeff Neuman via council <council(a)gnso.icann.org> Reply-To: Jeff Neuman <jeff(a)jjnsolutions.com> Date: Monday, March 29, 2021 at 5:24 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Fwd: ICANN70 GAC Communique.pdf Dear Councilors, Please find enclosed the ICANN70 GAC Communique. This is the first communique in over a year that has GAC Consensus Advice. It also includes follow up on previous GAC Advice. The Advice centers around ePDP Phase 2 and follows up on advice regarding SubPro and IGOs. I would also like to remind the Council of several statements from the ICANN Board at ICANN70 acknowledging that the non-consensus advice is also deemed important by the Board and that they hold intersessional meetings to discuss even the things not designated as GAC Advice. Therefore, we may as a Council, want to consider responding to those items as well (even though we have not done so in the past). I would like to ask for some volunteers that want to assist me on drafting the first response to the Communique. Once that small team is finished with the draft, we can then circulate to the full Council. Sincerely, Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC Jeff(a)JJNSolutions.com +1.202.549.5079 Http://www.jjnsolutions.com From: Jorge.Cancio(a)bakom.admin.ch <Jorge.Cancio(a)bakom.admin.ch> Sent: Monday, March 29, 2021 4:51 AM To: Jeff Neuman Cc: philippe.fouquart(a)orange.com; manal(a)tra.gov.eg Subject: ICANN70 GAC Communique.pdf Dear Jeff Please find attached the finalized GAC Communique for ICANN 70 kindly Jorge

3 2

For your review: Council SSAD Small Team draft letter
by Caitlin Tubergen 01 Apr '21

01 Apr '21

Dear Councilors, Further to the discussion from today’s meeting, please provide feedback to the draft SSAD letter to the Board by COB Friday, 26 March: https://docs.google.com/document/d/1YjR-YsjqRSTnU0a_bbG3zXUwpeJ7g6cO1kIRudr…. Thank you. Best regards, Caitlin From: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Tuesday, March 23, 2021 at 3:36 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: Council SSAD Small Team draft letter Dear Councilors: Following the Council's recent engagement with the Board regarding the SSAD consultation, the SSAD Small Team worked together to draft a letter<https://docs.google.com/document/d/1YjR-YsjqRSTnU0a_bbG3zXUwpeJ7g6cO1kIRudr…>, confirming the outcomes of the meeting and posing additional questions for the Board's consideration. The letter still has several comments and proposed edits, which have been left in for the sake of transparency (since all commenters may not have had an opportunity to review the most recent edits). For ease of readability, you may wish to review the draft in "viewing" mode to avoid the array of colors. This letter is on the agenda for tomorrow's meeting, and Council leadership will go over it in greater detail tomorrow. We request that you do not make any additional changes to the Google Doc at this time; instead, please express concerns or provide additional comments via the mailing list. Thank you. Best regards, Caitlin

6 8

Operational Design Phase Flow Charts
by Steve Chan 30 Mar '21

30 Mar '21

Dear Councilors, On the GNSO Council call on 24 March 2021, Maxim and others noted that version 3.0 of the Operational Design Phase (ODP) process paper (see blog here: https://www.icann.org/en/blogs/details/advancing-the-operational-design-pha…) no longer included a process flow. I’m happy to inform you all that my colleagues in the Global Domains and Strategy function have developed complementary flow charts to help readers better understand the process paper. Two flow charts are available, the first depicting the ODP within the policy development and implementation life cycle and the second depicting the community consultation process: https://community.icann.org/display/ODP/Version+History If you have any questions, please let me know. Best, Steve Steven Chan  Senior Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

1 0

Expression of Interest open: Chair for the Transfer Policy PDP WG
by Emily Barabas 30 Mar '21

30 Mar '21

Dear Councilors, An announcement was posted on ICANN.org today opening the Expression of Interest process to identify a Chair for the PDP WG to Review the Transfer Policy. Information about the EOI is being distributed through the SO/AC/SG/C leaders, but please feel free to share the announcement with anyone who may be interested: https://www.icann.org/en/announcements/details/call-for-expressions-of-inte… . The deadline to submit an Expression of Interest is Friday 16 April at 23:59 UTC. Kind regards, Emily Emily Barabas Policy Manager, GNSO Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

FW: FOLLOW UP: Process & practice for transmission of GNSO Council Recommendations Reports to the ICANN Board
by philippe.fouquart＠orange.com 30 Mar '21

30 Mar '21

Dear Councillors, During our vote on the Recommendations report last week, we had a discussion about the intended content and triggering points for sending such a report to the board, what’s the rule/practice etc. and staff agreed to provide some clarifications as to what is actually documented and what it isn’t. Mary kindly provided the following note for our review/questions. Regards, Philippe From: Gnso-chairs [mailto:gnso-chairs-bounces@icann.org] On Behalf Of Mary Wong via Gnso-chairs Sent: Thursday, March 25, 2021 3:15 AM To: gnso-chairs(a)icann.org Subject: [gnso-chairs] FOLLOW UP: Process & practice for transmission of GNSO Council Recommendations Reports to the ICANN Board Dear Philippe, Pam and Tatiana, I write to follow up on the discussion during the GNSO Council’s Public Meeting earlier today, about the timeline for transmitting a GNSO Council Recommendations Report to the Board as well as the scope and contents of such a report. I hope that this note is a useful reference for you and the Council regarding the existing process, without presuming whether or if the Council may wish to standardize future practice. As you know, the ICANN Bylaws require that the GNSO Council approve a separate Recommendations Report for delivery to the ICANN Board, after it approves PDP recommendations. Here is some additional information to supplement the staff comments from the call today: * Format and Content: Neither the Bylaws nor the PDP Manual prescribe a particular format or specific contents for a Recommendations Report. However, org staff developed a template a number of years ago that has since been used for all such reports, with sections that describe (among other things) the GNSO Council’s deliberations, whether any external expert advice was sought, and the expected implementation impact (including on parties that will be affected by the recommended policy). As a matter of practice, it has been the exception rather than the norm to include the complete PDP Final Report as part of the Recommendations Report, as it seemed more critical to maintain the conciseness of the latter, especially given the fact that the Board receives and reviews the full Final Report in any event (along with all the public comments submitted during the Public Comment Proceeding held prior to Board action). I’ll also note here that the Recommendations Report typically includes at minimum a link to the full Final Report and the Council’s deliberations. * Timing of Submission to the Board: Neither the Bylaws nor the PDP Manual specify a time frame or deadline for delivery of the report to the Board. Looking at the various PDPs from the last decade, you will see that transmission of the Recommendations Report has sometimes taken place after the mandatory Public Comment Proceeding prior to Board action or, at times, while it is ongoing. More recently, staff has tended to send the Recommendations Reports to the Board before opening the Public Comment Proceeding, in view of the fact that the PDP Manual recommends (but does not require) that the Council take action on the Recommendations Report at its first meeting following its approval of the PDP recommendations “if feasible”. In general, staff strives to transmit all reports and documents as expediently as possible in the circumstances. Of the PDPs that were completed in the last six-plus years, all Recommendations Reports (with the sole exception of RPMs) were generally sent either within a matter of days of Council approval or, in those cases where a Public Comment Proceeding was open prior to the transmission, shortly after the proceeding ended. I hope this information is helpful and also demonstrates that there has never been an instance where ICANN org staff has deviated from the applicable rules and requirements, or sought to artificially prolong or hinder the Board’s process for consideration of GNSO PDP recommendations. Thanks and cheers Mary _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

ACTION REQUIRED - Draft of GNSO Council Comments on SSR2 Final Report
by policy＠bacinblack.com 30 Mar '21

30 Mar '21

Dear all, On behalf of Council leadership, please navigate to the Google doc link below for a draft of comments intended to be submitted on behalf of the GNSO Council regarding the SSR2 Final Report. The public comment was extended to 8 April 2021 and leadership would like suggested adds, changes, or deletes posted by 2 April 2021. Similar to Council comments submitted regarding the draft Budget and Operating Plans each fiscal year, the intent is to compliment and not supersede comments submitted by the SGs/Cs. Council leadership recongnize that several of the SSR2 recommendations are quite contentious, and as you will see with the current draft, it attempts to avoid making statements on the substance of those recommendations. Rather, the comments are more focused on prior work of the GNSO related to DNS Abuse, the formation of a scoping team on accuracy, and that the ICANN Board consider current demands on the GNSO. Link to draft of comments: https://docs.google.com/document/d/1Xe4ru1vr9WqmDlmQuBgHGgczCWE7y-Eo/edit Given that ICANN70 is around the corner, the desire is to handle input and changes to the draft remotely. However, if any of the suggested changes become contentious, leadership will consider forming a quick small-team to resolve them towards getting to a final agreeable version. Therefore, it is imperative that you provide your inputs early and often. Thank you for your attention and inputs. B Berry Cobb GNSO Policy Consultant Principal | <http://bacinblack.com/> BAC in Black Consulting Mob: +1 (720) 839-5735 <https://twitter.com/berrycobb> <https://www.linkedin.com/in/berrycobb/>

2 1