Okay, lets send a letter.
Bart, can you do a first draft please?
From: philippe.fouquart@orange.com [mailto:philippe.fouquart@orange.com]
Sent: Friday, January 18, 2019 7:46 AM
To: Bart Boswinkel <bart.boswinkel@icann.org>; Austin, Donna <Donna.Austin@team.neustar>; csc-effectivenessrt@icann.org
Subject: RE: [CSC-EffectivenessRT] [Ext] Re: Public announcement
Donna, Bart, and team,
I don’t have a strong view on this either, if it’s current/good practice of form rather than substance because it’s “bylaws driven”, so be it. Even I find it a bit
heavy-handed too, I don’t have any alternative to suggest.
Regards,
Philippe
From: CSC-EffectivenessRT [mailto:csc-effectivenessrt-bounces@icann.org]
On Behalf Of Bart Boswinkel
Sent: Friday, January 18, 2019 9:59 AM
To: Austin, Donna; csc-effectivenessrt@icann.org
Subject: Re: [CSC-EffectivenessRT] [Ext] Re: Public announcement
Hi Donna, all,
The reason for suggesting that the RT informs the ICANN Board and ICANN Org, has no relation with the substance but with point as Trang pointed out earlier this is a ICANN Bylaw driven review, and as such
informing the Board and Org on major milestones is a matter of good practice.
Kind regards,
Bart
From: "Austin, Donna" <Donna.Austin@team.neustar>
Date: Friday, 18 January 2019 at 00:29
To: Bart Boswinkel <bart.boswinkel@icann.org>, "csc-effectivenessrt@icann.org" <csc-effectivenessrt@icann.org>
Subject: RE: [CSC-EffectivenessRT] [Ext] Re: Public announcement
Thanks Bart, 15 February sounds good.
I don’t see any reason for sending a letter to the Board or ICANN Org (I expect you’re keeping them informed). This is not controversial and I don’t remember doing it for the Charter Review,
but happy to go along with the wishes of others.
From: CSC-EffectivenessRT [mailto:csc-effectivenessrt-bounces@icann.org]
On Behalf Of Bart Boswinkel
Sent: Thursday, January 17, 2019 2:34 AM
To: csc-effectivenessrt@icann.org
Subject: Re: [CSC-EffectivenessRT] [Ext] Re: Public announcement
Hi Donna, all,
It think it may be useful to run through Initial report (Elaine?), although the CSC has been kept appraised of the progress of RT. If all agree I will suggest it to Byron for the upcoming CSC ( 15 February
2019) call, which is close to the end of public comment period.
In addition, it may be a good idea to inform the ICANN Board and ICANN Org on progress to date and schedule.
This could be a single letter along lines that RT was formed and started its activities in September 2018 , after adoption of the Template by the ccNSO and GNSO Councils, and RT has very recently published
its Initial Report for public consultation.
Kind regards,
Bart
From: "Austin, Donna" <Donna.Austin@team.neustar>
Date: Thursday, 17 January 2019 at 03:06
To: Steve Chan <steve.chan@icann.org>
Cc: Bart Boswinkel <bart.boswinkel@icann.org>, "csc-effectivenessrt@icann.org" <csc-effectivenessrt@icann.org>
Subject: [Ext] Re: [CSC-EffectivenessRT] Public announcement
Thanks Steve and yayy everyone!
Bart, do you think we need to meet with the CSC to go over the report? I think we did this for the Charter Review and wondered if we should do the same this time around.
Sent from my iPhone
On Jan 16, 2019, at 5:37 PM, Steve Chan <steve.chan@icann.org> wrote:
Team,
The CSC Effectiveness Initial Report has been published and the public comment period has now been initiated. Congratulations on the milestone!
https://www.icann.org/public-comments/csc-effectiveness-initial-2019-01-16-en [icann.org]
Best,
Steve
From: Bart Boswinkel <bart.boswinkel@icann.org>
Date: Tuesday, January 15, 2019 at 11:30 AM
To: Steve Chan <steve.chan@icann.org>
Cc: "csc-effectivenessrt@icann.org" <csc-effectivenessrt@icann.org>, Maria Otanes <maria.otanes@icann.org>
Subject: Public announcement
Hi Steve,
Could you be so kind to submit announcement doc for public comment and to web-admin etc.
Before you do please check spelling☺
Link to initial report is included
Thnaks and kind regards,
BArt
_______________________________________________
CSC-EffectivenessRT mailing list
CSC-EffectivenessRT@icann.org
https://mm.icann.org/mailman/listinfo/csc-effectivenessrt
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.