[CWG-Stewardship] Notes, Recordings, Transcript CWG IANA DT-C Meeting 13 March

[Brenda Brewer]

Dear all, 

 

The notes, recordings and transcripts for the CWG IANA DT-C Meeting - 13 March are available here:
https://community.icann.org/pages/viewpage.action?pageId=52892544


Action Items


Work in Google doc

Action Item:  Donna looks at old documentation, and inform group on relevancy, in relation to scope
of DT C

Group members to look at and suggest ways to approach items a-I in template. Share in Google docs to
allow others of group to chime in

*         

*        Staffan item A

*        Sarah item B

*        Martin Item C

*        Stephanie Item D

*        Kurt Item E

*        Staffan item F

*        Sarah Item G

*        Martin Item H

*        Stephanie Item I

Action Item:  Grace set up Google docs

Action Item:  Call on Monday: time to be determined. Group to be informed by email based on outcome
Doodle poll:   <http://doodle.com/v9x7x8hc5kzvisfn> http://doodle.com/v9x7x8hc5kzvisfn


Notes


Archive is public:  <http://mm.icann.org/pipermail/dt3/> http://mm.icann.org/pipermail/dt3/

Members of DT-C CSC include: 

*        Donna Austin is lead

*        Staffan Jonson

*        Sarah Falvey

*        Martin Boyle

*        Stephanie Duchesneau

*        Kurt Pritz

Kim Davies is potential IANA Liaison

Ashley Heineman is potential NTIA Liaison 

Discussion on next call(s)

- 2 calls next week

- this time is ok with Martin, Stephanie

- martin would like Monday / Friday

- Monday could be problematic for Donna

See no opposition to Monday and Friday at 16:00 UTC

 

Dividing the work

- suggest looking into dependencies in scope template to divide work

 

Functional analysis is a good starting point, but also need to focus on the scope of the DT C
template. That is is expectation from co-chairs and DT design

Functional analysis: 

Become clear of what will be carried from RFP 3 discussions

Starting with template, to divide work

Suggestion: List of that could be handled. Suggest approach for each of the items, settle the list
on Monday

Comment: Authorization function, If it is in, I do not see it. 

A volunteer group, should be gate keeper and be able to act swiftly. Putting it on volunteer
committee would be dangerous and is not in template.

Hard job and opportunity,

Identify where should CSCS should play a role

Suggest: Operational way ahead. Authorization discussion should not stop progress

Start with template and views 

Preconceived about CSC, 

Donna volunteers to go back to RFP 3 documents on CSC, and Interim report.

Get a sense of what CSC is responsible for.( elevator, 30 minutes pitch)

Donna: monitoring of performance

Staffan: minimal effort to look at performance, role is instrumental, if acceptable to SLE's and
check if IANA performs its technical role (reduce to technical function), in combination with
automation, to 
take away capture idea

Sarah: Replaces NTIA technical role, automation is important

Martin: There is role of monitoring performance and montoring reports, and reposting back to own
communities about performances, and getting back issues, when issues are identified: communities: 
Registry constuency, ccNSO and Regional ccTLD organisations

Role in service audits, monitor that work and audit and re-audit that work

There is a role when something goes wrong: contact with Function Operator. CSC should be talking to
IANA to put it right, able to escalate ( for example to CEO)

Foreword looking role (what is happening ahead)

Budget for development

 

Stephanie: agree with all being said. Audit, minimum audit, 

CSC touch point, empowered to address issues-> start conversation and initiate escalation

 

Kurt: Operation changing by IANA ( see David Conrad email on the list). CSC is charged to design the
monitor process: If CSC (quality assurance function. CSCS receives reports, and monitor, Escaltion
process should be well documented. Charge CSC with escalation

Desing it  and then outsourcing it..Independent. ICANN paid for , and CSC select

Output of today's call:

Action to look at items

Work in Google doc

Action Item:  Donna looks at old documentation, and inform group on relevancy, in relation to scope
of DT C

Group members to look at and suggest ways to approach items a-I in template. Share in Google docs to
allow others of group to chime in

*         

*        Staffan item A

*        Sarah item B

*        Martin Item C

*        Stephanie Item D

*        Kurt Item E

*        Staffan item F

*        Sarah Item G

*        Martin Item H

*        Stephanie Item I

Action Item:  Grace set up Google docs

Action Item:  Call on Monday: time to be determined. Group to be informed by email based on outcome
Doodle poll:  <http://doodle.com/v9x7x8hc5kzvisfn> http://doodle.com/v9x7x8hc5kzvisfn

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150316/285df986/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 92 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150316/285df986/image001-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5035 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150316/285df986/smime-0001.p7s>