January 2021 - council - lists.icann.org

ICANN News Alert -- ICANN70 Will Be Held as Virtual Community Forum
by Nathalie Peregrine 15 Jan '21

15 Jan '21

[Image removed by sender. ICANN Announcement Alerts] ICANN70 Will Be Held as Virtual Community Forum [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/G2R0Ej203s06C0dP000…> 14 January 2021 LOS ANGELES – 14 January 2021 – The Internet Corporation for Assigned Names and Numbers (ICANN) today announced that the ICANN Board of Directors has made the decision [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/I0207C30P00tNd200j0…> to convene ICANN70 as a Virtual Public Meeting due to the continuing impact of the COVID-19 pandemic. This meeting was initially planned to be held in Cancún, Mexico. In consultation with community leaders, the ICANN70 Virtual Community Forum dates have been modified and the meeting is now scheduled to be held 22-25 March 2021. The health and safety of the ICANN community is always a top priority, and as such, holding ICANN70 as an in-person meeting would not be feasible on its scheduled date. Along with its resolution, the Board details its rationale. A number of challenges to in-person meetings still remain, including uncertainties around the ability and willingness of participants to travel, whether physical distancing requirements are possible to implement, the impact of a potential case among participants, and the progress of the second wave of the virus across the world. The Board fully appreciates the importance of face-to-face interaction and looks forward to a return to in-person ICANN Public Meetings as soon as is practical. The Board has directed ICANN org to work in coordination with the ICANN community to meet the expected outcomes of an ICANN Community Forum and support the community's ongoing priorities, policy advice, and development work in a virtual format. ICANN70 will be the fourth ICANN Virtual Public Meeting since the pandemic began. ICANN org began a community engagement process in September 2020 to consider lessons learned from previous virtual meetings and how those learnings can impact future ICANN Public Meetings. ICANN org will implement several community suggestions to enhance the virtual experience for ICANN70. ICANN thanks our regional partners in Latin America and the Caribbean (LAC) as well as the local host committee in Mexico that worked tirelessly to prepare for this meeting in Cancún. We appreciate their understanding and we look forward to returning to the LAC region in the coming years. Those interested in attending ICANN70 must register [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/SR0E2d03P000NC00200…> to participate. To learn more about the meeting time zone, language interpretation options, and schedule, visit https://70.schedule.icann.org [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/dd0P029Nj00E300R0v0…>. You can sign up to receive ICANN announcements in your inbox here [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/n0C00aw020NP0ER0320…>. For more information, visit the ICANN Meetings website [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/JR2PC00b2E0Nxj30d00…>. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. [Image removed by sender. shadow] [Image removed by sender. Twitter][newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/L002ER0020cj0Cy300P…> [Image removed by sender. Facebook][newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/n0C00dz020NP0ER0320…> [Image removed by sender. Instagram][newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/y2jC300N0d0PERe00A0…> [Image removed by sender. Linkedin][newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/V3RB000dj20E200CP00…> [Image removed by sender. YouTube][newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/dd0P02gNj00E300R0C0…> [Image removed by sender. shadow1] Unsubscribe [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/n0C00hD020NP0ER0320…> | https://www.icann.org [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/r00i0E2j0REP3NC2000…> [newsalerts.icann.org]<https://urldefense.com/v3/__https:/newsalerts.icann.org/Q0jE03R0Cj2P00N2d00…>

1 0

For your review - SSAD Consultation Messaging
by Marika Konings 14 Jan '21

14 Jan '21

Dear Councilors, On behalf of the small team that worked on the proposed messaging to the ICANN Board in relation to the SSAD consultation (Kurt, Stephanie, Marie, Greg, Tom, Jeff, Farell, Philippe, Pam and Tatiana), please find the end result here for your review: https://docs.google.com/document/d/1ZJjYNh12Jq5gN3YLv8CQHZM2jjAkloh2/edit. You are encouraged to provide any comments or concerns you may have by Wednesday 20 January at the latest so that, if any concerns are raised, these can be dealt with during the upcoming Council meeting. Best regards, Marika

1 0

FW: [Ext] Thursday, 14 January 2021
by Julie Bisland 14 Jan '21

14 Jan '21

FYI: From: ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, January 14, 2021 at 9:05 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 14 January 2021 [http://r20.rs6.net/on.jsp?ca=1611b0be-3d44-4bad-b7b9-f0aefaddfb5d&a=1122025…] Thursday, 14 January 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: Changes Coming to Registry Reports on the ICANN Open Data Platform · NEW: ICANN Continues the Pandemic Internet Access Reimbursement Program · NEXT WEEK: Revised Operational Design Phase Concept Paper · REMINDER: Request For Community Selection Panel Participants – 2021 Community Excellence Award Program · REMINDER: FY22 Additional Budget Requests Due Friday, 29 January 2021 · REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members · REMINDER: Volunteers Needed for Advisory Group on ICANN's North America Stakeholder Engagement Plan · REMINDER: Nomination Period for the ICANN Community Excellence Award Now Open Public Comment · Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 · Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget Information Sharing NEW: Changes Coming to Registry Reports on the ICANN Open Data Platform As of 15 March 2021, the ICANN Open Data platform [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> will become the permanent home of Registry Reports [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. Reports to be posted on the platform include the Registry Functions Activity Reports and the Per-Registrar Transactions Reports. With this change, these reports will no longer be available on https://icann.or [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>g [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> as of 15 March 2021. If you have an automated script that downloads registry reports from https://icann.org [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>, you will need to modify your script to use the ICANN Open Data API to download the reports. Before you can access the Open Data platform, you must create an ICANN Account [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. Once you have an account, you will be able to use the Open Data platform API. Learn more [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> NEW: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested community members must apply in advance of ICANN70, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 5 March 2021 at 23:59 Coordinated Universal Time (UTC). The application process will open 8 February 2021 and program details are available here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. The goal of this program is to facilitate participation in ICANN Public Meetings during this global pandemic. It offers community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> NEXT WEEK: Revised Operational Design Phase Concept Paper From: Theresa Swinehart, Senior Vice President, Global Domains & Strategy ICANN org has shared a revised version of the Operational Design Phase Concept Paper [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. The new version follows community consultation during ICANN69, including written feedback by a number of community groups. The concept paper proposes an Operational Design Phase (ODP) that is to become part of the policy and implementation life cycle. The ICANN organization will conduct the ODP for consensus policy recommendations that are approved by the Generic Names Supporting Organization (GNSO) Council. The purpose of the ODP is to provide the Board with relevant information to decide, as required by the Bylaws, whether a recommendation is in the best interest of the ICANN community or ICANN. Please provide your input by Friday, 22 January 2021, to mary.wong(a)icann.org<mailto:mary.wong@icann.org>. REMINDER: Request for Community Selection Panel Participants – 2021 ICANN Community Excellence Award Program From: David Olive, Senior Vice President, Policy Development Support On 1 December 2020, Supporting Organization and Advisory Committee chairs received an email request to provide up to two members from their respective group to help choose the recipient of the 2021 ICANN Community Excellence Award. The deadline to provide names to david.olive(a)icann.org<mailto:david.olive@icann.org> is Monday, 25 January 2021. The 2021 ICANN Community Excellence Award will be presented during ICANN71 in June 2021. A community selection panel will be formed to review the nominations and select the award recipient. Ideally, panelists will serve a maximum of two consecutive terms on the selection panel to ensure diversity and equal opportunity among community members. The time commitment for the selection panel includes weekly one-hour calls between the end of March through June 2021. REMINDER: FY22 Additional Budget Requests Due Friday, 29 January 2021 ICANN org has launched the FY22 Additional Budget Request process. This process pertains to a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities that are not already included in the recurring ICANN budget. Submissions are due on Friday, 29 January 2021 at 23:59 UTC to planning(a)icann.org<mailto:planning@icann.org>. Learn more [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement ICANN has announced [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> a call for nominees to volunteer to serve as mentors to the Fellowship Program and as members to its Selection Committee. There will be a total of seven mentors and seven Selection Committee members, and each group is welcome to nominate one individual for each role. Interested Supporting Organizations and Advisory Committees should select their respective Fellowship Program mentor and Selection Committee representative by Sunday, 31 January 2021 and notify fellowshipconsultation(a)icann.org<mailto:fellowshipconsultation@icann.org>. Individual self-nominations will not be considered. Criteria for mentors and Selection Committee members can be found here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. REMINDER: Volunteers Needed for Advisory Group on ICANN's North America Stakeholder Engagement Plan From: Naela Sarras, Vice President, Global Stakeholder Engagement, North America Community members are invited to join a short-term regional advisory group, that will help advise the GSE North America team on the development of the next iteration of the North America Stakeholder Engagement Plan. This effort seeks community input to enhance the important work of stakeholder engagement across North America by actively soliciting input into ICANN policy and work processes. This advisory group will be time-limited (February - May 2021), will include two webinars, and be directed toward answering specific questions. With help from the community, the team hopes to surface implementable ideas with measurable impact to enhance engagement. Kindly send your reply with one or two named volunteers for this activity by Friday, 12 February 2021. Please send your reply to naela.sarras(a)icann.org<mailto:naela.sarras@icann.org> and joe.catapano(a)icann.org<mailto:joe.catapano@icann.org>. REMINDER: Nomination Period for the ICANN Community Excellence Award 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 deadline for submissions is Monday, 29 March 2021, and 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=001_LBAZYrWlHnVUWrLo…> and submit your nominations here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…>. Public Comment Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> Close Date: Friday, 22 January 2021 Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> Close Date: Monday, 15 February 2021 Volume 3, Issue 4 | Archive [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001_LBAZYrWlHnVUWrLo…> | Next Issue: Monday, 18 January 2021

1 0

Recording and slide deck Operational Design Phase (ODP) webinar 13 January 2021 20:00 UTC
by Nathalie Peregrine 14 Jan '21

14 Jan '21

Dear all, Please find below the recording and slide deck of the webinar on the latest version of the Operational Design Phase Concept Paper held on 13 January 2021 at 20:00 UTC. Webinar slide deck PDF<https://community.icann.org/download/attachments/153520877/Presentation_ODP…> Webinar recording Zoom recording<https://icann.zoom.us/rec/play/mXDJ6Osb5uvGAw0EnHRFigaJsGuO2qyWsg7Nfk0Y23AR…> Thank you, Kind regards, Nathalie

1 0

FW: Proposed GNSO Liaison to ccPDP4 & GNSO/ccNSO cooperation on IDN
by philippe.fouquart＠orange.com 13 Jan '21

13 Jan '21

Dear Councillors Please note the following correspondence with the ccNSO relative to the appointment of a GNSO Liaison to ccPDP4 ((de)selection of IDN ccTLD strings). Regards, Philippe From: FOUQUART Philippe TGI/OLN Sent: Wednesday, January 13, 2021 4:42 PM To: 'Katrina Sataki' <katrina(a)nic.lv> Cc: gnso-chairs(a)icann.org; Ducos, Sebastien <Sebastien.Ducos(a)team.neustar>; 'Maarten Simon' <maarten.simon(a)sidn.nl>; ariel.liang(a)icann.org Subject: Proposed GNSO Liaison to ccPDP4 & GNSO/ccNSO cooperation on IDN Dear Katrina, Hope this letter finds you well, and best wishes for the new year! Internationalized Domain Names (IDNs) are a topic of joint interest for the GNSO and the ccNSO. On 14 March 2019, the ICANN Board approved a set of recommendations developed by ICANN org on how to allocate IDN variant TLD labels. On 26 January 2020, the ICANN Board approved the Recommendations for the Technical Utilization of the RZ-LGR on how to employ the RZ-LGR to determine valid IDN TLDs and their variant labels. The ICANN Board requested that the GNSO and ccNSO take into account those IDN variant TLD recommendations and RZ-LGR Technical Utilization recommendations while developing their respective policies to define and manage IDN variant TLDs for the current TLDs and future TLD applications. The ICANN Board further requested that the GNSO and ccNSO keep each other informed of the progress in developing the relevant details of their policies and procedures to ensure a consistent solution for IDN variant gTLDs and IDN variant ccTLDs. The GNSO is aware that ccPDP4 on the (de)selection of IDN ccTLD Strings is underway. Its first Sub-Group, which will focus on the variant management topic and likely be of interest to the GNSO, is expected to start its meeting in February 2021. In the meantime, the GNSO Council launched a Drafting Team to develop a charter and an initiation request for an Expedited Policy Development Process (EPDP) on IDNs. The Drafting Team has been meeting regularly since 8 December 2020 and aims to complete its deliverables for GNSO Council's review by April 2021. To facilitate the coordination between the GNSO and ccNSO on the IDN topic, the GNSO Council proposes to appoint Dennis Tan Tananka as its liaison to follow and monitor the ccPDP4, including its Sub-Group on Variant Management. Dennis was involved in a number of IDN policy efforts at ICANN, including the development of variant management recommendations and the technical study group on the utilization of RZ-LGR. More importantly, he participates in the ccPDP4 as a member and chairs the GNSO Council's Drafting Team on the IDNs EPDP Charter. Dennis plans to continue his engagement in the future GNSO EPDP on IDNs once it is chartered by the GNSO Council. With in-depth knowledge of IDNs and great familiarity with the work in both groups, Dennis should be able to serve this liaison role well by keeping both the GNSO and the ccNSO up-to-date of each other's progress, as well as timely spotting/raising issues if the ccNSO and/or GNSO potentially develop recommendations that may cause inconsistency for managing variant ccTLDs and variant gTLDs. Please let me know if you have any questions or concerns about GNSO Council's proposed appointment of Dennis Tan Tanaka as its liaison to the ccPDP4. Thank you for your consideration. Best Regards, Philippe Fouquart, GNSO Chair _________________________________________________________________________________________________________________________ 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

Reminder: Please update your Zoom app regularly
by Nathalie Peregrine 12 Jan '21

12 Jan '21

Dear all, A friendly reminder to please update your Zoom apps regularly, as this will help avoid issues such a logging in delays and new features being unavailable to some. Please go to this page for further information as to how to proceed, the whole process only takes a few seconds: https://support.zoom.us/hc/en-us/articles/201362233-Upgrade-update-to-the-l… Thank you all! Nathalie

1 0

GNSO Council Program Suite - 21 January 2021
by policy＠bacinblack.com 12 Jan '21

12 Jan '21

Dear All, Please find attached links to the latest version of the GNSO Council's Program Suite for the meeting on 21 January 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+21+January+2021 Links to the Program Suite: * 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 Project Changes for this Period: * Transfer policy Final Issue report now available; moved to Initiation phase * Council consideration of the RPM's Phase 1 Final Report consensus recommendations * Delivery of SubPro Final Report and initial briefing * SSC leadership approved Key Project Activities for February 2021 (ADR): * Council to consider Transfer Policy Issue Report and possible launch of PDP * Council confirmation of EPDP_P2A project plan * 1st meeting of RPM_IGO_CRWT * Council consideration of the SubPro Final Report consensus recommendations * Review EPDP-P1 IRT Wave 1 report findings and what that means for IRTs of PPSAI + T&T * The SCBO to submit draft of comments of ICANN Org FY22 Draft Operating Plan and Budget for review by GNSO Council. * ICANN Org briefing document on Registration Data Accuracy due 26 Feb 2021 * WS2 Small Team Update and next steps * Continue discussions around the Standing Committee on Continuous Improvement (ATRT3, 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/>

1 0

Final Issue Report on a Policy Development Process to Review the Transfer Policy
by Emily Barabas 12 Jan '21

12 Jan '21

Dear Councilors, Further the GNSO Council resolution<https://gnso.icann.org/en/council/resolutions/2020#202006> passed on 6 June 2020 requesting a Preliminary Issue Report on the Transfer Policy, please find attached the Final Issue Report on a Policy Development Process to Review the Transfer Policy. Information will follow regarding a webinar to support your review of the Final Issue Report. 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

Re: [council] GNSO Council Liaisons
by Steve Chan 12 Jan '21

12 Jan '21

Dear Councilors, I just wanted to follow-up on the message below. After reviewing the email, I realized I made a typo that hopefully did not create too much confusion. For the second liaison vacancy, I put EPDP Phase 2 instead of EPDP Phase 2A. With the EPDP Phase 2A having already kicked off, there remains an immediate need to identify a Council liaison to this group. Please give some consideration to whether you might able to serve in this role. Best, Steve From: council <council-bounces(a)gnso.icann.org> on behalf of Steve Chan <steve.chan(a)icann.org> Date: Monday, December 21, 2020 at 3:31 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] GNSO Council Liaisons Dear Councilors, Following the affirmative vote to approve the Consent Agenda on the 17 December 2020 meeting, a number of GNSO Council liaisons are now confirmed. However, note that during the meeting, Olga withdrew her name as the GNSO Council liaison to the EPDP Phase 2 and that there is still an outstanding vacancy for the EPDP Phase 2A. In consultation with Council leadership, here is the proposed path forward. EPDP Phase 2: As this PDP has now concluded, there does not appear to be a pressing need to identify a new liaison, though one will be needed once an Implementation Review Team (IRT) is established. However, and without making too many assumptions, there may be reason that the IRT for Phase 2 will be merged or perhaps be a continuation of the existing IRT, which could allow Sebastien to serve as the single Council liaison to the IRT (assuming there is some form of streamlined IRT and Sebastien is willing of course). The Council leadership proposal here is to leave this position vacant, at least for the moment. EPDP Phase 2A: There is however a need to identify a liaison here, in a timely fashion, as the EPDP Team has already held its first meeting. To give you a sense of the commitment, liaisons typically take part in leadership planning meetings, share information and updates between the WG and Council, provide guidance regarding WG processes, etc. (see role description here: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liai…). However, I would note that during the EPDP Phase 2, the liaison also served as the vice-chair, and this possibility is I understand under discussion within the EPDP Phase 2A currently. Assuming that ends up being the outcome, the liaison would then be asked to both fulfill the requirements of being a GNSO Council liaison to the WG, as well as that of being a vice-chair, which is primarily chairing WG calls when the Chair is unavailable. That said, the Chair has indicated that he fully anticipates being available for this limited duration effort. The Council leadership proposal here is of course to identify a volunteer to fill this position. 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

Final Proposed Agenda | GNSO Council Meetings 21 January 2021 at 19:00 UTC
by Andrea Glandon 12 Jan '21

12 Jan '21

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 21 January 2021 at 19:00 UTC. Draft GNSO Council Agenda 21 January 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/mIgmCQ 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 19:00 UTC Coordinated Universal Time: 19:00 UTC: https://tinyurl.com/yahj6bpc 11:00 Los Angeles; 14:00 Washington; 19:00 London; 20:00 Paris; 22:00 Moscow; (Friday) 06:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/96919081324?pwd=RTN5MHBIcnBpY2tRUlRQd3lOb2IxUT09 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/2020/minutes/minutes-gnso…> of the GNSO Council meeting on 19 November 2020 were posted on 3 December 2020. Minutes<https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso…> of the GNSO Council meeting on 17 December 2020 were posted on 3 January 2021. 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 (5 minutes) 3.1 - Confirmation of of SSC selection processes: * GNSO Non-Registry Liaison to the Customer Standing Committee (CSC) - Milton Mueller (motion<https://community.icann.org/x/oYgmCQ>) * 2021 GNSO Appointed Mentor to the ICANN Fellowship Program - TBD (motion<https://community.icann.org/x/oYgmCQ>) * GNSO’s Representative(s) to the Community Representatives Group that will nominate the Independent Review Process (IRP) Standing Panel - TBD (motion<https://community.icann.org/x/oYgmCQ>) Item 4: COUNCIL VOTE - Affirm Intent of EPDP Phase 1 Recommendation 7 (25 minutes) In adopting the Expedited Policy Development Process (EPDP) on the Temporary Specification Final Report and Recommendations, the Council requested that an informal Implementation Review Team (IRT) be established, which was done. After the recommendations were approved by the ICANN Board, the informal IRT transitioned to a formal IRT and has diligently been working to implement the policy recommendations. Within the IRT, there are diverging views amongst some IRT members on how to implement recommendation 7, especially in relation to the Thick WHOIS Transition Policy for .COM, .NET, and .JOBS The ICANN Board, taking note of the potential impasse, sent a letter<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> to the GNSO Council on 11 March 2020. The Council considered the letter and agreed that recommendation 7 did not explicitly overturn the Thick Whois Transition Policy; to do so will require the GNSO Council to initiate policy development. The Council sent a response<https://urldefense.com/v3/__https:/www.icann.org/en/system/files/correspond…> to the ICANN Board on 29 May 2020. The IRT has continued to try and implement recommendation 7 but has still been unable to reach agreement. As such and per the Council’s letter, the Council requested a briefing from, ”the GNSO Council liaison detailing the precise nature of the impasse so that the GNSO Council can make an informed determination on how to proceed.” During its September 2020 Council meeting, the Council received a briefing from the GNSO Council liaison to the IRT, Sebastien Ducos. The Council agreed to convene a small team of Councilors that was charged with establishing a path forward to try and resolve the impasse. That small team met to determine what the best practical path forward may be. During the Council’s October 2020 meeting, it considered a draft motion<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-mot…> that would do two things 1) Affirm the intent of EPDP Phase 1 Recommendation 7; and 2) initiate an EPDP on the Thick WHOIS Transition Policy. This draft motion was further discussed during the November 2020 Council meeting where a number of potential approaches to resolve policy conflicts were discussed. After the November Council meeting, the small team was reconvened and worked towards a revised path forward but was unable to reach consensus. A motion was submitted to the Council list on 7 December 2020 and considered during the 17 December Council meeting, but the vote was deferred. Here, the Council will vote to adopt the motion. 4.1 - Presentation of motion<https://community.icann.org/x/oYgmCQ> (Council Vice-Chair, Pam Little) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) 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 5: COUNCIL VOTE - Final Report and Recommendations From the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs PDP WG (15 minutes) Chartered in March 2016 to review all the RPMs that have been developed by ICANN, the PDP is focused on RPMs developed for the 2012 New gTLD Program (i.e., Trademark Clearing House, Sunrise, Claims, and Uniform Rapid Suspension). The WG was tasked with considering the overarching issue as to whether or not the RPMs collectively fulfill their purposes or whether additional policy recommendations will be necessary. After the Co-Chairs determined additional time was needed to accommodate substantive work, the most recent Project Change Request was submitted and granted for the Council’s September meeting, establishing a target date of no later than the end of November. The WG was able to successfully complete its work by this timeline and delivered its Final Report<https://gnso.icann.org/en/issues/rpm-phase-1-proposed-24nov20-en.pdf> to the GNSO Council on 24 November 2020. A summary briefing on the Final Report and recommendations was provided during the 17 December 2020 meeting and a more comprehensive webinar was held on 11 January 2021. Here, the Council will vote to adopt the Final Report of the PDP WG. 5.1 – Presentation of motion<https://community.icann.org/x/oYgmCQ> (GNSO Council liaison to the PDP, John McElwaine) 5.2 – Council discussion 5.3 – Council vote (voting threshold: Supermajority) 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 BRIEFING – New gTLD Subsequent Procedures PDP Final Report (25 minutes) The PDP was chartered in January 2016 to review the 2012 New gTLD Program round to determine what, if any changes may need to be made to the existing 2007 Introduction of New Generic Top-Level Domains policy recommendations. After extensive WG deliberations and a number of community consultations, the WG delivered its Final Report to the GNSO Council on [date]. Because of the volume of outcomes (e.g., recommendations, implementation guidance, etc.) and length of the report, PDP leadership believes that similar to the Final Report for the All Rights Protection Mechanisms (RPMs) in All gTLDs PDP WG, a preliminary briefing is beneficial. Here, the Council will receive a briefing to better understand the scope of substantive recommendations that it will be asked to vote on in a future meeting. 6.1 – Introduction of topic (Council leadership) 6.2 - Briefing (GNSO Council liaison to the PDP, Flip Petillion - presentation) 6.3 – Council discussion 6.4 – Next steps Item 7: COUNCIL UPDATE - Update from the Standing Committee on Budget and Operations (SCBO) (10 minutes) Per its charter, the GNSO Standing Committee on Budget and Operations (SCBO) was established to coordinate and facilitate dialogue to fully understand ICANN's strategic and operational planning and budgetary processes, in particular in preparation for the annual budgetary comments cycle as it relates to the GNSO Council’s remit. The SCBO is currently in the midst of the annual process, considering the Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget<https://www.icann.org/public-comments/draft-opplan-budget-fy22-26-2020-12-1…> that is currently available for public comment. While the SCBO is comprised of members and experts from across the GNSO community, the input of the SCBO is limited to the GNSO Council’s remit in managing the GNSO’s policy development process and the GNSO’s role as a Decisional Participant in the Empowered Community. As the public comment period will conclude (15 February 2021) prior to the next GNSO Council meeting, the SCBO believes it is timely to provide a status update during the January meeting. Here, the Council will receive an update from the SCBO. 7.1 – Introduction of topic (SCBO Chair, John McElwaine) 7.2 – Council discussion 7.3 – Next steps Item 8: ANY OTHER BUSINESS (20 minutes) 8.1 - GNSO Standing Committee for Continuous Improvement - objections to expanding upon the high-level outline and developing a more detailed draft proposal? 8.2 - GNSO Council feedback on the updated Operational Design Phase concept paper - objections to draft Council feedback (if input is available) 8.3 - GNSO Council Additional Budget Requests (if applicable) 8.4 - Update on the ICANN Meetings strategy 8.5 - Update on the IGO Work Track kickoff 8.6 - Small team proposed input to the ICANN Board regarding the SSAD consultation _______________________________ 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 19:00 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 11:00 San José, Costa Rica (CST) UTC-6 13:00 New York/Washington DC, USA (EDT) UTC-5 14:00 Buenos Aires, Argentina (ART) UTC-3 16:00 Rio de Janeiro, Brazil (BRST) UTC-3 16:00 London, United Kingdom (GMT) UTC+0 19:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 20:00 Paris, France (CEST) UTC+1 20:00 Moscow, Russia (MST) UTC+3 22:00 Singapore (SGT) (+1 day) UTC+8 03:00 Melbourne, Australia (AEDT)(+1 day) UTC+11 06:00 ---------------------------------------------------------------------------- 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/yahj6bpc

1 0