<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I agree that the current draft language on this point appears too narrow. However, Malcolm's proposed language is overbroad and goes beyond what was agreed to. I can understand the desire of the drafters to avoid using the term "regulate," since ICANN is not a regulatory body and is thus incapable of regulating as such. The trick is capturing the conceptual essence of the term without using it, and without substituting terms of substantially broader or narrower effect. The essence of regulation is prescribing or imposing rules and/or requirements. As such, I find Bradley's suggested language to fall much closer to carrying out the intent of the CCWG Report, and I support that language as well:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><font face="arial, helvetica, sans-serif" color="#0000ff"><span style="font-size:12.8px">ICANN shall not impose terms and conditions on services that use the Internet’s unique identifiers or the content that such services carry or provide.</span><br></font></div><div class="gmail_default"><font face="arial, helvetica, sans-serif" color="#0000ff"><span style="font-size:12.8px"><br></span></font></div><div class="gmail_default"><font color="#000000" face="verdana, sans-serif"><span style="font-size:12.8px">I do not support the new note to the drafters that Malcolm has proposed as a "request." I don't think this objectively frames the issue, and I don't think it is necessary to include a pontificatory paragraph with our suggested language. I suggest we scuttle this, rather than taking the time to negotiate an acceptable version. All we need to say is that we believe the draft bylaws didn't adequately capture this particular point and we propose the language above as a replacement.</span></font></div><div class="gmail_default"><font color="#000000" face="verdana, sans-serif"><span style="font-size:12.8px"><br></span></font></div><div class="gmail_default"><font color="#000000" face="verdana, sans-serif"><span style="font-size:12.8px">Greg</span></font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"> <u></u></span></font></p><div style="font-size:12.8px"><table border="0" cellspacing="0" cellpadding="0" width="800" style="width:600pt"><tbody><tr><td width="100" valign="top" style="width:75pt;padding:0in"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"><img width="100" height="43" src="cid:image001.jpg@01D1842F.8BD05270" alt="http://hilweb1/images/signature.jpg"></span></font><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u><u></u></span></font></p></td><td width="8" style="width:6pt;padding:0in"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"> <u></u><u></u></span></font></p></td><td style="padding:0in"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><font size="1" color="#002e62" face="Arial"><span style="font-size:8.5pt;font-family:Arial,sans-serif">Gregory S. Shatan | Partner<br></span></font></b><font size="1" color="black" face="Arial"><span style="font-size:7.5pt;font-family:Arial,sans-serif">McCARTER & ENGLISH, LLP<br><br>245 Park Avenue, 27th Floor | New York, New York 10167<br>T: <a href="tel:212-609-6873" value="+12126096873" style="color:rgb(17,85,204)" target="_blank">212-609-6873</a><br>F: <a href="tel:212-416-7613" value="+12124167613" style="color:rgb(17,85,204)" target="_blank">212-416-7613</a><br><a href="mailto:gshatan%20@mccarter.com" style="color:rgb(17,85,204)" target="_blank"><font color="#225599">gshatan @mccarter.com</font></a> | <a href="http://www.mccarter.com/" style="color:rgb(17,85,204)" target="_blank"><font color="#225599">www.mccarter.com</font></a> <br><br></span></font><font size="1" color="#777777" face="Arial"><span style="font-size:7pt;font-family:Arial,sans-serif">BOSTON | HARTFORD | STAMFORD | NEW YORK | NEWARK <br>EAST BRUNSWICK | PHILADELPHIA | WILMINGTON | WASHINGTON, DC</span></font><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u><u></u></span></font></p></td></tr></tbody></table></div><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="2" face="Calibri"><span style="font-size:11pt"><u></u> </span></font></p></div></div></div></div></div>
<br><div class="gmail_quote">On Sat, Apr 9, 2016 at 3:47 PM, Marilyn Cade <span dir="ltr"><<a href="mailto:marilynscade@hotmail.com" target="_blank">marilynscade@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">I am not sure that this discussion even belongs in the CCWG ACCT.<div><br></div><div>Can we perhaps move it to a later discussion? </div><div>M<br><br><div>> To: <a href="mailto:lists@christopherwilkinson.eu" target="_blank">lists@christopherwilkinson.eu</a><br>> From: <a href="mailto:malcolm@linx.net" target="_blank">malcolm@linx.net</a><br>> Date: Fri, 8 Apr 2016 23:00:19 +0100<br>> CC: <a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a><br>> Subject: Re: [CCWG-ACCT] Implementation flaw in Mission section<div><div class="h5"><br>> <br>> <br>> <br>> On 08/04/2016 21:09, Christopher Wilkinson wrote:<br>> > Dear Malcolm:<br>> > <br>> > This, as I think you know, goes too far and is politically unsustainable.<br>> > <br>> > Who, then is to regulate offending or illegal content or services in TLDs with global scope?<br>> > Who, then is to enforce commitments reached prior to delegation of the domain?<br>> <br>> Dear Christopher,<br>> <br>> I think you know that this is properly a matter for governments, acting<br>> within their own jurisdiction according to national sovereignty, and<br>> that ICANN has no legitimacy to some supervening global authority in the<br>> regulation of Internet content or the businesses that use the Internet.<br>> <br>> Kind Regards,<br>> <br>> Malcolm.<br>> -- <br>> Malcolm Hutty | tel: <a href="tel:%2B44%2020%207645%203523" value="+442076453523" target="_blank">+44 20 7645 3523</a><br>> Head of Public Affairs | Read the LINX Public Affairs blog<br>> London Internet Exchange | <a href="http://publicaffairs.linx.net/" target="_blank">http://publicaffairs.linx.net/</a><br>> <br>> London Internet Exchange Ltd<br>> Monument Place, 24 Monument Street, London EC3R 8AJ<br>> <br>> Company Registered in England No. 3137929<br>> Trinity Court, Trinity Street, Peterborough PE1 1DA<br>> <br>> <br>> _______________________________________________<br>> Accountability-Cross-Community mailing list<br>> <a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br></div></div></div></div> </div></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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>