<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Dear all,</div>
<div>Please find included notes from todays call</div>
<div>
<div>
<p align="LEFT" style="font-family: Arial; font-size: 15px;"><span style="font-size: 11pt;"><b>Action Stephanie: capture discussion in next version overview document, and circulate for discussion</b></span></p>
<p align="LEFT" style="font-family: Arial; font-size: 15px;"><span style="font-size: 11pt;"><b>Action staff: Send out Dodole for Monday afternoon ( at latets closure 1 before close of the call)</b></span></p>
</div>
<div><span style="font-size: 11pt;"><b><br>
</b></span></div>
<span id="OLK_SRC_BODY_SECTION"><top>
<p align="LEFT"><span style="font-size: 11pt; font-family: Arial;"><b>Agenda DTC (CSC) meeting 20 March 2015 (16.00-18.00 UTC)</b></span></p>
<p align="LEFT"><span style="font-size: 11pt; font-family: Arial;"><b>1. Welcome and roll call</b></span></p>
<p align="LEFT"><span style="font-size: 11pt; font-family: Arial;"><b>2. Work process before Monday 6 PM UTC</b></span></p>
<p align="LEFT"><span style="font-size: 11pt; font-family: Arial;"><b>3. documents </b></span></p>
<span style="font-size: 11pt; font-family: Arial;">
<ol>
<li><b>Google Doc</b><span style="font-size: 11pt;"></span></li><li><b>Donna overview</b><span style="font-size: 11pt;"></span></li><li><b>Template</b>
<p align="LEFT"><span style="font-size: 11pt;"><b>4. Preparation before Istanbul</b></span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>5. Next meeting & AoB</b></span></p>
<div style="font-family: Calibri, sans-serif; font-size: 14px;"><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">1. All DT members present + Kim Davies ( IANA )</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">2. Prep Monday 6 pm UTC ( delivery time discussion paper DTC )</span></p>
<p align="LEFT"><font face="Arial" size="3"><b>3. Document Discussion</b></font></p>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li>
<p align="LEFT"><font face="Arial" size="3">G</font><font face="Arial">OOGLE DOC</font><font face="Arial" size="3"> </font><span style="font-size: 11pt;">Staffan's changes, reflect discussion with ccTLDs ove rlast days</span></p>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Suggestion to go over text, in particular insertions from SSAC 069</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Changes section a</span></p>
<p align="LEFT"><font face="Arial" size="3">Kim: the way changes are presented is </font><font face="Arial">artefact</font><font face="Arial" size="3"> from IANA contract</font></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">1.1. is superset of 1.2 ( Changes in area 1.1 automatically result in changes in area 1.2.)</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Point 2. Substantial changes for TLD</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Kim suggest text for Google text </span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">1. Changes an appointed registry makes: 1.1 Changes to the root zone file (technical changes published in the DNS) 1.2 Changes to the root zone database (updates to technical and contact data published on the IANA website and via WHOIS protocols)2. Changes of registry appointments (i.e. delegation of new TLDs, transfer of existing TLDs, removing delegation of existing TLDs)</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Donna: capture in table is what is currently situation and what needs to change as result of transition</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">See table C2.9.a.b</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Martin: Caution about invovlement of the CSC (third parties) in sensitive area of ccTLD delegations and redelgations</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Also similar concern with regard to gTLD delegation and redelgation</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">As suggested by Donna: no role for CSC in delegation and redelegation of TLDs </span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Q: will it be challenged during the meeting?</span></p>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li>
<p align="LEFT" style="font-size: 11pt;"><br>
</p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Note Potential overlap with Authorization:</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">No role of CSC with regard to Authorization, only lead to delays</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">- Maybe only role in MONITORING of Authroriztion.</span></p>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Current reporting:</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">- Monthly reporting only seen by NTIA (confidential) ( DNSES key rollover, changes</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Question: how would CSC deal with confidential reports.</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">In some cases ( issues with regard to individual)</span></p>
<p align="LEFT" style="font-size: 11pt;"><span style="font-size: 11pt;">Public reports: </span></p>
<font size="3"><span style="font-size: 11pt;"></span></font></li><li style="font-size: 11pt;">IETF report<span style="font-size: 11pt;"></span></li><li style="font-size: 11pt;">Aufdit data reprot<span style="font-size: 11pt;"></span></li><li style="font-size: 11pt;">Dashboard ( root zone changes report)
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li style="font-size: 11pt;">
<p align="LEFT"><span style="font-size: 11pt;">Point 3.2 (SSAC 069 report). In the course of regular business of IANA need correct licenses to conduct work. </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Pro-active</span></p>
<p align="LEFT"><span style="font-size: 11pt;">certification, implies third party, understand</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Sarah: Government related issues, and should be treated as such</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Defer issue certifiction to DT OFAc licensing etc</span></p>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li style="font-size: 11pt;">
<p align="LEFT"><span style="font-size: 11pt;">CSC discussion</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Sentences on cusotmers in Composition section and internal method of working</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Sentences, on SLE/SLA are referred in table. Role of CSC is to monitor SLE/SLA. </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Include Placeholder langauge. </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Martin: CSC could organise discussion. Primary role to get information out of IANA, and making it available to wider community if reviewing at SLE/SLA, initiate dicussion.</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Sarah: SLE are set, and then somebody needs to check against these criteria.</span></p>
<p align="LEFT"><span style="font-size: 11pt;">For monitoring CSC members look at their members</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Often forgotten communicating with broader community</span></p>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li style="font-size: 11pt;">
<p align="LEFT"><br>
</p>
<p align="LEFT"><span style="font-size: 11pt;">Kim: Does group have a sense of scope what falls under Naming function?</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Not just root zone</span></p>
<p align="LEFT"><span style="font-size: 11pt;">also includes: .INT and .ARPA</span></p>
<p align="LEFT"><span style="font-size: 11pt;">And auxilliary functions, IDN Table repository</span></p>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li style="font-size: 11pt;">
<p align="LEFT"><span style="font-size: 11pt;">Question: If CSC does not take these on, who will?</span></p>
<p align="LEFT"><span style="font-size: 11pt;">In curren tversion 2.1 of proposal .INT and IDN Table are included. David Conrad reading through document</span></p>
<p align="LEFT"><span style="font-size: 11pt;">.ARPA addressed in IETF proposal</span></p>
<p align="LEFT"><span style="font-size: 11pt;">.INT and IDN-> Specific DT s</span></p>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top></top></span></li><li style="font-size: 11pt;">
<p align="LEFT"><span style="font-size: 11pt;">Kurt: CSC would be vehicle for changing SLA</span></p>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top>
<p align="LEFT"><b style="font-size: 11pt;">CSC on review</b></p>
</top></span><span id="OLK_SRC_BODY_SECTION"><top>
<p align="LEFT"><span style="font-size: 11pt;">Stephanie, there is another DT for this</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Should be role for the CSC, ensure it does not fall in the cracks</span></p>
<p align="LEFT"><span style="font-size: 11pt;"> </span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>CSC and appeals mechanism</b></span></p>
<p align="LEFT"><span style="font-size: 11pt;">Strike section, part of letter'</span></p>
</top></span>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top>
<p align="LEFT"><span style="font-size: 11pt;"><b>Breach of IFO functions</b></span></p>
<p align="LEFT"><span style="font-size: 11pt;">Map against Kurt did.</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Donna: porposed text questions some of the text . Do GAP analysis between the two.</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Note also DT M (escalation), and need to coordinate</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Kurt: suggest to look at Donna's document</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Escalation process is complex to design, and implement</span></p>
<p align="LEFT"><span style="font-size: 11pt;">REal escalation process needs to be improved over time</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Include Placeholder Breach by IFO </span></p>
</top></span>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top>
<p align="LEFT"><span style="font-size: 11pt;"><b>Overview of Consensus elements</b></span></p>
<p align="LEFT"><span style="font-size: 11pt;">Donna present document</span></p>
<p align="LEFT"><span style="font-size: 11pt;">What are key-points what CSC would do. </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Includes mapping to sections of template DT C ( section A-J)</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Includes and builds on Sarah's table</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Area not covered C (Stepanie) and D (Martin)</span></p>
<p align="LEFT"><span style="font-size: 11pt;"> </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Template Marika does not provide structure to tell story</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Stephanie: Add specific Placeholders section, to show waiting for further input</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Use Kurt's org chart</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Staffan: Good way to present in Istanbul </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Area's it may be challenged. Escalation</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Martin: Possible they might be challenged. </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Is current table, key of what we are doing. Current escalation process, is internal in CSC, </span></p>
<p align="LEFT"><span style="font-size: 11pt;">External Escalation is once issue for other DT </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Kurt: Suggest to use overview as starting point for deliverable. Get sense of group core is right</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Donna: work through document to seek agreement, </span></p>
</top></span>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section A</b>: Agreement</span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section B</b>: Include monitoring the IANA and ensuring (agreed)</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Also suggested Oversight of the performance </span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section C</b>: Restucture to reflect: Engage in cooperative communication ir order to ...</span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section D</b>: Agreed</span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section E</b>: change to IANA Naming Function, possibly broader then direct customer </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Kim: more often then annual. </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Issue: intermediating between IETF and community on implementation</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Emeging technologies and services and periodc reveiws as separate point </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Monthly meetings to include emeging technologies</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Annual meeting, is getting people together, and consider </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Agreement to split in two bullits</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Suggested txt: </span></p>
<p align="LEFT"><span style="font-size: 11pt;">The CSC will engage with IANA, the direct customers of the IANA naming function, and the ICANN community to discuss emerging technologies and issues that might impact the provision of IANA services. • (E2-> F) The CSC shall hold an annual meeting with the IANA Functions Operator, the direct customers of the IANA Naming Functions, and the ICANN community to discuss the performance of the IANA Naming functions and any changes to the services that are underway or forthcoming. </span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section F</b>: rather call it operation/addressing problems, </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Identify that CSC may get involved b=in between meetings, second four stage process ( STRAWMAN), it is multi-stage escalation process is recomemdend,</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Needst oevolve over time (evolutionar approach)</span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section G</b>: The CSC could be intital point of context (not escalation)</span></p>
<p align="LEFT"><span style="font-size: 11pt;">The reality of process today: current escalation is not always need, </span></p>
<p align="LEFT"><span style="font-size: 11pt;">What is expectation if IANA has tried to address issue. Medition point</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Theres has to be some criteria/ parameters around complaints. Mindful if complaint was already </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Remove initial, </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Strike last sentence (The CSC .... and its processes)</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Include referenceto ccNSO/GNSO when relevant</span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section H</b>: </span></p>
<p align="LEFT"><font face="Arial">Different</font><font face="Arial" size="3"> numbers in different proposals</font></p>
<p align="LEFT"><span style="font-size: 11pt;">Why is SSAC member?</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Proposal is minimum compostion</span></p>
<p align="LEFT"><span style="font-size: 11pt;">In other document reference to direct customers</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Include mimimal compostion</span></p>
<p align="LEFT"><span style="font-size: 11pt;">However keep as small as possible</span></p>
<p align="LEFT"><span style="font-size: 11pt;">- Registry operator are full of technical/operator capable people, SSAC could be asked as for advise</span></p>
<p align="LEFT"><span style="font-size: 11pt;">- Go forward with lean configuration</span></p>
<p align="LEFT"><span style="font-size: 11pt;">- CSC corespond with larger groups </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Makes sense to have communication with SSAC (liaison role) useful, in particular when isse beyond one group purview </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Alternative approach look at principles </span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section I</b>: </span></p>
<p align="LEFT"><span style="font-size: 11pt;">Be clear what purpose of addtional memebr sand liaisons are: and notleave it it up to CSC to appoint.</span></p>
<p align="LEFT"><span style="font-size: 11pt;">At same time addtional people may be useful</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Reference in Underlyimng documetn to liaisosn as "temporary". Note in other context permanent</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Attach liaisons to CSC from GAC, ALAC, non-contracted part GNSO</span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Section J</b>: Include marker, refer to mechanisms identified in CCWG Accountability</span></p>
<p align="LEFT"><span style="font-size: 11pt;">Stepahnie suggest additional bullet: The CSC shall facilitate public comment periods and other community participation opportunities in the event that changes are proposed that would affect oversight of the IANA Naming Functions. </span></p>
<p align="LEFT"><span style="font-size: 11pt;"> Agreed</span></p>
</top></span>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION"><top>
<p align="LEFT"><span style="font-size: 11pt;">Google doc, background for DT C, proceeed working on overview document </span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Action Stephanie: capture discussion in next version overview document, and circulate for discussion</b></span></p>
<p align="LEFT"><span style="font-size: 11pt;"><b>Action staff: Send out Dodole for Monday afternoon ( at latets closure 1 before close of the call)</b></span></p>
<p align="LEFT"><span style="font-size: 11pt;"> </span></p>
<p align="LEFT"><span style="font-size: 11pt;"> </span></p>
</top></span></li></ol>
</span></top></span></div>
<div><br>
</div>
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</body>
</html>