<p dir="ltr">Hmm... just to further understand the practicality of this. So the new IANA (names part of the functions) will be funded by the registries right. Well i have a few set of questions below:</p>
<p dir="ltr">- How does/will something like newgTLD process look like? I.e will ICANN accredit or the new entity?<br>
- What exactly will the new entity be doing?<br>
- What will ICANN's new role be? I am assuming PDP (based on IGP) if that is the case it means the new entity will work on the ICANN's community developed policy right? And how does that improve accountability.<br>
- Who determine what staff to employ for the new entity? I presume there will then be a need for board of Directors, bylaw, membership etc. <br>
- Is the new entity going to be established in any country?<br>
- What will the composition of such new entities board look like? cctld, gtld, end-users?<br>
- Who will generally oversee the accountability of the new entity?<br>
- Who/what determines how the funds is shared between ICANN and the new entity?</p>
<p dir="ltr">Cheers!</p>
<p dir="ltr">sent from Google nexus 4<br>
kindly excuse brevity and typos.</p>
<div class="gmail_quote">On 24 Oct 2014 14:55, "James Gannon" <<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a>> wrote:<br type="attribution"><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 think in the case of using the same funding sources that it currently has within ICANN that, it would be important to structure it so as those funds would be payed directly to the IANA entity directly and not via revenue directed from within ICANN.
<div>The separation would be needed for accountability and to pre-empt any conflict of interest in my opinion.<br>
<div><br>
</div>
<div>James</div>
</div>
<div><br>
</div>
<div>
<div>On 24 Oct 2014, at 12:45, Amr Elsadr <<a href="mailto:aelsadr@egyptig.org" target="_blank">aelsadr@egyptig.org</a>> wrote:</div>
<br>
<blockquote type="cite">
<div style="word-wrap:break-word">
<div>Hi,</div>
<div><br>
</div>
<div>The issue of financing the new IANA was addressed in the IGP paper (<a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2408226" target="_blank">http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2408226</a>) in very much the same way Eduardo suggests. I also
think it sounds pretty reasonable. If current financing of IANA comes from the revenues accrued by ICANN from domain name registrations and paid by TLD registries, then that portion of the revenue used to finance IANA now can be redirected to whatever the
new IANA might be.</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
<div>Amr</div>
<br>
<div>
<div>On Oct 24, 2014, at 6:16 AM, Eduardo Diaz <<a href="mailto:eduardodiazrivera@gmail.com" target="_blank">eduardodiazrivera@gmail.com</a>> wrote:</div>
<br>
<blockquote type="cite">
<div dir="ltr">Robert:
<div><br>
</div>
<div>It will depend: if the final option is to keep the function under the ICANN umbrella, then my understanding is that ICANN will keep financing it. On the other hand, if it is moved outside ICANN, then i presume it can be supported by all entities requiring
its services.</div>
<div><br>
</div>
<div>-ed </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 23, 2014 at 6:57 PM, Robert Guerra <span dir="ltr">
<<a href="mailto:rguerra@privaterra.org" target="_blank">rguerra@privaterra.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Curious if the question of how the "new" IANA would be financed has been asked ?<br>
<br>
<br>
<br>
<br>
Sent from my iPhone<br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<b><font face="verdana, sans-serif">NOTICE:</font></b> <span>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.</span>
</div>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
</blockquote>
</div>
<br>
</div>
<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" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br></blockquote></div>