- ALAC - lists.icann.org

Fwd: [ICANN Community Leaders] 23 April 2020
by Maureen Hilyard April 23, 2020

April 23, 2020

Thursday, 23 April 2020 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 - NEW: ICANN org’s Multifaceted Response to DNS Abuse - NEW: Webinar to Discuss New Projections Based on Economic Impact of COVID-19 - NEW: Policy Development Fundamentals Course on ICANN Learn - NEW: Consensus Playbook Now Available - REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process ICANN68 Planning - REMINDER: ICANN68 Publication Support Public Comment - CLOSES TODAY: Proposal for Bangla Script Root Zone Label Generation Rules - EXTENDED: Phase 1 Initial Report of the Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process - Addendum to the Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 - Guidelines for Developing Reference Label Generation Rules (LGRs) for the Second Level Version 2 - ICANN Africa Regional Plan for Fiscal Years 2021-2025 - NEW: Draft PTI FY21-24 Strategic Plan Information Sharing NEW: ICANN org’s Multifaceted Response to DNS Abuse From: Göran Marby, President and CEO While the March report <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> from ICANN’s Domain Abuse Activity Reporting <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> system shows a general reduction in second-level gTLD domain names identified as being used in phishing, malware distribution, and botnet command and control, it has been widely reported that criminals are taking advantage of the global COVID-19 pandemic by launching malicious online campaigns. There have also been numerous reports of spikes in the use of COVID-19-related domain names for DNS Abuse. ICANN’s response to DNS Abuse is always multifaceted, reflecting the need to address abuse within the constraints of ICANN’s Bylaws and policies as defined by the ICANN community, and by obeying local law and regulatory requirements. In general, ICANN Contractual Compliance (ICANN Compliance) enforces the contractual obligations set forth in ICANN’s policies and agreements, including the Registry Agreement (RA) and the Registrar Accreditation Agreement (RAA), the Office of the Chief Technology Officer (OCTO) provides subject-matter expertise, and the Global Domains Division (GDD) works with the contracted parties to help support the delivery of registry and registrar services in accordance with contractual and consensus policy obligations. In the case of COVID-19-related abuse, the same actors within the ICANN organization have prioritized handling of COVID-19-related DNS Abuse, working with their respective communities to help mitigate the new threats. These threats include phishing, business email compromise, malware distribution, scams, and many other types of attacks. In some cases, the criminals are luring Internet users into giving away their access credentials and confidential information with the promise that they are buying supposed cures for the coronavirus and personal protective equipment. In other cases, the attackers are spreading disinformation or infecting unsuspecting users’ devices with malware. Unfortunately, many of these malicious activities use or leverage domain names and some in the Internet community are reasonably asking what role ICANN has in attempting to stem these abuses. Read more <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> NEW: Webinar to Discuss New Projections Based on Economic Impact of COVID-19 From: Susanna Bennett, Senior Vice President and Chief Operating Officer ICANN org will hold two public webinars to discuss the impact of the COVID-19 pandemic on its current and planned work. ICANN org has recently developed new projections in ICANN’s Revised Draft FY21-25 Operating and Financial Plan and Revised Draft FY21 Operating Plan and Budget, which will be presented during the webinars for information and discussion and will be proposed for adoption by the ICANN Board in early May. Please join one of the two scheduled informational webinars on 28 April 2020 to learn more about the impact of COVID-19 on ICANN’s planned work as detailed in the Revised Draft FY21-25 Operating and Financial Plan and Revised Draft FY21 Operating Plan and Budget. ICANN welcomes the community’s questions and comments. Webinar #1 Tuesday, 28 April 2020, 15:00-16:30 UTC Remote Participation <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> Webinar #2 Tuesday, 28 April 2020, 23:00-00:30 UTC Remote Participation <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> NEW: Policy Development Fundamentals Course on ICANN Learn From: David Olive, Senior Vice President, Policy Development Support Policy Development Fundamentals is a new foundational course available on ICANN Learn <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…>, ICANN's free and open online learning platform. The course takes learners through an overview of the different components of policy development at ICANN. Along with the DNS Fundamentals course, Policy Fundamentals will serve as a cornerstone for developing capacity in the ICANN ecosystem. Both courses will be translated into Arabic, Chinese, French, Russian, and Spanish. NEW: Consensus Playbook Now Available From: David Olive, Senior Vice President, Policy Development Support The Consensus Playbook <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> aims to provide community members with practical tools and best practices for building consensus, bridging differences, and breaking deadlocks within ICANN processes. The playbook stresses that consensus building should be considered as a journey and provides detailed guidance from the beginning to the end of the process, including 15 “plays” applicable to the various phases of community work. The playbook does not seek to change the definition of consensus or the methods of decision-making of a community group; it does not seek to introduce any new requirements either. It is designed for the ICANN community and is only permitted to be used by the ICANN community in support of ICANN-related work. The playbook shall not be used for any non-ICANN related purposes. Originating from the GNSO Policy Development Process (PDP) 3.0 initiative <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> and a subsequent Additional Budget Request <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…>, the Consensus Playbook has been created for the ICANN community to reference and use. The Consensus Building Institute (CBI), an external vendor contracted by ICANN org, developed the playbook with the requirement of broad applicability across the community, beyond GNSO policy development working groups. CBI interviewed 14 ICANN community leaders across the Supporting Organizations and Advisory Committees, who shared their extensive consensus-building experience in leading and participating in working groups and community groups. All ICANN community members are strongly encouraged to review the playbook. We anticipate additional opportunities for the ICANN community to discuss its contents and practical utility. REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process Announcement <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> On 31 March 2020, ICANN opened a call for Expressions of Interest for panelists to serve on the omnibus Standing Panel for ICANN's Independent Review Process (IRP). Candidates for the IRP omnibus Standing Panel should review the Expressions of Interest document <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…>before submission. The document includes the following information: - Panel Position Description - Required or Highly Preferred Skills - Required or Highly Preferred Experience - Time Commitment - Compensation and Selection Expressions of Interest should be submitted to irp-standingpanel-eoi2020(a)icann.org <IRP-Standingpanel-EOI2020(a)icann.org> by 23:59 UTC on Friday, 31 July 2020. ICANN68 Planning REMINDER: ICANN68 Publication Support Executive: David Olive, Senior Vice President, Policy Development Support Design and Translation Deadline If you require design assistance for your publication, you need to provide all the text, images, layout, and publication type/size requirements (i.e. newsletter vs. 1-pager vs. trifold, etc.). You will receive a maximum of 2 iterations of the publication. Please provide everything by Wednesday, 13 May 2020. Please keep in mind that all materials, new or updated, need to be evergreen. Translation-only Deadline If your publication requires translation, please provide the final material(s) by Monday, 25 May 2020. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. Public Comment CLOSES TODAY: Proposal for Bangla Script Root Zone Label Generation Rules <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> Close Date: Thursday, 23 April 2020 EXTENDED: Phase 1 Initial Report of the Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> Close Date: Monday, 4 May 2020 Addendum to the Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> Close Date: Tuesday, 5 May 2020 Guidelines for Developing Reference Label Generation Rules (LGRs) for the Second Level Version 2 <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> Close Date: Tuesday, 12 May 2020 ICANN Africa Regional Plan for Fiscal Years 2021-2025 <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> Close Date: Wednesday, 27 May 2020 NEW: Draft PTI FY21-24 Strategic Plan <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> Close Date: Monday, 1 June 2020 Volume 2, Issue 33 | Archive <http://r20.rs6.net/tn.jsp?f=0019H9vcYFiK-3VOkZfPDnHWP6z4allpes_Ct8fJ1qxO71k…> | Next Issue: Monday, 27 April 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> | About Constant Contact <http://www.constantcontact.com/legal/about-constant-contact> Sent by david.olive(a)icann.org in collaboration with [image: Trusted Email from Constant Contact - Try it FREE today.] <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> Try email marketing for free today! <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> _______________________________________________ SO-AC-SG-CLeaders mailing list SO-AC-SG-CLeaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Overlap between ALSes and non-At-Large parts of the ICANN community
by Alan Greenberg April 23, 2020

