June 2021 - council - lists.icann.org

IDN Operational Track - proposed agenda item
by Kurt Pritz 05 Jun '21

05 Jun '21

Dear Council Members: I and my RySG Councillor colleagues are writing to propose an agenda item for the May 2021 Council meeting: Next Steps for IDN Operational Track The purpose of this discussion is to reconsider the Council recommended approach for proceeding with the Operational Track vis-à-vis the adoption of the IDN Implementation Guidelines v4.0. The current approach calls for the formation or “reconstituting” of an IDN Guidelines Working Group to review the issues related to its implementation (raised by RySG) and assess a path forward. In the meantime, the Council has spun up the IDN EPDP (i.e., the Policy Track), whose charter is nearing completion. The IDN EPDP will consider some of the same issues that the IDN Implementation Guidelines version 4.0 is addressing. Similarly, the SubPro PDP also considered some of the same issues, and there is a likelihood that the SubPro IRT and IDN EPDP will approach these issues from a different perspective and develop what might be contradicting results. In both of these cases (overlap with the Guidelines Operational Track and with the SubPro IRT), some of the issues require policy considerations rather than operational implementation and are better suited for discussion in a policy development process. These issues are the principle and implementation of the same entity at the second level, and the harmonization of IDN tables (i.e., the creation of a consistent set of variant rules in a given registry TLD). Therefore, I recommend a briefing during the next meeting so that we can better understand these issues, consider our approach, and make a recommendation to the Board. Dennis Tanaka, chair of the IDN EPDP, could lead that presentation. As I understand it so far, a preferable approach would be to continue deferring the adoption of the IDN Implementation Guidelines 4.0 until the issues overlapping with the SubPro PDP and IDN EPDP can be fully deliberated and implemented by the corresponding Implementation Review Teams. Conditions for such a deferral might include: a. a security / stability check to ensure we are not deferring implementation of IDN Guidelines v4.0 that address stability / security issues, b. a provision that the IDN EPDP could forward to the Council IDN Guideline-specific recommendations as they are created, rather than waiting for the final report, and c. coordination with the SubPro IRT so that the SubPro implementation work will not be delayed in any way. In addition to the overlapping efforts between the IDN Guidelines, the SubPro PDP, and the IDN EPDP, the ccNSO is also undertaking an IDN Policy re-write for ccTLDs. While GNSO and ccNSO policies are separable in the ICANN world, differences in outcomes can lead to confusing results for domain registrants and users. Therefore, I think we should take advantage of the timing coincidence between the GNSO and ccNSO efforts to normalize results between the two wherever possible. As described above, there are now several IDN-related efforts for the purpose of enhancing their availability, ease of use and security. I think we should take advantage of the timing of this EPDP to reconcile the various approaches so that there is a coherent approach to IDN policy making and ensuring a good user experience. Thanks for taking the time to read and consider this. Best regards, Maxim Alzoba Sebastien Ducos Kurt Pritz

2 3

Potential Communication Error for ePDP IDN Working Group
by Jeff Neuman 04 Jun '21

04 Jun '21

All, I was crafting a note to send to the GAC about participation in the IDN ePDP when I noticed that the calls for participation (and the Charter itself) is very confusing. The Working Group is supposed to be a Hybrid Model Working Group (NOT representative) open to anyone. The only limitation was that there was expected to a certain number of "Members" that could be called on for Consensus Calls. But there could be a potentially unlimited number of "Participants". The message sent out to the Cs/SGs/SOs/ACs while technically correct in asking for up to 3 Members, does not state anywhere that the leaders should let their groups know that anyone can participate as a Participant (which would not be considered in the up to 3 category). It would be great if we could let send a modified message out to the leaders reminding them that the Working Group is open to anyone that wants to participate. Sincerely, Jeff [cid:image001.png@01D75940.AC8ADE40] 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

2 2

Reminder: Document and Motion deadline Sunday, 06 June 2021 at 23:59 UTC for GNSO Council Meeting 16 June 2021 at 10:30 UTC
by Nathalie Peregrine 04 Jun '21

04 Jun '21

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 06 June 2021 at 23:59 UTC) of the GNSO Council Meeting on Wednesday,16 June 2021 at 10:30 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/2YG1CQ Thank you. Nathalie

1 1

FYI | FW: [Ext] Thursday, 3 June 2021
by Terri Agnew 03 Jun '21

03 Jun '21

