<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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;}
span.EmailStyle17
{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;}
--></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"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Alan Greenberg<br>
</span><br>
>Milton makes reference to the "Principle of Separability", but that <o:p></o:p></p>
<p class="MsoNormal">>is one of the work products of the CWG, and not a premise going in.
<o:p></o:p></p>
<p class="MsoNormal">>I believe that it was driven by the lack of trust in ICANN, and that
<o:p></o:p></p>
<p class="MsoNormal">>there may well be ways to ensure that ICANN does not violate the
<o:p></o:p></p>
<p class="MsoNormal">>MS trust. That is not there today, and that is why we will have an
<o:p></o:p></p>
<p class="MsoNormal">>Accountability CCWG to address just that kind of question.<br>
<br>
<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">Sorry, Alan, we fundamentally disagree on the approach to this. Whether I trust ICANN or not, we are making global governance arrangements that require checks
and balances. It is not about trusting people or not trusting people, it is about giving the stakeholders who rely on IANA a basic form of accountability for the long term.
<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 am still having trouble understanding the motivations for this concerted rear-guard action against the simple expedient of Contract Co. First it was claimed
that it was something that could be “captured” but then the error of this perception was clearly explained: it is a shelf corporation and it takes instructions from the MRT. Now it is claimed that this is too complex; but it’s not complex at all compared to
what you offer as an alternative, namely creating an entity within ICANN that requires modification of the bylaws in a way that magically creates a group within ICANN that has the power to overrule the board of a corporation it is part of. None of the problems
regarding the composition of the MRT or the threat of capturing the MRT are simplified or improved by what you propose; in fact they are worsened.
<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">Is this really just an attempt to reverse the separability option? If so, I think that’s something that will not ever be acceptable to the bulk of the community
nor will such a proposal make it through the Washington DC gauntlet. <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"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p class="MsoNormal" style="margin-left:4.8pt"><br>
Alan<br>
<br>
At 04/12/2014 08:55 AM, Maarten Simon wrote:<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi all,<br>
<br>
I am of the same opinion and wonder, not noing much about Californian corporate law, if we could find a solution in adding specific elements to ICANN’s bylaws specifically aimed on the IANA function.
<br>
<br>
If we could arrange via the bylaws that the ICANN board explicitly has to follow orders from a MRT-like structure, we might not need a contract but have an (internal) MoU/SLA or whatever. If the ICANN board would at a certain moment in time still decide not
to follow orders of the MRT, I would assume it may be sued by affected parties for violating its own bylaws. We further may dictate in the bylaws that ICANN has to give up the IANA function if decided by this MRT and of course seal it by dictating that these
specific articles may only be changed with the explicit consent of the MRT. <br>
<br>
As I said, I have no clue if such a solution would be possible under Californian law. Under my legal system I think it would.<br>
<br>
Best,<br>
<br>
Maarten<br>
<br>
<b>From:</b> <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org"> mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Eduardo Diaz<br>
<b>Sent:</b> woensdag 3 december 2014 1:19<br>
<b>To:</b> Holly Raiche<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] Do we really need a Contracting Co.?<br>
<br>
Holly and all:<br>
<br>
I have the same questions and concerns. Are we taking the route of a Contrac Co, because is what NTIA is expecting to see as part of the proposal or is it because concerns of ICANN accountability. My impression is the second.<br>
<br>
-ed<br>
<br>
On Tue, Dec 2, 2014 at 7:12 PM, Holly Raiche <<a href="mailto:h.raiche@internode.on.net"> h.raiche@internode.on.net</a>> wrote:<br>
Seun<br>
<br>
You have summed up the issue wonderfully.<br>
<br>
Yes, we appear to be going down the second route. But there are still questions around that route. Alan’s (and Olivier’s and many other's) inputs have asked hard questions about the route - as have I. In particular, I asked about the proposed Contract
Co. If it is to be created, what is to be its nature, size, powers, funding. From Greg, it emerged that what was envisaged was a shelf company and the multi stakeholder processes under its umbrella would be the mechanisms of accountability. Since then,
it appears that the Contract Co will be more than a shelf company, so the many questions about its nature, powers, funding remain. And without answers, I am not sure why the first alternative - fixing the accountability mechanisms - has been rejected. It
appears we are hoping the creation of a legal entity (however small) will solve problems. I remain to be convinced.<br>
<br>
Holly<br>
<br>
On 3 Dec 2014, at 7:21 am, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a> > wrote:<br>
<br>
<br>
Hi Chuck,<br>
<br>
Thanks a lot for sharing this url....its really useful and i am going to hope that the accountability team are looking at scenarios like that to fix ICANN. Inview of this, there are generally 2 routes:<br>
- Fix the accountability mechanisms within ICANN and let the NTIA role naturally go away<br>
- While the accountability mechanism is yet to be fixed, provide a means by which IANA can still be moved out of ICANN
<br>
I presume we are currently going the second route at the moment. So a question that i may ask is, will it not be better to work towards the first route through the second route? This will mean maintaining the ability to move IANA from current operator with
an external body (can be an existing body like ISOC, IETF etc) or the lightweight (Contracting Co earlier proposed) and then provide certain principles/mechanisms that this CWG expect to have been addressed within specific time-frame.<br>
That will give ICANN (and its community) enough time to work on improving its accountability measures within the timeline indicated by this CWG.<br>
Regards<br>
On Tue, Dec 2, 2014 at 2:05 PM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com">cgomes@verisign.com</a>> wrote:<br>
Seun,<br>
<br>
Please see the letter I sent to Fadi in 2013: <a href="https://www.icann.org/resources/correspondence/gomes-to-chehade-2013-08-30-en">
https://www.icann.org/resources/correspondence/gomes-to-chehade-2013-08-30-en</a> .<br>
<br>
Chuck<br>
<br>
<b>From:</b> <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org"> mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Seun Ojedeji<br>
<b>Sent:</b> Tuesday, December 02, 2014 3:57 AM<br>
<b>To:</b> Avri Doria<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>
<br>
<b>Subject:</b> Re: [CWG-Stewardship] Do we really need a Contracting Co.?<br>
<br>
On Tue, Dec 2, 2014 at 7:33 AM, Avri Doria <<a href="mailto:avri@acm.org">avri@acm.org</a>> wrote:<br>
<br>
On 02-Dec-14 07:16, Seun Ojedeji wrote:<br>
I also don't understand the view that ICANN community and corporate are separate.
<br>
<br>
The ICANN Board and Staff are independent of the Community and can overrule the community either by a vote of the Board, or by calling an action 'implementation' that does not require community agreement.<br>
<br>
Okay, may i ask if this is happening at the moment and what the NTIA role has been in making sure it does not happen? because what we are trying to transition is the NTIA role and not ICANN management itself....if there is something that needs to be fixed in
the ICANN structure then it could be put in the requirement for transition (most of which should be looked into by the accountability cwg).
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
especially since the Board, given its understanding of the its fiduciary responsibility sees itself as NOT representing the community. Adn the staff is governed by a CEO that is not subject, in any way, to community appproval in hiring or contract renewal.
The Community has NO influence over ICANN Staff.<o:p></o:p></p>
<p class="MsoNormal"> <br>
Well in the RIR world the board (by by-law) acts in the interest of the organisation. They may also choose not to listen to the community but they usually wisely choose otherwise.... ;).<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">What does that mean? and how is ICANN community different from a typical RIR community.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
In the RIRs there is no body with a vote that can overrule the will of the community in policy making.<o:p></o:p></p>
<p class="MsoNormal"> <br>
The RIR board by the by-law could decide not to approve a policy proposal, its just that they have not had any reason to exercise such powers. So if you are saying there has been consistence instances where a policy that achieved consensus in the ICANN community
was overruled by the board, then there is definitely something wrong and will be good to have an example of such scenario to understand why they took such action and determine how to avoid such in future. This is how we build the organisation from inside especially
if we understand that ICANN is the home for gTLD<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Please when you think of who pays, think of it from the customer perspective, think of participation, think of the resources that's already been expended in this current ICG process.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
How does the contractor paying hurt the consumers?<o:p></o:p></p>
<p class="MsoNormal"> <br>
I think it will be safer to answer this with another question, where will the contractor get the money to pay from?
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
I persist in seeing the only real possibility of capture in a massively multistakeholder body is that the community process can be captured by ICANN corporate decisions made that disregard the community's consensus, and that is what we need to protect against.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <br>
Looks like you are now referring the MRT to be a MASSIVE multi-stakeholder body, please can we fashion out the composition and charter of this organisation so we appreciate what we are looking at. It sure seem there is going to be a lot of mechanism required
to ensure that the multistakeholder body is indeed inclusive. <br>
Regards<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
avri<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">_______________________________________________<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">CWG-Stewardship mailing list<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
<br>
-- <br>
------------------------------------------------------------------------<br>
Seun Ojedeji,<br>
Federal University Oye-Ekiti<br>
web: <a href="http://www.fuoye.edu.ng/">http://www.fuoye.edu.ng</a><br>
Mobile: <a href="tel:%2B2348035233535">+2348035233535</a><br>
alt email:<a href="http://goog_1872880453/"> </a><a href="mailto:seun.ojedeji@fuoye.edu.ng">seun.ojedeji@fuoye.edu.ng</a><br>
The key to understanding is humility - my view !<br>
<br>
<br>
<br>
<br>
-- <br>
------------------------------------------------------------------------<br>
Seun Ojedeji,<br>
Federal University Oye-Ekiti<br>
web: <a href="http://www.fuoye.edu.ng/">http://www.fuoye.edu.ng</a><br>
Mobile: +2348035233535<br>
alt email:<a href="http://goog_1872880453/"> </a><a href="mailto:seun.ojedeji@fuoye.edu.ng">seun.ojedeji@fuoye.edu.ng</a><br>
The key to understanding is humility - my view !<br>
<br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a> <br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br>
<br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a> <br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br>
<br>
<br>
-- <br>
NOTICE: This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If
you have received this email by mistake, please notify the sender and delete this message immediately.<br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>