April 23, 2020

This is a long message, but the issue is important. Please take the time to read it carefully. This particularly applies to current ALAC Members and RALO Leaders. Over the past years, there have been many discussions about whether it is problematic to have both individuals and ALSes associated with At-Large to be members (or voting members) of other parts of the ICANN Community (and in particular, NCSG). These issues have never been resolved, and although they have come up for discussion regularly, addressing them has always been deferred. To the extent that these issues fall under the remit of the ALS-Mobilization Working Party (WP), they have been discussed at length. We are in the process of finalizing our report on ALS Expectations and Criteria, and as such have tentatively finalized our recommendation related to these areas. I would like to present them to this group so that any comments can be brought back to the WP. We looked at two areas: 1. Whether there is any problem with ALS representatives joining and participating in other parts of ICANN 2. Whether an organization that is an ALS can be an institutional member of some other part of ICANN To set the stage, one should note: - we have MANY individuals associated with At-Large (including ALAC Members) who are members of NCSG and a few who are members of various other parts of the GNSO, ccNSO, GAC, SSAC, the Board and no doubt other parts of ICANN; - we have about 40 ALSes that are also institutional members of NCSG. - Other groups, particularly within the GNSO have rules that multiple memberships may exist, but only once can have vote-casting privileges (such as between the Registrar and Registry SGs, or the Business and Intellectual Property Constituencies). There also rules that prohibit multiple memberships in specific situations. 1. ALS Representatives There was virtually no concern with an ALS Representative being a non-voting member of some other part of ICANN (presuming the concept of a non-voting member applies to that other group). ALS Reps may cast votes within RALOs (either based on their own views or directed by their ALS leadership or membership (we do NOT tell ALSes how to conduct their affairs). There was some concern about an ALS Rep doing so while also holding a vote in some other part of ICANN. However, there was a very strong consensus that the nature of votes within a RALO, and the impact that these votes have on substantive policy issues or the selection of individuals was not sufficiently large as to warrant rules prohibiting such involvement. The group did however strongly support full disclosure of any such overlaps. According, our current recommendation reads: There is no prohibition on an ALS Representative holding roles in other parts of ICANN (non-At-Large), but those roles comparable to those listed below must be formally declared. a) Member of another constituent part of ICANN (AC/SO, sub-constituency) b) Leadership role in any of the above c) Member of a non-At-Large working group (such as GNSO PDP, CCWG, etc) d) Formally appointed representative of a non-At-Large ICANN group to a PDP, CCWG, Specific Review, etc) e) Leader of a non-At-Large working group (such as GNSO PDP, CCWG, Specific Review) Note that this is ONLY in reference to ALS Representatives. Some WP members expressed concern if, for instance, an ALAC member help an influential role in another part of ICANN, but rules governing ALAC Members are FAR out of the scope of the WP. We did note that the ALAC might wish to have such a discussion at some point. 2. ALS Institutional Membership This question concerns whether an entity that is an ALS may also be a member of some other part of ICANN (regardless of whether the representatives to each part of ICANN are the same or different people). Again, there was little concern for an ALS being an non-voting INSTITUTIONAL member of some other part of ICANN. The discussion on whether dual voting is problematic was quite spirited and strong positions were taken on both sides. However, after a substantial discussion on what the actual harm was that we were trying to avoid, and in fact, the perceived harm of currently having nearly 40 ALSes with voting rights in both and At-Large RALO and the NCSG, there was a very strong consensus in the WP there was in fact no real harm. Accordingly our current recommendation reads: There is no prohibition related to an ALS being an institutional member of some other part of ICANN (such as the NCSG or IPC within the GNSO, or a member of the ccNSO), but such an overlapped membership must be declared in the ALS application and in the biennial report. So in summary, in both cases, there was a strong consensus that although concerns had been expressed, we could not find any real harm in the current status quo, and that disclosure could address any perceived conflicts. I and the WP would appreciate comments, and in particular, those from people who believe that our recommendations are wrong (explaining why). Alan

