<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<title>BC comment on CCWG-Accountability 2nd Proposal [v5.1]</title>
<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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">My responses to Becky’s questions:<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt;text-indent:.5in">1. Do you agree or disagree with the following statement: "To the extent<br>
that registry operators voluntarily assume obligations with respect to<br>
registry operations as part of the application process, ICANN should have<br>
the authority to enforce those commitments.”<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#44546A">DISAGREE. Not if enforcing those commitments takes ICANN out of its own mission.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;text-indent:.5in">2. Do you agree or disagree with the following statement: "ICANN shall not<br>
regulate services that use the Internet's unique identifiers, or the<br>
content that such services carry or provide.” - Wherever you land, please<br>
explain what you mean by “regulate” and “services."<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> AGREE.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">By “regulate” I mean impose legally binding commitments and conditions on the service not related to the domain registration itself,
but moving beyond the registration to include the content, activities or prices of the services that happening to be using the domain. Services means online offerings, either commercial or noncommercial, through which one party provides something that another
party wants. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">In response to Steve Metalitz’s comment here:
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;text-indent:.5in">One point that those in this discussion who are relatively new to ICANN may not fully appreciate is the extent to which all the terms of contracts between ICANN and gTLD registries and accredited
registrars are subjected to public comment and robust debate before they are executed.<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I would say that the existence of public comment on proposed policies is good, but there is nothing (except the mission statement
and IRP) that prevents ICANN from ignoring them. In effect, Steve is saying that ICANN should have no limitations on its mission because the public can comment on such deviations. This just doesn’t work.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">There will be pressure on ICANN to stray from its mission and the limits imposed on it, just as any national government ends up with
laws that are unconstitutional. The fact that one group or coalition of groups succeeds in getting something imposed on us via a contract does not necessarily mean it should stand. We have to have a clear and firm mission limitation.<o:p></o:p></span></p>
</div>
</div>
</body>
</html>