Hi Anne,
I am happy to be corrected, but I read this to be in relation to last week’s Board vote and more precisely:
Resolved (2023.03.16.08), the Board directs the ICANN Interim President and CEO, or her designee(s), to deliver the Implementation Plan to the Board no later than 1 August 2023.
The timely delivery of the Implementation Plan requires the satisfactory completion of the following four deliverables by the last day of the ICANN77 Public Meeting (15 June 2023):
- A plan and timeline as agreed upon by the ICANN Board and the GNSO Council for consideration and resolution of all Outputs contained in Section
B of the Scorecard;
- A working methodology and IRT work plan and timeline as agreed upon by ICANN org and the GNSO Council;
- A GNSO Council project plan and timeline for policy work, or an alternate path, on how to handle closed generics for the next round of new gTLDs;
and
- A project plan from the GNSO Internationalized Domain Names (IDNs) Expedited Policy Development Process (EPDP) Working Group (WG) identifying
all charter questions that will impact the next Applicant Guidebook, along with considerations to ensure a consistent solution on IDN Variant TLDs with the ccPDP4 on IDN ccTLDs (in accordance with prior Board Resolution
2019.03.14.09), and a timeline by when the IDNs EPDP WG will deliver relevant recommendations to the GNSO Council.
Resolved (2023.03.16.09), the Board requests that the GNSO Council deliver the plans referenced in the preceding paragraph by the last day of the ICANN77 Public Meeting (15 June
2023).
For June 15th amongst the 4 points, we need to have figured out with the Board how we want the 38 points and in what time frame these will be handled. This is about identifying
what needs to be resolved in what manner (the triage exercise launched this week), and for those items that won’t be immediately closed, identify a path to resolution with timelines.
Becky and Avri had highlighted rough timelines in their presentation of Section B of the Scorecard by noting estimated ETAs up to ICANN79. What we are now asked to do collectively
is to agree on finetuned plans and timelines everyone will have to stick to.
Note the work to be also done in parallel regarding Closed Generics, IDNs and our involvement in insuring productive IRT participation.
In fine this will be transmitted by the Board to Org during their ICANN76 meeting in June, with mission for Org to deliver an implementation plan by August 1st. With that
plan the Board will be able to derive and announce a Launch date.
This is still a very large amount of work for us to have done in the next 7 weeks, but doesn’t include the full resolution of all 38 items in the Scorecard.
Kindly,
Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
+33612284445
France & Australia
From:
Anne ICANN <anneicanngnso@gmail.com>
Date: Thursday, 23 March 2023 at 1:20 am
To: Sebastien Ducos <Sebastien@registry.godaddy>
Cc: COUNCIL@GNSO.ICANN.ORG <council@gnso.icann.org>, GNSO-Chairs <gnso-chairs@icann.org>, gnso-secs@icann.org <gnso-secs@icann.org>
Subject: Re: [council] FW: [CORRESPONDENCE] Tripti Sinha to Sebastien Ducos GNSO Chair - Board Action on SubPro Final Report
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@.
Thanks Sebastien. As to timing for the Board to take action, I note the following language from Tripti's letter:
The Board acknowledges that the satisfactory completion of these deliverables by 15 June 2023 will require a collective commitment from the Board, the GNSO Council, and ICANN org as they form the critical
path for ICANN org to produce the Implementation Plan.
The listed deliverables in the Boad's letter seem to include items that are not necessarily set to be completed by June 15, 2023. Could you share the Leadership perspective on this point? Have I misunderstood
how the Board is characterizing the "deliverables"?
Thank you,
Anne
On Wed, Mar 22, 2023 at 8:25 AM Sebastien--- via council <council@gnso.icann.org> wrote:
Dear Council Colleagues,
It appears that I have omitted to forward the below message from Tripti Sinha sent on 17 March 2023, last Friday.
Apologies for the delay.
Kindly,
Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
+33612284445
France & Australia
From: Gnso-chairs <gnso-chairs-bounces@icann.org> on behalf of Wendy Profit via Gnso-chairs <gnso-chairs@icann.org>
Date: Friday, 17 March 2023 at 12:49 am
To: gnso-chairs@icann.org <gnso-chairs@icann.org>, Jonathan Zuck <JZuck@innovatorsnetwork.org>, nico.caballero@board.icann.org <nico.caballero@board.icann.org>
Cc: Secretary <secretary@icann.org>, Correspondence <Correspondence@icann.org>, gac-leadership@icann.org <gac-leadership@icann.org>, Board Ops Team <board-ops-team@icann.org>, Tripti Sinha <tripti.sinha@board.icann.org>, gac-staff@icann.org <gac-staff@icann.org>, AtLarge Staff <atlarge_forward@icann.org>, gnso-secs@icann.org <gnso-secs@icann.org>
Subject: [gnso-chairs] [CORRESPONDENCE] Tripti Sinha to Sebastien Ducos GNSO Chair - Board Action on SubPro Final ReportCaution: 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@.
Dear Sebastien Ducos,
(cc: ALAC Chair Jonathan Zuck, GAC Chair Nico Caballero)
Please find the attached letter from Tripti Sinha with regard to the recent action by the ICANN Board with regard to the New gTLD Subsequent Procedures Final Report.
Thank you and best regards,
Wendy Profit
Board Operations Senior Manager
ICANN
_______________________________________________
council mailing list
council@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.