8 7

Fwd: ICANN News Alert -- ICANN Systems Controls Validated by Annual IANA Functions Audit
by Maureen Hilyard April 22, 2020

April 22, 2020

[image: ICANN Announcement Alerts] *ICANN Systems Controls Validated by Annual IANA Functions Audit <https://newsalerts.icann.org/I010SC80P0gFNd220o0RE00>* 22 April 2020 LOS ANGELES – 22 April 2020 – The Internet Corporation for Assigned Names and Numbers (ICANN) has completed another year of audits of the key systems used to deliver the Internet Assigned Numbers Authority (IANA) functions. Accounting firm RSM US LLP conducted the audits of the Registry Assignment and Maintenance Systems (RAMS) and the root zone Domain Name System Security Extensions (DNSSEC) services for the period of 1 December 2018 through 30 November 2019. For the seventh consecutive year, a Service Organization Control (SOC) 2 audit of the RAMS shows that the ICANN organization has the appropriate controls in place to ensure the security, availability, and integrity of IANA request processing. For the tenth consecutive year, an exception-free audit has been completed for the management of the DNSSEC root key signing key (KSK), which is the trust anchor of the Domain Name System. Using the SOC 3 framework, the audit demonstrates that effective security, availability, and process integrity controls exist to manage the root KSK. The report is publicly available at http://iana.org/audits. <https://newsalerts.icann.org/f00od0P08T001R22CNEGg00> This year's audit period included reviewing the final milestones relating to regeneration of KSK assets. Following the first KSK rollover in 2018, this audit period involved the deletion of the first KSK and associated destruction of equipment and assets surrounding those, dating back to 2010. "We have come a long way in the ten years since we conducted our first KSK ceremony and started our third-party audit program. From developing strong controls to ensuring comprehensive transparency in our process, this team has managed to meet the audit criteria set by the AICPA every single year. I am very proud of everyone who contributed to that achievement," said Kim Davies, President of Public Technical Identifiers and Vice President for IANA at ICANN. SOC audits evaluate an organization's controls in relation to "trust services principles and criteria" and are managed by the American Institute of Certified Public Accountants (AICPA). 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: shadow] *[image: Twitter] <https://newsalerts.icann.org/R00P081R2d0020g0CUEoHN0>* [image: Facebook] <https://newsalerts.icann.org/gV080NP02201RE0dC000Iog> [image: Instagram] <https://newsalerts.icann.org/b0000dRPoCW0Eg1J020280N> [image: Linkedin] <https://newsalerts.icann.org/MN0E0208Co01d00KP0gR0X2> [image: YouTube] <https://newsalerts.icann.org/wR8EN0dCP0000g1L0022Y0o> [image: shadow1] Unsubscribe <https://newsalerts.icann.org/y1oC82gN0d0PERZ00M00020> | https://www.icann.org <https://newsalerts.icann.org/p0000C01OE0200NRdP0g8p2> <https://newsalerts.icann.org/c00022gC0PNR01dEP081p00>

