March 2021 - council - lists.icann.org

GNSO Council resolutions 24 March 2021
by Nathalie Peregrine 24 Mar '21

24 Mar '21

Dear all, Please find below the resolutions from the GNSO Council meeting on Wednesday 24 March 2021 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page. 20210324 – 1 Consent agenda * Confirmation of the Recommendations Report<https://gnso.icann.org/sites/default/files/policy/2021/presentation/draft-c…> to the ICANN Board regarding adoption of relevant Outputs from the New gTLD Subsequent Procedures PDP. Vote results <https://urldefense.com/v3/__https:/gnso.icann.org/en/meetings/gnso-council-…> 20210324 – 2 IANA Naming Functions Contract Amendment Submitted by: Pam Little Seconded by: Tomslin Samme-Nlar Whereas, 1. On 16 September 2018, the first IANA Function Review (IFR) was convened by the ICANN Board, in compliance with Article 18 of the ICANN Bylaws. The IFR Team (IFRT) published<https://www.icann.org/public-comments/ifr-initial-report-2020-10-08-en#:~:t….> its Initial Report for public comment on 08 October 2020. 2. The IFRT developed four recommendations, with Recommendation 4 suggesting an amendment to the IANA Naming Function Contract. The IFRT followed the Bylaws required steps regarding contract amendment recommendations found in Section 18.6, which include consultation with the ICANN Board, consultation with the Customer Standing Committee, conducting a public input session for ccTLD and gTLD registry operators, and to conduct a public comment<https://www.icann.org/public-comments/iana-naming-function-contract-amend-2…> proceeding on the amendment. 3. Pursuant to the ICANN Bylaws Section 18.6 (b)(i), IFR Recommendations requiring a contract amendment must be approved by a supermajority vote of the ccNSO Council and GNSO Councils. Resolved, 1. The GNSO Council approves Recommendation 4 contained in the IFR Final Report, which recommends that Article VII, Section 7.1 (a) of the IANA Naming Function contract be amended to remove this statement, "The relevant policies under which the changes are made shall be noted within each monthly report" be removed from the IANA Naming Function contract. 2. The GNSO Council requests the GNSO Secretariat to communicate this decision to the Co-Chairs of the IFRT and relevant ICANN staff accordingly. Vote results<Vote%20results> 20210324 – 3 Approval of the Charter for the Working Group to Conduct a Policy Development Process to Review the Transfer Policy Submitted by: Pam Little Seconded by: Maxim Alzoba Whereas, 1. On 12 January 2021, the GNSO Council received the Final Issue Report on a Policy Development Process (PDP) to Review the Transfer Policy. The Final Issue Report included a Draft Charter that incorporated a number of PDP 3.0 Improvements<https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-final…>. It also sets out proposed scope of work and recommended a working group structure based on a “representative model<https://gnso.icann.org/sites/default/files/file/field-file-attach/pdp-3-2-w…>”. 2. On 8 February, the GNSO Chair sought input from the chairs of all ICANN Supporting Organizations, Advisory Committees, Stakeholder Groups and Constituencies regarding the proposed membership model, the number of representatives from their community group and timing for launch the proposed PDP. 3. On 18 February 2021, the GNSO Council passed a resolution<https://gnso.icann.org/en/council/resolutions/2021#202102> to initiate a two-phased PDP to Review the Transfer Policy which will determine if changes to the policy are needed to improve the ease, security, and efficacy of inter-registrar and inter-registrant transfers. During the 18 February 2021 meeting, the Council discussed the Draft Charter and decided to form a small group of Councilors to finalize the Charter, with a focus on the working group membership model and composition. 4. On 24 February 2021 and 4 March 2021, the Council small team discussed the input received from community groups and considerations such as expertise and technical knowledge of the Transfer Policy, interest in the topic and impact of PDP outcome. 5. On 12 March 2021, the Council small group completed its work and submitted a final version of the Charter of the PDP to Review the Transfer Policy to the full GNSO Council. RESOLVED: 1. The GNSO Council approves the Charter of the PDP to Review the Transfer Policy. 2. The GNSO Council directs staff to: (a) communicate the results of this motion to the GNSO SG/Cs as well as ICANN SO/ACs and invite them to identify members and alternates for the working group following the working group composition described in the Charter; (b) initiate a call for expressions of interest seeking interested candidates to chair the PDP to Review the Transfer Policy. Vote results<Vote%20results> Kind regards, Nathalie

