March 2021 - council - lists.icann.org

FW: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart
by philippe.fouquart＠orange.com 16 Mar '21

16 Mar '21

Dear Councillors, Please note the attached correspondence, with a specific emphasis for those on the SSAD small team that will take part in our call later today. Regards, Philippe -------- Message d'origine -------- De : Wendy Profit via Gnso-chairs <gnso-chairs(a)icann.org> Date : 16/03/2021 17:51 (GMT+01:00) À : gnso-chairs(a)icann.org, gnso-secs(a)icann.org Cc : Maarten Botterman <maarten.botterman(a)board.icann.org>, Secretary <secretary(a)icann.org>, Correspondence <Correspondence(a)icann.org>, Board Ops Team <board-ops-team(a)icann.org> Objet : [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Philippe Fouquart Dear Philippe Fouquart, Please find the attached letter from Maarten Botterman regarding the recent discussions on the Standardized System for Access/Disclosure (SSAD) from 22 February 2021. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _________________________________________________________________________________________________________________________ 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

**Don't forget to register!** ICANN70: GNSO Sessions - How to Get Organized and Remote Participation Details
by Julie Bisland 16 Mar '21

16 Mar '21

Dear all, All ICANN70 GNSO sessions have been listed for your reference on the ICANN70 GNSO wiki page. For all access information and Zoom details however, please refer to the ICANN70 schedule on the meeting website. Registration is compulsory to access the meeting schedule. Information can be found on this page [events.icann.org]<https://urldefense.com/v3/__https:/events.icann.org/ICANNEventsPortal/icann…> or follow instructions below. Access information will not be circulated via mailing lists. The ICANN meeting website, which ICANN Meetings’ Team has put together, allows you to download all GNSO-related meetings to your inbox calendar in one go. HOW TO DOWNLOAD ICANN70 SESSION INFORMATION TO YOUR CALENDARS: Step 1 - Create a profile and your personalized ICANN70 schedule Go to the Meeting Schedule webpage [70.schedule.icann.org]<https://urldefense.com/v3/__https:/70.schedule.icann.org/__;!!PtGJab4!tqxc8…> and create a profile and login. Every session on the Full Agenda can be selected and added to your individual schedule by clicking the [cid:image001.png@01D71A47.EEEF9D80] in the upper right corner of each meeting. This adds it to your individual schedule, My Agenda, which you can then add to your calendar. See next step. Step 2 - To import your schedule into your calendar: once you’ve added all your chosen meetings to your schedule, click on [cid:image002.png@01D71A47.EEEF9D80] (View My Agenda) * Click the down arrow next to Export * Select Export My Agenda (ics) * Open the exported meetings .ics and add to your chosen calendar * For Microsoft Outlook, right-click on the exported meetings .ics file and choose Show in Folder Right-click on the file, and select Open with Microsoft Outlook. Save & Close. Note: Your Agenda can only be exported from the desktop app; the ICANN70 phone app does not offer this feature Step 3 - All remote participation sessions will use Zoom rooms. You can find the Zoom room links for public meetings on the ICANN70 Meeting Schedule [70.schedule.icann.org]<https://urldefense.com/v3/__https:/70.schedule.icann.org/agenda*/?limit=20&…>. PLEASE ENSURE YOU HAVE UPDATED YOUR ZOOM APP TO THE LATEST VERSION TO ACCESS ICANN70 SESSIONS. Please download the latest Zoom app [zoom.us]<https://urldefense.com/v3/__https:/zoom.us/download__;!!PtGJab4!tqxc8RJNnQI…> on your participation device (mobile or desktop computer). Need to learn or brush-up on using Zoom? Check out the Joining a Zoom Meeting Tutorial [support.zoom.us]<https://urldefense.com/v3/__https:/support.zoom.us/hc/en-us/articles/201362…>. Step 4 - Download the mobile app by searching for “ICANN Meetings” in your app stores. There are three options to connect your audio: 1) Via VoIP, choose Computer Audio (from a smartphone choose Call using Internet Audio) 2) Getting a dial out from Zoom to your phone, choose Call Me (from a smartphone choose Call My Phone) 3) Phoning into the audio bridge (access numbers and Meeting ID are provided for that option), choose Telephone Audio (from a smartphone choose Dial in) Registration is compulsory to access the meeting schedule. Access information will not be circulated via mailing lists. 1- REGISTRATION: Information can be found on this page [events.icann.org]<https://urldefense.com/v3/__https:/events.icann.org/ICANNEventsPortal/icann…> or follow instructions below. Please go to this link via an Incognito page if using Google (FILE/NEW INCOGNITO WINDOW): https://events.icann.org/icann70/registration [events.icann.org]<https://urldefense.com/v3/__https:/events.icann.org/icann70/registration__;…> 2- SCHEDULE ACCESS: Once you are registered, you will receive two emails: 1. The first email will be your registration confirmation within the next 5-10 minutes. 2. The second email will come within 15-30 minutes, and provide your access link to https://70.schedule.icann.org [70.schedule.icann.org]<https://urldefense.com/v3/__https:/70.schedule.icann.org/__;!!PtGJab4!tqxc8…>. The second email will contain a link asking you to "Claim your account". Please follow the steps to create a password for this event, which is not the same as your registration password (for security purposes), previous event passwords will also not work. Access and ability to log into the schedule platform can take up to 30 minutes after completing the registration process. Important Note: Participation links will be posted 24-hours prior to the session start times for security purposes. 3 LINKS TO BOOKMARK NOW: ICANN70 Meeting Schedule [70.schedule.icann.org]<https://urldefense.com/v3/__https:/70.schedule.icann.org/__;!!PtGJab4!tqxc8…> GNSO ICANN70 Wiki Page<https://community.icann.org/x/HINeCQ> GNSO Session agendas<https://community.icann.org/x/AgxACQ> For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team