1 0

Fwd: ICANN News Alert -- ICANN Announces Webinar to Discuss New Funding Projections Based on Economic Impact of COVID-19
by Maureen Hilyard April 22, 2020

April 22, 2020

[image: ICANN Announcement Alerts] *ICANN Announces Webinar to Discuss New Funding Projections Based on Economic Impact of COVID-19 <https://newsalerts.icann.org/CRg00u0HP0oC0Nd82201E00>* 22 April 2020 LOS ANGELES – 20 APRIL 2020 – The Internet Corporation for Assigned Names and Numbers (ICANN) announced today that it will hold two public webinars to discuss the impact of the COVID-19 pandemic on its current and planned work. ICANN org has recently developed new projections in ICANN's Revised Draft FY21-25 Operating and Financial Plan and Revised Draft FY21 Operating Plan and Budget, which will be presented during the webinars for information and discussion and will be proposed for adoption by the ICANN Board in early May. Please join one of the two scheduled informational webinars on 28 April 2020 to learn more about the impact of COVID-19 on ICANN's planned work as detailed in the Revised Draft FY21-25 Operating and Financial Plan and Revised Draft FY21 Operating Plan and Budget. ICANN welcomes the community's questions and comments. Webinar Information 28 April 2020 1. 1500 – 1630 UTC https://icann.zoom.us/j/95689685323?pwd=YWdWK1VNZnJsVEVaeFpha05zN0t1QT09 <https://newsalerts.icann.org/tdEg220oC80Pv00NR00001I> 2. 2300 – 0030 UTC https://icann.zoom.us/j/99482978256?pwd=RUJyZU9USzFjOTA0dWcwOVNWY2ZqZz09 <https://newsalerts.icann.org/uJN0008R0P0d0w02og2CE10> 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: shadow] *[image: Twitter] <https://newsalerts.icann.org/U2xg00E0PR0Cdo021N000K8>* [image: Facebook] <https://newsalerts.icann.org/p0000C01yE020LNRdP0g8o2> [image: Instagram] <https://newsalerts.icann.org/TzNCo0g010008RM20P02dE0> [image: Linkedin] <https://newsalerts.icann.org/V8RA000do10E200CP02gNN0> [image: YouTube] <https://newsalerts.icann.org/j2BR012PC00080gNEdO0o00> [image: shadow1] Unsubscribe <https://newsalerts.icann.org/p0000C01CE020PNRdP0g8o2> | https://www.icann.org <https://newsalerts.icann.org/v0080NoQ0dPECgD1R022000> <https://newsalerts.icann.org/m000NE20002d1Pg8RoR0CE0>

