<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:276106474;
mso-list-type:hybrid;
mso-list-template-ids:689738104 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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=MsoPlainText>Malcolm, all:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I noticed this discrepancy too. By singling out the RA and RAA I agree that the drafting goes beyond what the instructions intended. While I also understand the lawyerly inclination to avoid “regulate”, I do not agree that your suggestion of “constrain” is a suitable alternative – that seems much weaker, and I think the lawyers got it right by using the word “impose terms and conditions”. After all, that’s what regulators do, and it encapsulates the concept of constraint. Rather:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I agree that this is a discrepancy which should be addressed. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Bradley<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] On Behalf Of Malcolm Hutty<br>Sent: Friday, April 08, 2016 7:29 AM<br>To: Accountability Cross Community<br>Subject: [CCWG-ACCT] Implementation flaw in Mission section</p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I have found a discrepancy between CCWG Final Report and the implementation of the draft Bylaws in the Mission section.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The Report approved by the Chartering Organisations says:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>"* Clarify that ICANN’s Mission does not include the regulation of services that use the Domain Name System or the regulation of the content these services carry or provide." (paragraph 134)<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The Draft Bylaws implements this as follows:<o:p></o:p></p><p class=MsoPlainText>"* ICANN shall not use its contracts with registries and registrars to impose terms and conditions that exceed the scope of ICANN’s Mission on services that use the Internet’s unique identifiers or the content that such services carry or provide." (Article I Section 1.1 (c))<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Firstly, this draft bylaw would pick on only one means by which ICANN might seek to regulate content (through the RA or RAA contracts), and prohibits that. There is no such limitation in the CCWG Report: our Report prohibits any attempt to regulate content by ICANN, whether through the RA/RAA contracts or by any other means.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Certainly, the RA/RAA contract is the most likely means by which ICANN might seek to regulate content and services. However, if ICANN manages to come up with some other means (including means that cannot now be<o:p></o:p></p><p class=MsoPlainText>imagined) then a full implementation of the CCWG Report would cover that too.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>This is a clear and objective discrepancy.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Secondly, the CCWG Report expresses this limitation as an exclusion from the Mission. That was quite deliberate, and significant. We never expressed this section as a bare prohibition on some action, it was always considered to be essential that it was a Mission limitation.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>This aspect of the Report's proposal is not reflected in the draft bylaw at all. That is also clear discrepancy.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The significance of this is that a Mission limitation has a broader scope. Excluding regulation of content from the Mission means any action aimed at regulating content can be challenged, including actions that (if done for some legitimate purpose) would be entirely OK. By contrast, a Bylaw that merely prohibits a certain class of action is weaker, because it says it's OK for ICANN to regulate content if it can find some way of doing so within its permitted powers. That's simply not consistent with the Report approved by the Chartering Organisations.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Finally, in the future there may arise some disagreement as to whether a specific activity constitutes "regulation", in particular in marginal cases. Before we adopted the Report, our lawyers advised us not to seek to tightly define this in every particular, but to allow precedent to develop as cases arise. We accepted that advice. The implementation team should therefore avoid seeking to resolve that deliberate ambiguity in favour of the narrowest possible definition of regulation: again, that's not consistent with the Report.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I therefore propose we transmit the following request to the implementation team.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>"Article I Section 1.1(c) implements paragraph 134 of the CCWG Report (prohibition of regulation of content) as a prohibition use of its contracts with registries and registrars to regulate content. This does not fully implement our Report. Please ensure that ICANN is prohibited from regulating content through any mechanism, not only through registry and registrar contracts. Furthermore, please exclude express this as an exclusion from the Mission, not merely a bare prohibition on certain actions, so that activities that would otherwise be permitted to ICANN can be challenged if they are designed to achieve this prohibited purpose."<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I hesitate to offer alternative wording: the lawyers may wish to come up with their own, and we should let them. But I will offer these observations and a brief suggestion.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>1. I understand that the lawyers wished to avoid use of the word regulation. Fine.<o:p></o:p></p><p class=MsoPlainText>2. When moving away from the word regulation, they also moved away from describing a class of activity (regulation) to a specific action (using X contract in Y way). I think this is where they went wrong. This in itself limits the scope of the restriction.<o:p></o:p></p><p class=MsoPlainText>3. Sticking as closely as possible to the text of the Report that Chartering Organisations have approved would seem advisable. So if they want to avoid the word regulation, look for some synonym.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thus compare our Report:<o:p></o:p></p><p class=MsoPlainText>"Clarify that ICANN’s Mission does not include the regulation of services that use the Domain Name System or the regulation of the content these services carry or provide."<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>with the implementation team's draft bylaw<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>"ICANN shall not use its contracts with registries and registrars to impose terms and conditions that exceed the scope of ICANN’s Mission on services that use the Internet’s unique identifiers or the content that such services carry or provide."<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>and my alternative suggestion for this Bylaw<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>"ICANN's Mission does not include seeking to constrain or impose requirements upon the services the use the Domain Name System, nor seeking to constrain the content that those services carry or provide".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>That would follow the Report as closely as possible, preserve the restriction as a limit on ICANN's Mission as intended, and still achieve the lawyers' goal of avoiding the word "regulate".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Kind Regards,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Malcolm.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-- <o:p></o:p></p><p class=MsoPlainText> Malcolm Hutty | tel: +44 20 7645 3523<o:p></o:p></p><p class=MsoPlainText> Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | <a href="http://publicaffairs.linx.net/"><span style='color:windowtext;text-decoration:none'>http://publicaffairs.linx.net/</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText> London Internet Exchange Ltd<o:p></o:p></p><p class=MsoPlainText> Monument Place, 24 Monument Street, London EC3R 8AJ<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText> Company Registered in England No. 3137929<o:p></o:p></p><p class=MsoPlainText> Trinity Court, Trinity Street, Peterborough PE1 1DA<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>Accountability-Cross-Community mailing list <a href="mailto:Accountability-Cross-Community@icann.org"><span style='color:windowtext;text-decoration:none'>Accountability-Cross-Community@icann.org</span></a><o:p></o:p></p><p class=MsoPlainText><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"><span style='color:windowtext;text-decoration:none'>https://mm.icann.org/mailman/listinfo/accountability-cross-community</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>=================================================================<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> Reminder: Any email that requests your login credentials or that asks you to click on a link could be a phishing attack. If you have any questions regarding the authenticity of this email or its sender, please contact the IT Service Desk at 212.484.6000 or via email at <a href="mailto:ITServices@timewarner.com"><span style='color:windowtext;text-decoration:none'>ITServices@timewarner.com</span></a> <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>=================================================================<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p></div>
<P>=================================================================<br/>This message is the property of Time Warner Inc. and is intended only for the use of the<br/>addressee(s) and may be legally privileged and/or confidential. If the reader of this message<br/>is not the intended recipient, or the employee or agent responsible to deliver it to the intended<br/>recipient, he or she is hereby notified that any dissemination, distribution, printing, forwarding,<br/>or any method of copying of this information, and/or the taking of any action in reliance on<br/>the information herein is strictly prohibited except by the intended recipient or those to whom<br/>he or she intentionally distributes this message. If you have received this communication in<br/>error, please immediately notify the sender, and delete the original message and any copies<br/>from your computer or storage system. Thank you.<br/>=================================================================<br/>
</P></body></html>