<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Having responded one way regarding transparency issues, I'm going to respond another way. We should not be diverted by the thought of adding significant transparency changes to what we already have.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">We need to focus. There are worthy concerns that are not fully addressed in WS1, and that is unfortunate. But the core of our proposal is at risk. We need to bear down on filling in the gaps, resolving concerns from within and without, and generally tighten things up. Our work needs to be interpolation and renovation, not extrapolation. We should be open-minded as to processes that can advance these efforts.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Our proposal needs a significant upgrade in clarity and intelligibility. This has been a big and unwieldy beast; we all know that. Explane has been a great help in painting a picture at the highest level, but we can't put the Explane proposal forward; it's just a teaching aid. The full proposal may also be a form of reference; but, as the main thing that people need to comprehend, it leaves much to be desired. We need a readable, cogent, coherent, logical piece that tells the reader what our proposal is, with enough detail to avoid FUD-like responses, but without getting bogged down in the weeds. I hesitate to call it an "Executive Summary," because it should be able to stand on its own. We can have annexes for the deep dives and the methodology, etc. But the heart of the document needs to be right up front, and it needs to be compelling.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 30, 2015 at 6:59 PM, Edward Morris <span dir="ltr"><<a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><div>HI Alan,</div>
<div> </div>
<div>I've raised this issue intermittently throughout our work. In Istanbul, Steve DelBianco kindly called upon me to talk about the failings of the DIDP to highlight the problem. In Buenos Aires, I raised the issue again and Thomas suggested towards the end of the meeting that perhaps we could move some transparency reform to work stream 1. Nothing became of that.</div>
<div> </div>
<div>This is not something we want to do in a rushed manner. Although simplistic on the face, much of what we need to do here is quite technical, involves state specific statutes (privacy, for example) and needs to be done carefully with the community working closely with ICANN staff, even in areas we may have some differences, in order to achieve an optimal outcome. I was quite happy with the status quo reference model whereby the community would have access in extraordinary situations to the most important documentation fairly soon through WS! (inspection rights via membership) while the more comprehensive and structural reforms would be developed in WS2. Now that we're faced with apparently serious proposals to eliminate both WS 2 (Board proposal) and membership, consideration needs to be given to other ways to tackle transparency within the CCWG effort.</div>
<div> </div>
<div>I should let people know that I've been working with Farzaneh Badii and Sarah Clayton on an analysis of all DIDP requests and responses. We're looking not only at quantifying things like success rates and DCND (defined conditions of nondisclosure) rejection rates but are also attempting to evaluate whether concerns that have been expressed to me privately by multiple Board members (for example, improper use of the DIDP by litigants in legal actions against ICANN as a substitution for / replacement of permissible discovery) are valid. The project is well underway and we hope to be able to present the results to everyone prior to our Dublin meeting.</div>
<div> </div>
<div>Best,</div>
<div> </div>
<div>Ed Morris</div>
<div> </div>
<hr align="center" size="2" width="100%">
<div><span style="font-family:tahoma,arial,sans-serif;font-size:10pt"><b>From</b>: "Alan Greenberg" <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>><br>
<b>Sent</b>: Wednesday, September 30, 2015 8:55 PM<br>
<b>To</b>: "Robin Gross" <<a href="mailto:robin@ipjustice.org" target="_blank">robin@ipjustice.org</a>>, "Accountability Cross Community" <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><span class=""><br>
<b>Subject</b>: Re: [CCWG-ACCT] A way to avoid the 'The Single Member Can Do Anything!' problem</span></span>
<div> </div><div><div class="h5">
How is it that this was not on our original list of requirements?<br>
<br>
Alan<br>
<br>
At 30/09/2015 03:08 PM, Robin Gross wrote:
<blockquote type="cite">Agree 100%. We would be sorely amiss in our duty to enhance ICANN's accountability if we did not address the concerns about transparency in decision making at ICANN.<br>
<br>
Robin<br>
<br>
<br>
On Sep 30, 2015, at 11:26 AM, Phil Corwin wrote:<br>
<blockquote type="cite">Transparency of Board meetings and deliberations is long overdue and sorely needed. It should be the rule with very narrow exceptions.<br>
<br>
Sunlight is the best disinfectant.<br>
<br>
Philip S. Corwin, Founding Principal<br>
Virtualaw LLC<br>
1155 F Street, NW<br>
Suite 1050<br>
Washington, DC 20004<br>
<a href="tel:202-559-8597" value="+12025598597" target="_blank">202-559-8597</a>/Direct<br>
<a href="tel:202-559-8750" value="+12025598750" target="_blank">202-559-8750</a>/Fax<br>
<a href="tel:202-255-6172" value="+12022556172" target="_blank">202-255-6172</a>/Cell<br>
<br>
Twitter: @VLawDC<br>
<br>
"Luck is the residue of design" -- Branch Rickey<br>
<br>
Sent from my iPad<br>
<br>
On Sep 29, 2015, at 10:24 PM, Edward Morris <<a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>> wrote:<br>
<blockquote type="cite">Hi Jordan,<br>
<br>
I appreciate the spirit in which this thread is intended.<br>
<br>
<br>
--That is, aside from the five community powers and the ability to enforce the bylaws against the Board, the other powers the California law grants to member/s (document inspection, dissolve the company, etc), should face such high thresholds to action that they can, practically speaking, never be actioned at all.<br>
So how to resolve this? The CCWG's choice of a Single Member (following its earlier choice of multiple members) was to meet the accountability requirements the community has asked for. But nobody asked for the community to have these other powers.<br>
<br>
<br>
I disagree with this premise with regards the inspection right. I've certainly made that a central component of what I've tried to accomplish here. Kieren has been a strong advocate, as well, calling it a "red line";<br>
<br>
---<br>
<br>
On 07/08/2015 11:37 PM, Kieren McCarthy wrote:<br>
A quick view specifically on "rights of inspection".<br>
I think enabling that some entity gets this right would be one of the<br>
most useful of all possible accountability improvements.<br>
It would - perhaps over time - pull out any motivations that might exist<br>
for ICANN to be misleading or less than truthful in its reporting. This<br>
is going to be especially important as ICANN receives increasingly large<br>
amounts of revenue and particularly given its current weak financial<br>
controls.<br>
(See: <a href="http://www.ionmag.asia/2015/07/icann-finances-swallow-the-money/" target="_blank"> http://www.ionmag.asia/2015/07/icann-finances-swallow-the-money/</a>)<br>
I predict that ICANN corporate will fight hard to prevent any entity<br>
from gaining this right. And that it will continue to fight hard even<br>
when someone has that right. That in itself should be a good indicator<br>
for why it should be a redline for the accountability group.<br>
To my mind, not allowing ICANN to hide information is the epitome of<br>
actual accountability. If you can't hide it, then to save on<br>
embarrassment you consider how best to share it. Over time, everyone gains.<br>
<br>
Kieren<br>
<br>
-----<br>
I agree with Kieren. One of the reasons I've been content with putting transparency in work stream 2 is I've known the Inspection right came with membership in work stream 1. If that is to be excised then we need to do transparency in work stream 1. You can not have accountability without transparency. I've been involved in reconsideration requests where we have fought and lost in our attempts to get documents from ICANN that would have allowed us to have a chance of winning either the reconsideration or the IRP that would conceivably follow. Without access to documents many of the reforms we're proposing will be of minimal value to litigants. Of course, I await the specifics of the discovery mechanisms that will accompany the IRP and reconsideration reforms.<br>
<br>
I've watched as many "fears" of the legally uneducated became "truths" when repeated enough. I saw the concept of the derivative lawsuit, a power that should be welcomed by anyone interested in true accountability, so misconstrued and tangled CCWG members and participants acted out of fear this legal right could be used on a regular basis for anything, rather than what it is: a remedy designed for use in extreme situations as protection against double dealing and other types of corporate malfeasance.<br>
<br>
Rather than try to explain Inspection beyond what Kiernen has done above let me ask this: 1. Why don't we want the right of Inspection (aka in ICANN circles as the Auerbach rights)? 2. If we have them why do we want to create high thresholds for the use of those powers? Tell me how these two positions strengthen ICANN's accountability to a greater degree than inspection rights with low thresholds.<br>
<br>
And, perhaps most of all, where has the discussion occurred leading one and all to believe that we don't want these rights? Point to the thread, the legal advice etc. I've seen the big FUD over derivative rights. Where is something similar, or honest rejection of Inspection rights? Don't assume these are not important issues to some of us merely because we haven't been discussing them. They were in all of the proposals that have gone out for public comment. There is little need to fight for something you already have. I'm looking forward to receiving an analysis of the public comments to see this outpouring of opposition to the inspection rights. It must be there because I'm hard pressed to find extensive opposition anywhere else.<br>
<br>
Do we need these rights? Well, if we are going to dump them we need a complete revamp of ICANN's transparency policy to be done in work stream 1. No transparency, no accountability. No accountability, no transition.<br>
<br>
Best,<br>
<br>
Ed<br>
<br>
<br>
- I reproduce here California Corporations Code §8333:<br>
<br>
<br>
The accounting books and records and minutes of proceedings<br>
of the members and the board and committees of the board shall be<br>
open to inspection upon the written demand on the corporation of any<br>
member at any reasonable time, for a purpose reasonably related to<br>
such person's interests as a member.<br>
<br>
<br>
This is the heart of the Inspection right. It is so key I'll give it a name: the Anti-FIFA clause.<br>
<br>
It is a guarantee the corruption at FIFA will not happen at the new ICANN.<br>
<br>
The anti-FIFA clause is the principle reason I strongly support the Inspection right.<br>
<br>
No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com/" target="_blank">www.avg.com</a><br>
Version: 2015.0.6140 / Virus Database: 4419/10680 - Release Date: 09/22/15<br>
Internal Virus Database is out of date.<br>
<ATT00001.c></blockquote>
_______________________________________________<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></blockquote>
<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></blockquote>
</div></div></div></span>
<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>