1 0

FOR REVIEW: ALAC Sub-Committee on Outreach and Engagement - Draft FY21 Strategy Open for Comment
by ICANN At-Large Staff April 21, 2020

April 21, 2020

Dear All, On behalf of Maureen, ALAC Chair, and Daniel Nanghaka, Chair of the ALAC Sub-Committee on Outreach and Engagement, please find the first draft of the FY21 At-Large Virtual Outreach and Engagement Strategy at: https://community.icann.org/display/atlarge/ICANN+FY21+At-Large+Virtual+Out… . This draft strategy includes the main FY21 priorities and activities of the ALAC Sub-Committee on Outreach and Engagemen, with a focus on virtual activities given the current COVID-19 situation. Please feel free to review and add your comments on the Google doc through 30 April 2020. Maureen has requested that you read the draft strategy ahead of the ALAC monthly meeting scheduled for Tuesday, 28 April 2020 from 16:00 – 18:00 UTC. Kind regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Fwd: [ccnso-members] ccPDP Retirement Working Group Draft Report Webinars
by Barrack Otieno April 21, 2020

April 21, 2020

Dear ALAC, For those that expressed interest in the ccPDP retirement Webinars, use the details below to join the meeting. Best Regards ---------- Forwarded message --------- From: Kimberly Carlson <kimberly.carlson(a)icann.org> Date: Tue, Apr 21, 2020 at 3:49 PM Subject: [ccnso-members] ccPDP Retirement Working Group Draft Report Webinars To: ccTLDcommunity(a)cctld-managers.org <ccTLDcommunity(a)cctld-managers.org>, ccnso-members(a)icann.org <ccnso-members(a)icann.org> Cc: ccnso-council(a)icann.org <ccnso-council(a)icann.org>, gac-staff(a)icann.org < gac-staff(a)icann.org> Dear all, In March 2017, the ccNSO Council resolved to initiate a Policy Development Process (PDP) to develop policies for Review Mechanisms and on the retirement of ccTLDs. The initial focus was on retirement of the ccTLDs then development of policy for a Review Mechanism. (Issue Report <https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-05/…> ) The *Working Group on the retirement of ccTLDs* has completed their substantive work and produced a draft final report. The full report will be published for public comment at the end of April/early May. In preparation, Working Group will conduct two webinars to accommodate different time zones (you only need to attend one webinar, each session will cover the same material): *ccPDP Retirement Working Group Draft Report Webinar #1 | 23 April 2020 | 21:00 UTC* Register in advance for this webinar: https://icann.zoom.us/webinar/register/WN_M2BNZHXVQvmX8KZ4bIBL1g *ccPDP Retirement Working Group Draft Report Webinar #2 | 24 April 2020 | 11:00 UTC* Register in advance for this webinar: https://icann.zoom.us/webinar/register/WN__RbvBUXnTsexiVc0fxYHgA After registering, you will receive a confirmation email containing information on how to join the webinar. If you unable to attend either session, the presentation along with the recordings will be posted on the wiki: https://community.icann.org/x/oYPsBw Thank you and look forward to your participation and feedback. Best regards, Kimberly Carlson Policy Support - Lead _______________________________________________ Ccnso-members mailing list Ccnso-members(a)icann.org https://mm.icann.org/mailman/listinfo/ccnso-members _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A

