May 2021 - council - lists.icann.org

FW: Secretary's Notice
by philippe.fouquart＠orange.com May 21, 2021

May 21, 2021

Dear SG/C leaders, Please note this second notice, this one on the FY22 operational plan & budget. Regards, Philippe From: ECAdmin [mailto:ecadmin-bounces@icann.org] On Behalf Of Peg Rettino via ECAdmin Sent: Friday, May 21, 2021 6:43 PM To: ecadmin(a)icann.org Cc: maarten.botterman(a)board.icann.org; Goran Marby <goran.marby(a)icann.org> Subject: [ECAdmin] Secretary's Notice Greetings, Attached please find the Secretary’s Notice to Empowered Community of Board Approval of FY22 Operating Plan and Budget sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org<mailto:peg.rettino@icann.org> Slack: peg.rettino Direct: 310-301-3868 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Fw: [ECAdmin] Secretary's Notice
by philippe.fouquart＠orange.com May 21, 2021

May 21, 2021

Dear SG/C leaders, Please note the attached notice. Regards, Philippe From: ECAdmin [mailto:ecadmin-bounces@icann.org] On Behalf Of Peg Rettino via ECAdmin Sent: Friday, May 21, 2021 6:44 PM To: ecadmin(a)icann.org Cc: maarten.botterman(a)board.icann.org; Goran Marby <goran.marby(a)icann.org> Subject: [ECAdmin] Secretary's Notice Greetings, Attached please find the Secretary’s Notice to Empowered Community of Board Approval of FY22-26 Five Year Operating and Financial Plan sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org<mailto:peg.rettino@icann.org> Slack: peg.rettino Direct: 310-301-3868 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

GNSO Council resolutions 20 May 2021
by Nathalie Peregrine May 20, 2021

