[ICANN-CSC] FW: Agenda for Nov 21 CSC call

[Trang Nguyen]

All,

Please see attached the revised draft October CSC report based on today’s
discussion. Changes made include:

1. Date of report changed from 22 November 2016 to today’s date (28
November 2016)
2. Changed header above table to “Changes to Service Level Agreement(s)
that the CSC is considering or
Recommending”
3. Changed header in table from “Actual SLA” to “Actual performance”
4. Added text below table regarding change to definition of “Type”

We will circulate the email distribution list shortly.

Best,

Trang


-----Original Message-----
From: Trang Nguyen <trang.nguyen at icann.org>
Date: Monday, November 21, 2016 at 8:07 PM
To: "icann-csc at icann.org" <icann-csc at icann.org>
Subject: Re: [ICANN-CSC] FW:  Agenda for Nov 21 CSC call

>All,
>
>Please find attached the revised CSC report template as well as a proposed
>draft of this month’s report. Both are based on discussions today. We hope
>this accurately reflects comments expressed.
>
>Best,
>
>Trang
>
>-----Original Message-----
>From: <icann-csc-bounces at icann.org> on behalf of Trang Nguyen
><trang.nguyen at icann.org>
>Date: Monday, November 21, 2016 at 2:08 PM
>To: "icann-csc at icann.org" <icann-csc at icann.org>
>Subject: [ICANN-CSC] FW:  Agenda for Nov 21 CSC call
>
>>All,
>>
>>Please see attached proposed drafts of the monthly CSC findings report,
>>content for the CSC webpage, and listing of processes/entities with
>>linkage to the CSC. I am also attaching an email from Bart with
>>additional
>>suggestions for the listing of processes/entities with linkage to the
>>CSC.
>>
>>Best,
>>
>>Trang
>>
>>-----Original Message-----
>>From: Trang Nguyen <trang.nguyen at icann.org>
>>Date: Friday, November 18, 2016 at 12:09 PM
>>To: Byron Holland <byron.holland at cira.ca>
>>Cc: Bart Boswinkel <bart.boswinkel at icann.org>
>>Subject: Re: [ICANN-CSC] Agenda for Nov 21 CSC call
>>
>>>Hi Byron,
>>>
>>>In preparation for next Monday¹s call, please find attached:
>>>
>>>1) A proposed draft of the monthly CSC findings report
>>>2) Proposed draft content for the CSC webpage
>>>3) Listing of processes/entities where the CSC has interactions with.
>>>Please note that I¹ve included the CCG, but I am really not sure what
>>>the
>>>interaction between the CSC and CCG is. I spoke to Greg Shatan after the
>>>CSC F2F in Hyderabad and he mentioned that he would write a memo
>>>explaining what he thinks the interaction would be. I have not yet
>>>received such memo.
>>>
>>>I wanted to share these with you first for input/feedback before sharing
>>>with the larger group.
>>>
>>>Best,
>>>
>>>Trang
>>>
>>>-----Original Message-----
>>>From: <icann-csc-bounces at icann.org> on behalf of Byron Holland
>>><byron.holland at cira.ca>
>>>Date: Friday, November 18, 2016 at 9:06 AM
>>>To: "ICANN-CSC at icann.org" <ICANN-CSC at icann.org>
>>>Subject: [ICANN-CSC] Agenda for Nov 21 CSC call
>>>
>>>>Colleagues,
>>>>
>>>>Please see below for the agenda for our call on Monday.  Basically, the
>>>>objective of the call is to discuss the format of the monthly report
>>>>(item 2 and document attached).  We should also discuss who it gets
>>>>sent
>>>>to (item 3) and remind ICANN/PTI of the long list of action items from
>>>>Hyderabad.  The text here is as Maria recorded them in the chat -
>>>>document attached.  I think it would be worthwhile to run through them
>>>>to
>>>>ensure that everyone is on the same page.
>>>>
>>>>Regards,
>>>>Byron
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>Customer Standing Committee (CSC) Meeting 3
>>>>21 November 2016 @ 22:00 ­ 23:00 UTC (17:00-18:00 EST)
>>>>
>>>>Agenda
>>>>
>>>>1.	Welcome and Introduction
>>>>
>>>>2.	Review of Draft Monthly Performance Report provided by PTI Overview
>>>>of
>>>>SLE
>>>>
>>>>3.	Distribution of Final Monthly Performance Report
>>>>
>>>>4.	Update on Action Items from Last Meeting
>>>>
>>>>a.	Draft operating procedures
>>>>b.	Make sure the communications are stating the flow of website,
>>>>reporting and summaries
>>>>c.	Proposed content for website
>>>>d.	Short term ­ initial report from PTI so that CSC can add component
>>>>and
>>>>publish third week of     November
>>>>e.	Review the bylaws that are associated with CSC
>>>>f.	Draft document that states all requirements that CSC will fulfill
>>>>g.	Make sure the CSC is clear on any entity that may impact or have
>>>>related requirement of the CSC
>>>>h.	Create a template/draft to see what makes sense for various reports
>>>>i.	CSC to provide ICANN staff a list of needs so support could be
>>>>provided
>>>>j.	Ask PTI to provide language for graphics
>>>>k.	A calendar of calls need to be scheduled
>>>>
>>>>5.	Other Business
>>>>
>>>>6.	Adjournment
>>>>
>>>
>>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: default.xml
Type: application/xml
Size: 3222 bytes
Desc: default.xml
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20161128/d2739d9b/default-0001.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRAFT - CSC Report - Oct2016_v2_CLEAN.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 103435 bytes
Desc: DRAFT - CSC Report - Oct2016_v2_CLEAN.docx
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20161128/d2739d9b/DRAFT-CSCReport-Oct2016_v2_CLEAN-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DRAFT - CSC Report - Oct2016_v2_REDLINE.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 104601 bytes
Desc: DRAFT - CSC Report - Oct2016_v2_REDLINE.docx
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20161128/d2739d9b/DRAFT-CSCReport-Oct2016_v2_REDLINE-0001.docx>