<div dir="ltr">After further investigation, seems I am missing part of where the SLAs are...<div><br></div><div>There was a consultation process on performance standards that occurred from Nov 20, 2012 through Feb 28, 2013. <br><a href="https://www.icann.org/resources/pages/iana-kpis-2012-11-20-en ">https://www.icann.org/resources/pages/iana-kpis-2012-11-20-en </a><div><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:15px"><br></span></div><div>The result of that consultation concluded that the IANA should provide a monthly report on key performance indicators, as well as data about request made and processed, and implementation of new global policy.<span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:15px"> </span></div><div><a href="https://www.icann.org/en/system/files/files/report-comments-iana-kpis-22apr13-en.pdf">https://www.icann.org/en/system/files/files/report-comments-iana-kpis-22apr13-en.pdf</a></div><div><br></div><div>The archive of those reports can be found here:</div><div><a href="https://www.iana.org/performance/metrics">https://www.iana.org/performance/metrics</a><br></div>You will want section c293 for the number resources part (append #c293 to any of the URLs in the archive to jump straight there)<br></div><div><br></div><div>___Jason</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 10, 2014 at 9:37 AM, Jason Schiller <span dir="ltr"><<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I think there is a lot of confusion here first wrt to making the policy that the IANA operators follow and the oversight that the IANA operators follow said policy and meet the appropriate SLAs.<div><br></div><div> Secondly, I think there is much confusion wrt the term "ICANN". Some times people use ICANN to me the small group of people employed by ICANN who perform the IANA operations, some times people mean the ICANN Board who ratifies Global Number Policy, sometimes people mean the entire ICANN community who discusses Domain Name concerns and such, and some time people mean a combination of some or all of those pieces. </div><div><br></div><div>First let me say WRT Global Policy making, we have a very good process, per the <a href="https://aso.icann.org/documents/memorandums-of-understanding/memorandum-of-understanding/" target="_blank">ASO MoU</a>. This does not change with NTIA stepping away.</div><div><br></div><div>What does change is the <a href="http://www.ntia.doc.gov/files/ntia/publications/sf_26_pg_1-2-final_award_and_sacs.pdf" target="_blank">contract</a> between the NTIA and ICANN for the IANA functions. This document has some vague language about SLAs. I understand the "real" SLAs are in this <a href="http://www.ntia.doc.gov/other-publication/2012/icann-proposal" target="_blank">doc</a>.</div><div><br></div><div>I already recommended (and David Huberman supported) step 1: we pull out those SLAs and put them in a document. And asked ARIN staff to start on that work. I'd like to ask the CRISP team, specifically Michael for a status on this work, and for that doc to be posted here once compiled.</div><div><br></div><div>Step 2: We then need to decide what legal vehicle we should have, and who should it be between. Should it be an MoU, a contract for services of the IANA function, or some other legal document? And should it be between the five RIRs and the portion of ICANN that currently performs the IANA service? Or the NRO, or the incorporated NRO? Should the document contain the SLAs or reference the SLA document?</div><div><br></div><div>Step 3: We need to define a transparent process to review the monthly performance of the ICANN operator and its (in)ability to meet the SLAs and adhere to Global Policy. </div><div><br></div><div>Step 4: We need a process for declaring the operator of the IANA service out of compliance. We also need a process for actions taken due to non-compliance including threatening to remove the contract, and removing the contract.</div><div><br></div><div>Step 5: We need a process for modifying the SLAs. </div><div><br></div><div>Step 6: We need to ensure our processes include the appropriate community interaction for reviewing the operations of IANA function, and how those measurements are taken, declaration of (non-)compliance, and changes to SLA metrics. </div><div><br></div><div>___Jason</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 2:07 PM, David Huberman <span dir="ltr"><<a href="mailto:David.Huberman@microsoft.com" target="_blank">David.Huberman@microsoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
As someone who very much wants to see the addressing function taken away from ICANN and moved directly to the NRO, I'm not sure MONC is any more useful than the NRO self-governing. The NRO is, after all, strictly bottom-up. RIR members elect board members. RIR board members select a CEO. The CEOs run the NRO. There's accountability up and down the chain.<br>
<br>
My question is how do we leverage the NTIA's desire to step back to dissolve the MOU between USGOV and ICANN wrt the clause, "Establishment of policy for and direction of the allocation of IP number blocks;"<br>
<br>
David<br>
<br>
David R Huberman<br>
Microsoft Corporation<br>
Principal, Global IP Addressing<br>
<br>
[1] <a href="https://www.icann.org/resources/unthemed-pages/icann-mou-1998-11-25-en" target="_blank">https://www.icann.org/resources/unthemed-pages/icann-mou-1998-11-25-en</a><br>
<div><div>_______________________________________________<br>
Iana-transition mailing list<br>
<a href="mailto:Iana-transition@arin.net" target="_blank">Iana-transition@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/iana-transition" target="_blank">http://lists.arin.net/mailman/listinfo/iana-transition</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|<a href="tel:571-266-0006" value="+15712660006" target="_blank">571-266-0006</a></font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</div>