1 0

Agenda for GNSO and GAC session at ICANN70
by philippe.fouquart＠orange.com 16 Mar '21

16 Mar '21

Dear Councilor, The following has been agreed with the GAC as our agenda for the ICANN70 session: 1. EPDP/ (Phase 2 and 2a) / SSAD 2. DNS Abuse 3. Accuracy Scoping Team 4. Next steps on collaborating on Subsequent Procedures of New gTLDs Regards, Philippe _________________________________________________________________________________________________________________________ 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.

2 1

Motion: Approval of the Charter for the Working Group to Conduct a Policy Development Process to Review the Transfer Policy
by PAMELALITTLE 15 Mar '21

15 Mar '21

Dear GNSO Council colleagues, On behalf of the Council small team (Olga, Carlton, Greg and myself), please find a final version of the Charter for the Working Group to Conduct a Policy Development Process to Review the Transfer Policy (" Charter"). We thank the GNSO Council Liaison to the GAC and Council members who provided input regarding the composition of this PDP Working Group. We have considered all the input received and revised previously proposed composition as follows (see page 16 of the Charter): "Membership Structure The membership structure of this PDP is based on a representative model taking into account the unique characteristics of this Working Group, including, expertise and technical knowledge of the Transfer Policy, interest in the topic and impact of PDP outcome. However, the composition of this Working Group should not serve as a precedent for the composition of future PDP Working Groups, in particular with respect to the number of members representing each SO/AC/SG/C. *Note that some groups may choose not to appoint any members to the WG. The table below indicates the maximum number of members and alternates that groups may appoint. Group Members Alternates RrSG 10 10 RySG 3 3 IPC 2 2 BC 2 2 ISPCP 2 2 NCSG 2 2 GAC 2 2 ALAC 2 2 SSAC 2 2 RSSAC 2 2 ccNSO 2 2 ASO 2 2" I now submit the attached motion for the Approval of the Charter to be considered at the GNSO Council meeting on March 24, 2021 at 17:30 UTC. Respectfully submitted, Pam Little

3 3

Motion - IANA Naming Functions Contract Amendment
by PAMELALITTLE 15 Mar '21

15 Mar '21

Dear Councilors, Please find the attached motion for the Approval of Recommendation 4 in the IFR Final Report regarding IANA Naming Functions Contract Amendment to be considered at the GNSO Council meeting on March 24, 2021 at 17:30 UTC. Respectfully submitted, Pam Little

4 3

GNSO Council Program Suite - 24 March 2021
by policy＠bacinblack.com 15 Mar '21

15 Mar '21