FYI From: ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, June 3, 2021 at 10:04 AM To: Terri Agnew <terri.agnew(a)icann.org> Subject: [Ext] Thursday, 3 June 2021 [https://r20.rs6.net/on.jsp?ca=b53f4a0c-6527-4d46-a705-3f52769075d0&a=112202…] Thursday, 3 June 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents ICANN71 Resources · Registration · Schedule · Virtual Backgrounds · Participation Guides · Policy Outlook Report · GNSO Briefing Information Sharing · ENDS TODAY: ICANN71 Prep Week · TODAY: Join ITI Session on Upcoming Improvements to Public Comment · NEW: Designation of ICANN Board Seat 9 · NEW: Call for Expressions of Interest: Chair of the EPDP on IDNs · NEW: Participate or Observe: EPDP on IDNs · NEW: ICANN71 Virtual Meeting Improvements & Updates · REMINDER: Call for Expressions of Interest: ICANN 2022 NomCom Chair and Chair-Elect Public Comment · CLOSES TUESDAY: Maximal Starting Repertoire Version 5 (MSR-5) · Draft North America Engagement Plan FY21-25 ICANN71 Resources Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Participation Guides [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> GNSO Briefing [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Information Sharing ENDS TODAY: ICANN71 Prep Week ICANN announced the ICANN71 Prep Week schedule of nine sessions to prepare the ICANN community for the ICANN71 Virtual Policy Forum. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> TODAY: Join ITI Session on Upcoming Improvements to Public Comment The Information Transparency Initiative (ITI) team is preparing to release enhancements to the ICANN Public Comment feature in August 2021. The ITI team is hosting an ICANN71 Prep Week session to demonstrate these improvements and solicit your feedback. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> NEW: Designation of ICANN Board Seat 9 On 2 June 2021, the Address Supporting Organization (ASO) notified the Empowered Community (EC) Administration of its selection of Mr. Alan Barrett for Seat 9 of the ICANN Board. Sections 7.2(a) and 7.8(c) of the ICANN Bylaws specifically require the EC Administration to "promptly notify the Secretary in writing" and "promptly provide the Secretary (with a copy to the Decisional Participants) with written notice of the designation of those ICANN Board Directors" nominated by the Nominating Committee, a Supporting Organization, and the At Large community. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> NEW: 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 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> 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<mailto:gnso-secs@icann.org>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> NEW: 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<mailto:gnso-secs@icann.org> to sign up as a participant or an observer. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> NEW: ICANN71 Virtual Meeting Improvements and Updates The shift to virtual meetings over the past year has given ICANN the opportunity to expand and improve the virtual meeting format. With ICANN70 under our belts and ICANN71 just around the corner, we would like to highlight some of the recent updates and enhancements that have been implemented for ICANN Public Meetings through some ICANN org platforms. Learn more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…>. REMINDER: 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 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> no later than 23 June 2021. A suggested form for submitting an Expression of Interest is available h [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…>ere [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Public Comment CLOSES TUESDAY: Maximal Starting Repertoire Version 5 (MSR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Close Date: Tuesday, 8 June 2021 Draft North America Engagement Plan FY21-25 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> Close Date: Friday, 2 July 2021 Volume 3, Issue 41 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001P-DetEtA3qH1bhTC…> | Next Issue: Monday, 7 June 2021

1 0

ICANN71 Virtual Meeting Improvements & Updates
by Nathalie Peregrine 02 Jun '21

02 Jun '21

https://www.icann.org/en/blogs/details/icann71-virtual-meeting-improvements… 1 June 2021 Ashwin Rangan<https://www.icann.org/>, SVP, Engineering and Chief Information Officer (CIO) The shift to virtual meetings over the past year has given us a fantastic opportunity to expand and improve upon our virtual meeting format. It has, however, been something of a whirlwind, since we have had less time than usual to onboard and introduce new features. With ICANN70 under our belts and ICANN71 just around the corner, we'd like to highlight some of the recent updates and enhancements that have been implemented for ICANN meetings through some of ICANN org's platforms. * ICANN has linked registration with the meeting schedule using ICANN Account<https://account.icann.org/help>, which enables attendees to register and login with the same credentials in both places. * New 1:1 meeting feature – Our community requested some sort of "hallway" meeting space to allow for the ad hoc conversations we have been sorely missing since our shift to virtual. During ICANN70, ICANN offered all registered attendees the opportunity to schedule their own 1:1 meetings with other registrants through the third party ICANN meetings platform operated by Pathable. ICANN will continue to provide this service to all registered participants for ICANN71<https://71.schedule.icann.org/> * Automated Real-Time Transcription (RTT) – During ICANN70, ICANN org introduced automated RTT on Zoom in English only when English was spoken. For ICANN71, we are now able to offer automated RTT in English at all times, regardless of the language being spoken. Automated captions are available for your own meetings as well and can be enabled within your meeting settings in the Zoom web portal. Zoom itself has also released several updates to their platform, including the highly anticipated Immersive View<https://blog.zoom.us/introducing-zoom-immersive-view/>. This new gallery view includes pre-built scenes, such as a classroom or a café, and places video participants into seats within the scene to promote engagement. We've also seen some changes to existing tools, such as annotation: a new vanishing pen tool allows you to highlight text or objects on a shared screen without having to manually undo the annotation. There is also the addition of a full suite of emoji for in-meeting reactions; previously participants were limited to far fewer. Just over a year ago, ICANN67 – as a virtual meeting – was a novelty. In that short span of roughly 15 months, both ICANN meetings and the Zoom platform have evolved substantially. We are always looking for opportunities to enhance our meetings as this space evolves, and will provide updates whenever significant changes occur.

1 0