1 0

Agenda of our next Council meeting of 24 March 2021 - ODP liaison
by Flip Petillion 24 Mar '21

24 Mar '21

Dear Councilors, 1. next Council meeting Item 3 / Consent Agenda of our next Council meeting of 24 March 2021 is: Confirmation of the draft Recommendations Report to the ICANN Board regarding adoption of relevant Outputs from the New gTLD Subsequent Procedures PDP<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…>. As this is supposed to be a communication by the GNSO Council to the Board, I propose to amend this draft as follows: Annex B Although the draft contains a link to the Final Report, I propose to substitute Annex B to this draft with the Full Report approved by Council on 18 February 2021. That way, the Final Report will be formally handed over to the Board. I do not think this change is contentious given the Final Report contains Annex B. Other changes I would like to propose to ensure consistency with the GNSO Council motion we unanimously adopted, are as follows: On page 3, Executive Summary first paragraph : I propose to add the following language (in yellow): On 18 February 2021, the GNSO Council voted to approve, by a GNSO Supermajority, the Affirmations, Recommendations, and Implementation Guidance (collectively referred to as "Outputs") that were determined to have received either Full Consensus or Consensus designations by the New gTLD Subsequent Procedures Policy Development Process (PDP) Working Group. This reflects that the New gTLD Subsequent Procedures Policy Development Process (PDP) Working Group operated on the basis that unless consensus was reached, the status quo would remain in place as a default position. This Recommendations Report is being sent to the ICANN Board for its review of the Outputs approved by the GNSO Council, which the GNSO Council recommends be adopted by the ICANN Board. Please see Annex A of this Recommendations Report for a summary of all of the Outputs. Page 8, second and third paragraph: I propose to delete the following language (in yellow), as it is inconsistent with the Council resolution: The GNSO Council has requested that the ICANN Board initiate an Operational Design Phase (ODP) on the Final Report of the Subsequent Procedures PDP Working Group and its approved Outputs as soon as possible. The objective of the ODP is to perform an assessment of GNSO Council recommendations in order to provide the Board with relevant operational information to facilitate the Board’s determination, in accordance with the Bylaws, on the operational impact of the implementation of the approved Outputs, including whether the approved Outputs are in the best interests of the ICANN community or ICANN. The results of the ODP assessment may provide additional insight into the period of time needed to implement the adopted Outputs, including whether there is community work that must be completed prior to either implementation or the opening of subsequent application rounds. In reviewing the Final Report, the Board may identify specific topic areas and/or Outputs that require further analysis to support Board consideration. In addition, it is likely that the Outputs contained in the Final Report that the GNSO Council did not approve may nevertheless warrant the Board’s attention and examination of possible ways forward: The GNSO Council resolution language stated: “2. Recognizing that nearly a decade has passed since the opening of the 2012 round of new gTLDs, the GNSO Council requests that the ICANN Board consider and direct the implementation of the Outputs adopted by the GNSO Council without waiting for any other proposed or ongoing policy work unspecific to New gTLD Subsequent Procedures to conclude, while acknowledging the importance of such work.” Page 9, second paragraph: I propose to delete the following language (in yellow) as it is inconsistent with the Council resolution: Under its Charter requirements, the Working Group took into account outputs of concluded efforts (for example the Competition, Consumer Trust and Consumer Choice Review (CCT) and the Cross Community Working Group on the Use of Country and Territory Names (CCWG-UCTN) ) and coordinated its work with other relevant efforts that ran concurrently (for example the Review of All Rights Protection Mechanism in All gTLDs (RPMs) Policy Development Process and the Name Collision Analysis Project (NCAP) ). In its resolution approving the PDP’s Outputs, the GNSO Council requested that “the ICANN Board consider and direct the implementation of the Outputs adopted by the GNSO Council without waiting for any other proposed or ongoing policy work unspecific to New gTLD Subsequent Procedures to conclude, while acknowledging the importance of such work.” Drawing on the ODP assessment, the Board may consider the extent to which it is feasible to advance implementation of subsequent procedures independent of any other relevant community work, such as the impending Expedited Policy Development Process (EPDP) focused on Internationalized Domain Names (IDNs) and in particular, IDN variant TLDs. Page 11: I propose to change the following language (in yellow and strikethrough) The Working Group’s Final Report was submitted to the GNSO Council on 18 January 2021 and can be found in full here. The full text of all Outputs are is included as Annex B to this Recommendations Report. 2. ODP liaison for the Council I examined the next steps for the Sub Pro PDP and the ODP. I understand that the ODP Process Paper encourages the Council to appoint a liaison to the ODP to streamline communications between ICANN org’s ODP team and the Council should any questions on the substance or intent of recommendations arise. I observed that the liaison will serve as the primary contact between ICANN org’s ODP team and the GNSO Council on questions pertaining to the substance or intent of the GNSO Council recommendations. The liaison is expected to keep the GNSO Council informed about their engagement with ICANN org on these questions and should be empowered. As the Process Paper suggests that the ODP liaison preferably has had previous involvement with the relevant PDP, please note that I offer to be the ODP liaison for the Council. Respectfully submitted, Flip Flip Petillion fpetillion(a)petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law [id:image001.png@01D3691D.DA7539C0]<https://www.petillion.law/> Attorneys – Advocaten – Avocats