May 20, 2021

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday 20 May 2021 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page. 20210520-1 CONSENT AGENDA * Appointment of the GNSO Council liaison to the System for Standardized Access/Disclosure Operational Design Phase - Janis Karklins Vote results<https://gnso.icann.org/sites/default/files/policy/2021/presentation/gnso-co…> 20210520 – 2 Adoption of the GNSO Review of the GAC ICANN70 Virtual Community Forum Communiqué for submission to the ICANN Board Whereas, 1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the ICANN70 Virtual Community Forum GAC Communiqué<https://gac.icann.org/contentMigrated/icann70-gac-communiqu> and requests that the GNSO Council Chair communicate the GNSO Review of the ICANN70 Virtual Community Forum GAC Communiqué to the ICANN Board. 2. The GNSO Council requests that the GNSO Council Chair also informs the GAC Chair of the communication between the GNSO Council and the ICANN Board. Vote results<https://gnso.icann.org/sites/default/files/policy/2021/presentation/gnso-co…> 20210520 – 3 Motion to initiate the Expedited Policy Development Process on Internationalized Domain Names and adoption of the EPDP on IDNs Charter Whereas, 1. On 14 March 2019, the ICANN Board approved a set of recommendations<https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-0…> developed by ICANN org on how to allocate Internationalized Domain Name (IDN) variant TLD labels. The ICANN Board requested that the GNSO and ccNSO take into account those IDN variant TLD recommendations while developing their respective policies to define and manage IDN variant TLDs for the current TLDs and future TLD applications, while keeping each other informed of the progress in developing the relevant details of their policies and procedures to ensure a consistent solution for IDN variant gTLDs and IDN variant ccTLDs. 2. On 26 June 2019, the GNSO Council established a Scoping Team<https://community.icann.org/display/IDNST> to develop recommendations for the GNSO Council’s consideration on how to address the IDN variant TLD recommendations, as well as issues in the Final Proposed Draft version 4.0 of Internationalized Domain Name ("IDN") Implementation Guidelines<https://www.icann.org/news/announcement-2018-05-10-en> (“IDN Guidelines v. 4.0”), for which the ICANN Board had agreed<https://www.icann.org/en/system/files/correspondence/chalaby-to-drazek-04ju…> to the GNSO Council request [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> to defer its adoption. The Scoping Team met between 15 August 2019 and 12 December 2019. 3. On 23 January 2020, the GNSO Council discussed the Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> from the Scoping Team, which suggested tackling IDN related issues in two tracks: Operational Track and Policy Track. The Policy Track would be tasked to deliberate on: i) the definition and management of IDN variant TLDs, and ii) the change process of the IDN Guidelines and any policy issues related to the IDN Guidelines v. 4.0 identified by the Operational Track Team (consisted of members in the GNSO Contracted Parties House) and agreed upon by the IDN Guidelines Working Group. 4. On 26 January 2020, the ICANN Board approved the Recommendations for the Technical Utilization of the RZ-LGR<https://www.icann.org/en/system/files/files/rz-lgr-technical-utilization-re…> on how to employ the RZ-LGR<https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en> to determine valid IDN TLDs and their variant labels. The ICANN Board requested that the GNSO and ccNSO take into account those RZ-LGR Technical Utilization recommendations while developing their respective policies to define and manage IDN variant TLDs for the current TLDs and future TLD applications. 5. On 21 October 2020, the GNSO Council agreed to establish a Drafting Team<https://community.icann.org/x/CYAmCQ> to develop both a draft charter and an Initiation Request for an EPDP on IDNs. The GNSO Council agreed with the Scoping Team’s suggestion that an Issue Report is likely not needed in order to initiate the Policy Track work, and an EPDP is the desired approach. The Drafting Team met between 8 December 2020 and 4 May 2021. 6. On 10 May 2021, the Drafting Team submitted the draft EPDP charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/idns-epdp…> and the Initiation Request<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-init…> for the GNSO Council’s consideration. 7. On 20 May 2021, the Drafting Team Chair provided a briefing to the GNSO Council on the content of the draft charter prior to the Council vote to initiate the EPDP and adopt the charter. RESOLVED, 1. The GNSO Council hereby approves the Initiation Request<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-init…> for the EPDP on IDNs and as such initiates the EPDP. 2. The GNSO Council approves the Charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/idns-epdp…> of the EPDP on IDNs. 3. The GNSO Council directs staff to: (a) communicate the results of this motion to the GNSO SG/Cs as well as ICANN SO/ACs and invite them to identify Members for the working group following the working group composition described in the Charter; (b) communicate the results of this motion to the ICANN Org GDS Team and invite them to identify at least one (1) staff liaison for the working group; (c) launch a call for expressions of interest seeking interested candidates to Chair the EPDP on IDNs; and (d) solicit candidates for the GNSO Council liaison to the EPDP on IDNs. Vote results<https://gnso.icann.org/sites/default/files/policy/2021/presentation/gnso-co…> Thank you, Kind regards, Nathalie

1 0

Recordings, attendance & Zoom chat | GNSO Council meeting | Thursday, 20 May 2021 at 19:00 UTC
by Terri Agnew May 20, 2021

May 20, 2021

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and chat of the GNSO Council meeting held on Thursday, 20 May 2021 at 19:00 UTC. Audio only: https://icann.zoom.us/rec/play/KTFuNl0FC6hjtSQDruozbX8ziSwtp2hwM9zQHWu8DZDo… Zoom Recording (includes visual and rough transcript. To access the rough transcript, select the Audio Transcript tab): https://icann.zoom.us/rec/share/_n8LY9LCwbng3hVQ8yhHdKwZUFkTiYnHkJ9SVs5a1gL… Zoom chat: https://icann.zoom.us/rec/sdownload/984YOMvJ8q1OYlzktHrs7gJ-JVijx27og-EzyW9… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. With kind regards, Terri

1 0

Accuracy scoping team volunteer
by Owen Smigelski May 20, 2021

