[council] PLEASE READ - ICANN76 Stakeholders/Board sessions

Thu Feb 16 17:16:17 UTC 2023

I thini that's a strong set of questions that I stand behind.
---
Mark W. Datysgeld
Director at Governance Primer
ICANN GNSO Councilor
________________________________
From: Sebastien--- via council <council at gnso.icann.org>
Sent: Thursday, February 16, 2023 12:00
To: COUNCIL at GNSO.ICANN.ORG; GNSO-Chairs; gnso-secs at icann.org
Subject: Re: [council] PLEASE READ - ICANN76 Stakeholders/Board sessions

> Dear Council Colleagues,
>  
> A short note to correct my previous email:
> While the Board would like us to prepare our response to their question ahead of our meeting, the March 1st deadline if for us to submit our questions to them.
>  
> Here are some questions already floated:
> Ensuring Board and ICANN org input to PDP processes
> How do we minimize the need for an ODP and minimize its impact when it is needed? 
> What further information or details should the GNSO integrate into a PDP Final Report to ensure it delivers Board-ready recommendations?
> Getting to the next round of new gTLDs
> What in the Boards view would be required of the GNSO Council and Community to secure a Next Round Launch Date by the 2023 AGM?
> WHOIS Disclosure System
> The Council’s recommendations were delivered 3 months ago which corresponds to ICANN Org’s ramp up requirement; has the development been initiated? What assistance can the Council and its small team offer to ensure initial timelines are met?
>  
> Kindly,
>  
>  
> Sebastien Ducos
> GoDaddy Registry | Senior Client Services Manager
> +33612284445
> France & Australia
> sebastien at registry.godaddy
>  
>  
> From: council <council-bounces at gnso.icann.org> on behalf of Sebastien--- via council <council at gnso.icann.org>
> Date: Thursday, 16 February 2023 at 2:00 pm
> To: COUNCIL at GNSO.ICANN.ORG <council at gnso.icann.org>, GNSO-Chairs <gnso-chairs at icann.org>, gnso-secs at icann.org <gnso-secs at icann.org>
> Subject: [council] FW: PLEASE READ - ICANN76 Stakeholders/Board sessions
> Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad at .
>
>  
>
> Dear Council Colleagues,
>  
> Please find below a letter from Tripti Sinha on behalf of the Board regarding our session in Cancun.
>  
> In particular the Board would like for us to respond to the following by March 1st:
>  
> The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT).  IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented.  What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process?  Please be as concrete as possible.
>  
> Please note that as per our discussion with Becky today, I also expect we will receive a list of clarifying questions on the SubPro Recommendations themselves.
>  
> Kindly,
>  
>  
> Sebastien Ducos
> GoDaddy Registry | Senior Client Services Manager
> +33612284445
> France & Australia
> sebastien at registry.godaddy
>  
>  
> From: Gnso-chairs <gnso-chairs-bounces at icann.org> on behalf of Vinciane Koenigsfeld via Gnso-chairs <gnso-chairs at icann.org>
> Date: Tuesday, 14 February 2023 at 7:23 pm
> To: gnso-chairs at icann.org <gnso-chairs at icann.org>
> Cc: becky.burr at board.icann.org <becky.burr at board.icann.org>, matthew.shears at board.icann.org <matthew.shears at board.icann.org>
> Subject: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions
> Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad at .
>
>  
>
> Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors
>  
>  
> Dear Generic Names Supporting Organization Council Leaders,
>  
> *Please reply no later than Wednesday 1 March 2023*
>  
> The Board and I very much look forward to welcoming and meeting with you during ICANN76 in Cancún, between 11-16 March. It is with great pleasure and excitement that we are finally going to Mexicó, after having had to cancel the in-person component of both ICANN67 and ICANN70. We are grateful to our friends and stakeholders in Latin America for their patience and understanding in the process, and delighted to say ¡ Cancún aquí vamos! (Cancún, here we are!).
>  
> The last three years have certainly proven eventful for all of us, but in unison with ICANN organization, we are more determined than ever to work closely with you to make 2023 and the many years after that, productive and successful.
>  
> This time in particular, the Board proposes a slight change in the approach to our bilateral sessions. We understood that there was an appetite for questions more tailored to each stakeholder group’s needs. Therefore, we will not be sending the same question from the Board to all of you. Having said this, to maintain our commitment to transparency, all of the questions the Board to sends to each group will be published in the Community Digest. 
> The second improvement that we are putting in place starting at ICANN76, is to provide you with a summary of what we heard from you during these bilateral sessions. This summary will be in two forms:
>
> 1.       A blog highlighting key take aways from ICANN76 (and every ICANN meeting after that)
>
> 2.      Summaries of bilateral sessions will be included in the Policy Outcomes Report we publish after each ICANN meeting
>
>  
>
> These are only initial steps, and we will continue to discuss with you ways improve the way we interact moving forward. In the meantime, please find herewith the questions we would like to ask your Group ahead of our joint session in Cancún:  
>  
> The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT).  IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented.  What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process?  Please be as concrete as possible.
>  
> We look forward to hearing your thoughts on this soon.
>  
> We would be grateful if you could send to Board Operations (board-ops-team at icann.org)  the questions you would like the Board to address during our face-to-face meetings. Given the finite time available for these meetings, please list your questions in order of priority. We would also appreciate getting your questions no later than Wednesday 1 March, 2023.
>  
> We thank you in advance for your time on this matter.
>  
> Best regards,
>  
> Tripti Sinha
> Chair, ICANN Board of Directors
>  
>  
>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20230216/151bce58/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 44606 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/council/attachments/20230216/151bce58/image002-0001.png>