3 3

Council SSAD Small Team draft letter
by Caitlin Tubergen 24 Mar '21

24 Mar '21

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

2 1

Reminder: GAC Meeting with the GNSO on 24 March 2021 at 14:00 UTC.
by Steve Chan 24 Mar '21

24 Mar '21

Dear Councilors, I wanted to remind you all about the meeting with the GAC, scheduled for 14:00 UTC on 24 March 2021 (see session here). You are all more than likely aware that this meeting is scheduled, based on the discussion on list from Jeff, the GNSO’s liaison to the GAC. However, as there was no meeting invitation sent, we thought it best to be sure you’re all aware. See you all there. 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

3 2

FW: Informal/preliminary questions & messages from GAC leadership &topic leads
by Jeff Neuman 23 Mar '21

23 Mar '21

Dear Council Members, Please find enclose a document provided to me this morning from the GAC Point of Contact to the GNSO containing questions (and context) that GAC Leadership and Topic Leads would like to see addressed during our March 24th bilateral. My General Comments: 1. For most (if not all) of these questions, I do not believe that there is necessarily a unified Council view. Rather, I believe that there are different views from the different constituencies and SGs. 1. We should also remind the GAC that the GNSO Council is the manager of the policy process and does not "represent" the GNSO as a whole when it comes to policy issues. Council members can certainly speak individually on their own view or on the view of the constituency/stakeholder group. * Where there has been Council action, then of course the Council can speak to the reasons why they took that action (or decided not to take a different action). Therefore, the questions on what the Council did on the SSAD recommendations is certainly one the Council can and should speak to (page 3). * With respect to the questions on Accuracy Scoping, that also would be appropriate for the Council to speak to (page 2-3) because it asks what our view is on potential policy development activity. * However, in my opinion, the first two questions on ePDP Phase 2a are not ones where the Council can respond (as representing the GNSO). These two questions are ones that really should be answered at this point by the SGs/Cs (to the extent that they have positions on these). * There is a question on whether the Council would support the continuation of ePDP Phase 2A. This is a good question for the Council to respond to if it so chooses. * The questions on DNS Abuse that are presented are not ones that the Council (as a Council) has taken a position, and my guess is that each SG and C have their own view. 1. For those questions above where the Council does not (or should not) have a view, I would recommend that we nominate no more than 2 or 3 people that can speak to each of these questions and represent the different points of view. If we make it a free for all, I believe that any one of these questions could spark conversation that would take up the entire time. * Just as the GAC appoints Topic Leads for each of these, I think it would be good for us to do the same. * And we also want the GAC to speak as well. This is one of the few times that we get to interact with the GAC and it would be great to hear their views as well as having us express our views in one direction. I would like to respond to my GAC Point of contact with some feedback prior to our bilateral session. It would be great for us to respond by thanking them for these questions, set their expectations as to what we can and cannot address as a Council, and potentially sending them a list of questions for them to think about. Sincerely, Jeff [cid:image001.png@01D71CA4.B06E9390] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Jorge.Cancio(a)bakom.admin.ch <Jorge.Cancio(a)bakom.admin.ch> Sent: Friday, March 19, 2021 8:10 AM To: Jeff Neuman <jeff(a)jjnsolutions.com> Cc: gac-leadership(a)icann.org; julia.charvolen(a)icann.org; gnso-secs(a)icann.org Subject: AW: Agenda for GNSO and GAC session at ICANN70 - informal/preliminary questions&messages from GAC leadership&topic leads Dear Jeff Please find attached some informal and preliminary questions and messages the GAC topic leads have prepared (under the guidance of GAC Leadership) concerning topics 1-3 of our agenda next week. We would be very thankful if you could relay these to GNSO Council, and we hope this helps to conduct a very fruitful discussion at the GAC-GNSO bilateral next week. Kind regards Jorge Von: Julia Charvolen <julia.charvolen(a)icann.org<mailto:julia.charvolen@icann.org>> Gesendet: Montag, 15. März 2021 18:22 An: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Cc: Cancio Jorge BAKOM <Jorge.Cancio(a)bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>; Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; GACLEADERSHIP <gac-leadership(a)icann.org<mailto:gac-leadership@icann.org>> Betreff: Agenda for GNSO and GAC session at ICANN70 Dear All, As requested, this email is to confirm the agenda for the ICANN70 GAC joint session with the GNSO scheduled for Wednesday 24 March. The agenda is as follows: 1. EPDP/ (Phase 2 and 2a) / SSAD 2. DNS Abuse 3. Accuracy Scoping Team 4. Next steps on collaborating on Subsquent Procedures of New gTLDs Thank you. Kind regards, Julia

