<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div>Siva — Back in December, we gathered consensus around this rationale between WS1 and WS2:</div>
<div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><br>
</div>
<div>Proposed rationale for designating Work Streams: (updated to reflect discussion thru 12-Jan)</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>Work Stream 1 is designated for accountability enhancement mechanisms that must be in place or committed to, before IANA transition occurs.</div>
<div><br>
</div>
<div>WS1 mechanisms are those that, when in place or committed to, would provide the community with confidence that any accountability mechanism that would further enhance Icann's accountability would be implemented if it had consensus support from the community,
even if it were to encounter Icann management resistance or if it were against the interest of Icann as a corporate entity.</div>
<div><br>
</div>
<div>All other consensus items could be in Work Stream 2, provided the mechanisms in WS1 are adequate to force implementation of WS2 items despite resistance from ICANN management and board.</div>
<div><br>
</div>
</blockquote>
</blockquote>
</div>
<div>
<div id="">
<div>The legal team’s formulation between WS1 and WS2 legal questions fits with that proposal. </div>
<div><br>
</div>
<div>—</div>
<div>
<div>Steve DelBianco</div>
<div>Executive Director</div>
<div>NetChoice</div>
<div><a href="http://www.netchoice.org/">http://www.NetChoice.org</a> and <a href="http://blog.netchoice.org/">http://blog.netchoice.org</a></div>
<div>+1.703.615.6206</div>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Sivasubramanian M<br>
<span style="font-weight:bold">Date: </span>Wednesday, March 11, 2015 at 7:54 PM<br>
<span style="font-weight:bold">To: </span>Accountability Cross Community<br>
<span style="font-weight:bold">Subject: </span>[CCWG-ACCT] Work Stream 1 and Work Stream 2: Comments based on impressions from Meeting Notes.<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div class="gmail_default" style="color:rgb(51,51,51)"><font face="trebuchet ms,sans-serif">Hello</font></div>
<div class="gmail_default" style="color:rgb(51,51,51)"><font face="trebuchet ms,sans-serif"><br>
</font></div>
<div class="gmail_default" style="color:rgb(51,51,51)"><font face="trebuchet ms,sans-serif"><br>
</font></div>
<div class="gmail_default" style="color:rgb(51,51,51)"><font face="trebuchet ms,sans-serif">I was not present for the Legal Sub Team call <a href="https://community.icann.org/pages/viewpage.action?pageId=52891852">https://community.icann.org/pages/viewpage.action?pageId=52891852</a>
on 10th March and have not listened to the recording either. This comment is based on the Introductory section of the Meeting Notes, which might not be points discussed at length during the Sub Team meeting, quoted below, and raised here as a point to consider
by the whole group:</font></div>
<div class="gmail_default" style="color:rgb(51,51,51)"><font face="trebuchet ms,sans-serif"><br>
</font></div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote">
<font face="trebuchet ms,sans-serif">Notes: 2. Brief Discussion:<br>
</font>
<ul style="margin:0px;line-height:19.0476188659668px">
<li><font face="trebuchet ms,sans-serif">WS2 - no need to be in place before transition takes place but needs to take place post transition. </font></li></ul>
<font face="trebuchet ms,sans-serif"><span style="line-height:19.0476188659668px"><br>
</span>Three items need to be put in place as part of WS1. </font>
<ul style="margin:0px;list-style-type:disc">
<li><font face="trebuchet ms,sans-serif">Recalling members of the ICANN board of directors.</font></li></ul>
<ul style="margin:0px;list-style-type:disc">
<li><font face="trebuchet ms,sans-serif">Community empowerment over ICANN’s management.</font></li></ul>
<ul style="margin:0px;list-style-type:disc">
<li><font face="trebuchet ms,sans-serif">Limiting the scope of ICANN’s activity. </font></li></ul>
</blockquote>
<div class="gmail_default" style="color:rgb(51,51,51)">
<div>
<ul style="margin:10px 0px 0px;line-height:19.0476188659668px">
<li style="list-style-type:none;background-image:none"></li></ul>
<div><span style="line-height:19.0476188659668px"><font face="trebuchet ms,sans-serif"><br>
</font></span></div>
</div>
<div><font face="trebuchet ms,sans-serif">One of the several proposals for Work Stream 2 was based on the rationale that pre-transition changes to the Accountability framework is minimal with major improvements to discussed and carried out on an ongoing basis
post transition. </font></div>
<div><font face="trebuchet ms,sans-serif"><br>
</font></div>
<div><font face="trebuchet ms,sans-serif">With almost zero discussion on Work Stream 2, without even the formation of work stream 2, it is highly undesirable to think of such changes to the Accountability framework as the inclusion of provisions to recall members
of the Board, limiting the scope of ICANN's activity or even Community empowerment over ICANN management. </font></div>
<div><font face="trebuchet ms,sans-serif"><br>
</font></div>
<div><font face="trebuchet ms,sans-serif">Within a well-considered and larger Accountability environment such changes could be effected in phases, in tune with a larger and clearer blue print, but without even a beginning on such a blue print, it is unwise
to think of the changes as proposed for WS1. These provisions, if included pre-transition and in a rush, could prove counter productive.</font></div>
<div><font face="trebuchet ms,sans-serif"><br>
</font></div>
<div><font face="trebuchet ms,sans-serif">I would propose the bare minimal improvements to the Accountability framework, if such improvements are to be made in a rush. At best, WS 1 could discuss such changes but leave it for implementation post transition,
after more elaborate thinking.</font></div>
<div><font face="trebuchet ms,sans-serif"><br>
</font></div>
<div><font face="trebuchet ms,sans-serif">Sivasubramanian M</font></div>
<div><span style="line-height:19.0476188659668px"><font face="trebuchet ms,sans-serif"><br>
</font></span></div>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:rgb(51,51,51)">
<br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:rgb(51,51,51)">
<br>
</div>
<div>
<div class="gmail_signature">
<div dir="ltr"><a href="https://www.facebook.com/sivasubramanian.muthusamy" target="_blank">Sivasubramanian M</a></div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>