February 2020 - council - lists.icann.org

FW: [ICANN Community Leaders] 24 February 2020
by Terri Agnew 24 Feb '20

24 Feb '20

FYI. From: SO-AC-SG-CLeaders <so-ac-sg-cleaders-bounces(a)icann.org> on behalf of ICANN Community Leadership Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, February 24, 2020 at 9:00 AM To: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> Subject: [ICANN Community Leaders] 24 February 2020 [http://r20.rs6.net/on.jsp?ca=15294eee-aca2-4f8f-bf61-84378d085abb&a=1122025…] Monday, 24 February 2020 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. This week marks the one-year anniversary of the ICANN Community Leadership Digest! After ICANN67, there will be a short survey to gather feedback and recommendations for continuous improvement. Thank you for reading. Table of Contents ICANN67 Planning · NEW: ICANN67 Planning Call · DUE TODAY: Areas of Interest from the ICANN Board for ICANN67 Constituency Day Information Sharing · NEW: EPDP Recommendation 17.2 Questionnaire · REMINDER: Nomination Period for ICANN Community Excellence Award 2020 Now Open Public Comment · CLOSES TOMORROW: Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget · Second Security, Stability, and Resiliency (SSR2) Review Team Draft Report · Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 · Draft Proposal for NextGen@ICANN Program Improvements · Name Collision Analysis Project (NCAP) Study 1 · Middle East and Adjoining Countries (MEAC) Strategy 2021-2025 · Revised Community Travel Support Guidelines ICANN67 Planning NEW: ICANN67 Planning Call From: David Olive, Senior Vice President, Policy Development Support An ICANN67 Planning call will be held on Tuesday, 25 February 2020 at 16:00 UTC for all Supporting Organization, Advisory Committee, Stakeholder Group, and Constituency leaders. ICANN org will continue to make further announcements as circumstances warrant. DUE TODAY: Areas of Interest from the ICANN Board for ICANN67 Constituency Day From: Maarten Botterman, ICANN Board Chair ACTION ITEM Our first meeting of the year is approaching fast! The Board and I very much look forward to engaging with you. As we continue working with you on the format of our engagement with your groups, we would like to experiment a new way of interacting by offering you to choose one or two area(s) of interest and having an open discussion with the Board on those, instead of asking you to come up with specific questions. We are also suggesting that the list of areas of interest be shared with the entire Community using this digest, in order to increase transparency and allow the groups to improve their own understanding of their peers’ point of views on different issues. As for time allocation, we propose to allocate the first part of our time together to be spent on your specific areas of interest, and to allow sufficient time to address the areas of interest indicated by the Board, if they have not been covered by that time. So you are aware, we are not changing the current total time allotted per group. In preparation for our meetings, the Board proposes the following areas of interest to have an open discussion with you: 1. Key priorities for action of ICANN constituencies in 2020 (e.g. prioritization of recommendations, streamlining of reviews, improve effectiveness of ICANN’s multistakeholder model, ...) 2. Specific developments coming up that ICANN constituencies feel need to be addressed when updating the ICANN Strategic Plan. We would be very grateful if you could send Board Operations, board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>, your area(s) of interest, in order of priority, no later than Monday, 24 February 2020. We look forward to hearing your thoughts on our suggestions and on how to further improve our interaction. We thank you in advance for your time on this matter. Information Sharing NEW: EPDP Recommendation 17.2 Questionnaire From: Cyrus Namazi, Senior Vice President, Global Domains Division INFORMATION SHARING As part of ICANN org’s research for Recommendation 17.2 of the EPDP Team’s Phase 1 Final Report, the Global Domains Division (GDD) has prepared a short questionnaire to collect input on the risks, feasibility, and costs of differentiating between legal and natural persons in registration data directory services (RDDS). Members of ICANN community groups with a view on the subject are invited to fill out and share the questionnaire at https://icannprds.typeform.com/to/ehG295 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> before Friday, 20 March 2020. Results will be integrated into the report on Recommendation 17.2 for the EPDP Team. REMINDER: Nomination Period for ICANN Community Excellence Award 2020 Now Open From: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING The nomination period for the ICANN Community Excellence Award 2020 is now open. Formerly known as the Multistakeholder Ethos Award, the ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within ICANN’s multistakeholder model. Learn more about the nomination process [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> and submit your nominations here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Public Comment CLOSES TOMORROW: Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 25 February 2020 Second Security, Stability, and Resiliency (SSR2) Review Team Draft Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Wednesday, 4 March 2020 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 23 March 2020 Draft Proposal for NextGen@ICANN Program Improvements [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 31 March 2020 Name Collision Analysis Project (NCAP) Study 1 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 31 March 2020 Middle East and Adjoining Countries (MEAC) Strategy 2021-2025 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 3 April 2020 Revised Community Travel Support Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 13 April 2020 Volume 2, Issue 16 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Thursday, 27 February 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

Fwd: [ICANN Community Leaders] Notes and Additional Materials from the 21 February ICANN67 Program Planning Call
by Drazek, Keith 22 Feb '20

22 Feb '20

FYI Begin forwarded message: From: David Olive <david.olive(a)icann.org> Date: February 22, 2020 at 1:27:24 PM EST To: SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning(a)icann.org> Cc: "so-ac-sg-cleaders(a)icann.org" <so-ac-sg-cleaders(a)icann.org> Subject: [EXTERNAL] [ICANN Community Leaders] Notes and Additional Materials from the 21 February ICANN67 Program Planning Call Dear Community Leaders: Please find the following information, as agreed: 1. Summary Notes (attached) 2. Action Items (copied below from summary notes) * Tanzanica King’s document on each group their meeting schedule for review, with a view towards deciding which of the scheduled sessions you wish to retain as part of the formal ICANN67 meeting schedule, which to reschedule (e.g. to become an online meeting subsequent to ICANN67 or to be held at ICANN68), and which to cancel. (Attached) * ICANN org staff to work on a skeletal plenary schedule, based on the feedback from this call, to enable community groups to plan their individual and bilateral sessions around the “must have” sessions (e.g. Public Forum, sessions with the Board). (in progress) * Schedule the next call for Tuesday 25 February, where all community groups will share their groups’ views on a revised, trimmer ICANN67 schedule. (done, calendar invited shared) * If need be, organize a quick vote to finalize topics/sessions for the revised schedule on the Tuesday Call. 1. Meeting Chat Record (attached) 2. Recording: https://icann.zoom.us/rec/play/6ZQuc7uurzw3ToCTuQSDA6B5W9S6Lf2shHMb_PBYn0bm… [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_rec_play…> Please let us know if you have any questions. Talk to all of you on Tuesday. Best regards. David David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) Washington, D.C.

1 0

FW: Notice of Expiration of Rejection Action Petition Period for Board Approval of FY21 IANA Budget
by Drazek, Keith 21 Feb '20

21 Feb '20

FYI, the formal notice of expiration of the RAP period for the FY21 IANA budget. Keith From: ECAdmin <ecadmin-bounces(a)icann.org> On Behalf Of Ozan Sahin Sent: Friday, February 21, 2020 3:15 AM To: ecadmin(a)icann.org Subject: [EXTERNAL] [ECAdmin] Notice of Expiration of Rejection Action Petition Period for Board Approval of FY21 IANA Budget Dear Empowered Community Administration representatives, I am writing to confirm that, in accordance with the timelines and procedures set out in Annex D of the ICANN Bylaws, the 21-day Rejection Action Petition Period pertaining to the FY21 IANA Budget that was approved by the ICANN Board has expired. No Rejection Action Petition Notices (as defined in Annex D, Section 2.2(c)(i)) were received by the Empowered Community Administration within the prescribed timeframe. As such, under Annex D, Section 2.2(c)(ii), the Rejection Process for FY21 IANA Budget is thus automatically terminated. The next step is for the Empowered Community Administration to deliver to the ICANN Secretary a notice certifying that the Rejection Process has been terminated with respect to this particular Rejection Action. ICANN will then post the Rejection Process Termination Notice on the ICANN website. Please let staff know if the Empowered Community Administration wishes for staff to assist you with the requisite Rejection Process Termination Notice. Best regards, Ozan Sahin (on behalf of the staff supporting Empowered Community Administration)

1 0

Recordings, attendance & Zoom chat/ GNSO Council meeting on Thursday, 20 February 2020 at 21:00 UTC.
by Terri Agnew 21 Feb '20

21 Feb '20

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 February 2020 at 21:00 UTC. Audio only: https://icann.zoom.us/rec/play/78Yvc72g_D03E9fEsASDAvEqW47pLvis1yQc_KcImU3n… Zoom Recording (includes visual and rough transcript. To access the rough transcript, select the Audio Transcript tab): https://icann.zoom.us/rec/share/45FNcr77-01ObJXp5U7hR-0vP7bXT6a8gSNI-PIJxUw… Zoom chat: https://icann.zoom.us/rec/download/v8IqdO2h-Gk3T9CW5ASDVqJxW9XpL6ysgXAf-aUF… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> With kind regards, Terri

1 0

GNSO Council resolution 20 February 2020
by Nathalie Peregrine 20 Feb '20

20 Feb '20

Dear all, Please find below the resolution from the GNSO Council at its meeting on Thursday 20 February 2020 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page. Adoption of the PDP 3.0 Implementation Final Report Whereas, 1. GNSO Policy Development Process (PDP) 3.0 is a GNSO Council initiative aimed at introducing incremental improvements to enhance the efficiency and effectiveness of GNSO PDPs. 2. On 24 October 2018, the GNSO Council resolved<https://gnso.icann.org/en/council/resolutions#201810> to adopt the GNSO PDP 3.0 Proposed Improvements Paper<https://gnso.icann.org/en/drafts/pdp-increase-effectiveness-efficiency-23oc…> and provided full support for fourteen (14) improvements. 3. In January 2019 during the GNSO Council’s Strategic Planning Session (SPS), the GNSO Council decided that a Small Team<https://community.icann.org/display/GCP> of Councilors should be convened to support the implementation efforts in collaboration with the GNSO support staff. Led by Rafik Dammak, a GNSO Council Vice Chair, the Small Team met regularly between April 2019 and February 2020, with designated leads working with staff to advance the implementation of each improvement. 4. To facilitate the GNSO Council’s review, the Small Team delivered four packages to the GNSO Council in an incremental manner: Package one<https://mm.icann.org/pipermail/council/2019-August/022965.html>, on improvements 1, 2, 3, and 6 was delivered on 13 August 2019; Package two<https://mm.icann.org/pipermail/council/2019-September/023075.html>, on improvements 11, 12, 14, and 16 was delivered on 25 September 2019; Package three<https://mm.icann.org/pipermail/council/2019-October/023185.html>, on improvements 5 and 13 was delivered on 22 October 2019; and Package four<https://mm.icann.org/pipermail/council/2019-November/023292.html>, on improvements 9 and 15 was delivered on 21 November 2019. 5. During the process of developing and finalizing the proposed implementation, the ICANN community and the ICANN org were consulted for input and suggestions via various mechanisms, including but not limited to: interviews and small group discussions, GNSO Council mailing lists and meetings, invitation to provide written input, and a public webinar on 9 December 2019. 6. While the PDP 3.0 precedes ICANN’s Evolution of the Multistakeholder Model (MSM) project, the implementation is nevertheless connected. The GNSO Council commented<https://mm.icann.org/pipermail/comments-multistakeholder-model-next-steps-2…> on the Evolution of the MSM’s initial report and engaged with Brian Cute, the project’s facilitator, before and during the ICANN66 meeting in Montréal. In Appendix C of ICANN’s Draft FY21-25 Operating & Financial Plans and Draft FY21 Operating Plan & Budget<https://www.icann.org/en/system/files/files/draft-op-financial-plan-fy21-25…>, which documents the outcome of Phase 1 and Phase 2 of the project, three (3) out of the six (6) workstreams align with the PDP 3.0 implementation; the GNSO is being proposed to lead the “Issue A: Consensus + representation and Inclusivity” workstream. 7. In January-February 2020, the Small Team conducted additional activities, including: 1) revising the GNSO PDP working group charter template; 2) identifying sections in the current GNSO Operating Procedures that could be revised after the GNSO Council reviews the effectiveness of PDP 3.0 implementation; and 3) discussing “Parking Lot” items that might benefit from future work. 8. In January 2020 during GNSO Council’s SPS, the GNSO Council dedicated several sessions to the discussion of PDP 3.0 and agreed on several action items<https://community.icann.org/x/RgZlAg> as the next steps for the implementation efforts. 9. On 10 February 2020, the Small Team completed thirteen (13) out of fourteen (14) PDP 3.0 improvements and delivered its Final Report to the GNSO Council for its consideration. The Final Report <https://community.icann.org/download/attachments/126422990/%5BFinal%5D%20GN…> provides an overview of the PDP 3.0 implementation process and outcomes, a consolidation of all of the work products incorporating community feedback as appropriate, and suggested effective time frame for deployment of the improvements. 10. The last remaining work product related, the Consensus Playbook, is originated from PDP 3.0 Improvement #4 and not complete. While, the Consensus Playbook is not strictly a PDP 3.0 product, it is intended to be utilized by the broader ICANN community beyond the GNSO. Its pending status should not prevent the GNSO Council adoption of the Implementation Final Report from the PDP 3.0 Small Team. Adoption of the Consensus Playbook will be voted upon by the GNSO Council at a later date. Resolved, 1. The GNSO Council hereby adopts the GNSO PDP 3.0 Implementation Final Report and instructs GNSO Support Staff to work with the GNSO Council leadership on the deployment of improvements based on the effective time frame proposed by the PDP 3.0 Small Team. 2. The GNSO Council requests future charter drafting teams of the GNSO Council to commence chartering for upcoming PDP efforts by utilizing the revised GNSO working group charter template and other related PDP 3.0 work products, and report to the GNSO Council on whether they help achieve the intended outcomes. 3. The GNSO Council requests that after all PDP 3.0 improvements are in effect, the GNSO Council conducts a review of the implementation effectiveness in a timely manner. 4. The GNSO Council requests that following the GNSO Council review of the PDP 3.0 implementation effectiveness, the GNSO Council considers any necessary updates to the GNSO Operating Procedures and uses the relevant work product in the PDP 3.0 Implementation Final Report as a starting point. 5. The GNSO Council confirms that none but one (1) “Parking Lot” item (Statement of Interest Review) identified by the PDP 3.0 Small Team should be moved forward until the GNSO Council has the opportunity to evaluate the PDP 3.0 implementation effectiveness. 6. The GNSO Council thanks to the PDP 3.0 Small Team, GNSO support staff, and others who have contributed to the implementation of GNSO PDP 3.0 improvements as well as the proposed implementation work products to enhance the efficiency and effectiveness of GNSO PDPs. Vote results<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-coun…>

1 0

Reminder: SCBO 1st Draft of 5YS&OP + FY21 Draft Budget
by Nathalie Peregrine 20 Feb '20

20 Feb '20

Dear Council, On behalf of the SCBO Chair, the following is submitted. Please find attached a GNSO Council’s working draft from the SCBO on ICANN’s draft Five Year Strategic and Operating Plan, including comments on the draft FY21 budget. The public proceeding will close 25 Feb. 2020. The SCBO welcomes suggested edits or ideas to consider either through red-lines of the attached draft or you they can be sent over the mailing list. Below is the proposed schedule of the SCBO: SCBO Schedule: * 10 Feb – GNSO Council documents & motion deadline * 12 Feb – 4th SCBO meeting * 18 Feb – Meet with the CCNSO’s SOPC to share draft positions at 16:00UTC * 20 Feb – GNSO Council meeting (SCBO on AoB) * 25 Feb – Deadline to submit comments * 08 Mar – Joint session at ICANN67 w/ SOPC; (8 March at 15:00 local time) Please advise if you have any questions. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant

1 0

FW: [SOAC-Leaders-ICANNMeeting-Planning] FW: ICANN67 Update Call Materials | 20 February 2020 at 18:00 UTC
by Drazek, Keith 20 Feb '20

20 Feb '20

FYI From: SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning-bounces(a)icann.org> On Behalf Of David Olive Sent: Thursday, February 20, 2020 4:46 PM To: so-ac-sg-cleaders(a)icann.org; SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning(a)icann.org> Subject: [EXTERNAL] [SOAC-Leaders-ICANNMeeting-Planning] FW: ICANN67 Update Call Materials | 20 February 2020 at 18:00 UTC Dear Community Leaders and Representatives: Enclosed are the call materials from the ICANN67 Update call held on Thursday, 20 February 2020. Chat transcript attached. Zoom Recording: https://icann.zoom.us/rec/play/vZUpJuz6pzg3T4CTsgSDBfBwW9Xof6ishCdMr6EIn0vh… Best regards. David David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) Washington, D.C.

1 0

FW: [CORRESPONDENCE] Maarten Botterman to Keith Drazek - ICANN Policy on Transfer of Registrations between Registrars - Gaining FOA
by Drazek, Keith 20 Feb '20

20 Feb '20

FYI, a letter confirming the ICANN Board’s 26 January resolution concerning deferral of compliance enforcement of the Gaining Registrars Form of Authorization (FOA) requirement. Regards, Keith From: Wendy Profit <wendy.profit(a)icann.org> Sent: Thursday, February 20, 2020 2:53 PM To: Drazek, Keith <kdrazek(a)verisign.com>; gnso-chairs(a)icann.org; gnso-secs(a)icann.org Cc: Maarten Botterman <maarten.botterman(a)board.icann.org>; Correspondence <Correspondence(a)icann.org>; Secretary <secretary(a)icann.org>; Board Ops Team <board-ops-team(a)icann.org> Subject: [EXTERNAL] [CORRESPONDENCE] Maarten Botterman to Keith Drazek - ICANN Policy on Transfer of Registrations between Registrars - Gaining FOA Dear Keith, Please find the attached letter from Maarten Botterman in response to the GNSO Council’s letter of 31 October 2019 related to ICANN’s Policy on Transfer of Registrations between Registrars. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094

1 0

FYI: FW: [ICANN Community Leaders] 20 February 2020
by Michelle DeSmyter 20 Feb '20

20 Feb '20

FYI: [http://r20.rs6.net/on.jsp?ca=60d6fd3f-8d56-49ca-9f1c-cf5150bf34bf&a=1122025…] Thursday, 20 February 2020 ICANN Community Leadership Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support team publishes this twice-weekly digest to help ICANN community leaders track requests and updates. Table of Contents ICANN67 Planning · TODAY: ICANN67 Update Information Sharing · TOMORROW: ICANN68 Travel Support Deadline · REMINDER: Nomination Period for ICANN Community Excellence Award 2020 Now Open Public Comment · Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget · Second Security, Stability, and Resiliency (SSR2) Review Team Draft Report · Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 · Draft Proposal for NextGen@ICANN Program Improvements · Name Collision Analysis Project (NCAP) Study 1 · Revised Community Travel Support Guidelines · NEW: Middle East and Adjoining Countries (MEAC) Strategy 2021-2025 ICANN67 Planning TODAY: ICANN67 Update ICANN org will provide a short update and answer questions about ICANN67 today at 18:00 UTC. Please join: https://icann.zoom.us/my/icann67prepweek [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> ICANN org will continue to make further announcements as circumstances warrant. Information Sharing TOMORROW: ICANN68 Travel Support Deadline Executive: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING Community travel support requests for ICANN68 are due to the relevant community group support team by Friday, 21 February 2020. The deadline for submissions is critical to allow for Office of Foreign Assets Control review, travel arrangements, and confirmed reservations as required for visa applications. Benefits of having community travel support requests 120 days before the next ICANN Public Meeting include: · Allow ICANN org to gather the documentation required (hotel and flight confirmations) for supported travelers to apply for their visa. · Allow enough time for supported travelers to complete and submit their visa application, which often vary per ICANN Public Meeting location. · Allow enough time for supported travelers to apply for a transit visa (if required), which often vary per ICANN Public Meeting location. · Allow ICANN org to purchase less expensive airfares. · Allow supported travelers to plan their pre-and-post ICANN Public Meeting travel in advance. · Allow ICANN org to set-up supported travelers in advance as vendors with Finance allowing us to wire their per diem/stipend funds in a timelier manner. REMINDER: Nomination Period for ICANN Community Excellence Award 2020 Now Open From: David Olive, Senior Vice President, Policy Development Support INFORMATION SHARING The nomination period for the ICANN Community Excellence Award 2020 is now open. Formerly known as the Multistakeholder Ethos Award, the ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within ICANN’s multistakeholder model. Learn more about the nomination process [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> and submit your nominations here [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…>. Public Comment Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan & Budget [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 25 February 2020 Second Security, Stability, and Resiliency (SSR2) Review Team Draft Report [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Wednesday, 4 March 2020 Initial Report of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Team – Phase 2 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 23 March 2020 Draft Proposal for NextGen@ICANN Program Improvements [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 31 March 2020 Name Collision Analysis Project (NCAP) Study 1 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Tuesday, 31 March 2020 Revised Community Travel Support Guidelines [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Monday, 13 April 2020 NEW: Middle East and Adjoining Countries (MEAC) Strategy 2021-2025 [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> Close Date: Friday, 3 April 2020 Volume 2, Issue 15 | Archive [r20.rs6.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__r20.rs6.net_tn.jsp-3Ff-…> | Next Issue: Monday, 24 February 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe so-ac-sg-cleaders(a)icann.org [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> Update Profile [visitor.constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__visitor.constantcontac…> | About Constant Contact [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> in collaboration with [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…> Try email marketing for free today! [constantcontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.constantcontact.com…>

1 0

FW: Approved Board Resolutions | Special Meeting of the ICANN Board - ICANN
by Drazek, Keith 20 Feb '20

20 Feb '20

FYI From: SO-AC-SG-CLeaders <so-ac-sg-cleaders-bounces(a)icann.org> On Behalf Of David Olive Sent: Thursday, February 20, 2020 9:24 AM To: so-ac-sg-cleaders(a)icann.org Subject: [EXTERNAL] [ICANN Community Leaders] Approved Board Resolutions | Special Meeting of the ICANN Board - ICANN https://www.icann.org/resources/board-material/resolutions-2020-02-19-en Approved Board Resolutions | Special Meeting of the ICANN Board 19 Feb 2020 1. Main Agenda:<https://www.icann.org/resources/board-material/resolutions-2020-02-19-en#1> a. Impact of COVID-19 on ICANN67<https://www.icann.org/resources/board-material/resolutions-2020-02-19-en#1.a> •• Rationale for Resolutions 2020.02.19.01 – 2020.02.19.04<https://www.icann.org/resources/board-material/resolutions-2020-02-19-en#1.…> 1. Main Agenda: a. Impact of COVID-19 on ICANN67 Whereas, on 23 June 2018, the ICANN Board approved for ICANN organization to proceed to contracting in support of ICANN67 in Cancún, Mexico (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.d). Whereas, the ICANN Board is responsible for a decision to change an ICANN Public Meeting location once such a meeting location has been approved for contracting and announced. Whereas, in December 2019, a new strain of coronavirus, referred to as COVID-19, emerged and on 30 January 2020 was declared by the World Health Organization (WHO) as a public health emergency of international concern. As of 18 February 2020, there are over 73,000 confirmed cases globally, with over 1,800 reported deaths. While most of these cases are in China, there are confirmed cases in 25 other countries around the world. As we understand the situation, much remains unknown about the spread of COVID-19, though it is documented to be transmittable even through asymptomatic carriers. Whereas, as an organization with staff and stakeholders across the globe, in January 2020 ICANN org convened an adaptive crisis management team (A-CMT) in order to assist ICANN org in tracking and assessing the impact of COVID-19 on ICANN's work. Whereas, ICANN org, through the A-CMT, briefed the Board on the current status of COVID-19, including the potential impacts on ICANN67. The Board also received a briefing from a representative of International SOS regarding the status of the Mexican authorities' ability to respond to the global health emergency and its readiness to address a suspected or confirmed case if one were to emerge during ICANN67. ICANN org also provided a similar briefing to the SO/AC leadership on 18 February 2020. Whereas, there are currently 1,350 registrations for ICANN67, with participants from approximately 155 countries or territories flying in from around the world. While there are no confirmed COVID-19 cases to date either in Mexico or within the Latin American region at present, it is a fluid situation that can be impacted by unknowingly infected travelers. The Board is concerned about the potential of an ICANN67 participant inadvertently bringing COVID-19 into the region, or for the potential of other cases being identified in the area. Whereas, if there is a suspected or confirmed case of COVID-19 among the participants in ICANN67, be it from the community, ICANN org, or ICANN Board, neither the ICANN org or Board will be in a position to control the impact on other participants or the ability to continue with the meeting. The federal and state health authorities for the region will direct the response, including possible hospitalization and quarantine of the patient and those who have been in close proximity to the patient. Whereas, if significant numbers of ICANN community or org members are impacted by COVID-19 while in Cancún or after they return to their home countries, there is a high risk that the community's ability to do its work could be impacted. Whereas, the Board is aware of multiple events that have been cancelled or postponed in both the areas more directly impacted by COVID-19, as well as areas where there are few to no confirmed cases, due to the risks and concerns posed by hosting a large international gathering during the time when little is understood about the transmission or containment of COVID-19. Some of the more recent cancellations include the GSMA's Mobile World Congress in Barcelona, Spain; Facebook's Global Marketing Summit in San Francisco, California; and INTA's Annual Meeting in Singapore. Whereas, the Board understands the import of the face-to-face interactions as provided for at ICANN's public meetings. However, health and security are paramount, and the Board also recognizes the ICANN community's unique ability to conduct challenging work through remote participation avenues, and the ICANN org's ability to provide for broad remote participation facilities. Whereas, the Board heard the community inputs that were solicited and provided to ICANN org, and acknowledges that many in the community remained ready to attend an in-person meeting for ICANN67. The deliberations amongst the Board represented the full range of viewpoints on this sensitive and challenging issue. Resolved (2020.02.19.01), by virtue of the public health emergency of international concern posed by COVID-19, the daily evolving developments, and the high global risk still identified, the Board directs the ICANN President and CEO, or his designees, to take all necessary actions to not hold ICANN67 as an in-person meeting in Cancún, Mexico. Resolved (2020.02.19.02), as the Board has determined to not proceed to Cancun, Mexico for ICANN67, the Board directs the ICANN President and CEO to move ICANN67 to ICANN's first fully remote public meeting. Resolved (2020.02.19.03), the Board directs the ICANN President and CEO, or his designees, to immediately begin engagement with the ICANN community to achieve an appropriate schedule for the remote public meeting. This includes engagement with those Review Teams, Working Groups, or other committees that have meetings scheduled before or after ICANN67 to determine appropriate alternative arrangements for those meetings. Resolved (2020.02.19.04), the Board sends its deep gratitude to the host committees, hotels, and venues of ICANN67 in Cancún and our regrets for the impacts this global health emergency causes on our meeting plans. The Board is committed to joining you in 2021 as planned for ICANN70. Rationale for Resolutions 2020.02.19.01 – 2020.02.19.04 The Board takes this action today in as a result of the COVID-19 outbreak, considered a public health emergency of international concern by the World Health Organization. While the Board recognizes and upholds the value of face-to-face interactions at ICANN's Public Meetings, and the advancement of ICANN community work that happens at these meetings, we cannot move forward with an in-person meeting at the cost of the health of attendees, ICANN org staff members, and the host country. Just as the Board has previously considered in moving meetings due to the emerging Zika virus, health and safety must be the paramount concern. At the time of the Board decision, the December 2019 COVID-19 outbreak now stands at over 73,000 confirmed cases across 26 countries, with more than 1,800 deaths attributed to the virus. Each day, new information and questions emerge on the mode of transmission, the methodology for preventing the spread of the virus, the ability for carriers to transmit the virus without having any symptoms, and the potential for fatality once infected. While most of the confirmed cases are within China, the spread outside of China has included multiple people infected at or after contact with the 109 attendees of a conference in Singapore, including one attendee who has been identified as the source of at least 11 new cases in England, France, and Spain after he returned from the meeting. A single cruise ship has been the source of at least 500 confirmed cases. Over 1,000 passengers and crew from a different cruise ship disembarked and started flying around the world, only to learn that a fellow passenger tested positive for COVID-19 . While health officials have not declared a pandemic, the extent of new clusters or pockets of cases outside of China are being monitored, with health officials noting that the "next three weeks" will be crucial in such a determination. Those three weeks span the time when the ICANN community is expected to converge on Cancún for ICANN67. The ICANN Board has been watching how other large, international conferences are responding to COVID-19 in light of the emerging situation. The GSMA cancelled its Mobile World Congress event in Barcelona, Spain, saying, "With due regard to the safe and healthy environment in Barcelona and the host country today, the GSMA has cancelled MWC Barcelona 2020 because the global concern regarding the coronavirus outbreak, travel concern and other circumstances, make it impossible for the GSMA to hold the event." Facebook cancelled its Global Marketing Summit, scheduled for 9-12 March in San Francisco, California, noting "Out of an abundance of caution, we canceled our Global Marketing Summit due to evolving public health risks related to coronavirus." Approximately 5,000 people were expected to attend. IBM has withdrawn from the RSA Conference, scheduled for 24-28 February in San Francisco, California, stating, "The health of IBMers continues to be our primary concern as we monitor upcoming events and travel relative to Novel Coronavirus (COVID-19). As a result, we are cancelling our participation in this year's RSA conference." The International Trademark Association postponed and relocated its 2020 Annual Meeting, originally scheduled for 25-29 April in Singapore, just as more than two dozen other conferences have been cancelled in the Asian region due to the outbreak. It is within this framework that the Board considers the impact of COVID-19 on the plans for ICANN67 in Cancún. There are over 1,350 registered attendees, traveling from 155 countries or territories – including the 26 countries that have confirmed cases. While ICANN org can, and has, planned for detection of the virus during the meeting and can provide best practice guidelines for attendees to try to reduce the risk of transmission, if even a single attendee at the conference presents with COVID-19, ICANN would contribute to the global spread of COVID-19 and bring the virus into Mexico and the LAC region. Separately, the impact to the attendees and the ability to even proceed with the meeting cannot be known at this time. Taking all of this into account, the global health emergency presented by COVID-19 makes it inappropriate for ICANN to convene an in-person Public Meeting at this time. While we have every confidence in the ability of the Federal and State health authorities in Cancún, Mexico to respond to suspected or confirmed cases, it is still too early in the path of COVID-19 to raise the risk of spread in this way. The ICANN org has initiated planning for ICANN's first remote-only meeting, so that the important work of the ICANN community can continue even without the face-to-face interaction. With this resolution, the Board is directing the ICANN org to coordinate with the ICANN community to achieve an appropriate schedule for the sessions planned for ICANN67. The Board also recognizes that there are other face-to-face meetings attendant to ICANN67, such as Review Team meetings or Nominating Committee meetings, that must also be reconfigured as a result of this decision, and the Board directs ICANN org to identify appropriate alternative arrangements for those sessions. Prior to taking this decision, the Board received briefings from ICANN org, as well as experts from International SOS (ISOS), on the status of COVID-19 and preparations for ICANN67. ICANN's President and CEO contacted the leadership of ICANN's SOs and ACs to see how the different constituencies were reacting to the outbreak, and convened a session on 18 February 2020 with the SO/AC leadership to share ICANN org's briefing and make an ISOS doctor available to receive questions. ICANN org then followed up with the leadership to further the understanding of the community on this issue. While we understand that many in the community are still willing and interested to travel to an in-person ICANN67, the risks and uncertainty discussed above are too difficult to mitigate. We understand that this cancellation poses some hardship on those with existing plans to travel to Cancún, and we greatly apologize for this. We also thank the ICANN community for its commitment to pursue the work of this meeting remotely, as we know that the ICANN community is well-suited for this effort. As the Board, we have been assured that a remote public forum remains on the schedule, and we look forward to engaging directly with you as we do at every Public Meeting. The ICANN Board thanks the host committee as well as our community in Latin America and the Caribbean (LAC) who worked tirelessly to host this meeting in Cancún. We appreciate their understanding and look forward to returning to the LAC region for ICANN70 in 2021. This action is within ICANN's mission and the public interest, as it is the only path to assure that the work of the ICANN community continues as planned for ICANN67. It is the proper decision on many levels, from not putting ICANN org staff at risk; risking the need to divert the resources and attention of ICANN org to a response to a COVID-19 outbreak amongst ICANN org or the community; to taking a responsible and proper measure to protect against contributing to the global outbreak. This decision has resource implications that are being quantified. However, the resources that could be used in the event that ICANN needs to respond to a COVID-19 case/outbreak are currently unquantifiable and likely extremely high. This decision has no impact on the security, stability, or resiliency of the Internet's DNS. This is an organizational administrative decision that does not require public comment. Published on 19 February 2020 David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) Washington, D.C.

1 0