THanks Sebastien. indeed it would be important for the two not to collide - especially since it is likely some on Council will be the appointed representatives.
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2024


On Mon, Apr 3, 2023 at 3:09 AM Sebastien@registry.godaddy <Sebastien@registry.godaddy> wrote:

Hi Anne,

 

I can certainly pass the comment on but will not include it in our formal request.

The IRT is not run by us, it will include non-GNSO members, I don’t want to confuse the two.

 

For what it is worth, as ICANN doesn’t officially start until Monday – no weekend calendar – if the IRT decides on an early work session, the most logical for them would be to run it on the Sunday colliding with ours.

 

Kindly,

 

 

Sebastien Ducos

GoDaddy Registry | Senior Client Services Manager

signature_3002786824

+33612284445

France & Australia

sebastien@registry.godaddy

 

 

From: Anne ICANN <anneicanngnso@gmail.com>
Date: Monday, 3 April 2023 at 3:15 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] Sunday of ICANN 77

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@.

 

Support this idea.  I also think it may be a good idea to schedule a Subpro IRT in person meeting on the preceding Saturday if ICANN Org is amenable, keeping in mind that representatives in the IRT should likely be funded.   Is this a reasonable comment to add to the draft letter re the IRT?

Anne

Anne Aikman-Scalese

GNSO Councilor

NomCom Non-Voting 2022-2024

 

 

On Thu, Mar 30, 2023 at 12:19 AM Sebastien--- via council <council@gnso.icann.org> wrote:

Dear Council Colleagues,

 

Based on the outcomes of ICANN 76 and in particular the amount of work we will need to deliver by the end of ICANN 77 – 15 June –, I have taken the liberty to look into the possibility of adding a workday ahead of ICANN 77 to gather the Council on Sunday 11 June 2023.

 

I would like to dedicate this day to finalising anything that might remain pending for 15 June (obviously aiming to be prepared earlier), and organise a workshop, the format of which remains to be defined, to ensure that we are all up to speed on everything SubPro: the set of Recommendations the Board approved and those pending, expectations we need to have regarding the IRT and how we will want to play our role to ensure the process runs smoothly, depending on the outcome of the small team refreshers on GNSO Tools we might not all be familiar with, etc.

Being able to efficiently run such a workshop will require preparation from all of us including a fair amount of reading (or re-reading). We are preparing a full list of documents we should all be familiar with.

 

With your agreement I will formally transmit our request for ICANN to facilitate this extra day. My understanding is that there is support for the idea, that the venue should be available for our arrival a day early, and that ICANN will assume the additional expenses. I would like to be able to send the said request on Monday 3 April.

 

Looking forward to your reaction and comments about this opportunity.

 

Kindly,

 

 

Sebastien Ducos

GoDaddy Registry | Senior Client Services Manager

signature_752651594

+33612284445

France & Australia

sebastien@registry.godaddy

 

_______________________________________________
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.