Hi all again!

@Bart  Apologies for misinterpreting your words

@Stephen Maybe we can just kindly ask ICANN org to provide us with the status of Retirement Policy implementation? It would make perfect sense both in light of recently approved ccNSO Outline ccNSO Policy Implementation Assistance process (whether ICANN org needs assistance ?) and in light of upcoming FY25 Plan&Budget

Best,

Irina

From: Stephen Deerhake @ ASNIC <sdeerhake@nic.as>
Sent: Monday, November 13, 2023 8:32 PM
To: Bart Boswinkel <bart.boswinkel@icann.org>; Irina Danelia <i.danelia@cctld.ru>; ccnso-council@icann.org
Subject: Re: [ccnso-council] [Ext] RE: Background material items 13 and 17 Council Meeting 200

Greetings Irina and Bart,

Thank you Irina for bringing the “completion” of the “PDP3 Retirement implementation” within ICANN Org (and presumably, IANA) to the Council’s attention.

Not sitting on the Triage Committee, I was not aware of this proclamation on behalf of ICANN Org.  As the Chair of the PDP3 WG with regards to ccTLD Retirement and the Review Mechanism, I of course have an extreme interest in how ICANN Org (and the Board) are handling these matters.

For the record, I find the complete lack of communication between ICANN Org/IANA/ICANN Board to the ccNSO Community regarding their implementation of the adopted Retirement Policy distressing.

I fear we are going down the same rabbit hole with respect to the Board and their consideration of the proposed Review Mechanism policy. 


Are we as the proposing SO going to sit idly by whilst the Board repeats their back side scratching for over a year as they did with the Retirement policy?

I think we as the ccNSO Council need to call the Board out on their inaction on policy which has been developed by the ccNSO Community, with consultation with other SO/AC’s, approved by the ccNSO Community, and finally, endorsed by the ccNSO Community, and has withstood not one, but two community-wide public comment periods.

What is their hesitation here?  More importantly, what is behind their inability to communicate to the ccNSO Community their hesitation to express their potential concerns regarding the proposed Review Mechanism policy?

Best,

Stephen

From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Bart Boswinkel via Ccnso-council <ccnso-council@icann.org>
Reply-To: Bart Boswinkel <bart.boswinkel@icann.org>
Date: Monday, November 13, 2023 at 11:06
To: Irina Danelia <i.danelia@cctld.ru>, "ccnso-council@icann.org" <ccnso-council@icann.org>
Subject: Re: [ccnso-council] [Ext] RE: Background material items 13 and 17 Council Meeting 200

Hi Irina,

I have been informed the Board Ad-hoc working group was closed at the request of the group. Note that ccNSO was not informed  to date about completion of the implementation work.

Kind regards,

Bart

From: Irina Danelia <i.danelia@cctld.ru>
Date: Monday, 13 November 2023 at 16:24
To: Bart Boswinkel <bart.boswinkel@icann.org>, "ccnso-council@icann.org" <ccnso-council@icann.org>
Subject: [Ext] RE: [ccnso-council] Background material items 13 and 17 Council Meeting 200

Hi Bart, all!

With regards item 17.

Bart, You’ve mentioned at Triage Committee meeting that ICANN staff reported to ICANN Board on completion of PDP3 Retirement implementation. Is this report publicly available? It seems to be an important milestone for ccNSO

Thanks in advance,

Irina

From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Bart Boswinkel via Ccnso-council
Sent: Monday, November 13, 2023 4:59 PM
To: ccnso-council@icann.org
Subject: [ccnso-council] Background material items 13 and 17 Council Meeting 200

Dear all,

Please find included the documents relating to item 13 (Update Council 360 Review) and Item 17 (November Monitor Portfolio of activities 2023-2025)  on the agenda of meeting 200

Regarding item 13, please note this includes a comparison with current Terms of Reference, including the questions, and a clean version of the proposed Terms for review.

Kind regards,

Bart