[ICANN-CSC] CSC Meeting 3: Recordings, Notes, & Chat

Mon Nov 28 21:16:05 UTC 2016

The comment I was trying to make during the meeting is that the problem that Lars identified was already caught by the lawyers when DT-A’s report and the SLE’s were put into the actual IANA Naming Function Contract. <https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30sep16>  The words the lawyers used in the contract (see page 4 of Annex A) are slightly different but substantially identical to the words discussed today. I propose that we adopt the words used in the actual contract.  Just to be clear here are the wording differences with emphasis added:

1.       This is the wording that was original circulated

“Type.  Whether the threshold specified is a minimum target (compliance must be less than the target) or a maximum target (compliance must not be more than the target).”

2.       This is the proposed amendment that was discussed on the call today:

Type. Whether the threshold specified is a minimum target (compliance must  be no less than the target) or a maximum target (compliance must not be more than the target).

3.       This is the wording in the actual contract that I propose be used:

“4. Type. Whether the threshold specified is a minimum target (compliance must not be less than the target) or a maximum target (compliance must not be more than the target).

From: icann-csc-bounces at icann.org [mailto:icann-csc-bounces at icann.org] On Behalf Of Elise Gerich
Sent: November 28, 2016 3:32 PM
To: ICANN-CSC at icann.org
Subject: Re: [ICANN-CSC] CSC Meeting 3: Recordings, Notes, & Chat

Attached is an Appendix with the revision that was made during the call and is consistent with the naming contract language.  This should cover the revision made on the call today.

--Elise

From: Elise Gerich <elise.gerich at iana.org<mailto:elise.gerich at iana.org>>
Date: Monday, November 28, 2016 at 10:25 AM
To: "ICANN-CSC at icann.org<mailto:ICANN-CSC at icann.org>" <ICANN-CSC at icann.org<mailto:ICANN-CSC at icann.org>>
Subject: Re: [ICANN-CSC] CSC Meeting 3: Recordings, Notes, & Chat

Hello Everyone,

One of the actions that was mentioned on the call last week was the desire to have an appendix with definitions of some of the terms used in the report.  Attached is a proposed Appendix to the report with the service definitions from Design Team A’s final, adopted report.

Will this satisfy the request to append definitions to the October 2016 report from PTI to the CSC?

Secondly, there was an action item for me to confirm whether programmatically we can add the relevant exception explanations in front of the appropriate category of the report.  This should be programmatically possible and we are working on revising the program to do so.  That feature is not yet ready for the October 2016 report.

Talk to you all later today.

Regards,
--Elise

From: <icann-csc-bounces at icann.org<mailto:icann-csc-bounces at icann.org>> on behalf of Maria Otanes <maria.otanes at icann.org<mailto:maria.otanes at icann.org>>
Date: Tuesday, November 22, 2016 at 4:03 AM
To: "ICANN-CSC at icann.org<mailto:ICANN-CSC at icann.org>" <ICANN-CSC at icann.org<mailto:ICANN-CSC at icann.org>>
Subject: [ICANN-CSC] CSC Meeting 3: Recordings, Notes, & Chat

Dear Customer Standing Committee,

Please find the meeting recordings and notes below. A more detailed version of notes and a copy of the chat is attached.

Adobe Connect Recording
https://participate.icann.org/p8k196cyu5h/

Audio Recording
http://audio.icann.org/stewardship-transition/csc-iana-21nov16-en.mp3

----------
Customer Standing Committee (CSC) Meeting 3
21 November 2016 @ 22:00-23:00 UTC

Notes

Action Items:
1. Elise: Confirm that program can do. need to confirm if the exceptions will be interleved as proposed.

2. Action PTI staff: include Glossary of Terms in first report. Terms to be used from DT-A

3. Trang: include commentary section in CSC Findings template (Jay and Kal comments).
To send out to membership CSC 21 November (completed)

4. Trang to check IANA Function Agreement on changes SLEs.

5. Secretariat: Doodle poll next meetings: End November, mid December

Decisions:
1. Distinguish between the two reports going forward:
PTI report and CSC report.
Description:
•              PTI report is the monthly report the CSC will RECEIVE form PTI re performance
•              CSC Report is the monthly CSC report for the community.

2. Include Glossary of terms in Reports. Glossary of DT-A (CWG-Accountability SLE group) could be used.

3. PTI should not put in resources that CSC knows and indicated will change.

4. Distribution of Final Monthly Performance Report
All TLD managers,
regional Organsiations
SO/AC chairs
All CSC members
Recipient in ICANN

Webpage and should go in pair with PTI report

----------

All the best,
Ria

_______________________________________________________________________________________________
Ria Otanes
Secretariat Operations Coordinator
Internet Corporation for Assigned Names and Numbers
Washington, DC Office
Office +1 (202) 249-7540 | Cell +1 (202) 679-5185
Email maria.otanes at icann.org<mailto:maria.otanes at icann.org>
Skype maria.otanes.icann
[cid:image001.png at 01D24990.816DA310]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20161128/8f8990a1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8726 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20161128/8f8990a1/image001-0001.png>