<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I didn't say it was all of WS2; I said that if we don't trust WS2 to deliver, then we need to bring it all into WS1. Do you think that WS2 is a mirage?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">And I didn't say that we "just need to get this done." I'm all for targeted addition of 6333 rights, and there are quite a number of other areas in our proposal where we still have open points, and I'm not saying let's just get this done in those areas either.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">As for being tired and exhausted, that's not my issue, either -- I spent 8 years at a law firm where the average billable hours were over 2800 hours a year, and where the top biller had close to 4000 hours (and he did it in 6 days a week, because he was Jewish and observant). That's exhausting. This is a piece of cake.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Regardless, I stand by my position that statutory equivalency aside, the rest of this should stay in WS2.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Gerg</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 28, 2015 at 6:06 PM, Schaefer, Brett <span dir="ltr"><<a href="mailto:Brett.Schaefer@heritage.org" target="_blank">Brett.Schaefer@heritage.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Greg,<br>
<br>
This is hardly bringing all of WS2 into WS1. I know people are tired, exhausted by this process, but the view that we "just need to get this done" is a recipe for regret later in my opinion.<br>
<span class=""><br>
Brett<br>
<br>
<br>
<br>
<br>
________________________________<br>
Brett Schaefer<br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs<br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy<br>
The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002<br>
<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a><br>
<a href="http://heritage.org" rel="noreferrer" target="_blank">heritage.org</a><<a href="http://heritage.org/" rel="noreferrer" target="_blank">http://heritage.org/</a>><br>
<br>
</span><span class="">On Oct 28, 2015, at 5:51 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>>> wrote:<br>
<br>
Brett,<br>
<br>
</span><span class="">The issue of "final authority" in the comparison of member and designator is not monolithic and in many cases not far different under either model.<br>
<br>
I think significant changes to DIDP policy and to lobbying disclosure policy, each with numerous subparts with new concepts, and a reach that may go well beyond the stated subject matter (e.g., contacts with all government officials starts to look like law enforcement contact disclosure, which should be a topic unto itself), amounts to a trainload, or at least several boxcars.<br>
<br>
I have concerns with process, timing and substance. Frankly, my concerns on substance are probably the most limited (though not insignificant within those limitations). I am more concerned about getting this done, and burying the limited but necessary need for 6333-type disclosure (and perhaps other statutory disclosure, as Rosemary pointed out) in a big multipart package.<br>
<br>
I think there is quite a bit of heavy lifting here, and a few radical points. We should give this the breathing room it deserves and save the negotiation and discussion of this for WS2. Or let's just blow up all of WS2 and bring it in to WS1. We should not be too greedy in WS1 -- "Pigs get fat, but hogs get slaughtered."<br>
<br>
BTW, I never said I was opposed to it because it was "new." I'm not some sort of accountability Luddite. But it is a significant chunk of work beyond what is necessary now, even in light of the shift in models.<br>
<br>
As to your question in your follow-up email, I'm saying that moving the entire subject of transparency into WS1 signals a failure to believe that WS2 is real and can be relied on. If I'm a fool to believe in WS2, then we have bigger issues than where to deal with broad transparency reforms in our workflow.<br>
<br>
Greg<br>
<br>
</span><span class="">On Wed, Oct 28, 2015 at 5:23 PM, Schaefer, Brett <<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>>> wrote:<br>
Greg,<br>
<br>
</span><span class="">I disagree. The question of where final authority rests is fundamental.<br>
<br>
I also disagree with your characterization of this as a trainload of new reforms. It is an important clarification of an existing policy, DIDP, and incorporation of a well established disclosure standard.<br>
<br>
This is not heavy lifting or radical. It seems that your sole case for not doing it is that it is "new". It is not. It was sidelined last December on part based on the model we were considering. This would have been a much more live issue absent membership.<br>
<br>
Also, designator is new. Should we not consider that either?<br>
<br>
Best,<br>
<br>
Brett<br>
<br>
<br>
________________________________<br>
Brett Schaefer<br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs<br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy<br>
The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002<br>
</span><a href="tel:202-608-6097" value="+12026086097">202-608-6097</a><tel:<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a>><br>
<a href="http://heritage.org" rel="noreferrer" target="_blank">heritage.org</a><<a href="http://heritage.org" rel="noreferrer" target="_blank">http://heritage.org</a>><<a href="http://heritage.org/" rel="noreferrer" target="_blank">http://heritage.org/</a>><br>
<br>
__________<br>
<span class=""><br>
On Oct 28, 2015, at 4:51 PM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>>>> wrote:<br>
<br>
Brett,<br>
<br>
I disagree with this as a justification for bringing in a trainload of new transparency demands.<br>
<br>
If the Community wants to spill the Board because it is refusing to accept the exercise of a specific reserved power, that is all the justification we need to spill the Board, or as many Board members as needed to successfully exercise the power. There's no need to build a case beyond that.<br>
<br>
You are also vastly overstating the "reversal" -- the spill/recall rights are statutorily identical under the Designator model, and the bylaw rights are functionally identical. Only the budget/op plan rights are diminished from an enforcement and "fiduciary duty" perspective.<br>
<br>
Finally, the most rapid recourse under EITHER model is to spill the Board. Anybody who thinks that litigation will provide "rapid recourse" hasn't been involved in litigation; under our circumstances, litigation as a form of "rapid recourse" is even more unlikely than for a typical litigant.<br>
<br>
Greg<br>
<br>
Greg<br>
<br>
</span><span class="">On Wed, Oct 28, 2015 at 4:12 PM, Schaefer, Brett <<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>>>> wrote:<br>
Greg,<br>
<br>
I agree on the specifics of the right of inspection, but I think you are overlooking the broader enforcement issue.<br>
<br>
Under the membership model, final authority for various power resided in the member, not the Board.<br>
<br>
The designator reverses that authority – the power now remains with the Board, not the designator. Under the designator, as we heard repeatedly last week, the most rapid means of recourse is to spill the Board or remove a director. To do that in a responsible way, you need justification. That requires more robust access to information, ICANN documents, etc. to build a case.<br>
<br>
In my mind, greater transparency is instrumental if the designator is to avail itself of its far more limited power.<br>
<br>
Best,<br>
<br>
Brett<br>
<br>
<br>
<br>
</span>From: Greg Shatan [mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>>>]<br>
<span class="">Sent: Wednesday, October 28, 2015 4:01 PM<br>
To: Seun Ojedeji<br>
</span>Cc: Schaefer, Brett; <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>>><br>
<span class=""><br>
Subject: Re: [CCWG-ACCT] Contribution on Transparency Reforms for CCWG<br>
<br>
There seems to be an attempt at severe "mission creep" (or in this case, "mission leap") taking place here.<br>
<br>
When we moved from "member" to "designator" as our reference model, we gave up the statutory right of inspection under Section 6333 of the California Corporations Code. In order to bridge the gap between "member" and "designator," we discussed trying to give the Sole Designator essentially the same rights that the Sole Member would have had under Section 6333. The member's rights under 6333 are actually quite limited. This was not intended to move all transparency issues from WS2 to WS1. Yet it seems that there's a move by a "small subgroup" to try and take this narrow opening and wedge an entire transparency wishlist into Work Stream 1. This urge to overreach should be resisted by the CCWG, and even by the small subgroup.<br>
<br>
Section 6333 reads as follows:<br>
<br>
6333. 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>
We should strive to give the Designator similar rights in WS1 and nothing more. Widespread transparency "reforms" are well beyond the scope of WS1 or the time we have on our timeline to debate and consider each of the various proposals embodied in the small subgroup's document. Rather than using that document as a starting point, I suggest we park that document for use in WS2, and use Section 6333 as our starting point.<br>
<br>
Key points of Section 6333:<br>
<br>
1. It is a right exercised only by a member. In our prior model, it would have been a right exercised only by the Sole Member. Now, it should be a right exercised only by the Sole Designator<br>
2. It is limited to particular types of materials:<br>
<br>
* "accounting books and records"<br>
* "minutes of proceedings of the members"<br>
* "minutes of proceedings of ... the board"<br>
* "minutes of proceedings of ... committees of the board"<br>
<br>
1. It is a right that can only be exercised "for a purpose reasonably related to" the member's interests "as a member."<br>
2. It requires the member to activate the right by making a "written demand on the corporation" to initiate the right; the corporation is not obligated under 6333 to disclose anything on its own initiative or due to its mere existence as a corporation.<br>
3. It is a right to "inspection."<br>
Terms like "accounting books and records" and "open to inspection," among others, have fairly specific legal meanings in the context of 6333. Our counsel can enlighten us on the specifics, but it is important to be aware that these are limited terms.<br>
<br>
Our job should be to translate 6333 into the Bylaws as faithfully as possible. No more, no less. I hesitate to suggest any flexibility, lest there be another attempt to pass a camel through the eye of a needle.<br>
<br>
A final note -- Section 6336 provides a specific enforcement right if a corporation refuses a "lawful demand" under Section 6333. This should also be imported into the Bylaws.<br>
<br>
Greg<br>
<br>
<br>
</span><span class="">On Wed, Oct 28, 2015 at 3:24 PM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a><mailto:<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>><mailto:<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a><mailto:<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>>>> wrote:<br>
<br>
Hello Brett,<br>
<br>
I think we may be talking pass each other here. What is currently being done in relation to transparency is a NEW issue under WS1 i.e things required for stewardship transition to happen.<br>
<br>
I don't agree to the rationale that need for transparency is largely dependent on what model is decided upon. Transparency is an act that should always be encouraged (within the mission of an organisation) and its a continuous effort as much as it's a very tricky topic that needs to be carefully addressed (just like human rights within ICANN). Going members route would not necessarily increase/reduce transparency neither will designator, hence its model independent. So IMO that reason just does not "draw much water".<br>
<br>
Again a transcript, TOR, and timeline pointers for these new item would be appreciated as I have not found one yet.<br>
<br>
Regards<br>
<br>
Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.<br>
</span><span class="">On 28 Oct 2015 20:03, "Schaefer, Brett" <<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>>>> wrote:<br>
Seun,<br>
<br>
It is not a new issue, transparency was always on the accountability to do list. It was just not as considered as urgent as other issues because of the powers inherent in the membership model. The recent change in models was the impetus for the change, not a random desire to introduce items at the last minute. If membership had remained the model, in my opinion, I don’t think this would have happened.<br>
<br>
Best,<br>
<br>
Brett<br>
<br>
</span>From: Seun Ojedeji [mailto:<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a><mailto:<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>><mailto:<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a><mailto:<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>>>]<br>
<span class="">Sent: Wednesday, October 28, 2015 2:53 PM<br>
To: Schaefer, Brett<br>
</span>Cc: James Gannon; <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>>><br>
<span class="">Subject: RE: [CCWG-ACCT] Contribution on Transparency Reforms for CCWG<br>
<br>
<br>
Thanks Brett, I may have missed that particular session where it was decided that additional items be introduced to WS1. A pointer to that transcript will be helpful and it will also be good to know what working party James team is called, their TOR and what their meeting modalities/timelines are.<br>
<br>
That said, I am concerned that the CCWG is introducing new items at this last minutes of WS1. It makes me wonder what our priorities are.<br>
<br>
Thanks again for your response.<br>
<br>
Regards<br>
Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.<br>
<br>
________________________________<br>
Brett Schaefer<br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs<br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy<br>
The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002<br>
</span><a href="tel:202-608-6097" value="+12026086097">202-608-6097</a><tel:<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a>><tel:<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a><tel:<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a>>><br>
<a href="http://heritage.org" rel="noreferrer" target="_blank">heritage.org</a><<a href="http://heritage.org" rel="noreferrer" target="_blank">http://heritage.org</a>><<a href="http://heritage.org/" rel="noreferrer" target="_blank">http://heritage.org/</a>><br>
<span class="">On 28 Oct 2015 19:30, "Schaefer, Brett" <<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a><mailto:<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>>>> wrote:<br>
Seun,<br>
<br>
At the CCWG meetings last week, there was agreement that the move from member to designator (and the lesser powers it would have in many areas, including the right of inspection) should result in transparency concerns being moved from WS2 up to WS1.<br>
<br>
Best,<br>
<br>
Brett<br>
<br>
</span>From: <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>>> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>>>] On Behalf Of Seun Ojedeji<br>
<span class="">Sent: Tuesday, October 27, 2015 3:57 PM<br>
To: James Gannon<br>
</span>Cc: <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>>><br>
<span class="">Subject: Re: [CCWG-ACCT] Contribution on Transparency Reforms for CCWG<br>
<br>
<br>
Hi James,<br>
<br>
If I may ask, which of the work stream or working party does this fall? Will be good to know what action item of the CCWG gave birth to this. A pointer will be appreciated.<br>
<br>
Regards<br>
<br>
Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.<br>
<br>
________________________________<br>
Brett Schaefer<br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs<br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy<br>
The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002<br>
</span><a href="tel:202-608-6097" value="+12026086097">202-608-6097</a><tel:<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a>><tel:<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a><tel:<a href="tel:202-608-6097" value="+12026086097">202-608-6097</a>>><br>
<a href="http://heritage.org" rel="noreferrer" target="_blank">heritage.org</a><<a href="http://heritage.org" rel="noreferrer" target="_blank">http://heritage.org</a>><<a href="http://heritage.org/" rel="noreferrer" target="_blank">http://heritage.org/</a>><br>
<span class="">On 27 Oct 2015 20:16, "James Gannon" <<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a><mailto:<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a>><mailto:<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a><mailto:<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a>>>> wrote:<br>
Hi Greg,<br>
<br>
A number of NCSG members and others who spoke on this issue in Dublin including myself had started work on this during Dublin and once we had something that was readable we brought it to the group to continue the work.<br>
<br>
-James<br>
<br>
<br>
________________________________<br>
Brett Schaefer<br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs<br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy<br>
The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002<br>
</span><a href="tel:202-608-6097" value="+12026086097">202-608-6097</a><tel:202-608-6097><tel:202-608-6097<tel:202-608-6097>><br>
<a href="http://heritage.org" rel="noreferrer" target="_blank">heritage.org</a><<a href="http://heritage.org" rel="noreferrer" target="_blank">http://heritage.org</a>><<a href="http://heritage.org/" rel="noreferrer" target="_blank">http://heritage.org/</a>><br>
From: <<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>>>> on behalf of Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><mailto:<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>>>><br>
<span class="">Date: Tuesday 27 October 2015 at 7:09 p.m.<br>
</span>To: Robin Gross <<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a><mailto:<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>><mailto:<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a><mailto:<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>>>><br>
Cc: CCWG-Accountability Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>>>><br>
<span class="">Subject: Re: [CCWG-ACCT] Contribution on Transparency Reforms for CCWG<br>
<br>
In the interests of transparency, who is in the small subgroup?<br>
<br>
Thanks!<br>
<br>
Greg<br>
<br>
</span><span class="">On Tue, Oct 27, 2015 at 3:00 PM, Robin Gross <<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a><mailto:<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>><mailto:<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a><mailto:<a href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>>>> wrote:<br>
All:<br>
<br>
Here is a link to a document intended to contribute to CCWG's work on improving transparency at ICANN:<br>
<br>
<a href="https://docs.google.com/document/d/11sX-zY5uie9s7zNeGz2GIRXk7BBg2xrbN_pplpJnNvc/edit?pli=1#" rel="noreferrer" target="_blank">https://docs.google.com/document/d/11sX-zY5uie9s7zNeGz2GIRXk7BBg2xrbN_pplpJnNvc/edit?pli=1#</a><<a href="https://docs.google.com/document/d/11sX-zY5uie9s7zNeGz2GIRXk7BBg2xrbN_pplpJnNvc/edit?pli=1" rel="noreferrer" target="_blank">https://docs.google.com/document/d/11sX-zY5uie9s7zNeGz2GIRXk7BBg2xrbN_pplpJnNvc/edit?pli=1</a>><br>
<br>
The doc is the creation of small subgroup of CCWG participants focusing on this transparency issue. Feedback is most welcome!<br>
<br>
Thanks,<br>
Robin<br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
</span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>>><br>
<span class=""><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>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
</span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>>><br>
<span class=""><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>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
</span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>><mailto:<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><mailto:<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>
<br>
<br>
</blockquote></div><br></div></div>