[DTC CSC] Agenda for call tomorrow

Fri May 8 15:20:47 UTC 2015

Donna, all
Please find included notes from todays call
Kind regards,
Bart

——————————

"Punch List" items

Objective call is to work through punch list items.

Item 6

Comments:

It might be usefull to think about thresholds. It is not directly CSC related. Risk of michievous complaints, possible way to deal with those, frivolous complaints. Thisis DT M issue

Threshold intersting thought

Item 11

Comments:

Expression of Interst to ccNSO/GNSO (RySG). If only one place, need for  judgement call.

Need to understand: ccTLD issue, ccNSO need to approves, but thisdoes not imply ccTLD outside ccNSo could not apply.

Focus is on .ARPA (no constituency).

Choice between parties if even number, may become an issue.

Alternative: the CSC can put out an request for expressions of interest to arpa, .edu, .gov , etc. Then the CSC can evaluate the expressions of interest and send to the RySG and ccNSO  for ratification

Page 59: one addtional TLD operator (small pool) . Advise of the CSC to community.

Concern: Mechnism does not work for the first time.

5 TLDs reps on CSC, potentially (2 CC and 2 GTLD), 5th non-members may

Revisit

Item 12

Comments:

Add in accordance own rules and procedures (GNSO and ccNSO)

Item 13:

Comments

Best Practice, replacement needs to be in palce, but definetely witin 3 months.

Ask ccNSO and GNSO what they think.

Note that committee is small, one out may cause disbalance.

Alternatives:

-    appoint termporaly replacement/appointment,

-    no fundamental decisions

-    only ratified by SO, lacking on CSC

Expectation there are hardly formal votes. Only when it comes to formal voting, need for "full

CSC"

Draft charter provides for one month for replacement.

Use standby as temporaly. replacement

Item 14:

Comments

Does Liaison need to be registry operator?

Role of IFR is predominantly technical. The person from CSC needs to be able to brief the IFT of operation of PTI ( hence technical role, and most likly registry operator)

Small group, and hence internal decision making process., will most likely right person.

CSC to decide the liaison, ensure technical liaison with technical knowledge ( therfore rep of Regitry operator)

Item 15

Comments

Risk of overregualting if thsi is prescribed at thsi stage. For committee to decide in consultation with PTI

To be clear: PTI and NOT PTI board

Item 16

Comments

Special review relates to reveiw of IFR.

This if for the ccNSO and GNSO (Councils ) to work on. Alternative ways of dealing with problems, hence no prescribtive process for special review or alternative processes/action.

Item 17 - 20

Comments

Items not in scope DT C

Remark: item 17 not really understood.

question: what is role of CSC, if all important topics are in contract between ICANN and PTI?

This may part to discussion of whether CSC is part of ICANN or not. Need to anchor down PTI, question where and how to do it.

Serious concern around roe of CSC in context of escalation. At this stage no concern CSC or IFR are in ICANN, but enforcability is though ICANN ( contract between ICANN and PTI). CSC and IFR propose and produce reports. Othe rneeds to take action

Question lawyers is where to nest enforceabillity.

Item 21

Comments

Concern DT M may

Item 22

Comments

Dicretionary for CSC initally. CSC is put in to understadn when action is needed. At some point it is up to CSC to escalate. Members of CSC will reaching out to wider world.

Risk of overdefintion. There is an escaltion path, communication path.

Suggestion to include theresholds or targets (objective) not detemined by  CSC

Link with item 15,

What is systemic issue?

Link with remedial action: it is not taken, or does not resolve the problem.

Recognition it will be subjective

Item 23

Comments:

Individual remidation not a role of CSC

Agreed

Item 37

Comments

Relates to accountability work

From: Donna Austin <Donna.Austin at ariservices.com<mailto:Donna.Austin at ariservices.com>>
Date: Friday 8 May 2015 00:27
To: "dt3 at icann.org<mailto:dt3 at icann.org>" <dt3 at icann.org<mailto:dt3 at icann.org>>
Subject: [DTC CSC] Agenda for call tomorrow

Hi All

Looking forward to getting the band back together tomorrow :)

I’ve revised the Sidley Punchlist (see attached) to identify those issues we need to consider. I’ve added some thoughts in a comments column.

The plan for tomorrow is to work through the list, discuss each item and see where we end up.

Sidley will not be on the call tomorrow, I thought it was better for us to work through the list first and if we had any residual questions we needed answered we could send those to Sidley.

Thanks

Donna

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/dt3/attachments/20150508/e8220f95/attachment-0001.html>