1 0

Re: [ALAC] Overlap between ALSes and non-At-Large parts of the ICANN community
by Alan Greenberg April 20, 2020

April 20, 2020

Thanks Evan. Yes, overall behaviour for our community is well out of our scope, but this was discussed and it is one of the "sidebar" things we will be recommending to the ALAC to consider. Both submitting statements of interest and possible conflicts, and regular updating. Alan At 2020-04-20 01:00 AM, Evan Leibovitch wrote: >Hi Alan, > >I agree that disclosure is the best remedy. Just one general comment. > >Are the rules reciprocal? We have had instances in which members of >other constituencies have tried (sometimes ... energetically) to >influence At-Large positions and in some cases disrupt what might >otherwise be consensus. While often being candid and open about the >cross-participation, I have on numerous times heard the "I may work >for a contracted but I'm an end-user too!" refrain upon >confrontation. I would hesitate to put many limitations, or >disclosures, on At-Large participants contributing elsewhere in >ICANN if there is no reciprocity. > >To this end I would suggest that anyone participating in a >substantive discussion in either a RALO or an At-Large WG (who is >not a verifiable individual RALO participant or member of an ALS) >should be obligated to file and maintain an accurate SOI, I had to >have one on file anytime I did anything touching the GNSO, so it's >not like we'd be creating an imbalance, And anyone without conflicts >could do the SOI very quickly. > >- Evan

1 0

Fwd: [ICANN Community Leaders] 20 April 2020
by Maureen Hilyard April 20, 2020

April 20, 2020

