<HTML><BODY><p style='margin-top: 0px;' dir="ltr">I don't disagre.... we go too fast</p>
<p dir="ltr">--<br>
Sent from myMail app for Android</p>
Saturday, 21 November 2015, 09:43PM -05:00 from Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>>:<br><br><blockquote style='border-left:1px solid #FC2C38; margin:0px 0px 0px 10px; padding:0px 0px 0px 10px;' cite="14481608090000085532">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div >
<base target="_self" href="https://e-aj.my.com/" />
<div id="style_14481608090000085532_BODY">
And I continue to be very troubled that in haste, we may put into words,
Bylaws that ultimately prevent ICANN from doing its legitimate
business.<br><br>
Alan<br><br>
At 21/11/2015 10:35 AM, Paul Rosenzweig wrote:<br><br>
<blockquote type="cite" cite="">I agree with Malcolm. I
continue to be very troubled that we cannot put into words this very
fundamental concept. All agree there are some limited circumstances
when ICANN can and should be allowed to impose restrictions on activity
through contract. All agree that there are many other
circumstances in which that sort of action by ICANN would be
illegitimate. The Board's proposal seems to leave the question open
to later interpretation and for that reason I don't favor it -- but I
also think it is imperative that some definitional language be hammered
out .... without it the entire premise of IRP review and a limited ICANN
mission founders.<br><br>
Paul<br><br>
--<br>
Sent from myMail app for Android<br>
Friday, 20 November 2015, 07:52PM -05:00 from Malcolm Hutty
<<a href="//e-aj.my.com/compose/?mailto=mailto%3amalcolm@linx.net" target="_blank" >malcolm@linx.net</a>>:<br><br>
<br><br>
On 20 Nov 2015, at 21:39, Andrew Sullivan
<<a href="https://e-aj.my.com//compose?To=ajs@anvilwalrusden.com" target="_blank" >
ajs@anvilwalrusden.com</a>> wrote:<br><br>
>> On Fri, Nov 20, 2015 at 03:54:09PM -0500, David Post
wrote:<br>
>> This is a good example - can ICANN shut down my domain as
part of its<br>
>> "collaboration with anti-abuse people"?<br>
> <br>
> Unless you&apos;re a TLD, ICANN can&apos;t shut down
your domain anyway (at<br>
> least not without taking a whole bunch of other people out), so
if<br>
> that&apos;s all we&apos;re talking about it&apos;s
not a problem.<br><br>
On the contrary, ICANN can and does cause Registries to shut down
some registrants&apos; domains (by requiring them to redelegate it to
another person without the initial registrants&apos; consent).
<br><br>
We are arguing about the scope of circumstances in which ICANN should
be permitted to do this. Constraining the range of circumstances is the
entire point of this clause. <br><br>
Malcolm. <br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="https://e-aj.my.com//compose?To=Accountability%2dCross%2dCommunity@icann.org" target="_blank" >
Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl" target="_blank" >
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="/compose?To=Accountability%2dCross%2dCommunity@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl" target="_blank" >
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</blockquote>
</div>
<base target="_self" href="https://e-aj.my.com/" />
</div>
</div>
</blockquote></BODY></HTML>