<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I agree with Greg. This is a clarification in the text that does not change the report in any way.<div class=""><br class=""></div><div class="">Thanks,</div><div class="">Robin</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 26, 2016, at 10:22 AM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" class="">gregshatanipc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:verdana,sans-serif">I've replied to this point on the original thread. In short, my proposal does not change the report. If anything, the current proposed bylaws text changes the report by implying that a higher level of approval for the FOI was intended, when that was not the intent of the group or the proposal.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Apr 26, 2016 at 12:10 PM, Seun Ojedeji <span dir="ltr" class=""><<a href="mailto:seun.ojedeji@gmail.com" target="_blank" class="">seun.ojedeji@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr" class="">Hi Andrew,</p><p dir="ltr" class="">Hopefully part of my message is not quoted to imply I support changing the report(it's rather to raise the obvious implication of opening up an already submitted report). However, just to remove any doubt, It's a +1 from me on what you have said as well.</p><p dir="ltr" class="">Cheers!</p><p dir="ltr" class="">Sent from my LG G4<br class="">
Kindly excuse brevity and typos</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On 26 Apr 2016 14:35, "Andrew Sullivan" <<a href="mailto:ajs@anvilwalrusden.com" target="_blank" class="">ajs@anvilwalrusden.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Apr 26, 2016 at 12:29:30PM +0100, Seun Ojedeji wrote:<br class="">
> if there is consensus (based on CCWG charter) to change the report that was<br class="">
> already submitted in the manner proposed then i am fine with it as well.<br class="">
<br class="">
I am under the impression that, regardless of its consensus,<br class="">
CCWG-Accountability can't change the report. The report's been<br class="">
shipped off. It's the report that people are evaluating, not the<br class="">
state of CCWG consensus at any given time.<br class="">
<br class="">
This is why I have expressed, in some cases strongly, rather serious<br class="">
reservations about the way "implementation" has proceeded such that<br class="">
some things the CCWG said may be being adjusted. Most serious, in my<br class="">
opinion, is the continued inclusion of 1.1(d) in the draft bylaws.<br class="">
1.1(d)(ii) includes references to documents that aren't written and<br class="">
can't possibly be evaluated. It even includes a reference to an<br class="">
agreement between ICANN and an entity that does not yet exist and that<br class="">
might not be named as it is named in these draft bylaws. The idea<br class="">
that one can evaluate such a bylaw is, quite frankly, stupefying. Yet<br class="">
the inclusion of this provision means that the to-be-written contract<br class="">
(or under (F) any renewal thereof) can include any provision at all,<br class="">
and it won't be subject to challenge.<br class="">
<br class="">
The CCWG can't change its report now, and it must ensure that the<br class="">
bylaws actually conform with the report as it is written. If this<br class="">
creates facts that people are unhappy with, well, that's what<br class="">
amendment procedures are for. We'll get to see whether the Empowered<br class="">
Community actually can work as a community.<br class="">
<br class="">
Best regards,<br class="">
<br class="">
A<br class="">
<br class="">
--<br class="">
Andrew Sullivan<br class="">
<a href="mailto:ajs@anvilwalrusden.com" target="_blank" class="">ajs@anvilwalrusden.com</a><br class="">
_______________________________________________<br class="">
Accountability-Cross-Community mailing list<br class="">
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank" class="">Accountability-Cross-Community@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br class="">
</blockquote></div>
</div></div><br class="">_______________________________________________<br class="">
Accountability-Cross-Community mailing list<br class="">
<a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br class="">
<br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">Accountability-Cross-Community mailing list<br class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community<br class=""></div></blockquote></div><br class=""></div></body></html>