Dear all, The notes, recordings and transcripts for the CWG IANA DT-C Meeting #5 - 2 April are available here: https://community.icann.org/pages/viewpage.action?pageId=52895501 Action Items ACTION: Bernie, as DT-A staff lead, will take this issue to DT-A ACTION: Determine what expertise may be required to sit on CSC Notes Discussion of CWG Call 2 Apr: - presentation/status of Design Teams - mention of relationship of DT-C with DT-M - Template for DT output - DT-C Development of Charter - DTs due on 10 Apr, High Intensity work on 13,14 Apr 1) DT-A IANA SLE - Discussion of DT-A SLE documentation and understand input from IANA - DT-A Standalone work? Discussion with IANA for any agreed upon SLAs - Is DT-A the negotiator for SLAs? Should be result of negotiation between RyOs and IANA - Assumption that future SLAs negotiated between CSC and IANA - DT-A should perhaps include content on how future Service Levels be addressed; Current DT-C report does have content on how to address Service Levels going forward; ACTION: Bernie, as DT-A staff lead, will take this issue to DT-A 2) DT-M Escalation - Keep what we have - CWC and IANA in cases of remediation - Three parallel processes; will be included in proposal - 1st process - Emergency - 2nd process Customer Svc Complain Process - 3rd escalation to CSC - Specify in detail the triggers for escalation - Reference to Kurts work, ID of triggers is more detailed; illustrative and negotiated with IANA as to how that would work. - CSC version will take escalation to a certain point; if CSC believes of poor performance - Two process overlapping; 1) something gone wrong 2) service complaint resolution process (CSC mediating) 3) escalation, but not to whom, but CSC used as a mediator; Issue with committee of four worthy people having to perform mediation is a big task. - Remedial action is missing (Annex Z, point 1) - Ensure DT-M, this is not a part of CSC. CSC be made aware of the issue; provide instruction and plan to be delivered within "x" timeframe. - Assuming CSC is minimal organization; purely technical ops; still might require effort to handle escalations - Still unclear if there will be an MRT - Caution as to not to tailor task to fit organization. If CSC not a part of escalation, then where it will it go? - MB vision of CSC day to day monitoring process; if threshold breach, would alert ccNSO/GNSO as necessary. Use the SOs to trigger certain accountability mechanisms. 3) DT-N Periodic Review of IANA Function - DT-N has not really started; 1st meeting will be scheduled early next week - SD to integrate DT-C concepts into DT-N where appropriate - DT-N assumption that it will be a multi-stakholder body that would cover the review - How should review team be formed and constituted? - Concern - CSC primary role to monitor performance; unsure if CSC will be well equipped to do that from a resourcing perspective & work output perspective. This effort is yet to be sized. Periodic review could be significant amount of work; MB agrees that CSC not perform peridoc review - Role of CSC provides information, perhaps into AoC type of review process that could be multi-stakeholder; flag as way forwards; SF agrees with approach; some piece of the periodic reviews does need to be MS. 4) DT-C Document: - DT-C to develop Charter; seeking appropriate template - Should include bit on how escalation process flows through CSC - Discussion of Changes in latest version ACTION: Determine what expertise may be required to sit on CSC Final draft for Monday, call on Tuesday to wrap it up.
