<p dir="ltr">sent from Google nexus 4<br>
kindly excuse brevity and typos.<br>
On 4 Sep 2014 12:42, "John Curran" <<a href="mailto:jcurran@istaff.org">jcurran@istaff.org</a>> wrote:<br>
><br>
><br>
>><br>
>> That cultural failure leads to the sorts of staff and Board decisions that have eroded trust between ICANN-the-organisation and the ICANN community.<br>
><br>
><br>
> Again, you are referring to decisions that are being made within _ICANN_, and hence are<br>
> unaffected by any move of the IANA external to ICANN (particularly if ICANN is the one who<br>
> contracts with the IANA operator for the DNS IANA registry maintenance, as you propose<br>
> above...) <br>
><br>
+1 to this for all it's worth; Where the database really stays doesn't matter much to me. How the database update scripts are developed is what matters most to me and that is largely related to the policies used by IANA staff.<br>
So there are just 2 main ICANN accountability area:</p>
<p dir="ltr">- The management of ICANN as an organisation which generally includes it's leadership representation, role and deliverables. (I don't care about coca-cola, I care about the formula that produces the drink I ingest.)</p>
<p dir="ltr">- The other is ICANN as an IANA operator.</p>
<p dir="ltr">While I may be less concerned about the first. I am 100% concerned about the second as a community member who rely on the information in IANA database. So for me, I will like to see that the script ICANN uses to carry out IANA operation is developed by me (as the community) and that way, I am accountable as a community member.</p>
<p dir="ltr">So I wonder why it becomes a huge puzzle to make the community developed policies an absolute script source for IANA operation. As this is already practiced in the numbers world (and ofcourse not by paying members)</p>
<p dir="ltr">Cheers!</p>
<p dir="ltr">> I actually don't know if moving the IANA outside of ICANN is a good idea or not; there are<br>
> certain stability issues that weigh heavily, but we also have existence proof that such teams<br>
> can be transitioned from their parent organizations successfully. My main point is that moving<br>
> IANA (or not) doesn't actually have any meaningful impact on the ICANN accountability, which <br>
> appears (from those on the sidelines such as myself) to be the DNS communities principal <br>
> source of angst.<br>
><br>
> FYI,<br>
> /John<br>
><br>
> Disclaimer: my views alone.<br>
><br>
><br>
> _______________________________________________<br>
> IANAxfer mailing list<br>
> <a href="mailto:IANAxfer@elists.isoc.org">IANAxfer@elists.isoc.org</a><br>
> <a href="https://elists.isoc.org/mailman/listinfo/ianaxfer">https://elists.isoc.org/mailman/listinfo/ianaxfer</a><br>
><br>
</p>