2 3

FW: EPDP Phase 2A Chair Report to GNSO Council
by philippe.fouquart＠orange.com 23 Mar '21

23 Mar '21

Dear Councillors, Please find attached the slides for the "Status Update regarding EPDP phase 2A" that Keith will give tomorrow (item 7 on our agenda). Regards, Philippe From: Drazek, Keith [mailto:kdrazek@verisign.com] Sent: Tuesday, March 23, 2021 4:04 PM To: FOUQUART Philippe TGI/OLN <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: EPDP Phase 2A Chair Report to GNSO Council Hi Philippe, As outlined in the EPDP Phase 2A charter, I'm looking forward to providing my Chair report tomorrow to the GNSO Council. The attached slides will help guide our conversation during the Council meeting. Please share with the Council in advance of the meeting as you see fit. Best regards, Keith _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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

In preparation for the GNSO Council meeting 24 March 2021 17:30 UTC
by Nathalie Peregrine 22 Mar '21

22 Mar '21

Dear all, A few reminders in preparation for the GNSO Council meeting on Wednesday 24 March 2021 at 17:30 UTC. * 🔥Please remember to update your Zoom application, steps as to how to do this can be found here<https://urldefense.com/v3/__https:/support.zoom.us/hc/en-us/articles/201362…>.🔥 * 🚦Zoom access details will not be circulated via email, they will be published shortly before the session start time on this page<https://70.schedule.icann.org/meetings/GQMMy6pPhgZzFHpZN#/?limit=10&sortByF…>. 🚦Please remember to register or you will not be able to access the information. * 👀Please review the agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+GNSO…> and motions<https://community.icann.org/display/gnsocouncilmeetings/Motions+24+March+20…> as well as supporting documents<https://community.icann.org/display/gnsocouncilmeetings/Documents+24+March+…>. 👀 * 👀Please review all updated Program Management Tools<https://community.icann.org/display/gnsocouncilmeetings/Program+Management+…>: Action Item list<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>, Project List<https://community.icann.org/display/gnsocouncilmeetings/Project+List> , Action Decision Radar<https://community.icann.org/display/gnsocouncilmeetings/Action+Decision+Rad…>.👀 * 💻⚠️There are three votes on the GNSO Council agenda, if you cannot make the call, or are worried about connectivity issues, please use the GNSO Council Absence Notification form<https://forms.icann.org/en/gnso-council-absence-notification-form> to assign a proxy. 💻⚠️ Thank you, Kind regards, Nathalie

2 1

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

