<html>
<body>
That is your explanation, not mine...<br><br>
At 21/11/2015 09:57 PM, Paul Rosenzweig wrote:<br><br>
<blockquote type=cite class=cite cite="">I don't disagre.... we go
too fast<br><br>
--<br>
Sent from myMail app for Android<br>
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>
<dl>
<dd>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>
<dd>Alan<br>
<dd>At 21/11/2015 10:35 AM, Paul Rosenzweig wrote:<br><br>
<blockquote type=cite class=cite cite="">
<dd>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>
<dd>Paul<br>
<dd>--
<dd>Sent from myMail app for Android
<dd>Friday, 20 November 2015, 07:52PM -05:00 from Malcolm Hutty
<<a href="https://e-aj.my.com///e-aj.my.com/compose/?mailto=mailto%3amalcolm@linx.net">
malcolm@linx.net</a>>:<br>
<br>
<br>
<dd>On 20 Nov 2015, at 21:39, Andrew Sullivan
<<a href="https://e-aj.my.com//compose?To=ajs@anvilwalrusden.com">
ajs@anvilwalrusden.com</a>> wrote:<br>
<dd>>> On Fri, Nov 20, 2015 at 03:54:09PM -0500, David Post wrote:
<dd>>> This is a good example - can ICANN shut down my domain as
part of its
<dd>>> "collaboration with anti-abuse people"?
<dd>>
<dd>> Unless you&apos;re a TLD, ICANN can&apos;t shut down
your domain anyway (at
<dd>> least not without taking a whole bunch of other people out), so
if
<dd>> that&apos;s all we&apos;re talking about it&apos;s
not a problem.<br>
<dd>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>
<dd>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>
<dd>Malcolm.
<dd>_______________________________________________
<dd>Accountability-Cross-Community mailing list
<dd>
<a href="https://e-aj.my.com//compose?To=Accountability%2dCross%2dCommunity@icann.org">
Accountability-Cross-Community@icann.org</a>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br>
<dd>_______________________________________________
<dd>Accountability-Cross-Community mailing list
<dd>
<a href="https://e-aj.my.com//compose?To=Accountability%2dCross%2dCommunity@icann.org">
Accountability-Cross-Community@icann.org</a>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</dl></blockquote></blockquote></body>
</html>