<div dir="ltr"><div>Becky</div><div>Thank you for reply</div><div>But the qualifiers are subject to whose judgement? ICANN? OR the Community.</div><div>If these two composed qualifier are an option for ICANN to decide how reasonably appropriate achieve the mission's objhectives, If they do not avcheive those objectives reasonably appropriate they could claim that it was neither reasonable nor appropriate to do so.</div><div>Whether the text was or was not subject to public comments , I do not care. It is wrong at this stage</div><div>You put the acheivement of the mission subject to judgement of ICANN as being reasonably appropriate to acheive or not.</div><div>Please read the text carefully or consult other lawyers </div><div>Kavouss </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-11-03 21:56 GMT+01:00 Burr, Becky <span dir="ltr"><<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="-ms-word-wrap: break-word;">
<div>
<div>
<div><font face="Calibri,sans-serif">Confused Martin – none of the language re names has changed for months Martin, other than changing "</font><font face="Avenir Book" size="3">Domain names (forming a system referred to as "DNS</font><font face="Avenir Book"><span style="font-size:15px">”</span></font><font face="Avenir Book" size="3">)”
to "names in the root zone of the Domain Name System (</font><font face="Avenir Book"><span style="font-size:15px">“</span></font><font face="Avenir Book" size="3">DNS”). Otherwise the language remains exactly the same.</font> <br>
<span style="font-family:"Avenir Book";font-size:11pt"> </span></div><span>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div>J. Beckwith Burr</div>
<div>Deputy General Counsel & Chief Privacy Officer</div>
<div><br>
</div>
</div>
</span></div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<span style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in;text-align:left;color:black;font-family:Calibri;font-size:11pt">
<span style="font-weight:bold">From: </span>Martin Boyle <<a href="mailto:Martin.Boyle@nominet.uk" target="_blank">Martin.Boyle@nominet.uk</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, November 3, 2015 at 12:35 PM<br>
<span style="font-weight:bold">To: </span>Becky Burr <<a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a>>, Accountability Community <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>>, Andrew
Sullivan <<a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a>>, "<a href="mailto:iab@iab.org" target="_blank">iab@iab.org</a>" <<a href="mailto:iab@iab.org" target="_blank">iab@iab.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: WP2 Issues from last night's call<br>
</div><div><div class="h5">
<div><br>
</div>
<div>
<div lang="EN-GB" vlink="purple" link="blue">
<div>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt">Becky, all,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt">I’m sorry, but I have some concerns with the text as it has evolved for (new 1) the names part of the mission statement. Not having been on today’s
call, this might have been covered. However, the new wording does seem to me to extend the role of ICANN for ccTLDs.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt">For ccTLDs the ICANN policy role is limited to root-zone issues and those that can be directly linked to security, stability and resilience of the
DNS. The new wording appears to me to broaden the coverage.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt">First bullet: “reasonably necessary to facilitate openness, interoperability [and/or] security…”: I’m not sure I know what reasonably necessary
means, but in association with the qualities, it could easily be interpreted as harmonising on specific requirements. Could we think of some wording that limits the potential for mission creep? How about, “For which coordinated resolution is appropriate
and necessary to facilitate resilience, security and/or stability.”?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt">Second bullet: I have significant concerns about the word “designed.” Could we replace the bullet with, “That are developed through a bottom-up,
consensus-based multi-stakeholder process and that are necessary to ensure the stable and secure operation of the Internet’s unique names system.”?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt">Martin<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Verdana,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-family:Tahoma,sans-serif;font-size:10pt">From:</span></b><span lang="EN-US" style="font-family:Tahoma,sans-serif;font-size:10pt">
<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a> [<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">mailto:accountability-cross-community-bounces@icann.org</a>]
<b>On Behalf Of </b>Burr, Becky<br>
<b>Sent:</b> 03 November 2015 15:14<br>
<b>To:</b> Accountability Community; Andrew Sullivan; <a href="mailto:iab@iab.org" target="_blank">
iab@iab.org</a><br>
<b>Subject:</b> [CCWG-ACCT] WP2 Issues from last night's call<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">I’ve attached a revised deck trying to lay out our conclusions from last night.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">1. We concluded to resolve the support/coordinate problem by eliminating the chapeau in the Mission Statement. See Slide 1 and the side-by-side document<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">2. Kavouss strongly urged us to modify the language of the regulatory preclusion. I have taken a shot at that in purple in the side-by-side document<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">3. Greg Shatan proposed a modification to the contracting language also reflected in purple on slide 2<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">4. We agreed to put transparency points 1 and 2 in WS1 and to address points 3 and 4 as part of WS2.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">Becky<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt"><u></u> <u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">J. Beckwith Burr<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt">Deputy General Counsel & Chief Privacy Officer<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black;font-family:Calibri,sans-serif;font-size:10.5pt"><u></u> <u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div></div></span>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>