Dear all, Please find attached links to the latest version of the GNSO Council's Program Suite for the meeting on 24 March 2021. Per the agenda, the Council will not review these tools in detail. However, after your preliminary review in advance of the meeting and should you find an area that you have questions or parts that need clarification, please send your questions or comments to the mailing list. Agenda: * https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+GNSO+ Council+Agenda+24+March+2021 Links to the Program Suite: * Program/Project Management Framework: https://community.icann.org/x/0YvzC * Program Management Tool (PMT): https://community.icann.org/x/04vzC * Action/Decision Radar (ADR): https://community.icann.org/x/14vzC * Project List (PL): https://community.icann.org/x/1YvzC * Action Items (AIs): https://community.icann.org/x/RgZlAg Key Structural Changes for this Period: * An ask from the last SPS was to better understand how all the Program/Project tools work together. On the Program/Project Management <https://community.icann.org/x/0YvzC> wiki page, you will now find a high-level description of the framework and a diagram that demonstrates the parent-child relationship of Programs to Projects and how the work products supporting both compliment the framework. * Each program suite wiki page now includes a high-level description of the work product in addition to links of the latest work products. Key Project Changes for this Period: * Transfer policy - Adoption of Charter * Status update on EPDP-P2A * Introduction to EPDP-P1 IRT Wave 1.5 report findings and what that means for IRTs of PPSAI + T&T * ICANN Org briefing document on Registration Data Accuracy * Continued discussions on Framework on Continuous Improvement (ATRT3, GNSO3 Review, etc.) Key Project Activities for April 2021 (ADR): * Call for Volunteers to the PDP on Transfer Policy * SSR2 public comment * RPM Phase 1 - public comment for Board consideration * IGO_CRWT work plan * EPDP-P2 Financial + ODP & SubPro ODP * EPDP-P1 IRT Wave 1.5 report findings and what that means for IRTs of PPSAI + T&T * ICANN Org briefing document on Registration Data Accuracy * Continued discussions on Framework on Continuous Improvement (ATRT3, WS2, GNSO3 Review, etc.) Thank you. 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/>

3 2

FW: [Ext] Monday, 15 March 2021
by Andrea Glandon 15 Mar '21

15 Mar '21

