<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
hi,<br>
<br>
GNSO and ccNSO have no ability to sign a contract with anyone, they
are just parts of ICANN and ICANn cannot sign a contract with
itself.<br>
<br>
The contracting authority for IANA must be outside ICANN and it must
be an entity that is capable of signing a contract.<br>
<br>
avri<br>
<br>
<div class="moz-cite-prefix">On 01-Dec-14 17:13, Bertrand de La
Chapelle wrote:<br>
</div>
<blockquote
cite="mid:CAGF_KH-LYQ0dxz3ydYYqryJzzO2CfQev6AYc=7Gi-yEgD4ZN9A@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">Avri,
<div><br>
</div>
<div>I want to clarify. You wrote:</div>
<div><br>
</div>
<blockquote>
<div><i>The problem is that if the ICANN internal
multistakeholder community says A, the ICANN Board can say
Not A, and there is NOTHING we can do about it. </i> </div>
</blockquote>
<div class="gmail_extra"><br>
<div>
<div class="gmail_signature">
<div dir="ltr">
<table width="600">
<tbody>
<tr>
<td colspan="3" height="5">The avenue I am
exploring is to empower the ccNSO and the gNSO <u>as
such</u> with the capacity to sign an MoU with
the chosen IANA contractor (and to choose it).
In that approach, the ICANN Board would NOT be
in the loop. <br>
<br>
Does that clarify and answer your concern?<br>
<br>
B.</td>
</tr>
<tr>
<td colspan="3" height="5"><br>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Mon, Dec 1, 2014 at 4:57 PM, Avri
Doria <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<div><span class=""> <br>
<div>On 01-Dec-14 16:40, Seun Ojedeji wrote:<br>
</div>
<blockquote type="cite">- ICANN has built a highly
diverse multi-stakeholder environment and we should
leverage on that by providing mechanisms that will
energise it.</blockquote>
<br>
</span> Indeed the PRT does that. <br>
<br>
The problem is that if the ICANN internal
multistakeholder community says A, the ICANN Board can
say Not A, and there is NOTHING we can do about it.
Thus there needs to be an external entity that the ICANN
stakeholder environment we have created can directly
affect without threat of capture by ICANN Corporate.<br>
<br>
That is the primary Capture Entity we need to concern
ourselves with: ICANN Corporate.<span class=""><br>
<br>
avri<br>
<br>
</span></div>
<br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a moz-do-not-send="true"
href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/cwg-stewardship"
target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>