June 2021 - Ccnso-council - lists.icann.org

Re: [ccnso-council] Notes today's council meeting | 17 June (12:30 UTC)
by Joke Braeken July 8, 2021

July 8, 2021

NOTES | ccNSO Council Meeting 174 | 17 June 2021 (12:30 UTC) 1. Welcome and roll call Welcome by chair Alejandra Reynoso. We are quorate today. 2. Relevant Correspondence New item, to regular agenda: Relevant for items to be discussed in the agenda. ccNSO website has a correspondence section. 3. Minutes & Action Items a. Minutes Meeting 173, circulated 9 June 2021 b. Action items and To-do’s, if any All completed. 1 ongoing. See next meeting 4. Intermeeting Decisions (since 20 May 2021) a. Separation of ccPDP 3 Part 1 and Part 2 b. Adoption Meeting Guideline c. Extension CSC Membership selection process d. Launch call for volunteers NomCom 2022 e. Adoption revised Terms of Reference of the ccNSO Outreach and Involvement Standing Committee (OISC ToR version 2) CSC membership: Frederico Neves has been selected. See item 13.b on the agenda 5. Adoption ccPDP3 Retirement Final Report & Support Recommendation Last time ccNSO took a similar decision: 2013. ccPDP2 was not adopted by the Board, by mutual agreement with ccNSO. Stephen Deerhake and Eberhard Lisse (ccPDP3-RET leadership team) will give an introduction. Any comments on the proposed manner to take this decision? Stephen: referring to the ccNSO policy session earlier this week. Appreciation for ICANN staff and WG members in contributing to this development and co-chair. Any comments or questions? ccPDP3 leadership is happy to answer any questions. Alejandra thanks all. Eberhard: no additions. If and when council votes in favour, it needs to go to membership. Quorum requirements, and ⅔ of the quorum needs to vote in favour. Alejandra: do councilors have questions? Pablo: thanks to leadership team, participants and staff. Nick: assuming we approve it and we get the quorum and necessary votes in favour, this policy becomes effective. Is there going to be a review process after a while? After it has been put in practice, what was the experience? Eberhard: good point. Put in diary, after the next retirement, we should review the process. Stephen: echoes what Eberhard said. Once we see it in practice, it would make sense for those responsible in the future to have that review process take place. Bernard: ATRT3 review proposes to replace the SO/AC reviews with a continuous review programme. Includes the requirement of these reviews. Would be an opportunity for such a review. Bart: if needed, Council can start another PDP. regarding the 5 or 10 year timeframe: you need a trigger event to occur. Currently I do not see one happening. You do not know when that will happen. Nick: It might be 15 years from now. That is too long. All of the policies to be reviewed regularly by Council. Alejandra: first it needs to be put in practice, for a review to happen. Jordan: Keeping our policies under continuous review is a new and interesting idea, thanks for raising it Nick Move? Jordan Second? Pablo Alejandra: Any questions regarding the resolution itself? None Do you support? Ali: yes Biyi: yes Souleymane: yes Ai-Chin: yes Jiankang: yes Jordan: yes Giovanni: yes Irina: yes Nick: yes Pablo: yes Sean: yes Stephen: yes Javier: yes Laura: yes Marie-Noemie: yes Demi: yes Jenifer: yes Alejandra: yes Unanimous support. Thanks all. Stephen: thank you to council for the support Javier: thanks. Honour to be part of this group. Bart will circulate a members report for approval by Council. That will include the resolution and vote by Council. Afterwards it will be sent to members for voting. That will happen early next week. 6. GRC related items a. Appointment Sean Copeland Vice-Chair of GRC Vice-Chair will take over the role of Katrina by ICANN72 Pablo: Thanks to Sean. Move: Pablo Second: Stephen Any questions on the resolution? Resolution has been approved. Eberhard: excuses himself. b. Adjust role of GRC, update charter See previous meetings and prep meeting 3 committees: * Triage committee (workpload ccnso work plan and its execution) * OISC (how to keep community informed, recruit volunteers) * GRC (looking at overall governance and working methods of the ccNSO). GRC requested to review its own charter. Move? Pablo Second? Giovanni All in favour 7. Adoption Work Plan 2021-2023 a. Adoption of Annual Work Plan Bart: circulated. See email. Starting point is the mind map. Maps activities against the core purpose of the ccNSO: * ccNSO as Supporting organisation * Platform function * Decisional participant Basework of the activities for the next 2 years. Any comments or questions? Jordan: hopes to present something easier to comprehend in future . Quarterly prioritisation will be more digestible. Jordan speaks on behalf of the Triage Committee and its new role. Move? Javier Second? Jenifer Any questions regarding the resolution? None All in favour b. Progress expanded role Triage committee Jordan: Triage Committee will have its 1st meeting on 6 July. will report back to Council on progress made 8. Confirmation overview status implementation of recommendations 2nd ccNSO Review Table was not up to date. Some items were already completed, but not marked as such. Any further actions required by the ccNSO? None. 1 item is in ICANN org’s remit: ccNSO website update Recommendation to subscribe future reviewers to the list. This is deferred to a potential future new review. Move? Jenifer Second: Pablo Any questions on the decision in front of us? None All in favour 9. Council Election 2021 Timeline was shared with you. Election manager needs to be appointed. Any questions or comments? None Move? Stephen Second? Irina Questions on the resolution? None All in favour 10. ICANN Hybrid Meeting Icann org survey results have been made available. Alejandra summaries the conversation from the prep meeting. Split opinions. Later today, ICANN plenary on the post-pandemic future of ICANN meetings. Alejandra was asked to share views. Javier: move as fast and fair as possible, but here there is good vaccine flow. Pablo: agrees with Javier. Complicated situation. There are some who are more ahead of the curve than others. Moving ahead as soon as possible. Support for hybrid meetings Nick: difficult judgment. What is as fast as possible. You need a substantial proportion of attendees being able to attend. If this meeting was to be held in Europe, it would probably be illegal. What is the type of meeting? Jordan: opposed to this meeting in a hybrid meeting. Wrong signal to the global community to do this at this stage of the pandemic in North America, where ICANN has its headquarters. Division between those who have access and those who don’t. Will not be able to attend, will not have had my vaccine yet by the time of the meeting Irina: i would support having a hybrid meeting, even though i cannot attend myself probably Jenifer: Is there a possibility that ICANN can give people vaccines in Seattle? Pablo: in PR when you enter the airport, you can get vaccinated. Would like to have a vaccination station at ICANN73. Any comments regarding those from community members attending todays meeting? Byron: Question then - if not enough counties have had the vaccine yet, what is the benchmark that would be the trigger? 100% of countries? 80%? 70%? Stephen: The Seattle meeting is the AGM, which might be a big itch for ICANN. Jordan raises a very valid point however. 11. Updates PDP3 Part Review Mechanism See policy session at ICANN71 12. IDN ccPDP4: Update See policy session at ICANN71 13. Update ECA & CSC a. ECA (Informational) see written update b. CSC (Informational) see written update Frederico was appointed for the remainder of the term of Alejandra. But we need a volunteer starting in October too, for the full term Any questions or comments? Irina: typo on the date. 2019 Bart: We will update the typos. Move? Laura Second? Marie-Noemie Any questions on the resolution? None All in favour No objections 14. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat None 15. Update WGs taken (written updates, unless special developments Council needs to be aware off) a. SOPC b. IGLC c. GRC d. OISC e. TLD-OPS f. Technical WG g. MPC Any additional comments from Council liaisons? Giovanni: SOPC had its meeting earlier today at ICANN71. Exchange of views with the ICANN planning team. They will start a prioritisation project. To help shape the strategic and operational plan. See how SOPC can support the icann planning. Follow-up meetings in the pipeline. 16. Update liaisons a. Update ALAC Liaison (written update) b. Update GNSO Liaison (written update to follow) 17. Next Meetings ● July 22 -12:00 UTC ● September 16 – 20:00 UTC ● October @ ICANN72 (23-28 October) ● November 18 – 12:00 UTC ● December 17 – 18:00 UTC 18. AOB * No AOB by Other Councilors * DNS Abuse (additional item by Alejandra). See if ccNSO has a role? Attending ccTLD News, IGLC, Tech Day…. this topic comes back over and over. Alejandra was approached by several parties on the ccNSO View and to see whether there is a channel of communication for the ccNSO on this topic. Discussion on the role of the ccNSO as an agenda topic during the July meeting. Please do give it some thought before our next Council meeting 19. Closure Thanking all volunteers, all committees and WGs. also liaisons and others. Thanks to their commitment the ccnso can move forward with its work Thanks to the secretariat Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of ccnso-council <ccnso-council(a)icann.org> Reply to: Joke Braeken <joke.braeken(a)icann.org> Date: Thursday, 17 June 2021 at 13:40 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Notes today's council meeting | 17 June (12:30 UTC) Hello All, Notes during today’s ccNSO council meeting will be taken here: https://docs.google.com/document/d/1aTMtilufypzR71UOrHYHDFVW6wLGNuVgPfryHjx… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1aTMtilufypzR…> ccNSO Council Meeting 174 | 17 June 2021 14:30 CEST, 17 June 2021 12:30 UTC, 17 June 2021 ID# 12475 [71.schedule.icann.org]<https://urldefense.com/v3/__https:/71.schedule.icann.org/meetings/7cXTWpLH3…> Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

