<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.E-postmall18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-postmall19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:185409211;
mso-list-type:hybrid;
mso-list-template-ids:-595846782 134807567 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=SV link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>List<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>My respons to DT M minutes ago echo some points made in Martins proposal:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>“CWG agree that all these deliberations should be transparent. This is especially important since ccNSO might establish mechanisms to consider complaints also from non-members of ccNSO.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>Escalation through ccNSO and gNSO is just one possible track of complaints, accompanied by several parallel tracks and accountability measures from CCWG. There need not be rivalry between different escalation tracks. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>Parallel escalation tracks also relate to different sets of issues on IANA functions operations. Using current structures and institutions (ccNSO and gNSO) is merely one track. Operating within established institutions has the potential to become a cost-effective way of operating 99% of rather uncontroversial complaints towards IANA operations. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>It is true that ccNSO and gNSO are policy bodies. However, in current situation and proposal, several non-member ccTLD:s already put their trust in ccNSO being able to take all of naming communities interests into the framework.”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>I Agree in Martins proposed answers. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'>Staffan <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b>Från:</b> dt3-bounces@icann.org [mailto:dt3-bounces@icann.org] <b>För </b>Martin Boyle<br><b>Skickat:</b> den 31 maj 2015 19:06<br><b>Till:</b> dt3@icann.org<br><b>Ämne:</b> [DTC CSC] Public Comments 228 & 231<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>ALAC comments (and comments from the IPC):<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span lang=EN-GB><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-GB>Deliberations and output of the CSC will be completely transparent. Any exclusions must be explicitly documented: I’m generally ok with this, but we should note that by its nature, some detail will need to be withheld (for example on security issues or on malicious and repeated ccTLD redelegation requests.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span lang=EN-GB><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span lang=EN-GB>We have discussed escalation at length. We all recognise that escalation via the ccNSO & GNSO RySG will have problems associated with it. However, approval for action does need to be given – we cannot leave it to a small and unrepresentative group to make decisions for the registries – and the only escalation that the CSC can require is because of failure in delivery of the service. Hence the ccNSO and the RySG will simply be a gatekeeper – is this a problem of concern or is the CSC overreacting? The multi-stakeholder process is invoked because there is a concern. (This does not, I suppose, prevent other stakeholder groups calling for a special IFR or for raising their concerns with a periodic IFR.)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I would suggest that we respond along the lines of:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB>We agree with the comment that the CSC should work transparently. Indeed we believe that a key role of the CSC should be to engage with the wider community.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB>This is one of the reasons why we believe that the CSC should not have the unilateral power to invoke further action. As the first line mechanism, we believe that its main focus should be on ensuring remedial action, should deteriorating performance be identified.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB>However, we would note that there will be cases where complete transparency will not be appropriate and so the committee should have the discretion to maintain confidentiality in the rare cases where this is justified. Examples of this could include issues of security (where it may be necessary to limit CSC members’ access to such information) or where ccTLD redelegation requests are malicious action aimed at undermining confidence in the registry.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB>We recognise the issues associated with the proposed escalation path. We strongly believe that a small committee such as the CSC should not be empowered to launch an escalation process on its own decision – it is, after all, simply a customer committee representing the customer community in ensuring the delivery of the IANA functions service to registries. It seems reasonable that it should report back to the ccNSO and the RySG which would be able to assess from its membership whether the recommendation was appropriate.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB>We would note that (as this is the sole role of the CSC) the only grounds for a recommendation from the CSC for escalation are on the grounds of service failure of the operational performance. If the decision is made to pursue escalation, we agree that the process then needs to become multi-stakeholder.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB>ALAC identifies the CSC as being the equivalent of the MRT from the previous model: we do not believe that this is correct (the CSC was a separate entity in that model, too). The MRT role in the current model is that performed by the IFR and it would be via the IFR that wider issues (ie beyond the performance of the IANA functions operator) would be addressed.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I think an additional comment is needed for the IPC. This seems to think that “the CSC [should not be] run by and for the benefit of registries. For similar reasons, it is important that the work of the CSC be open and transparent. The IANA Function is a critical resource used by every person or thing that interacts with the Internet. As such, it is quintessentially a public resource, and its oversight should reflect that.” This again seems to be suggesting widening the CSC role into ground better covered by the IFR. Phrases like “There may be times when the needs of the “customers” are not aligned with the global public interest” strike me as bizarre. It needs a response so I suggest:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-GB>The CSC is solely about the performance of the function and we cannot imagine in this limited role where “the needs of the “customers” are not aligned with the global public interest.” We believe that the Customer Standard Committee role is of necessity limited and clearly defined to address performance issues <i>only</i>. It is essentially a technical function. Other issues are dealt with elsewhere in the proposed oversight model – in particular through the periodic and special IFR process. For this reason, we do not believe that it is appropriate for the CSC to be fully multi-stakeholder: this would risk the CSC losing its focus and duplicating or rivalling the work of more appropriate parts of the oversight model.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I’d welcome thoughts.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Martin<o:p></o:p></span></p></div></body></html>