<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1845852387;
mso-list-type:hybrid;
mso-list-template-ids:-629777908 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Steve:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for this great summary of transparency aspects in WS1 and WS2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In my personal view, the default for all Board activities should be full transparency, with redaction only for narrowly circumscribed matters.
<u>So, may I inquire whether the new COMMITMENT 1 you have noted below would have any effect on Board transparency?<o:p></o:p></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Beyond that inquiry, I am
<u>not</u> arguing for moving transparency matters into WS1 because of their legal and operational complexity – with one key exception.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> 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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What would be the benefits of such a voluntary Board action?:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It would help restore trust between the CCWG and the Board, which was substantially bruised in LA.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I hope that CCWG and Board members find these suggestions to be constructive, because that is the spirit in which they are offered.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best to all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Philip<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Philip S. Corwin, Founding Principal</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Virtualaw LLC</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">1155 F Street, NW</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Suite 1050</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Washington, DC 20004</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8597/Direct</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8750/Fax</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-255-6172/cell</span></b><b><span style="color:navy"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Twitter: @VlawDC</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">"Luck is the residue of design" -- Branch Rickey</span></i></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>On Behalf Of </b>Steve DelBianco<br>
<b>Sent:</b> Wednesday, September 30, 2015 10:44 PM<br>
<b>To:</b> Alan Greenberg; egmorris1@toast.net; Robin Gross; Accountability Cross Community<br>
<b>Subject:</b> Re: [CCWG-ACCT] A way to avoid the 'The Single Member Can Do Anything!' problem<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">This reply is to help inform today's discussion thread on Transparency. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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:<o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">We propose a new commitment in ICANN Bylaws: <o:p></o:p></span></p>
</div>
<div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><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""><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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""> text) for Core Value
2 in ICANN Bylaws:<o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><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 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""><o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">We require transparency as part of the new Community Forum (para 355 on p.53)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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.<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><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.<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><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. <o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><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)<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">And for WS2, there’s this:<o:p></o:p></span></p>
</div>
<div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><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)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Instituting a culture of transparency within the ICANN organization: (p.121)<o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">o Limiting ICANN's ability to deny transparency and disclosure requests. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">o Enhancing the Ombudsman’s role and function.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">o Enhancing ICANN’s whistleblower policy.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">o Increasing transparency about ICANN interactions with governments.<o:p></o:p></span></p>
</div>
</blockquote>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-family:"Calibri","sans-serif";color:black"><<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>> on behalf of Alan Greenberg<br>
<b>Date: </b>Wednesday, September 30, 2015 at 8:00 PM<br>
<b>To: </b>"<a href="mailto:egmorris1@toast.net">egmorris1@toast.net</a>", Robin Gross, Accountability Cross Community<br>
<b>Subject: </b>Re: [CCWG-ACCT] A way to avoid the 'The Single Member Can Do Anything!' problem<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><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>
<o:p></o:p></span></p>
<p class="MsoNormal"><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>
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><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">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">robin@ipjustice.org</a>>, "Accountability Cross Community" <<a href="mailto:accountability-cross-community@icann.org">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
<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: <br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><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>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><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>
202-559-8597/Direct<br>
202-559-8750/Fax<br>
202-255-6172/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">egmorris1@toast.net</a>> wrote:<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><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: <a href="http://www.ionmag.asia/2015/07/icann-finances-swallow-the-money/">
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/">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><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">_______________________________________________<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">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></span></p>
<p class="MsoNormal"><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">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></span></p>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com">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.<o:p></o:p></p>
</div>
</body>
</html>