2 1

[Request for Advice] ALAC session at ICANN 71
by Alejandra Reynoso July 5, 2021

July 5, 2021

Dear All As usual the MPC met one day after the conclusion of the ICANN meeting to review what went well, what can be improved and how to prepare for the next ICANN meeting from a ccNSO perspective. One of the items discussed was the "At-Large Policy Session 2: ccTLD Governance Models - Testimonies From At-Large End Users" ( https://go.icann.org/3w8Mqxg) Several comments were made, including: - Confusion as to why would ALAC host a ccTLD governance session and have people who do not work at the ccTLDs be the ones explaining how specific ccTLDs work. - If ALAC wanted to know more about ccTLDs it would have been better to hear it from the ccTLDs. The issue was that not all testimonials were factually correct i.e accusations were made on the basis of mis-representations and lack of understanding. - End users were supposed to talk about their experiences with their ccTLDs, not to explain how the ccTLD worked, nor on the perceived issues in the country between a ccTLD from a related territory and the government. The general feelings of those attending the MPC meeting was that the session was of low quality due to lack of preparation, and some argued that in hindsight we [the ccNSO] shouldn't have participated as they felt that by participating the ccNSO gave credence to the session. This is a small sample of comments, but I can see how others from our community might be just as confused and upset as a result of the session. Therefore, how do you propose we proceed with this matter? Should I write to the ALAC Chair? If so, what should be the goal and content of the message? Do nothing? Do you have another suggestion? Please advise, preferably by Monday 5 of July. Best regards, Alejandra -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso(a)cctld.gt 18 Ave. 11-95 Zona 15, V.H. III. (A-109) Guatemala, Guatemala www.gt

12 13

ICANN71 By the Numbers Report Now Available
by Kimberly Carlson June 29, 2021

June 29, 2021

https://meetings.icann.org/en/data-reports Data from ICANN Public Meetings helps provide reliable information on what attendees want, what ICANN is doing well, and where we have opportunities to improve. Learn more about the top ICANN71 sessions, Policy Forum general trends, and stats from Prep Week, click the link above to read the full report. ICANN Meeting "By the Numbers" & Technical Data Reports Why do we publish technical data from ICANN Public Meetings? Just like any other event, ICANN meetings need to innovate, adapt and evolve to meet their purpose: to support ICANN's multistakeholder model. One of the challenges that conference organizers face is to improve the conference, meeting after meeting, and maximize attendees' engagement and satisfaction. This is where meeting data comes into play. This data provides reliable information on what attendees want, what ICANN is doing well and where ICANN has opportunities to improve. By leveraging this data, we can be a stable and transparent organization that is responsive to our community's needs. For ICANN meetings, beyond the graphs and charts, we have published the raw data for each area. One of our biggest challenges is to standardize the information that we collect to ensure that data is consistent. Over the past few meetings, we have automated the collection of data through improvements in the registration system and meeting management software. Ultimately, our goal is to continue to improve on our metrics and to provide our community with more valuable data. If you would like to learn more about ICANN Meetings or have questions about this technical report, please contact: meetings(a)icann.org<mailto:meetings@icann.org>

1 0

Monday, 28 June 2021
by ICANN Community Leadership Digest June 28, 2021

June 28, 2021

Monday, 28 June 2021 ICANN Community Leadership Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Read more: How Domain Name System Policy is Developed, and How You Can Get Involved Table of Contents Information Sharing REMINDER: Request for Information on Identity Verification Methods for SSAD Now Open REMINDER: Participate or Observe: EPDP on IDNs Public Comment CLOSES FRIDAY: Draft North America Engagement Plan FY21-25 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A Information Sharing REMINDER: Request for Information on Identity Verification Methods for SSAD Now Open ICANN announced that it has now opened the Request for Information (RFI) to better understand what may be commercially available in the marketplace to deliver some or all of the System for Standardized Access/Disclosure to Non-Public Registration Data (SSAD), including existing methods for identity verification. The RFI overview document can be viewed here. Indications of interest are to be submitted by emailing SSAD-ODP-RFI(a)icann.org with the following information, upon which access will be provided to the RFI: Name of the organization Name of the contact Email address of the contact The RFI will be open until Monday, 19 July 2021 (23:59 UTC). Read more. REMINDER: Participate or Observe: EPDP on IDNs The Generic Names Supporting Organization (GNSO) Expedited Policy Development Process (EPDP) Team on Internationalized Domain Names (IDNs) welcomes anyone to join as a participant or an observer. Please contact gnso-secs(a)icann.org to sign up as a participant or an observer. Read more. Public Comment CLOSES FRIDAY: Draft North America Engagement Plan FY21-25 Close Date: Friday, 2 July 2021 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A Close Date: Monday, 19 July 2021 Volume 3, Issue 46 | Archive | Next Issue: Thursday, 1 July ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | Constant Contact Data Notice Sent by david.olive(a)icann.org powered by Try email marketing for free today!

1 0

Approval members report 18 June 2021
by Bart Boswinkel June 24, 2021

June 24, 2021

Dear all, Please find included the Members Report for your approval, The Members Report is required under section 12 of Annex B and must contain at least: a. A clear statement of the Council's recommendation. This statement is included in the executive summary and (new) section 2.3 b. The Final Report submitted to the Council; and c. A copy of the minutes of the Council's deliberation on the policy issue (see Item 10), including all the opinions expressed during such deliberation, accompanied by a description of who expressed such opinions: this is included in (new) section 2.3 Please let me know if you have any questions or objections to the Members Report ( specifically the additional paragraph in the exec summary and section 2.3) as soon as possible but ultimately by Wednesday 23 June 2021, 17.00 UTC. The goal is to submit the members Report to the ccNSO members on Thursday 24 June 2021, and publish it. Thank you and kind regards, Bart

2 2

Thursday, 24 June 2021
by ICANN Community Leadership Digest June 24, 2021

June 24, 2021

Thursday, 24 June 2021 ICANN Community Leadership Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Read more: How Domain Name System Policy is Developed, and How You Can Get Involved Table of Contents Information Sharing CLOSES TOMORROW: Call for Expressions of Interest: Chair of the EPDP on IDNs NEW: Request for Information on Identity Verification Methods for SSAD Now Open NEW: ICANN71 Governmental Advisory Committee Communiqué Now Available NEW: A Preview of ICANN71 Participation Metrics REMINDER: Call for Expressions of Interest: Chair of the EPDP on IDNs REMINDER: Participate or Observe: EPDP on IDNs Public Comment CLOSES NEXT WEEK: Draft North America Engagement Plan FY21-25 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A Information Sharing CLOSES FRIDAY: Call for Expressions of Interest: Chair of the EPDP on IDNs The Generic Names Supporting Organization (GNSO) Council announced that it is seeking Expressions of Interest for a chair of the Expedited Policy Development Process (EPDP) team that will address issues related to Internationalized Domain Names (IDNs). Candidates interested in serving in this role should review the Expression of Interest document before submission. The document details the role, required skills and experience, and the selection process. The deadline to submit an Expression of Interest is Friday, 25 June 2021 at 23:59 UTC. All submissions should be sent to gnso-secs(a)icann.org. Read more. NEW: Request for Information on Identity Verification Methods for SSAD Now Open ICANN announced that it has now opened the Request for Information (RFI) to better understand what may be commercially available in the marketplace to deliver some or all of the System for Standardized Access/Disclosure to Non-Public Registration Data (SSAD), including existing methods for identity verification. The RFI overview document can be viewed here. Indications of interest are to be submitted by emailing SSAD-ODP-RFI(a)icann.org with the following information, upon which access will be provided to the RFI: Name of the organization Name of the contact Email address of the contact The RFI will be open until Monday, 19 July 2021 (23:59 UTC). Read more. NEW: ICANN71 Governmental Advisory Committee Communiqué Now Available On Monday, 21 June 2021, the GAC issued its ICANN71 GAC Communiqué. It is available for review here. Previous GAC advice and past communiqués are available at https://gac.icann.org. NEW: A Preview of ICANN71 Participation Metrics Thank you to everyone who helped make the ICANN71 Virtual Policy Forum a success. More than 1,330 attendees participated from 147 countries and territories. The full ICANN71 By the Numbers Report, which will include more in-depth statistics, will be released within a few weeks. Read more. REMINDER: Call for Expressions of Interest: Chair of the EPDP on IDNs The Generic Names Supporting Organization (GNSO) Council announced that it is seeking Expressions of Interest for a chair of the Expedited Policy Development Process (EPDP) team that will address issues related to Internationalized Domain Names (IDNs). Candidates interested in serving in this role should review the Expression of Interest document before submission. The document details the role, required skills and experience, and the selection process. The deadline to submit an Expression of Interest is Friday, 25 June 2021 at 23:59 UTC. All submissions should be sent to gnso-secs(a)icann.org. Read more. REMINDER: Participate or Observe: EPDP on IDNs The Generic Names Supporting Organization (GNSO) Expedited Policy Development Process (EPDP) Team on Internationalized Domain Names (IDNs) welcomes anyone to join as a participant or an observer. Please contact gnso-secs(a)icann.org to sign up as a participant or an observer. Read more. Public Comment CLOSES NEXT WEEK: Draft North America Engagement Plan FY21-25 Close Date: Friday, 2 July 2021 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A Close Date: Monday, 19 July 2021 Volume 3, Issue 45 | Archive | Next Issue: Monday, 28 June ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | Constant Contact Data Notice Sent by david.olive(a)icann.org powered by Try email marketing for free today!

1 0

Alert Members report & voting process outcome ccNSO PDP Retirement Policy Retirement ccTLDs
by Bart Boswinkel June 24, 2021

June 24, 2021

Dear all, First of all apologies for cross-posting. As you may know the ccNSO Policy Development Process on retirement of ccTLDs has reached a very important milestone: the ccTLD Managers who are member of the ccNSO will have the opportunity to express whether they support the proposed policy. As every vote counts (due to the requirement that at least 87 out of 172 members need to cast a vote) and this policy is important for all, we want to bring this opportunity to vote to your attention. The voting will start on 07 July 2021, 00.01 UTC and is open up and until 28 July 2021, 23.59 UTC and only the primary contacts of the ccNSO member (see: https://ccnso.icann.org/en/primary-contact) will receive a ballot to vote. The primary contacts have already been contacted by the ccNSO Secretariat. The Members Report, which includes the recommended policy and ccNSO Council decision of 17 June 2021, is available at: https://ccnso.icann.org/en/workinggroups/pdp-retirement.htm The policy is included in the Final Paper of the Retirement Working Group section 1- 5 (Annex A of the Members Report). For ease of understanding, a summary and flow diagram of the proposed policy are included below, which is also included in the Members Report. Kind regards, Bart Boswinkel Issue Manager ccPDP3 Retirement ccTLDs Summary of recommended policy on the retirement of ccTLDs Objective of the Policy. The Policy should provide clear and predictable guidance and document a process that is orderly andreasonable up and to, but excluding, the removal of a ccTLD from the Root Zone. Applicability of the Policy. This Policy applies to all entries in the Root Zone database which are identified as ccTLDs and are subject to a Retirement Triggering Event, which are defined as: * For 2 letter ccTLDs which corresponded to an ISO 3166-1 Alpha-2 Code Element – The deletion of the Alpha-2 Code Element from the ISO 3166-1 Standard by the ISO 3166-1 Maintenance Agency (“ISO 3166/MA”). * For 2 letter Latin ccTLDs which do not correspond to an ISO 3166-1 Alpha-2 Code Element – The ISO 3166-1 Making a change (other than making it an ISO 3166-1 Alpha-2 Code Element) to any of these. * For IDN ccTLDs – The Triggering Event will be identified in the Policy on the (de-)selection of IDN ccTLD strings, which was initiated on 21 May 2020. Retirement Process Expectations. There is a good faith obligation for both the IANA Naming Functions Operator (IFO) and theManager of the retiring ccTLD to ensure an orderly shutdown of the retiring ccTLD which takes into consideration the interests of itsregistrants and the stability and security of the DNS. Notice of Removal & Standard Duration Removal Process. Once the IFO confirms that a Retirement Triggering Event has occurred and that the ccTLD should be retired, it shall promptly notify the Manager of the ccTLD that the ccTLD shall be removed from the Root Zone five (5) years from the date of the notice (Notice of Removal), unless the Manager has requested an extension and this extension was granted. Extension of Removal Process. If the Manager wishes to request an extension of the Default 5 years removal process, it must request this from the IFO as part of a Retirement Plan. Retirement Plan. If the Manager of the retiring ccTLD wishes to request an extension beyond the five (5) standard duration of the process, the manager must produce a Retirement Plan which is acceptable to the IFO. The retirement plan must be produced within twelve (12) months of the date the Notice of Removal was sent. To be acceptable, the Retirement Plan shall contain: * A copy of the Notice of Removal * Date the ccTLD is expected to stop taking registrations, renewals and transfers that exceed the Date of Removal fromthe Root Zone. * Details of a communications plan to advise the registrants of Retirement of the ccTLD. * The length of the extension requested (a maximum of five (5) additional years) including the proposed Date of the removal of the ccTLD from the Root Zone. * The reasons for requesting an extension as well as an impact analysis which supports the reasons for making the extension request. Granting Extension. Granting an extension to the Default Retirement Date is at the discretion of the IFO and shall not be unreasonably withheld. If the ccTLD manager and the IFO cannot agree on a Retirement Plan within the required timeframe the ccTLD shall be removed from the Root Zone 5 years from the date the IFO has sent the Notice of Removal to the Manager of the retiring ccTLD. If the request for an extension is rejected and the ccTLD Manager believes that the rejection is unreasonable or inconsistent with the Retirement Plan requirements, it may appeal the decision by the IFO. Oversight. This Policy is directed at ICANN and the IFO as the entity that performs the IANA Naming Functions with respect to ccTLDs. This Policy will not change or amend the role that the ICANN Board of Directors has with respect to individual cases of ccTLD Delegation, Transfer and Revocation. Review. The WG has identified two situations that could be subject to a review: * If the ccTLD Manager disagrees with the IFO’s decision to initiate the Retirement Process for a 2 letter Latin ccTLD which does not correspond to an ISO 3166-1 Alpha-2 Code Element following the ISO 3166-1 MA making a change to this entry. * If the ccTLD Manager disagrees with the IFO’s decision to refuse the request for an extension of the default five (5) year duration of the Retirement Process. [Diagram Description automatically generated]

1 0

July 2021 Council teleconference | 22 July at 12:00 UTC
by Kimberly Carlson June 24, 2021

June 24, 2021

Dear all, The July 2021 Council teleconference has been scheduled for 22 July at 12:00 UTC. Agenda will be circulated prior to the call. Call details: Join Zoom Meeting https://icann.zoom.us/j/92316801768?pwd=OTNtMmJNSHljdHRUVHpyWm53RG5MZz09 Meeting ID: 923 1680 1768 Passcode: Council-07 Wiki: https://community.icann.org/x/NIS1CQ (background material, attendance, recording, transcript will be posted as it becomes available)

1 0

Monday, 21 June 2021
by ICANN Community Leadership Digest June 21, 2021

June 21, 2021

Monday, 21 June 2021 ICANN Community Leadership Digest 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 CLOSES WEDNESDAY: Call for Expressions of Interest: ICANN 2022 NomCom Chair and Chair-Elect CLOSES FRIDAY: Call for Expressions of Interest: Chair of the EPDP on IDNs NEW: ICANN to Open Request for Information on Identity Verification Methods NEW: Survey Results on Transition to In-Person ICANN Public Meetings NEW: Enforcement of Registration Data Accuracy Obligations Before and After GDPR NEW: Hello World: Enabling Internationalized Domain Names (IDNs) REMINDER: Participate or Observe: EPDP on IDNs Public Comment CLOSES NEXT WEEK: Draft North America Engagement Plan FY21-25 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A Information Sharing CLOSES WEDNESDAY: Call for Expressions of Interest: ICANN 2022 NomCom Chair and Chair-Elect ICANN is seeking Expressions of Interest for the Chair and Chair-Elect of the 2022 Nominating Committee (NomCom). Expressions of Interest, which will be maintained as confidential, should be sent to nomcomchair2022(a)icann.org no later than 23 June 2021. A suggested form for submitting an Expression of Interest is available here. Read more. CLOSES FRIDAY: Call for Expressions of Interest: Chair of the EPDP on IDNs The Generic Names Supporting Organization (GNSO) Council announced that it is seeking Expressions of Interest for a chair of the Expedited Policy Development Process (EPDP) team that will address issues related to Internationalized Domain Names (IDNs). Candidates interested in serving in this role should review the Expression of Interest document before submission. The document details the role, required skills and experience, and the selection process. The deadline to submit an Expression of Interest is Friday, 25 June 2021 at 23:59 UTC. All submissions should be sent to gnso-secs(a)icann.org. Read more. NEW: ICANN to Open Request for Information on Identity Verification Methods ICANN will soon open a Request for Information (RFI) on identity verification methods related to the potential implementation of System for Standardized Access/Disclosure to Non-Public Registration Data (SSAD). We will be looking for information from experts, organizations, and businesses familiar with the design and operational requirements outlined in the SSAD-related recommendations and encourages submissions from a range of industries and backgrounds. Since the RFI will only be open for a few weeks, we request that the ICANN community start preparing for the RFI as soon as possible. Please share this request with your networks and contacts. Read more. NEW: Survey Results on Transition to In-Person ICANN Public Meetings ICANN announced that the survey results on the transition to in-person ICANN Public Meetings are now available. The results show that the majority of the community is interested in returning to in-person meetings. We saw similar results when we asked if you would be willing to attend in person if safety precautions were taken, such as physical distancing, onsite rapid testing, and face mask requirements. Find the survey results here. NEW: Enforcement of Registration Data Accuracy Obligations Before and After GDPR On 25 May 2018, the European Union's General Data Protection Regulation (GDPR) went into effect. In response, ICANN adopted the Temporary Specification for gTLD Registration Data (Temporary Specification) and the Interim Registration Data Policy for gTLDs (Interim Policy). This blog provides highlights of a report, which explains how GDPR has impacted ICANN organization's (org) enforcement of registrars' registration data accuracy obligations in generic top-level domains (gTLDs). For the full report click here. NEW: Hello World: Enabling Internationalized Domain Names (IDNs) For more than two decades, the technical community, ICANN, and volunteers around the world have been working together to internationalize the Domain Name System (DNS) to promote linguistic diversity on the Internet. Initially, this work has focused on the introduction of Internationalized Domain Names (IDNs) at the second level and eventually for top-level domains (TLDs). This has included the New Generic TLD (gTLD) Program, the largest expansion of the DNS to date as well as IDN country code TLDs (ccTLDs), making it possible for people around the world to connect with their communities through domain names in local languages and scripts such as Arabic, Chinese, Cyrillic, and Devanagari. Read more. REMINDER: Participate or Observe: EPDP on IDNs The Generic Names Supporting Organization (GNSO) Expedited Policy Development Process (EPDP) Team on Internationalized Domain Names (IDNs) welcomes anyone to join as a participant or an observer. Please contact gnso-secs(a)icann.org to sign up as a participant or an observer. Read more. Public Comment CLOSES NEXT WEEK: Draft North America Engagement Plan FY21-25 Close Date: Friday, 2 July 2021 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2A Close Date: Monday, 19 July 2021 Volume 3, Issue 44 | Archive | Next Issue: Thursday, 24 June ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | Constant Contact Data Notice Sent by david.olive(a)icann.org powered by Try email marketing for free today!

1 0

outcome of the selection process for one volunteer (1) to serve on the 2022 ICANN Nominating Committee (NomCom)
by Joke Braeken June 18, 2021

June 18, 2021

Dear Councillors, This is to inform you about the conclusion and outcome of the selection process for one volunteer (1) to serve on the 2022 ICANN Nominating Committee (NomCom) on behalf of the ccNSO. The selection process closed 17 June 2021 at 23:59 UTC. In the table below you will be able to find an overview of the ballot numbers, their date of receipt and the order of preference as listed by the individual council members. Participation of councilors in selection processes is tracked on the Council workspace. Date receipt ballot number Abdullah Akcam Eberhard Lisse Joerg Schweiger Juhani Juselius 10-Jun 1 4 2 1 3 10-Jun 2 2 3 1 4 10-Jun 3 3 4 2 1 10-Jun 4 1 3 2 4 10-Jun 5 3 0 2 4 11-Jun 6 1 4 2 3 14-Jun 7 1 2 4 3 14-Jun 8 2 1 4 3 15-Jun 9 2 0 4 3 15-Jun 10 2 1 3 4 15-Jun 11 3 2 1 4 16-Jun 12 1 2 3 4 16-Jun 13 2 3 1 4 16-Jun 14 4 2 1 3 17-Jun 15 4 3 2 1 17-Jun 16 4 3 1 2 39 35 34 50 The candidate with the most supportive votes is Juhani Juselius (.fi) Next steps The candidate receiving most supportive votes for one of the aforementioned roles, is selected. The ccNSO Secretariat will inform relevant ICANN staff of the selection of the candidates, and will inform and thank all candidates. Background The ccNSO Council issued a call for expressions of interest or for one (1) volunteer to serve on the 2022 ICANN Nominating Committee (NomCom) on behalf of the ccNSO. Read more here: https://ccnso.icann.org/en/announcements/announcement-26may21-en.htm The selection happens according to the ccNSO Guideline: ccNSO Appointment Procedures as published on https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso… Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0