Hi All

Comments provided in the attached.

By way of update, Philippe and I will be providing an update to the GNSO Council on our proposed plan and seeking agreement from the Council to our continued involvement as members of the CSC Effectiveness Review Team. The council meets on 27 September at which time we hope to be confirmed. If we are not confirmed, and the Council decides to run an open process for volunteers, this effort will be delayed by at least 6 weeks.

Donna

From: CSC-EffectivenessRT [mailto:csc-effectivenessrt-bounces@icann.org] On Behalf Of philippe.fouquart@orange.com
Sent: Friday, September 07, 2018 2:13 AM
To: Martin Boyle <martin.boyle.hertford@ntlworld.com>; Maria Otanes <maria.otanes@icann.org>
Cc: csc-effectivenessrt@icann.org
Subject: Re: [CSC-EffectivenessRT] FW: Draft Template CSC Effectiveness Review

All,

On some of Martin’s points:

- 6b I tend to agree, in the sense that I don’t quite see what the review team would do other than relying to the liaisons within the CSC.

- 9.5 if I understand correctly Martin you suggest that we don’t do number 3 “Conduct a public session at ICANN 63 (October 2018) that is intended to provide an opportunity for the community to provide input to the process”?

- On 9.6 I couldn’t find the typo (Barcelona) in the file..

I added Martin’s edits to the attached but didn’t touch the open elements of substance.

Maria, Monday would not be possible for me either with the ISPCP outreach session.

And wish Martin an enjoyable SG17 meeting…

Regards,

Philippe

From: CSC-EffectivenessRT [mailto:csc-effectivenessrt-bounces@icann.org] On Behalf Of Martin Boyle via CSC-EffectivenessRT
Sent: Wednesday, September 05, 2018 10:47 PM
To: Maria Otanes
Cc: csc-effectivenessrt@icann.org
Subject: Re: [CSC-EffectivenessRT] FW: Draft Template CSC Effectiveness Review

Sorry, this was lost in my preparation for ITU SG17.  I’m still there, but I have just scanned the template and have a few minor comments:

Section 4 heading:  “... can *also* be...”?

4.a: delete “In addiction,”

6.b.  Weren’t we building this into the schedule :  it’s not fair to leave this to the review team!

9.5.  Question:  if there were to be recommendations, could the consultation be done after submission of the review as part of any implementation process?  I am slightly nervous that we might see a minor recommendation delaying the report and the report is to the councils who would have responsibility for implementation.

6.  Isn’t Barcelona ICANN 63 (twice)?

10.  I thought we’d trimmed the timeline...?

I don’t particularly need another call until after the CSC and Council discussions.

I’m not scheduled to be in Barcelona, but could possibly, and if necessary, do an overnight trip.  But not on Monday!  However, I’m sure that you will manage fine without me and I could be in on remote.

Hope this helps

Martin 

Martin Boyle 

Sent from my iPhone

On 4 Sep 2018, at 23:27, Maria Otanes <maria.otanes@icann.org> wrote:

Dear all,

As a friendly reminder, I’m attaching the template document Bart circulated last week. Please let us know if you have any comments.

Would you like to schedule an additional call?

The next CSC meeting is scheduled for 17 September at 20:00 UTC. As discussed on last week’s call, we’ve included an agenda item for this team to meet with the CSC.

Lastly, when would you like to schedule the Effectiveness Review Team public session in Barcelona? May I suggest Monday, 22 October block 13:30-15:00? Please let me know if that works for you.

Best,

Ria

From: CSC-EffectivenessRT <csc-effectivenessrt-bounces@icann.org> on behalf of Bart Boswinkel <bart.boswinkel@icann.org>
Date: Wednesday, August 29, 2018 at 8:32 AM
To: "csc-effectivenessrt@icann.org" <csc-effectivenessrt@icann.org>
Subject: Re: [CSC-EffectivenessRT] Draft Template CSC Effectiveness Review

Dear all,

Please find included redline and clean version of template document.

In addition to Philippe’s suggested changes, I have:

Included sentence to mandate the RT to develop relevant performance indicators and use relevant metrics, reflecting the CSC Effectivenss measures as listed by martin and you have accepted

Updated section 9 about process/procedure to reflect yesterday’s discussion

Updated the schedule per yesterday’s discussion

Kind regards,

Bart

From: CSC-EffectivenessRT <csc-effectivenessrt-bounces@icann.org> on behalf of "philippe.fouquart@orange.com" <philippe.fouquart@orange.com>
Date: Tuesday 28 August 2018 at 16:10
To: Maria Otanes <maria.otanes@icann.org>, "csc-effectivenessrt@icann.org" <csc-effectivenessrt@icann.org>
Subject: Re: [CSC-EffectivenessRT] Draft Template CSC Effectiveness Review

Hi everyone,

Following our discussion earlier today, I made a quick revision of the attached. Editorial changes I’d say:

• Have attempted to include Debbie’s suggestion on section 6 to remove “possible”.
• We need to make sure that under 10 the number of [public] sessions matches our discussion

Regarding the point of how CSC may review the KPIs and metrics moving forward, I believe this falls under 3.C.i ,  but tend to think this belongs to the review itself rather than to the methodology so I didn’t change the text. I’d suggest we keep this for the review itself.

Regards,

Philippe

From: CSC-EffectivenessRT [mailto:csc-effectivenessrt-bounces@icann.org] On Behalf Of Maria Otanes
Sent: Monday, August 27, 2018 3:52 PM
To: csc-effectivenessrt@icann.org
Subject: [CSC-EffectivenessRT] Draft Template CSC Effectiveness Review

Dear Effectiveness Review Team,

Please find the draft template CSC Effectiveness Review document.

It can also be found on the Wiki: https://community.icann.org/x/JRRpBQ

All the best,

Ria

_______________________________________________________________________________________________

Ria Otanes

Secretariat Operations Coordinator

Internet Corporation for Assigned Names and Numbers (ICANN)

Telephone: +1 202 249 7540

Mobile: +1 202 679 5185

Skype: maria.otanes.icann

Washington, DC Office | UTC-4

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

<Template CSC Effectiveness Review version 02 29 August 2018 clean.docx>

<Template CSC Effectiveness Review version 02 29 August 2018 redline.docx>

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