19 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@01D71CAE.B6B0DB50] 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@01D71CAE.B6B0DB50] (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

FW: [Ext] Thursday, 18 March 2021
by Julie Bisland 18 Mar '21

18 Mar '21

FYI: From: ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, March 18, 2021 at 10:29 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 18 March 2021 [http://r20.rs6.net/on.jsp?ca=7d1fa4f2-0176-44fa-98b9-210b642c3ff2&a=1122025…] Thursday, 18 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. The ICANN Community Leadership Digest will pause publication during ICANN70. Publication will resume Monday, 29 March 2021. Table of Contents Information Sharing · REMINDER: ICANN Community Group Topics or Questions for Joint Meetings with the ICANN Board · CLOSING SOON: ICANN Nominating Committee Application Period Now Open · CLOSING SOON: 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: Virtual Conference Bag · PARTICIPATE: How-To Guides · PARTICIPATE: Networking · FOLLOW: Newsletters Public Comment · CLOSING ON MONDAY: 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 REMINDER: ICANN Community Group 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=0017SmFVDmyR7Evj6Zkc…> 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. CLOSING SOON: ICANN Nominating Committee Application Period Closes 29 March 2021 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=0017SmFVDmyR7Evj6Zkc…>candidate portal [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…>. All applications are confidential. Learn more. [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> CLOSING SOON: ICANN Community Excellence Award Nomination Period Closes 29 March 2021 From: David Olive, Senior Vice President, Policy Development Support The nomination period for the ICANN Community Excellence Award 2021 closes soon. 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=0017SmFVDmyR7Evj6Zkc…> and submit your nominations here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> by Monday, 29 March 2021. ICANN70 Resources REGISTER [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> PREPARE: Prep Week sessions [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> PREPARE: Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> PREPARE: GNSO Policy Briefing [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> PARTICIPATE: Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> PARTICIPATE: Virtual Conference Bag [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> PARTICIPATE: How-To Guides [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> PARTICIPATE: Networking [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> FOLLOW: Newsletters [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> Public Comment CLOSING ON MONDAY: 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=0017SmFVDmyR7Evj6Zkc…> 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=0017SmFVDmyR7Evj6Zkc…> 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=0017SmFVDmyR7Evj6Zkc…> 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=0017SmFVDmyR7Evj6Zkc…> 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=0017SmFVDmyR7Evj6Zkc…> Close Date: Thursday, 15 April 2021 Volume 3, Issue 22 | Archive [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=0017SmFVDmyR7Evj6Zkc…> | Next Issue: Monday, 29 March 2021 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe julie.bisland(a)icann.org [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=un&m=00…> Update Profile [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=oo&m=00…> | Customer Contact Data Notice [constantcontact.com]<https://urldefense.com/v3/__https:/www.constantcontact.com/legal/customer-c…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> powered by [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.com/v3/__http:/www.constantcontact.com/index.jsp?cc=nge&…> Try email marketing for free today! [constantcontact.com]<https://urldefense.com/v3/__http:/www.constantcontact.com/index.jsp?cc=nge&…>

1 0

Nomination Period for the ICANN Community Excellence Award Closes 29 March 2021
by Nathalie Peregrine 18 Mar '21

18 Mar '21

https://www.icann.org/en/announcements/details/nomination-period-for-the-ic… LOS ANGELES -17 March 2021 The Internet Corporation for Assigned Names and Numbers (ICANN) announced the opening of the nomination period for the ICANN Community Excellence Award in December 2020. The nomination period will close on 29 March 2021 at 23:59 UTC. Winner(s) will be announced at the ICANN71 Virtual Policy Forum, scheduled for 14-17 June 2021. Launched in 2014, the ICANN Community Excellence Award recognizes ICANN community members who have deeply invested in consensus-based solutions and contributed substantively to the ICANN multistakeholder model. Please submit your nominations via the nomination form<https://forms.gle/xzpuHXVaQMXad9ND8>, including detailed information outlining why the nominee meets the award criteria. Self-nominations will not be considered. Any additional information in support of nominations or questions about the award process may be submitted via email to excellenceaward2021(a)icann.org<mailto:excellenceaward2021@icann.org>. For more information, please refer to the ICANN Community Wiki<https://community.icann.org/x/YyOAAw>. 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.

1 0