May 20, 2021

Hi all, I would like to volunteer for the small team re: accuracy scoping until my temporary appointment expires. It is my understanding that Greg participated prior to his absence, and like Greg, I have a lot of experience dealing with whois accuracy issues and initiatives at ICANN. Thanks, Owen

2 1

FW: [Ext] Thursday, 20 May 2021
by Andrea Glandon May 20, 2021

May 20, 2021

[https://r20.rs6.net/on.jsp?ca=74f8a90c-fea9-4152-9a0f-232c0e2e9bc3&a=112202…] Thursday, 20 May 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing · NEW: ICANN71 Prep Week Schedule Now Available · TRANSLATION DEADLINE TOMORROW: ICANN71 Publication Support · DEADLINE TOMORROW: Participate in "ICANN Community Groups: An Introduction for Newcomers" · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Public Comment · CLOSES TOMORROW: GNSO Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Phase 1 Final Recommendations for ICANN Board Consideration · GNSO New gTLD Subsequent Procedures Final Outputs for ICANN Board Consideration · Maximal Starting Repertoire Version 5 (MSR-5) · NEW: Draft North America Engagement Plan FY21-25 Information Sharing NEW: ICANN71 Prep Week Schedule Now Available ICANN announced the ICANN71 Prep Week schedule of ten sessions to prepare the ICANN community for the ICANN71 Virtual Policy Forum taking place 14-17 June. ICANN71 Prep Week will be 1-3 June. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> TRANSLATION DEADLINE TOMORROW: ICANN71 Publication Support Translation-only Deadline For translation of a publication for ICANN71, please provide the final material(s) by Friday, 21 May 2021. This ensures that there is enough time to translate the publication. If the publication requires design assistance, 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 team to submit these requests to evin.erdogdu(a)icann.org and liana.teo(a)icann.org. DEADLINE ON MONDAY: Participate in "ICANN Community Groups: An Introduction for Newcomers" The Public Responsibility Support team seeks speakers from ICANN communities to participate in an introductory session for newcomers. Each speaker will have five minutes to provide an overview of their ICANN community group. The session will take place Wednesday, 2 June 2021, 13:00-14:30 UTC. Sign up [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> by Monday, 24 May 2021. Please contact deborah.escalera(a)icann.org with any questions. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> in advance of ICANN71, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 28 May 2021 at 23:59 UTC. The goal of this program is to facilitate participation in ICANN Public Meetings during this pandemic. It offers ICANN community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Public Comment CLOSES TOMORROW: GNSO Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Phase 1 Final Recommendations for ICANN Board Consideration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> Close Date: Friday, 21 May 2021 GNSO New gTLD Subsequent Procedures Final Outputs for ICANN Board Consideration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> Close Date: Tuesday, 1 June 2021 Maximal Starting Repertoire Version 5 (MSR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> Close Date: Tuesday, 8 June 2021 NEW: Draft North America Engagement Plan FY21-25 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> Close Date: Friday, 2 July 2021 Volume 3, Issue 38 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001_ERi90merKhFrzME…> | Next Issue: Monday, 24 May 2021

1 0

IDNs EPDP Initiation Request & Charter
by Ariel Liang May 19, 2021

May 19, 2021

GNSO Councilors, Following the motion submitted by Maxim Alzoba and in accordance with item 5 on the 20 May Council meeting agenda, please find attached the Expedited Policy Development Process (EPDP) on Internationalized Domain Names Initiation Request and the proposed Charter for your review. Staff would like to highlight the following elements in the Charter. More details will be provided during the presentation on the topic by Dennis Tan Tanaka, the Chair of the IDNs EPDP Drafting Team, prior to the Council vote. * Scope – This EPDP is expected to provide the GNSO Council with policy recommendations on: * The definition of all TLDs and the management of variant labels to facilitate the delegation of variant gTLDs in the root zone; and * How the IDN Implementation Guidelines, which Contracted Parties are required to comply with, should be updated in the future. * The scope of this EPDP may be expanded specifically as a result of the Operational Track. This EPDP is expected to provide the GNSO Council with recommendations to resolve issues for policy considerations in the IDN Implementation Guideline 4.0, IF and WHEN such issues are identified by the Operational Track Team and agreed to by the IDN Guidelines Working Group. * Principle – The charter questions were developed based on the following framework: * This WG should not revisit New gTLD Subsequent Procedures PDP (SubPro) recommendations in the context of future new gTLDs, but will consider questions asking whether such recommendations should be extended to existing gTLDs; * Where SubPro does not have a recommendation that corresponds to the Board approved recommendation related to IDNs, the charter will include questions about the impact of such recommendations on both future and existing gTLDs; * The SubPro’s Implementation Review Team (IRT) and this WG (including its future IRT) should coordinate on addressing implementation issues to achieve, to the extent possible, consistent solutions for new and existing gTLDs. * Charter question topics – At a minimum, the WG is expected to consider the following elements: * Consistent definition and technical utilization of RZ-LGR * “Same entity” at the top-level * “Same entity” at the second-level * Adjustments in registry agreement, registry service, registry transition process, and other processes/procedures related to the domain name lifecycle * Adjustments to objection process, string similarity review, string contention resolution, reserved strings, and other policies and procedures * Adjustments in registration dispute resolution procedures and trademark protection mechanisms * Process to update the IDN Implementation Guidelines * Expected completion timeframe – The WG’s last Final Report is expected to be delivered to the GNSO Council no later than 12 months after the WG convenes for its first meeting. * Working Group model – Representative + Open Model (Members + Participants + Observers) * Each of the following groups will be invited to appoint up to three (3) members to the WG: RySG, RrSG, IPC, BC, ISPCP, NCSG, ccNSO, ALAC, GAC, SSAC, RSSAC. No “Alternate” is envisioned in the WG composition. * In the event a group is unable to nominate a Member, at least one Participant should be responsible for keeping their respective group informed. * Participants will be able to actively participate in and attend all WG meetings, with the exception of the consensus designation process. * ccNSO is expected to appoint one (1) liaison to the WG, who may also serve as one of its Member(s). * ICANN Org GDS department is expected to appoint at least (1) staff liaison to the WG. * Each Member and Participant of the WG must acknowledge and accept the Statement of Participation. * For the purpose of assessing consensus, groups that do not fulfill their maximum membership allowance should not be disadvantaged. * Leadership structure – One (1) Chair + One (1) Vice Chair * The GNSO Council will appoint one (1) qualified, independent Chair (neutral, not counted as from the WG membership/participants) for the WG. * Staff is expected to publish a request for Expressions of Interest for the role of Chair. The GNSO Council leadership and Standing Selection Committee leadership will jointly review the responses and will propose a Chair to the GNSO Council. * The WG, once formed, may select one (1) Vice Chair to assist the Chair. The Vice Chair can be selected among the WG’s Members and Participants. If a Member is selected as the Vice Chair, this person shall change his/her Member status to Participant. Best Regards, Ariel Ariel Xinyue Liang Policy Sr. Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

2 1

Re: [council] Proposed framework for identifying the GNSO Council liaison to the SSAD ODP
by philippe.fouquart＠orange.com May 19, 2021

May 19, 2021

Dear Councillors, As a follow-up to this and as you would have noticed under our Consent agenda, I am glad to confirm that the leadership offers the appointment of Janis Karklins as the Council liaison to the SSAD ODP. We reached out to Janis according to the framework outlined below, Janis kindly accepted, and would be serving in his personal capacity. Moving forward, bearing in mind this is the first role of this kind, I would also like to draw your attention on future ODPs and whether we want to approach this role the same way, or further discuss the framework. Regards, Philippe From: FOUQUART Philippe TGI/OLN Sent: Friday, April 23, 2021 8:07 PM To: 'GNSO Council List' <council(a)gnso.icann.org> Cc: 'gnso-secs(a)icann.org' <gnso-secs(a)icann.org> Subject: RE: Proposed framework for identifying the GNSO Council liaison to the SSAD ODP Hi again, Since my initial email may be a bit dry to digest, let me just add or restate a couple of elements that were influential in our thinking: * The liaison should have previous involvement with the relevant PDP. * The liaison will serve as the primary contact between ICANN org's ODP team and the GNSO Council, which we interpret to mean that the role of liaison will be limited in scope, primarily serving as a messenger and escalation point between the GNSO Council and the ODP. Given the rather limited remit of the liaison, and as the ODP concept and scope will be reviewed after two ODPs have been completed, we believe it may be preferable to adopt the relatively straightforward and simple approach to this appointment described in the paper. In particular please note our suggestion that the former Chair or GNSO Council liaison to the PDP/EPDP may be an ideal GNSO Council liaison to the ODP. If they are unavailable, a former or sitting Councilor that took part in the PDP/EPDP may also make sense, given familiarity with both the substance and the operations of the GNSO Council. With this I wish you all a pleasant weekend, Regards, Philippe From: FOUQUART Philippe TGI/OLN Sent: Friday, April 23, 2021 7:56 PM To: 'GNSO Council List' <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Proposed framework for identifying the GNSO Council liaison to the SSAD ODP Dear Councillors, As briefly discussed during the AOB yesterday and given that this is the first of the kind, leadership and staff put together a proposed framework for identifying the GNSO Council liaison to the SSAD ODP (which I wrongly described as an EoI, my apologies :s). You will find here<https://docs.google.com/document/d/1cbIQBk8InVe65nBtwrl0Ub5pKSdr1BXePRZB1KD…> for your review. Regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

FW: [Ext] Monday, 17 May 2021
by Andrea Glandon May 17, 2021

May 17, 2021

[https://r20.rs6.net/on.jsp?ca=12677838-5f48-49d3-a8ee-a6de09759c3d&a=112202…] Monday, 17 May 2021 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing · NEW: Approved Resolutions from the 12 May 2021 Special Meeting of the ICANN Board · NEW: Chair's Blog: Recap of the April to May ICANN Board Workshop · TRANSLATION DEADLINE THIS WEEK: ICANN71 Publication Support · REMINDER: Participate in "ICANN Community Groups: An Introduction for Newcomers" · REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Public Comment · DEADLINE THIS WEEK: GNSO Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Phase 1 Final Recommendations for ICANN Board Consideration · GNSO New gTLD Subsequent Procedures Final Outputs for ICANN Board Consideration · Maximal Starting Repertoire Version 5 (MSR-5) Information Sharing NEW: Approved Resolutions from the 12 May 2021 Special Meeting of the ICANN Board Read the approved resolutions [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> of the special meeting of the ICANN Board held on 12 May 2021, including the adoption [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> of the FY22-26 Operating and Financial Plan and the FY22 Operating Plan and Budget. NEW: Chair's Blog: Recap of the April to May ICANN Board Workshop Read ICANN Board Chair Maarten Botterman's latest blog post [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> about the April to May ICANN Board Workshop. TRANSLATION DEADLINE THIS WEEK: ICANN71 Publication Support Translation-only Deadline For translation of a publication for ICANN71, please provide the final material(s) by Friday, 21 May 2021. This ensures that there is enough time to translate the publication. If the publication requires design assistance, 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 team to submit these requests to evin.erdogdu(a)icann.org and liana.teo(a)icann.org. REMINDER: Participate in "ICANN Community Groups: An Introduction for Newcomers" The Public Responsibility Support team seeks speakers from ICANN communities to participate in an introductory session for newcomers. Each speaker will have five minutes to provide an overview of their ICANN community group. The session will take place Wednesday, 2 June 2021, 13:00-14:30 UTC. Sign up [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> by Monday, 24 May 2021. Please contact deborah.escalera(a)icann.org with any questions. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> in advance of ICANN71, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 28 May 2021 at 23:59 UTC. The goal of this program is to facilitate participation in ICANN Public Meetings during this pandemic. It offers ICANN community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Public Comment DEADLINE THIS WEEK: GNSO Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Phase 1 Final Recommendations for ICANN Board Consideration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> Close Date: Friday, 21 May 2021 GNSO New gTLD Subsequent Procedures Final Outputs for ICANN Board Consideration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> Close Date: Tuesday, 1 June 2021 Maximal Starting Repertoire Version 5 (MSR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> Close Date: Tuesday, 8 June 2021 Volume 3, Issue 37 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001mnCEvBRY8d4vzdEZ…> | Next Issue: Thursday, 20 May 2021

1 0

FW: Approved Board Resolutions | Special Meeting of the ICANN Board 12 May 2021
by philippe.fouquart＠orange.com May 17, 2021

May 17, 2021

Hi again everyone, Please note also the full list of the board’s resolution, including a number of SSAC reports, the approval of both the FY22-26 Operating and Financial Plan<https://www.icann.org/en/system/files/files/op-financial-plan-fy22-26-oppla…> and the FY22 Operating and Budget<https://www.icann.org/en/system/files/files/budget-fy22-2021-en.pdf>. Regards, Philippe From: soac-chairs [mailto:soac-chairs-bounces@icann.org] On Behalf Of David Olive via soac-chairs Sent: Saturday, May 15, 2021 6:14 PM To: soac-chairs(a)icann.org Cc: Team-leaders(a)icann.org Subject: [soac-chairs] Approved Board Resolutions | Special Meeting of the ICANN Board 12 May 2021 Approved Board Resolutions | Special Meeting of the ICANN Board 12 May 2021 1. Consent Agenda:<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1> a. Singapore Office Lease Renewal<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.a> § Rationale for Resolutions 2021.05.12.01 – 2021.05.12.02<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.…> b. Payment of Legal Invoices<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.b> § Rationale for Resolutions 2021.05.12.03 – 2021.05.12.04<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.…> c. IANA Naming Function Review (IFR) Final Report<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.c> § Rationale for Resolutions 2021.05.12.05 – 2021.05.12.06<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.…> d. SAC045: SSAC Advisory on Invalid Top Level Domain Queries at the Root Level of the Domain Name System (DNS)<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.d> § Rationale for Resolutions 2021.05.12.07<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.…> e. SAC062: Advisory Concerning the Mitigation of Name Collision<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.e> § Rationale for Resolutions 2021.05.12.08<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.…> f. SAC065: SSAC Advisory on DDoS Attacks Leveraging DNSInfrastructure<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.f> § Rationale for Resolution 2021.05.12.09<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.…> g. SAC070: Security and StabilityAdvisory Committee (SSAC) Advisory on the Use of Static TLD / Suffix Lists<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.g> § Rationale for Resolution 2021.05.12.10<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#1.…> 2. Main Agenda:<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2> a. FY22-26 Operating and Financial Plan and FY22 Operating Plan and Budget Approval<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.a> § Rationale for Resolutions 2021.05.12.11 – 2021.05.12.12<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.…> b. Transfer to Reserve Fund and Creation of Supplemental Fund for Implementation of Community Recommendations (SFICR)<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.b> § Rationale for Resolutions 2021.05.12.13 – 2021.05.12.15<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.…> c. SAC063, SAC073 and SAC102 regarding the DNSSEC Key Rollover in the Root Zone<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.c> § Rationale for Resolutions 2021.05.12.16<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.…> d. GAC Advice: ICANN70 Communiqué (25 March 2021)<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.d> § Rationale for Resolutions 2021.05.12.17<https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.…> Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0