Monday, 20 April 2020 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 - REMINDER: PIR Transaction and Proposed Public Interest Commitments Update - REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process ICANN68 Planning - NEW: ICANN68 Publication Support Public Comment - CLOSES TODAY: Proposal for Chinese Script Root Zone Label Generation Rules - CLOSES THURSDAY: Proposal for Bangla Script Root Zone Label Generation Rules - Phase 1 Initial Report of the Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process - Addendum to the Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 - Guidelines for Developing Reference Label Generation Rules (LGRs) for the Second Level Version 2 - ICANN Africa Regional Plan for Fiscal Years 2021-2025 Information Sharing REMINDER: PIR Transaction and Proposed Public Interest Commitments Update Executive: Göran Marby, ICANN President and CEO Since Public Interest Registry (PIR) formally notified ICANN of the proposed change of control transaction on 14 November 2019 <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> , the ICANN org and Board have worked together to thoughtfully and thoroughly evaluate the proposed acquisition to ensure that the .ORG registry remains secure, reliable, and stable. Throughout this process, ICANN has urged PIR, the Internet Society (ISOC), and Ethos Capital (Ethos) to engage and consult with the .ORG community, and to provide full transparency regarding the proposed transaction. Today, ICANN is publishing <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> PIR's recently updated Public Interest Commitments (PICs), which were received by ICANN on 7 April 2020. PIR proposes that these PICs be added to the . <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…>ORG Registry Agreement <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…>should ICANN approve the change of control request submitted by PIR. Two versions of the PICs are being published: a "clean <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…>" version and a "redline <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…>" version that shows changes made by PIR from its 16 March 2020 version submitted to ICANN following PIR's Public Engagement process <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> . <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> The revised PICs that ICANN is publishing today are in response to additional questions posed by ICANN as part of its diligence around the change of control request. On 3 April 2020, ICANN provided PIR with two sets of questions. One set of questions are in follow-up to previous ICANN inquiries designed to further understand the proposed transaction and its potential effect on PIR and the .ORG top-level domain (TLD). The second set of questions relate specifically to the proposed PICs. PIR has indicated that it is working to answer all of the questions from ICANN. It is ICANN's intention to post PIR's responses to these questions when they are available, subject to any appropriate requests for confidentiality made by PIR. Many people have questioned the enforceability of PICs by ICANN. To be clear, PICs are enforceable by ICANN. Any Internet user may submit complaints to ICANN Contractual Compliance. In addition, ICANN Contractual Compliance may identify an issue through its proactive monitoring. ICANN's follow-up questions to PIR seek to ensure that ICANN has a clear understanding of each commitment within the PICs, such that it could be enforced should the need arise. The ICANN Board continues to have reservations regarding the enforceability of PIR's proposed PICs. The .ORG Registry Agreement stipulates a specified time period for ICANN to approve or withhold consent of the proposed change of control of PIR. ICANN and PIR have agreed to extend the deadline several times since the original deadline in mid-January, and the deadline for ICANN's response is now Monday, 20 April 2020. Similar to when voluntary commitments in the form of PICs were proposed by applicants for new generic TLDs, ICANN is providing PIR's proposed PICs to the ICANN community with this public notice. Given the fast-approaching deadline for ICANN to make a decision to approve or withhold consent on the requested change of control of PIR, the typical 30-day public notice period has been condensed to seven days. We recognize the full engagement of the .ORG community in PIR's consultation process, but wanted to ensure ICANN remained fully transparent in what is being considered, the concerns still present in the Board's review, and what the Board will be reviewing. How to Participate: Feedback may be submitted as a comment to this blog <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> or through correspondence to me or the ICANN Board. We thank the ICANN community for its active participation in this matter and remain committed to keeping you informed of new developments. REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process Announcement <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> On 31 March 2020, ICANN opened a call for Expressions of Interest for panelists to serve on the omnibus Standing Panel for ICANN's Independent Review Process (IRP). Candidates for the IRP omnibus Standing Panel should review the Expressions of Interest document <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…>before submission. The document includes the following information: - Panel Position Description - Required or Highly Preferred Skills - Required or Highly Preferred Experience - Time Commitment - Compensation and Selection Expressions of Interest should be submitted to irp-standingpanel-eoi2020(a)icann.org <IRP-Standingpanel-EOI2020(a)icann.org> by 23:59 UTC on Friday, 31 July 2020. ICANN68 Planning NEW: ICANN68 Publication Support Executive: David Olive, Senior Vice President, Policy Development Support Design and Translation Deadline If you require design assistance for your publication, you need to provide all the text, images, layout, and publication type/size requirements (i.e. newsletter vs. 1-pager vs. trifold, etc.). You will receive a maximum of 2 iterations of the publication. Please provide everything by Wednesday, 13 May 2020. Please keep in mind that all materials, new or updated, need to be evergreen. Translation-only Deadline If your publication requires translation, please provide the final material(s) by Monday, 25 May 2020. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. Public Comment CLOSES TODAY: Proposal for Chinese Script Root Zone Label Generation Rules <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> Close Date: Monday, 20 April 2020 CLOSES THURSDAY: Proposal for Bangla Script Root Zone Label Generation Rules <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> Close Date: Thursday, 23 April 2020 Phase 1 Initial Report of the Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> Close Date: Monday, 27 April 2020 Addendum to the Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> Close Date: Tuesday, 5 May 2020 Guidelines for Developing Reference Label Generation Rules (LGRs) for the Second Level Version 2 <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> Close Date: Tuesday, 12 May 2020 ICANN Africa Regional Plan for Fiscal Years 2021-2025 <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> Close Date: Wednesday, 27 May 2020 Volume 2, Issue 32 | Archive <http://r20.rs6.net/tn.jsp?f=0012tUUq7jk7WfOQXQshQulqFkHFQAfypxnFK1XemLquiYA…> | Next Issue: Thursday, 23 April 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> | About Constant Contact <http://www.constantcontact.com/legal/about-constant-contact> Sent by david.olive(a)icann.org in collaboration with [image: Trusted Email from Constant Contact - Try it FREE today.] <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> Try email marketing for free today! <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> _______________________________________________ SO-AC-SG-CLeaders mailing list SO-AC-SG-CLeaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Fwd: [ccnso-council] SAVE THE DATE / MARK YOUR CALENDARS: ccPDP on Retirement WG Webinar | Draft Final Report
by Barrack Otieno April 17, 2020

