[NCSG-PC] ICANN76 Stakeholders/Board sessions
Johan Helsingius
julf at Julf.com
Sat Feb 18 20:05:50 EET 2023
Hi,
I note that Paul is specifically asking for someone from Non-commercial
(and Contracted Parties). I guess it has to be a council member...
Julf
-------- Forwarded Message --------
Subject: Re: [council] [gnso-chairs] PLEASE READ - ICANN76
Stakeholders/Board sessions
Date: Sat, 18 Feb 2023 12:13:53 +0000
From: Paul McGrady via council <council at gnso.icann.org>
Reply-To: Paul McGrady <paul at elstermcgrady.com>
To: Mark W. Datysgeld <mark at governanceprimer.com>, Steve Chan
<steve.chan at icann.org>, Sebastien at registry.godaddy
<Sebastien at registry.godaddy>, 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>
*Disclaimers:*
*Subject to a final greenlight from Council Leadership to proceed.*
*Written early in the morning on a Saturday – forgive typos*.
Thanks Mark!
All, it would be great to have 1 or 2 more so that we are sure to get a
full range of eyes on this, especially helpful if they were
Non-commercial and Contracted Parties voices to round us out. Special
request that Jeff join the team as this is a question from the GAC.
Also, if you don’t have time to participate on the bespoke small team
but have thoughts on Tripti’s question, please do put your comments into
the document (diamonds in the rough welcome – the team can polish later).
Best,
Paul
*From:* Mark W. Datysgeld <mark at governanceprimer.com>
*Sent:* Friday, February 17, 2023 11:22 PM
*To:* Paul McGrady <paul at elstermcgrady.com>; Steve Chan
<steve.chan at icann.org>; Sebastien at registry.godaddy;
COUNCIL at GNSO.ICANN.ORG; GNSO-Chairs <gnso-chairs at icann.org>;
gnso-secs at icann.org
*Subject:* Re: [council] [gnso-chairs] PLEASE READ - ICANN76
Stakeholders/Board sessions
Since I have been been banging the drum about Council-Board interaction,
I think I should step up for this team.
Lead us to greatness, Paul.
---
Mark W. Datysgeld
Director at Governance Primer
ICANN GNSO Councilor
------------------------------------------------------------------------
*From:* Paul McGrady via council <council at gnso.icann.org
<mailto:council at gnso.icann.org>>
*Sent:* Friday, February 17, 2023 18:37
*To:* Steve Chan; Sebastien at registry.godaddy
<mailto:Sebastien at registry.godaddy>; COUNCIL at GNSO.ICANN.ORG
<mailto:COUNCIL at GNSO.ICANN.ORG>; GNSO-Chairs; gnso-secs at icann.org
<mailto:gnso-secs at icann.org>
*Subject:* Re: [council] [gnso-chairs] PLEASE READ - ICANN76
Stakeholders/Board sessions
Thanks Steve! The document looks great. I’ll await the final
greenlight from Seb that the bespoke small team is the final plan
and then the resulting flood of volunteers. Once we are at that
point, I hope Staff will send around a Doodle to help us get our
kickoff meeting scheduled.
Best,
Paul
*From:* Steve Chan <steve.chan at icann.org <mailto:steve.chan at icann.org>>
*Sent:* Friday, February 17, 2023 1:14 PM
*To:* Sebastien at registry.godaddy
<mailto:Sebastien at registry.godaddy>; Paul McGrady
<paul at elstermcgrady.com <mailto:paul at elstermcgrady.com>>;
COUNCIL at GNSO.ICANN.ORG <mailto:COUNCIL at GNSO.ICANN.ORG>; GNSO-Chairs
<gnso-chairs at icann.org <mailto:gnso-chairs at icann.org>>;
gnso-secs at icann.org <mailto:gnso-secs at icann.org>
*Subject:* Re: [gnso-chairs] PLEASE READ - ICANN76
Stakeholders/Board sessions
Dear Councilors,
Please find a Google doc created for this exercise. Permissions are
currently set to allow for comments, but once we know who will be
taking part in the effort besides Paul, we will provide Editor
rights:
https://docs.google.com/document/d/1igtbNSUBMc3cIFlR7-zTyg5epNwfm7ImkxaP_K-8Uw8/edit?usp=sharing
<https://docs.google.com/document/d/1igtbNSUBMc3cIFlR7-zTyg5epNwfm7ImkxaP_K-8Uw8/edit?usp=sharing>
Note that in the Google document, we have also included the
potential questions to the ICANN Board as by shared by Sebastien. We
are assuming that similar planning will be needed once the topics
are agreed to by the Council.
It sounds like the Councilors will organize themselves, but if you
need any assistance from support staff, just let us know.
Best,
Steve
*From: *Gnso-chairs <gnso-chairs-bounces at icann.org
<mailto:gnso-chairs-bounces at icann.org>> on behalf of Sebastien---
via Gnso-chairs <gnso-chairs at icann.org <mailto:gnso-chairs at icann.org>>
*Reply-To: *"Sebastien at registry.godaddy
<mailto:Sebastien at registry.godaddy>" <Sebastien at registry.godaddy
<mailto:Sebastien at registry.godaddy>>
*Date: *Friday, February 17, 2023 at 1:48 AM
*To: *Paul McGrady <paul at elstermcgrady.com
<mailto:paul at elstermcgrady.com>>, "COUNCIL at GNSO.ICANN.ORG
<mailto:COUNCIL at GNSO.ICANN.ORG>" <council at gnso.icann.org
<mailto:council at gnso.icann.org>>, GNSO-Chairs <gnso-chairs at icann.org
<mailto:gnso-chairs at icann.org>>, "gnso-secs at icann.org
<mailto:gnso-secs at icann.org>" <gnso-secs at icann.org
<mailto:gnso-secs at icann.org>>
*Subject: *Re: [gnso-chairs] PLEASE READ - ICANN76
Stakeholders/Board sessions
Hi Paul,
Thank you for raising your hand for this, it is much appreciated.
I think that in the past we would have taken this to the mailing
list, but I must admit it is not my favorite medium: I tend to get
quickly lost in the sub-threads (I am probably showing my age).
The current thinking should lead us to a small team setup, but given
the short timelines I wouldn’t want to waste any of it haggling over
how to form it.
Could I suggest that:
1. We initiate immediately a bespoke small team headed by Paul
McGrady + eventually a single co-lead from the other house
should anyone volunteer.
2. Membership to open to all Councillors. Should any Councillor
need external input, he/she can seek it but remains the small
team sole member.
3. Staff to create a bespoke Google Doc with the Board’s questions.
4. The small team takes it from there with the aim of gathering our
thoughts by March 3rd.
Council colleagues: Thoughts? Comments?
Kindly,
*Sebastien Ducos*
GoDaddy Registry | Senior Client Services Manager
signature_1287335570
+33612284445
France & Australia
sebastien at registry.godaddy <mailto:sebastien at registry.godaddy>
*From: *Paul McGrady <paul at elstermcgrady.com
<mailto:paul at elstermcgrady.com>>
*Date: *Thursday, 16 February 2023 at 4:32 pm
*To: *Sebastien Ducos <Sebastien at registry.godaddy
<mailto:Sebastien at registry.godaddy>>, COUNCIL at GNSO.ICANN.ORG
<mailto:COUNCIL at GNSO.ICANN.ORG> <council at gnso.icann.org
<mailto:council at gnso.icann.org>>, GNSO-Chairs <gnso-chairs at icann.org
<mailto:gnso-chairs at icann.org>>, gnso-secs at icann.org
<mailto:gnso-secs at icann.org> <gnso-secs at icann.org
<mailto:gnso-secs at icann.org>>
*Subject: *RE: PLEASE READ - ICANN76 Stakeholders/Board sessions
You don't often get email from paul at elstermcgrady.com
<mailto:paul at elstermcgrady.com>. Learn why this is important
[aka.ms]
<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;!!PtGJab4!5Op6xSBTHrIfGbtr3DjEq3l-bKmjB_LFUrniT_xfC6TL1CbdAgBX6o9JvVjLAh8B6jMHywSFJLUVnQlEU1i9xUSkzddn$>
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 .
Thanks Seb! I think our questions to the Board proposed below look
great and touch on important concerns.
As for Tripti’s question, what will be our mechanism to respond?
Should we (1) start a shared document that folks can contribute to,
(2) do we want to run a short-lived small team to develop a draft
for the broader Council to review (I’m happy to lead that effort if
you like), (3) do we send ideas to the mailing list and have staff
compile them and then we all edit the compilation, (4) something else?
Also, we need to have milestone deadlines so that we aren’t
scrambling and doing this on airplanes to Cancun. Thanks!
Best,
Paul
*From:* council <council-bounces at gnso.icann.org
<mailto:council-bounces at gnso.icann.org>> *On Behalf Of *Sebastien---
via council
*Sent:* Thursday, February 16, 2023 9:01 AM
*To:* COUNCIL at GNSO.ICANN.ORG <mailto:COUNCIL at GNSO.ICANN.ORG>;
GNSO-Chairs <gnso-chairs at icann.org <mailto:gnso-chairs at icann.org>>;
gnso-secs at icann.org <mailto: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 1^st 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
signature_3093328915
+33612284445
France & Australia
sebastien at registry.godaddy <mailto:sebastien at registry.godaddy>
*From: *council <council-bounces at gnso.icann.org
<mailto:council-bounces at gnso.icann.org>> on behalf of Sebastien---
via council <council at gnso.icann.org <mailto:council at gnso.icann.org>>
*Date: *Thursday, 16 February 2023 at 2:00 pm
*To: *COUNCIL at GNSO.ICANN.ORG <mailto:COUNCIL at GNSO.ICANN.ORG>
<council at gnso.icann.org <mailto:council at gnso.icann.org>>,
GNSO-Chairs <gnso-chairs at icann.org <mailto:gnso-chairs at icann.org>>,
gnso-secs at icann.org <mailto:gnso-secs at icann.org>
<gnso-secs at icann.org <mailto: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 1^st :
*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
signature_1469584128
+33612284445
France & Australia
sebastien at registry.godaddy <mailto:sebastien at registry.godaddy>
*From: *Gnso-chairs <gnso-chairs-bounces at icann.org
<mailto:gnso-chairs-bounces at icann.org>> on behalf of Vinciane
Koenigsfeld via Gnso-chairs <gnso-chairs at icann.org
<mailto:gnso-chairs at icann.org>>
*Date: *Tuesday, 14 February 2023 at 7:23 pm
*To: *gnso-chairs at icann.org <mailto:gnso-chairs at icann.org>
<gnso-chairs at icann.org <mailto:gnso-chairs at icann.org>>
*Cc: *becky.burr at board.icann.org <mailto:becky.burr at board.icann.org>
<becky.burr at board.icann.org <mailto:becky.burr at board.icann.org>>,
matthew.shears at board.icann.org
<mailto:matthew.shears at board.icann.org>
<matthew.shears at board.icann.org
<mailto: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 OrganizationCouncil 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 moredetermined 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 <mailto: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 --------------
_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
More information about the NCSG-PC
mailing list