[http://r20.rs6.net/on.jsp?ca=f13fb415-41fc-4bf0-8ccc-83cc2f16de30&a=1122025…] Monday, 15 March 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing · NEW: ICANN70 Topics or Questions for Joint Meetings with the ICANN Board · REMINDER: ICANN Nominating Committee Application Period Now Open · REMINDER: ICANN Community Excellence Award Nomination Period Now Open ICANN70 Resources · REGISTER · PREPARE: Prep Week sessions · PREPARE: Policy Outlook Report · PREPARE: GNSO Policy Briefing · PARTICIPATE: Virtual Backgrounds · PARTICIPATE: How-To Guides · PARTICIPATE: Networking Tools Public Comment · CLOSING IN ONE WEEK: IANA Naming Function Review: Recommendation for an IANA Naming Function Contract Amendment · EPDP Phase 2 Policy Recommendations for Board Consideration · Second Security, Stability, and Resiliency (SSR2) Review Team Final Report · Initial Report of the Third ccNSO Policy Development Process (ccPDP3): Retirement of ccTLDs · Proposal for Korean Root Zone Label Generation Rules Information Sharing NEW: ICANN70 Topics or Questions for Joint Meetings with the ICANN Board Please refer to this workspace [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> for a compilation of topics or questions from ICANN community groups for discussion with the ICANN Board as part of ICANN70 Virtual Community Forum programming. REMINDER: ICANN Nominating Committee Application Period Now Open The ICANN Nominating Committee invites interested individuals to submit applications for key leadership positions. Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the Internet's technical coordination and policy development. The deadline to submit applications is Monday, 29 March 2021 at 23:59 UTC. Applications should be submitted via the online [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…>candidate portal [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…>. All applications are confidential. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> REMINDER: ICANN Community Excellence Award Nomination Period Now Open From: David Olive, Senior Vice President, Policy Development Support The nomination period for the ICANN Community Excellence Award 2020 is now open. The winner(s) will be announced during ICANN71. The ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within ICANN’s multistakeholder model. Learn more about the nomination process [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> and submit your nominations here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> by Monday, 29 March 2021. ICANN70 Resources REGISTER [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> PREPARE: Prep Week sessions [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> PREPARE: Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> PREPARE: GNSO Policy Briefing [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> PARTICIPATE: Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> PARTICIPATE: How-To Guides PARTICIPATE: Networking Tools [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> Public Comment CLOSING IN ONE WEEK: IANA Naming Function Review: Recommendation for an IANA Naming Function Contract Amendment [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> Close Date: Monday, 22 March 2021 EPDP Phase 2 Policy Recommendations for Board Consideration [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> Close Date: Tuesday, 30 March 2021 Second Security, Stability, and Resiliency (SSR2) Review Team Final Report [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> Close Date: Thursday, 8 April 2021 Initial Report of the Third ccNSO Policy Development Process (ccPDP3): Retirement of ccTLDs [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> Close Date: Wednesday, 14 April 2021 Proposal for Korean Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> Close Date: Thursday, 15 April 2021 Volume 3, Issue 21 | Archive [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001xanPBiooWo3PIV4ee…> | Next Issue: Thursday, 18 March 2021

1 0

Final Proposed Agenda | GNSO Council Meeting 24 March 2021 at 17:30 UTC
by Andrea Glandon 15 Mar '21

15 Mar '21

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 24 March 2021 at 17:30 UTC. Draft GNSO Council Agenda 24 March 2021 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/jgxACQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 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 17:30 UTC (12:30 local time) Coordinated Universal Time: 17:30 UTC: https://tinyurl.com/2dc33d7k 10:30 Los Angeles; 13:30 Washington; 17:30 London; 18:30 Paris; 20:30 Moscow; (Thursday) 04:30 Melbourne GNSO Council Meeting Remote Participation: 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/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 21 January 2021 were posted on 4 February 2021. Minutes<https://gnso.icann.org/sites/default/files/policy/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 18 February 2021 were posted on 4 March 2021. Item 2: Opening Remarks / Review of Projects & Action List (0 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 (5 minutes) * Confirmation of the Recommendations Report to the ICANN Board regarding adoption of relevant Outputs from the New gTLD Subsequent Procedures PDP. Item 4: COUNCIL VOTE - IANA Naming Functions Contract Amendment (10 minutes) The Internet Assigned Numbers Authority (IANA) Naming Function Review Team (IFRT) Final Report contains a recommendation that requires GNSO Council action. The IFR is an evaluation of Public Technical Identifiers (PTI) performance of the IANA naming function against the contractual requirements in the IANA Naming Function Contract<https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30s…> and the IANA Naming Function SOW<https://pti.icann.org/iana-naming-function-services-service-level-agreements>. The IFR Review Team's Recommendation 4 (page 5 of the IFR Final Report<https://community.icann.org/pages/viewpage.action?pageId=120819021&preview=…> [PDF, 2.2MB]) calls for an amendment to Article 7, Section 7.1 (a) of the IANA Naming Function Contract. Pursuant to ICANN Bylaws Article 18.6 (iv)<https://www.icann.org/resources/pages/governance/bylaws-en/#article18>, there must be "public comment<https://www.icann.org/public-comments/iana-naming-function-contract-amend-2…> on the amendments that are under consideration by the IFRT through a public comment period that complies with the designated practice for public comment periods within ICANN." In addition, Article 18.6 (b) requires that in order for the recommendation of the IFRT that amends the IANA Naming Function Contract or IANA Naming Function SOW to become effective, one of the requirements is for GNSO approval by a Supermajority. The IANA Naming Function Contract<https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30s…> currently states at Article VII, Section 7.1 (a): Audits: “Contractor shall generate and publish via the IANA Website a monthly audit report identifying each root zone file and root zone “WHOIS” database change request and its status. The relevant policies under which the changes are made shall be noted within each monthly report. Such audit report shall be due to ICANN no later than 15 calendar days following the end of each month.” The IFRT recommends that this statement, "The relevant policies under which the changes are made shall be noted within each monthly report" be removed from the contract. Per the letter<https://gnso.icann.org/sites/default/files/file/field-file-attach/neves-sam…> from the Co-chairs of the IANA Naming Function Review (IFR), “This section refers to the Root Operations Audit Reports (https://www.iana.org/performance/root-audit) which is published monthly by PTI. This statement, carried over from the contract between ICANN and NTIA, is no longer required; further, implementation of this requirement has long been recognised as being operationally impracticable, as a single change request cannot be traced back to a single relevant policy. The IFRT is satisfied that there is no value to this statement remaining in the IANA Naming Function Contract, as the referenced line adds no value to the reports.” Here, the Council will vote to approve the IFRT Recommendation 4. 4.1 – Presentation of the Motion<https://community.icann.org/x/lQxACQ> (TBD) 4.2 – Council discussion 4.3 – Council vote (voting threshold: supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws, as a GNSO Supermajority is one of the required elements to allow for an amendment to either the IANA Naming Function Contract, IANA Naming Function SOW or CSC Charter, as set forth these Bylaws’ (Art.18.6). Item 5: COUNCIL VOTE - Charter for the Transfer Policy PDP (10 minutes) During its February Council meeting, the GNSO Council resolved<https://gnso.icann.org/en/council/resolutions/2021#202102> to initiate a PDP on the Transfer Policy, while also determining that further time was needed to draft the charter. The Preliminary Issue Report included a draft charter, which was included in the public comment proceeding. That draft charter is also included in the Final Issue Report, Annex A<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-iss…>. Comment on the draft charter was solicited from Councilors via a pre-recorded webinar <https://community.icann.org/x/J4FeCQ> prior to this Council meeting. A small team of Councilors was convened to refine the charter, focusing primarily on the membership structure. After receiving input from various communities, the small team proposed a representative structure that it believes allows for appropriate levels of participation. Here, the Council will vote to approve the Charter. 5.1 – Presentation of the Motion<https://community.icann.org/x/lQxACQ> (Pam Little, GNSO Council Vice-Chair) 5.2 – Council discussion 5.3 – Council vote (voting threshold: an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A: GNSO Policy Development Process of the ICANN Bylaws. Item 6: COUNCIL DISCUSSION - Nominating Committee Outreach Subcommittee Outreach (10 minutes) The Nominating Committee (NomCom) initiated<https://www.icann.org/news/announcement-2021-01-25-en> its application process on 25 January 2021 (with the deadline extended<https://www.icann.org/news/announcement-2021-02-23-en> to 29 March 2021). For this cycle, the NomCom will be selecting two members of the GNSO Council, one representing the Contracted Parties House and one representing the Non-Contracted Parties House. The GNSO Council provided updated criteria<https://www.icann.org/en/system/files/files/gnso-council-criteria-2021-29ja…> to the NomCom in January 2021. Here, the NomCom Outreach Subcommittee will provide information about the NomCom panel, about the positions being filled for the GNSO Council, and answer questions that the Council might have. 6.1 - Introduction of topic (NomCom Outreach Subcommittee) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION – Status Update Regarding EPDP Phase 2A (20 minutes) On 21 October 2020, the GNSO Council approved the initiation<https://gnso.icann.org/en/council/resolutions/2020#202010> of EPDP Phase 2A, to examine the topics of legal/natural and feasibility of unique contacts. In doing so, the Council required that: "[a]t the latest 3 months after reconvening, the Chair of the EPDP Team and GNSO Council Liaison to the EPDP will report back to the GNSO Council on the status of deliberations. Based on this report, which is expected to include an update on progress made and the expected likelihood of consensus recommendations, the GNSO Council will decide on next steps, which could include providing additional time for the EPDP to finalize its recommendations or termination of the EPDP if it is clear that no progress is being made or consensus is unlikely).” Here, the Chair of the EPDP Team and GNSO Council Liaison to the EPDP will provide an update to the Council. 7.1 – Introduction of topic (EPDP Team Chair, Keith Drazaek and GNSO Council Liaison to the EPDP, Philippe Fouquart) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL UPDATE - EPDP Phase 1 Rec 27 (Wave 1.5) (10 minutes) Recommendation 27 from the EPDP Phase 1 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…>, “... recommends that as part of the implementation of these policy recommendations, updates are made to the following existing policies / procedures, and any others that may have been omitted, to ensure consistency with these policy recommendations as, for example, a number of these refer to administrative and/or technical contact which will no longer be required data elements.” In support of this recommendation, ICANN org prepared the Wave 1 report, an updated version of which was shared with the Council on 19 February 2020. ICANN org has performed additional analysis for recommendation 27, resulting in the Wave 1.5 Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-epd…> that focuses on Privacy and Proxy Services Accreditation Issues (PPSAI) and Translation and Transliteration of Contact Information (T/T) policy recommendations, for which implementation has been started but not completed. For the Wave 1 Report, the staff support team conducted a first analysis of the report, identifying possible next steps for Council consideration that the Council subsequently reviewed to determine next steps. The Council may elect to follow a similar approach to the Wave 1.5 Report, to determine appropriate next steps. Here, the Council will discuss the Wave 1.5 Report. 8.1 – Introduction of topic (Council Leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: Council Discussion - Debrief on the Consultation with the ICANN Board on the Financial Sustainability of the SSAD (15 minutes) In the adoption<https://gnso.icann.org/en/council/resolutions/2020#202009> of the Expedited Policy Development Process (EPDP) on the Temporary Specification Phase 2 Final Report and Recommendations, the Council resolved that: “Noting some of the questions surrounding the financial sustainability of SSAD and some of the concerns expressed within the different minority statements, the GNSO Council requests a consultation with the ICANN Board as part of the delivery of the GNSO Council Recommendations Report to the ICANN Board to discuss these issues, including whether a further cost-benefit analysis should be conducted before the ICANN Board considers all SSAD-related recommendations for adoption.” The GNSO Council communicated<https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-…> its Recommendations Report to the Board 29 October 2020, in which the Council proposed, “to form a small team consisting of GNSO Council and ICANN Board members to develop a proposed approach and agree on expectations in relation to this consultation.” The ICANN Board responded<https://www.icann.org/en/system/files/correspondence/botterman-to-fouquart-…> on 1 December 2020, stating that it believed the Operational Design Phase (ODP) it envisioned, will help facilitate the consultation with the Council. The Council responded<https://www.icann.org/en/system/files/correspondence/fouquart-to-botterman-…> on 22 January 2021, suggesting that it is more important to agree upon the elements of the operational impact assessment, rather than relying on the ODP framework exclusively. That consultation<https://icann.zoom.us/rec/play/_2k5RrDvtGc-sYFIoR3Cv47dYIZpi2HlgNr-Pik__nBT…> between the Board and the GNSO Council took place on 22 February 2021. The Council will meet with the Board again, connected with ICANN70, on 1 April 2021. There, the Operational Design Phase for the SSAD will be one of the topics for discussion. A small team of Councilors is preparing a letter to be sent to the Board, in advance of the 1 April 2021 meeting, which is expected to be available for this 24 March Council meeting. Here, the Council will hold a debrief on the 22 February consultation and plan for the 1 April meeting. 9.1 – Introduction of topic (Council Leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: COUNCIL DISCUSSION - Introduction to the Briefing Paper on Accuracy Requirements and Programs from ICANN’s Global Domains & Strategy (GDS) (5 minutes) On 4 November 2020, the GNSO Council wrote<https://www.icann.org/en/system/files/correspondence/fouquart-to-swinehart-…> to ICANN org, requesting the preparation of a briefing document outlining both the existing accuracy requirements and programs as well as the impact that GDPR has had on implementing and enforcing the identified requirements and programs. This briefing is intended to inform an accuracy scoping team that the GNSO Council envisioned initiating , which would be tasked with furthering the community’s understanding of the issue and assist in scoping and defining the issue. On 10 December 2020, ICANN org responded<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…> to confirm its understanding of the request and to commit to delivering that briefing by 26 February 2021. ICANN org delivered the briefing<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…> on the 26th. In addition to the briefing providing an overview of accuracy requirements and programs, ICANN org included a suggestion that a study to measure accuracy of registration data might be beneficial. In parallel to the request for the briefing, ICANN SO/AC/SG/Cs were requested to start thinking about whether their groups would be interested to participate in a scoping team once created. To date, the BC, ISPCP, RySG and GAC have expressed an interest and identified potential volunteers with relevant knowledge and expertise. Here, the Council will discuss next steps as it relates to the briefing as well as the scoping team. 10.1 – Introduction of topic (Council Leadership) 10.2 – Council discussion 10.3 – Next steps Item 11: COUNCIL DISCUSSION - GNSO Council Consideration of SAC114 (5 minutes) On 15 February 2021, the SSAC shared<https://mm.icann.org/pipermail/council/2021-February/024465.html> SAC114<https://gnso.icann.org/sites/default/files/file/field-file-attach/ssac-comm…> with the GNSO Council, which are the Security and Stability Advisory Committee (SSAC)’s comments on the New gTLD Subsequent Procedures PDP’s Draft Final Report, but are directed at the ICANN Board for its consideration. While the comments are directed at the ICANN Board, they pertain to the work of the GNSO and as a result, the Council may benefit from considering SAC114 and formulating its impressions of the recommendations. Here, the Council will consider SAC114 and discuss next steps, if any. 11.1 – Introduction of topic (Council Leadership) 11.2 – Council discussion 11.3 – Next steps Item 12: COUNCIL DISCUSSION - GNSO Framework for Continuous Improvement (5 minutes) The GNSO Council has sought an approach to address work that focuses on GNSO structural, procedural and process improvement related work. The proposal from Council leadership is to create a GNSO Framework for Continuous Improvement that will help provide structure to manage the numerous non-PDP related efforts residing on the Council’s Action Decision Radar (ADR). An overview<https://mm.icann.org/pipermail/council/2021-January/024395.html> was developed and shared on 20 January 2021. Based on initial feedback from Councilors and other GNSO stakeholders, a much more detailed draft document was prepared and shared<https://mm.icann.org/pipermail/council/2021-March/024508.html> on 2 March 2021, which provides additional information about the structure and potential work assignments. Input was sought from the Council and SG/C Chairs. Here, the Council will consider whether the framework serves as an appropriate path forward, as well as relevant next steps. 12.1 – Introduction of topic (Council Leadership) 12.2 – Council discussion 12.3 – Next steps Item 13: ANY OTHER BUSINESS (10 minutes) 13.1 - Open Microphone _______________________________ 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 17:30 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 10:30 San José, Costa Rica (CST) UTC-6 11:30 New York/Washington DC, USA (EDT) UTC-4 13:30 Buenos Aires, Argentina (ART) UTC-3 14:30 Rio de Janeiro, Brazil (BRST) UTC-3 14:30 London, United Kingdom (GMT) UTC+0 17:30 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 18:30 Paris, France (CEST) UTC+1 18:30 Moscow, Russia (MST) UTC+3 20:30 Singapore (SGT) (+1 day) UTC+8 01:30 Melbourne, Australia (AEDT)(+1 day) UTC+11 04:30 ---------------------------------------------------------------------------- DST starts/ends on Sunday 28 March 2021, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 14 March 2021 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/2dc33d7k

2 1

Re: [council] [Ext] Re: REMINDER: For review - GNSO Framework for Continuous Improvement
by Julie Hedlund 15 Mar '21

15 Mar '21

Dear Wolf Ulrich, Thank you for the helpful update, it is very much appreciated. We understand that your group may need some additional time to gather feedback. As such, we would be grateful if you could provide us with a date by which you expect this feedback to be provided so that we can plan accordingly. With regards to the 'rush', it may be helpful to note that the projects the proposed framework intends to address have already been on the top of the Council's Action Decision Radar for a while now (see https://community.icann.org/x/14vzC for the latest version) and the Council is eager to abide by its planning. If the proposed framework is not the path chosen to address these projects, the Council and GNSO community will need to urgently think of an alternative approach, which is why this topic has been added to the Council agenda for the meeting on 24 March, so that the Council can consider feedback received and appropriate next steps. We hope this explanation provides further clarification. Kind regards, Julie From: Wolf-Ulrich Knoben <wuknoben(a)gmail.com> Date: Sunday, March 14, 2021 at 7:52 AM To: Julie Hedlund <julie.hedlund(a)icann.org> Cc: GNSO Council List <council(a)gnso.icann.org>, Heather Forrest <haforrestesq(a)gmail.com>, "Selli, Claudia" <claudia.selli(a)intl.att.com>, Wolf-Ulrich Knoben <wolf-ulrich.knoben(a)t-online.de>, Bruna Martins dos Santos <bruna.mrtns(a)gmail.com>, Raoul Plommer <plommer(a)gmail.com>, Raphaël Beauregard-Lacroix <rbeauregardlacroix(a)gmail.com>, "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, "Demetriou, Samantha" <sdemetriou(a)verisign.com>, "chair(a)rysg.info" <chair(a)rysg.info>, Sue Schuler <secretariat(a)rysg.info>, Zoe Bonython <secretariat(a)icannregistrars.org>, Brenda Brewer <brenda.brewer(a)icann.org>, "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org>, Tony Holmes <tonyarholmes(a)btinternet.com> Subject: [Ext] Re: REMINDER: For review - GNSO Framework for Continuous Improvement Dear Julie, due to technical reasons I just recently got aware of your email sticking in my spam folder. I’ve communicated with my colleagues already but – frankly speaking – we shall be not able to provide reliable input by 15 March<x-apple-data-detectors://4>. Moreover in cross-reading the document and taking into consideration the discussion around the former first draft we fail to understand the rush to get this on the next Council agenda. It will still require some deliberation within the community. As soon as we have taken a more in depth look at the document we’ll get back to you with hopefully some helpful comments. Best regards Wolf-Ulrich Von meinem iPhone gesendet Am 11.03.2021 um 21:55 schrieb Julie Hedlund <julie.hedlund(a)icann.org>: Dear Councilors and SG/C Chairs, Please see the message below. As a reminder, we would like to request your input on the questions below by 15 March so that the Council may be able to take a decision on the path forward during the next Council meeting on 24 March. As noted in Philippe’s email of 20 January (see https://mm.icann.org/pipermail/council/2021-January/024395.html), the staff support team has worked with the Council leadership team on a more detailed proposal for a GNSO Framework for Continuous Improvement that you will find attached to this email. The objective of the framework is to put in place an approach and structure that allows for the continuous scoping and execution of projects that are focused on GNSO structural, procedural and process improvements. The document analyzes and proposes a number of specific assignments in relation to the different projects that pertain to the scope of this effort from the Action Decision Radar (ADR) (https://community.icann.org/x/14vzC). It also proposes a possible way of organizing these assignments into task forces of a thematic nature. The document does not opine on the priority order in which these are expected to be addressed. Following your review of this document, we would like to request your input on the following: 1. With the details provided, does this framework approach make sense for dealing with some of the immediate priorities on the ADR as well as future projects that relate to structural, procedural and process improvements? If not, why not and what would be your proposed alternative? 2. Are there any aspects of the framework that can be further enhanced? If so, please provide further details. 3. Are there any assignments that are missing or should be modified? 4. Does the grouping of assignments make sense or is there another way in which assignments should be organized? We look forward to receiving your feedback. Kind regards, Julie From: council <council-bounces(a)gnso.icann.org> on behalf of Julie Hedlund via council <council(a)gnso.icann.org> Reply-To: Julie Hedlund <julie.hedlund(a)icann.org> Date: Tuesday, March 2, 2021 at 3:18 PM To: GNSO Council List <council(a)gnso.icann.org>, Heather Forrest <haforrestesq(a)gmail.com>, "Selli, Claudia" <claudia.selli(a)intl.att.com>, Wolf-Ulrich Knoben <Wolf-Ulrich.Knoben(a)t-online.de>, Bruna Martins dos Santos <bruna.mrtns(a)gmail.com>, Raoul Plommer <plommer(a)gmail.com>, Raphaël Beauregard-Lacroix <rbeauregardlacroix(a)gmail.com>, "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, "Demetriou, Samantha" <sdemetriou(a)verisign.com>, "chair(a)rysg.info" <chair(a)rysg.info>, Sue Schuler <secretariat(a)rysg.info>, Zoe Bonython <secretariat(a)icannregistrars.org> Cc: Brenda Brewer <brenda.brewer(a)icann.org>, "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org> Subject: [council] For review - GNSO Framework for Continuous Improvement Dear Councilors and SG/C Chairs, As noted in Philippe’s email of 20 January (see https://mm.icann.org/pipermail/council/2021-January/024395.html), the staff support team has worked with the Council leadership team on a more detailed proposal for a GNSO Framework for Continuous Improvement that you will find attached to this email. The objective of the framework is to put in place an approach and structure that allows for the continuous scoping and execution of projects that are focused on GNSO structural, procedural and process improvements. The document analyzes and proposes a number of specific assignments in relation to the different projects that pertain to the scope of this effort from the Action Decision Radar (ADR) (https://community.icann.org/x/14vzC). It also proposes a possible way of organizing these assignments into task forces of a thematic nature. The document does not opine on the priority order in which these are expected to be addressed. Following your review of this document, we would like to request your input on the following: 1. With the details provided, does this framework approach make sense for dealing with some of the immediate priorities on the ADR as well as future projects that relate to structural, procedural and process improvements? If not, why not and what would be your proposed alternative? 2. Are there any aspects of the framework that can be further enhanced? If so, please provide further details. 3. Are there any assignments that are missing or should be modified? 4. Does the grouping of assignments make sense or is there another way in which assignments should be organized? In order to move forward with consideration of the framework approach, and especially being able to tackle the different projects that are high on the ADR, we would like to request your input by 15 March so that the Council may be able to take a decision on the path forward during the next Council meeting on 24 March. If it is deemed helpful, the staff support team is also more than willing to set up a call to walk through the document and answer any questions you may have. We look forward to receiving your feedback. Kind regards, Julie Julie Hedlund, Policy Director <GNSO Framework for Continuous Improvement - 2 March 2021[1].pdf>

1 0

DEADLINE TODAY: Document and Motion deadline Sunday 14 March 2021 at 23:59 UTC for GNSO Council Meeting 24 March 2021 at 17:30 UTC
by Nathalie Peregrine 14 Mar '21

14 Mar '21

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday 14 March 2021 at 23:59 UTC) of the GNSO Council Meeting on Wednesday 24 March 2021 at 17:30 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/lQxACQ Thank you. Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) 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…>

1 0