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

Trang Nguyen trang.nguyen at icann.org
Tue Nov 29 00:14:35 UTC 2016


All, 

Here is the email list as discussed:

TO: ccTLD world list, ccTLD community list; ccNSO list; regional orgs; GDD
president; Chairs of SOs/ACs and RySG; CCG
CC: CSC, Trang, Bart, ICANN policy staff supporting chairs of SOs/ACs/RySG

TO: cctldworld at icann.org; cctldcommunity at cctld-managers.org;
ccnso-members at icann.org; l.todorov at aptld.org; peter at centr.org;
otieno.barrack at gmail.com; andres at lactld.org; akram.atallah at icann.org;
jbladel at godaddy.com; pdiaz at pir.org; patrik at frobbit.se;
alan.greenberg at mcgill.ca; oscar at lacnic.net; katrina at nic.lv;
bverd at verisign.com; thomas.schneider at bakom.admin.ch; tsinha at umd.edu;
ccg at ietf.org


CC: icann-csc at icann.org; trang.nguyen at icann.org; bart.boswinkel at icann.org;
heidi.ullrich at icann.org; carlos.reyes at icann.org; marika.konings at icann.org;
steve.sheng at icann.org; olof.nordling at icann.org; julie.hedlund at icann.org;
rysgsecretariat at gmail.com

I’ve also consulted with our internal engagement team and they recommend
that the report be sent to the RySG members list as well as the
registrars. If there are no objections to this, I can get the email
address for the registrars list tomorrow. As for the RySG members list, it
is not a public list, but we can ask the RySG secretariat to forward on
Byron’s behalf if the CSC agrees.

Lastly, the CSC charter mentions that the customers of the naming function
includes root server operators and other non-root functions. The
leadership of RSSAC is already included in the distribution list so I
think we have root server operators covered. We are checking with the
leadership teams of the RIRs and IETF to see if they would like to be sent
the report directly, or if they prefer to access it online once it is
posted.

Best,

Trang


-----Original Message-----
From: Trang Nguyen <trang.nguyen at icann.org>
Date: Monday, November 28, 2016 at 1:40 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 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
>>>>>
>>>>
>>>
>>
>



More information about the ICANN-CSC mailing list