<div dir="ltr">I'd like to add a quick +1 here. It would be a very positive step for the Board to match the transparency the community is exercising in this work.<div><br></div><div>Jordan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 5 October 2015 at 11:07, Matthew Shears <span dir="ltr"><<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I would support this as well - a necessary and overdue part of the
overall process. <br>
<br>
<div>On 04/10/2015 21:41, Greg Shatan wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:verdana,sans-serif">I support this as well,
particularly with regard to transparency on the part of the
Board in the accountability process.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">For example, calls
between counsel and the CCWG are on open and transcribed
calls, and all documents provided by counsel to the CCWG are
provided on the publicly archived email list and posted to a
publicly available wiki.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">The Board should do the
same. </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 Sat, Oct 3, 2015 at 8:21 AM, Robin
Gross <span dir="ltr"><<a href="mailto:robin@ipjustice.org" target="_blank">robin@ipjustice.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">I support Phil's proposal
to increase transparency of board decision making in these
accountability reforms. It would be a terrible oversight
if we did not.
<div><br>
</div>
<div>Thanks,</div>
<div>Robin
<div>
<div><br>
<div><br>
<div>
<div>On Oct 1, 2015, at 5:43 PM, Phil Corwin
wrote:</div>
<br>
<blockquote type="cite"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Steve:</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thanks
for this great summary of
transparency aspects in WS1 and WS2.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">However,
in my view, there is one glaring
omission, and that is a
requirement for greater
transparency in Board operations.</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"></span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">We
live in an age where nearly every
operation of government in
democratic nations is web-streamed
live. And ICANN is committed to
transparency. Yet there are no
videos or audios of Board meetings,
no transcripts, and the minutes
provide little in the way of detail
regarding how decisions were reached
and whether there was any
significant dissent by individual
Board members.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">In
my personal view, the default for
all Board activities should be full
transparency, with redaction only
for narrowly circumscribed matters.<span> </span><u>So,
may I inquire whether the new
COMMITMENT 1 you have noted below
would have any effect on Board
transparency?</u></span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Beyond
that inquiry, I am<span> </span><u>not</u><span> </span>arguing
for moving transparency matters into
WS1 because of their legal and
operational complexity – with one
key exception.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I
would favor WS1 requiring that all
Board activities encompassing
Accountability matters relating to
the IANA transition be fully
transparent to the community once
a final proposal has been approved
by the Chartering Organizations.</span></b></div>
<div><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></b></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">My
reason for that position is that
there is at present a yawning gap
between the information available to
the Board regarding the community’s
activities on accountability
matters, versus the community’s
access to Board consideration of the
same subject.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">The
Board has full access to every email
and every opinion from CCWG counsel
at the moment it is sent, and any
member of the Board can participate
fully in CCWG discussions and
meetings.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">By
way of contrast, the community has
no access to internal Board emails
regarding accountability, no access
to General Counsel and Jones Day
legal opinions except on a highly
selective and delayed basis, and has
no ability to even observe much less
participate in Board discussions of
accountability.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">The
result of this glaring information
asymmetry is a data disconnect
that is antithetical to achieving
consensus between the CCWG and the
Board regarding accountability.</span></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><span> </span>The
Board sees everything the CCWG is
doing in real time, while the CCWG
sees nothing of relevant Board
activities and information until it
chooses to share it.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Imagine
if the CCWG had equivalent access to
Board discussions and legal
documents before the LA F2F.
Perhaps the decision would have been
made not to hold the meeting if the
CCWG knew that the Board has
determined to never support the SMM.
Or perhaps CCWG access to Board
discussions and Jones Day analysis
on a more timely basis would have
fostered a constructive dialogue and
facilitated preparations that would
have permitted the LA meeting to be
far more productive, rather than
leaving many CCWG members with the
feeling they had walked into an
ambush.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Let
me go even further – not only do I
believe that WS1 should require
all Board activities encompassing
Accountability matters relating to
the IANA transition be fully
transparent to the community, I
would urge the Board to
voluntarily begin that practice
immediately.</span></b></div>
<div><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></b></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">What
would be the benefits of such a
voluntary Board action?:</span></div>
<div><span style="font-size:11pt;font-family:Symbol;color:rgb(31,73,125)"><span>·<span style="font:normal normal normal 7pt/normal 'Times New Roman'"> <span> </span></span></span></span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">It
would help make up for lost time. It
is quite apparent that the fallout
from the LA meeting includes adding
at least weeks if not months to the
CCWG’s process as it strives to
determine both the reasons for the
Board’s position and what it should
do now in reaction to it. CCWG
access to Board accountability
deliberations in real time would
substantially improve the overall
efficiency of the accountability
process – restricting information
g]flows is highly inefficient.</span></div>
<div><span style="font-size:11pt;font-family:Symbol;color:rgb(31,73,125)"><span>·<span style="font:normal normal normal 7pt/normal 'Times New Roman'"> <span> </span></span></span></span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">It
would demonstrate Board’s commitment
to a far higher level of
transparency, and its
acknowledgement that such
transparency is the bedrock
foundation of the enhanced
accountability that should accompany
the transition.</span></div>
<div><span style="font-size:11pt;font-family:Symbol;color:rgb(31,73,125)"><span>·<span style="font:normal normal normal 7pt/normal 'Times New Roman'"> <span> </span></span></span></span><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">It
would help restore trust between the
CCWG and the Board, which was
substantially bruised in LA.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Finally,
while I would not advocate open
participation in Board
accountability discussions to the
same extent that Board members can
participate in CCWG activities, I
would propose consideration of
establishment of a CCWG liaison
who can do so, as well as report
back to the CCWG on the Board’s
thinking and concerns.</span></b></div>
<div><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></b></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">CCWG
members seem aligned in thinking
that greater transparency is an
integral part of enhanced
accountability, and much of what the
CCWG has proposed relates to greater
Board accountability. It seems
inconceivable that such
accountability can be achieved if
the Board persists in its presently
opaque mode of operation following
the transition. The time to shine
light on Board operations is coming,
and its accountability deliberations
is the place to begin.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Let’s
be frank. The CCWG and the Board are
at an impasse, and if this
accountability effort fails it will
be seen as a failure of the MSM
itself. That is a mortal threat to
ICANN’s future and simply
unacceptable. Dramatic shifts are
required near-term to foster
positive progress in Dublin, which
is barely two weeks away.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I
hope that CCWG and Board members
find these suggestions to be
constructive, because that is the
spirit in which they are offered.</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Best
to all,</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Philip</span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy">Philip
S. Corwin, Founding Principal</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy">Virtualaw
LLC</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy">1155
F Street, NW</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy">Suite
1050</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy">Washington,
DC 20004</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy"><a href="tel:202-559-8597" value="+12025598597" target="_blank">202-559-8597</a>/Direct</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy"><a href="tel:202-559-8750" value="+12025598750" target="_blank">202-559-8750</a>/Fax</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy"><a href="tel:202-255-6172" value="+12022556172" target="_blank">202-255-6172</a>/cell</span></b><b><span style="color:navy"></span></b></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy"> </span></b></div>
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy">Twitter:
@VlawDC</span></b><span style="color:black"></span></div>
<div><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"> </span></div>
<div><b><i><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:navy">"Luck
is the residue of design" --
Branch Rickey</span></i></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black"></span></div>
</div>
<div><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div>
<div>
<div style="border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;border-top-style:solid;border-top-color:rgb(181,196,223);border-top-width:1pt;padding-top:3pt;padding-right:0in;padding-bottom:0in;padding-left:0in">
<div><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"><span> </span><a href="mailto:accountability-cross-community-bounces@icann.org" style="color:blue;text-decoration:underline" target="_blank"></a><a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a><span> </span>[mailto:<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank"></a><a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>]<span> </span><b>On
Behalf Of<span> </span></b>Steve
DelBianco<br>
<b>Sent:</b><span> </span>Wednesday,
September 30, 2015 10:44 PM<br>
<b>To:</b><span> </span>Alan
Greenberg;<span> </span><a href="mailto:egmorris1@toast.net" style="color:blue;text-decoration:underline" target="_blank"></a><a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>;
Robin Gross; Accountability
Cross Community<br>
<b>Subject:</b><span> </span>Re:
[CCWG-ACCT] A way to avoid the
'The Single Member Can Do
Anything!' problem</span></div>
</div>
</div>
<div> </div>
<div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">This
reply is to help inform today's
discussion thread on
Transparency. </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">Our
2nd draft report includes the
term transparency on 50
different pages. But what
really matters is how we add
greater transparency into WS1
proposals. See these elements:</span></div>
</div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">We
propose a new commitment in
ICANN Bylaws: </span></div>
</div>
<div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif;color:blue">COMMITMENT
1. In performing its
Mission, ICANN must
operate in a manner
consistent with its Bylaws
for the benefit of the
Internet community as a
whole, carrying out its
activities in conformity
with relevant principles
of international law and
international conventions,
and applicable local law
and through open and
transparent processes that
enable competition and
open entry in
Internet-related markets.</span><span style="font-family:Calibri,sans-serif"></span></div>
</div>
</blockquote>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">We
propose a new element (</span><span style="font-family:Calibri,sans-serif;color:blue">blue</span><span style="font-family:Calibri,sans-serif"><span> </span>text)
for Core Value 2 in ICANN
Bylaws:</span></div>
</div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">CORE
VALUE 2. Seeking and
supporting broad, informed
participation reflecting the
functional, geographic, and
cultural diversity of the
Internet at all levels of
policy development and
decision-making<span> </span></span><span style="font-family:Calibri,sans-serif;color:blue">to ensure that the
bottom-up, multistakeholder
policy development process
is used to ascertain the
global public interest and
that those processes are
accountable and transparent;</span><span style="font-family:Calibri,sans-serif"></span></div>
</div>
</blockquote>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">We
require transparency as part
of the new Community Forum
(para 355 on p.53)</span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">We
note that CWG-Stewardship
requirement for IANA budget
transparency in para 378:
the CWG-Stewardship Final
Proposal has expressed a
requirement that the budget be
transparent with respect to
the IANA Function’s operating
costs with clear itemization
of such costs to the project
level and below as needed.</span></div>
</div>
</blockquote>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">Our
new requirement for an annual
report on Transparency (para
511-512 on p.74): ICANN will
produce an annual report on
the state of improvements to
Accountability and
Transparency.</span></div>
</div>
</blockquote>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">We
give all AoC review teams
unprecedented access to ICANN
internal documents. See
Confidential Disclosure
policy, para 521 – 527 on
p.75. </span></div>
</div>
</blockquote>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">We
require each AoC review team
to be transparent about the
degree of consensus achieved
in their report. (para 529
on p.75)</span></div>
</div>
</blockquote>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">And
for WS2, there’s this:</span></div>
</div>
<div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">Transparency:
The community has expressed
concerns regarding the ICANN
document/information access
policy and implementation.
Free access to relevant
information is an essential
element of a robust
independent review process.
We recommend reviewing and
enhancing the Documentary
Information Disclosure
Policy (DIDP) as part of the
accountability enhancements
in Work Stream 2. (p.43)</span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif">The
subject of SO and AC
accountability should be
included in the purview of
the Accountability and
Transparency Review process
as part of Work Stream 2
working plan. (p.71)</span></div>
</div>
<div>
<div> </div>
</div>
<div>
<div>
<div><span style="font-family:Calibri,sans-serif">Instituting
a culture of transparency
within the ICANN
organization: (p.121)</span></div>
</div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<div><span style="font-family:Calibri,sans-serif">o
Limiting ICANN's ability
to deny transparency and
disclosure requests. </span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif">o
Enhancing the
Ombudsman’s role and
function.</span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif">o
Enhancing ICANN’s
whistleblower policy.</span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif">o
Increasing transparency
about ICANN interactions
with governments.</span></div>
</div>
</blockquote>
</div>
</blockquote>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div style="border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;border-top-style:solid;border-top-color:rgb(181,196,223);border-top-width:1pt;padding-top:3pt;padding-right:0in;padding-bottom:0in;padding-left:0in">
<div><b><span style="font-family:Calibri,sans-serif;color:black">From:<span> </span></span></b><span style="font-family:Calibri,sans-serif;color:black"><<a href="mailto:accountability-cross-community-bounces@icann.org" style="color:blue;text-decoration:underline" target="_blank"></a><a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>>
on behalf of Alan Greenberg<br>
<b>Date:<span> </span></b>Wednesday,
September 30, 2015 at 8:00 PM<br>
<b>To:<span> </span></b>"<a href="mailto:egmorris1@toast.net" style="color:blue;text-decoration:underline" target="_blank"></a><a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>",
Robin Gross, Accountability Cross
Community<br>
<b>Subject:<span> </span></b>Re:
[CCWG-ACCT] A way to avoid the
'The Single Member Can Do
Anything!' problem</span></div>
</div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black"> </span></div>
</div>
<div>
<div>
<div><span style="font-family:Calibri,sans-serif;color:black">Ed,
I didn't ask why we had not ever
discussed it, but rather why we
are now saying it had to be
included in the current
proposal. I was a member of the
ATRT2 and am more than painfully
aware how ineffective the DIDP
is, and I have LONG campaigned
for more transparency and
availability of internal
documents.<br>
<br>
The CCWG process is somewhat
stalled due to the reaction of
the Board to our draft proposal,
but it was the draft that the
CCWG was planning to make some
final adjustments to and submit
as final. The transparency and
access issues were not
mentioned. I believe that it is
a WS2 issue and discussing it
now will do nothing but
obfuscate the real issues that
we need to address.<br>
<br>
Alan<br>
<br>
At 30/09/2015 06:59 PM, Edward
Morris wrote:<br>
<br>
</span></div>
<div><span style="font-family:Calibri,sans-serif;color:black">HI
Alan,<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Best,<br>
<br>
Ed Morris<br>
</span></div>
<div class="MsoNormal" align="center"><span style="font-family:Calibri,sans-serif;color:black">
<hr align="center" size="2" width="100%"></span></div>
<div><b><span style="font-family:Calibri,sans-serif;color:black">From</span></b><span style="font-family:Calibri,sans-serif;color:black">: "Alan Greenberg"
<<a href="mailto:alan.greenberg@mcgill.ca" style="color:blue;text-decoration:underline" 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" style="color:blue;text-decoration:underline" target="_blank"></a><a href="mailto:robin@ipjustice.org" target="_blank">robin@ipjustice.org</a>>,
"Accountability Cross Community"
<<a href="mailto:accountability-cross-community@icann.org" style="color:blue;text-decoration:underline" target="_blank">accountability-cross-community@icann.org</a>><br>
<b>Subject</b>: Re: [CCWG-ACCT]
A way to avoid the 'The Single
Member Can Do Anything!' problem<span> </span><br>
<br>
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:<span> </span><br>
<br>
</span></div>
<div><span style="font-family:Calibri,sans-serif;color:black">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>
<span> </span><br>
<br>
</span></div>
<div><span style="font-family:Calibri,sans-serif;color:black">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" style="color:blue;text-decoration:underline" target="_blank"></a><a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>>
wrote:<br>
<span> </span><br>
<br>
</span></div>
<div><span style="font-family:Calibri,sans-serif;color:black">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:<span> </span><a href="http://www.ionmag.asia/2015/07/icann-finances-swallow-the-money/" style="color:blue;text-decoration:underline" target="_blank"></a><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 -<span> </span><a href="http://www.avg.com/" style="color:blue;text-decoration:underline" target="_blank"></a><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></span></div>
<div><span style="font-family:Calibri,sans-serif;color:black">_______________________________________________<br>
Accountability-Cross-Community
mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" style="color:blue;text-decoration:underline" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" style="color:blue;text-decoration:underline" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span></div>
<div><span style="font-family:Calibri,sans-serif;color:black"><br>
<br>
_______________________________________________<br>
Accountability-Cross-Community
mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" style="color:blue;text-decoration:underline" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" style="color:blue;text-decoration:underline" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span></div>
</div>
</div>
<div class="MsoNormal" align="center">
<hr style="color:rgb(160,160,160)" align="center" noshade size="1" width="100%"></div>
<div>No virus found in
this message.<br>
Checked by AVG -<span> </span><a href="http://www.avg.com" style="color:blue;text-decoration:underline" target="_blank"></a><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.</div>
</div>
</div>
</span></blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Accountability-Cross-Community mailing list
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Matthew Shears
Director - Global Internet Policy and Human Rights
Center for Democracy & Technology
<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>
<a href="tel:%2B%2044%20771%20247%202987" value="+447712472987" target="_blank">+ 44 771 247 2987</a> </pre>
<br><br>
<hr style="border:none;color:#909090;background-color:#b0b0b0;min-height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="https://www.avast.com/antivirus" target="_blank">
<img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo">
</a>
</td>
<td>
<p style="color:#3d4d5a;font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt">
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus" target="_blank">www.avast.com</a>
</p>
</td>
</tr>
</tbody></table>
<br>
</div>
<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><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr" style="font-size:small">Jordan Carter<br><br>Chief Executive <br><b>InternetNZ</b><br></div><div dir="ltr" style="font-size:small"><br>+64-4-495-2118 (office) | +64-21-442-649 (mob)<br>Email: <a href="mailto:jordan@internetnz.net.nz" style="color:rgb(17,85,204)" target="_blank">jordan@internetnz.net.nz</a> <br>Skype: jordancarter<br></div><div style="font-size:small">Web: <a href="http://www.internetnz.nz" target="_blank">www.internetnz.nz</a> </div><div dir="ltr" style="font-size:small"><br><i>A better world through a better Internet </i></div><br></div></div></div></div></div></div></div></div>
</div>