April 17, 2020

Dear AlAC, This is for information purposes. You can join the Webinar of you are interested in the content of the retirement Working groups draft final report. Best Regards ---------- Forwarded message --------- From: Kimberly Carlson <kimberly.carlson(a)icann.org> Date: Thu, 16 Apr 2020, 10:46 pm Subject: [ccnso-council] SAVE THE DATE / MARK YOUR CALENDARS: ccPDP on Retirement WG Webinar | Draft Final Report To: ccTLDcommunity(a)cctld-managers.org <ccTLDcommunity(a)cctld-managers.org>, ccnso-members(a)icann.org <ccnso-members(a)icann.org> Cc: ccnso-council(a)icann.org <ccnso-council(a)icann.org> *SAVE THE DATE / MARK YOUR CALENDARS: ccPDP on Retirement WG Webinar | Draft Final Report* The Working Group on the retirement of ccTLDs has completed their substantive work and produced a draft final report. The full report will be published for public comment at the end of April/early May. In preparation, Working Group will conduct two webinars: - *ccPDP Retirement Working Group Draft Report Webinar #1 | 23 April 2020 | 21:00 UTC* - *ccPDP Retirement Working Group Draft Report Webinar #2 | 24 April 2020 | 11:00 UTC* Additional information, as well as how to pre-register, will be sent early next week. _______________________________________________ Ccnso-council mailing list Ccnso-council(a)icann.org https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

2 1

Re: [ALAC] [ALAC-Announce] VOTE ANNOUNCEMENT: ALAC Vote: AFRALO-APRALO Statement on Middle East and Adjoining Countries (MEAC) Strategy 2021-2025
by Olivier MJ Crépin-Leblond April 17, 2020

April 17, 2020

Dear Colleagues, I am delighted to have seen this come together. Such inter-RALO collaboration should be supported. Kudos to AFRALO and APRALO. Kindest regards, Olivier On 17/04/2020 01:58, ICANN At-Large Staff wrote: > > Dear All, > > This is to let you know that the AFRALO-APRALO Statement on Middle > East and Adjoining Countries (MEAC) Strategy 2021-2025 is now final. > Maureen Hilyard, ALAC Chair, has asked the 15 ALAC members to ratify > this final statement. The statement was ratified by the AFRALO and > APRALO Leadership Teams. > > > > To read the final statement, please > visit: https://community.icann.org/x/3RqJBw > > > > Please note that the ALAC ratification vote will end on 20 April > 2020 23:59 UTC. > > > > Kind Regards, > > > > ICANN Policy Staff in support of the At-Large Community > > Website: atlarge.icann.org > <https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> > > Facebook: facebook.com/icannatlarge > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> > > Twitter: @ICANNAtLarge > <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> > > > _______________________________________________ > ALAC-Announce mailing list > ALAC-Announce(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/alac-announce > > At-Large Official Site: http://www.atlarge.icann.org > _______________________________________________ > By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html

1 0