<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div class=""><div class=""><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px" class=""><br class=""></pre><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px" class="">~°~</pre><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px" class=""><pre style="margin-top:0px;margin-bottom:0px" class="">Abstract
<a href="https://datatracker.ietf.org/doc/html/rfc7020" target="_blank" class="">RFC 7020</a> provides information about the Internet Numbers Registry
System and how it is used in the distribution of autonomous system
(AS) numbers and globally unique unicast Internet Protocol (IP)
address space.
This companion document identifies the IANA registries that are part
of the Internet Numbers Registry System at this time.</pre></pre><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px" class="">~°~</pre></div><div class=""><br class=""></div><div class="">...i don't think we need to go back to the time </div><div class="">when the IANA technical function was fully under </div><div class="">US DoC/NTIA contract [5]...permit me to paste the </div><div class="">below portion of text, from RFC7020, to conclude:</div><div class=""><br class=""></div><div class="">~°~</div><div class="">[...]</div><div class=""><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px" class="">The Internet Corporation for Assigned Names and
Numbers (ICANN) currently fulfills the IANA role in accordance
with the IETF-ICANN "Memorandum of Understanding Concerning
Technical Work of the Internet Assigned Numbers Authority", which
was signed and ratified in March 2000 [<a href="https://datatracker.ietf.org/doc/html/rfc2860" title=""Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority"" target="_blank" class="">RFC2860</a>]. In addition,
ICANN performs the IANA services related to the IP address space
and AS numbers according to global number resource policies that
have been developed by the community and formalized under a
Memorandum of Understanding between ICANN and the Regional
Internet Registries [<a href="https://datatracker.ietf.org/doc/html/rfc7020#ref-ASOMOU" title=""ICANN Address Supporting Organization (ASO) MoU"" target="_blank" class="">ASOMOU</a>] and documented in [<a href="https://datatracker.ietf.org/doc/html/rfc7020#ref-ICANNv4" title=""Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA"" target="_blank" class="">ICANNv4</a>],
[<a href="https://datatracker.ietf.org/doc/html/rfc7020#ref-ICANNv6" title=""Internet Assigned Numbers Authority (IANA) Policy For Allocation of IPv6 Blocks to Regional Internet Registries"" target="_blank" class="">ICANNv6</a>], and [<a href="https://datatracker.ietf.org/doc/html/rfc7020#ref-ICANNASN" title=""Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks to Regional Internet Registries"" target="_blank" class="">ICANNASN</a>].</pre></div><div class="">[...]</div><div class="">~°~</div><div class=""><br class=""></div><div class="">It cites a MoU between ICANN & IETF/IAB about </div><div class="">IANA role; back in march 2000; NRO was created </div></div></div></blockquote><div><br class=""></div>That MoU is for protocol numbers, port numbers, etc. under the control of the IETF/IAB</div><div>and administered as the technical functions portion of the IANA role. It has nothing</div><div>to do with the Number Resource portion of the IANA role which is under the control</div><div>of the RIR system aka the NRO.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="">on 24 october 2003 [4]. But ICP-2 [6] has been </div><div class="">ratified by ICANN on 04 june 2001, so LACNIC </div><div class="">enjoyed it first in 2002, then AfriNIC in 2005...</div><div class="">...ASO AC (1999) [7] predates NRO NC (2003).</div><div class="">__</div><div class="">[5]: <<a href="https://www.ntia.doc.gov/files/ntia/publications/ianacontract.pdf" target="_blank" class="">https://www.ntia.doc.gov/<wbr class="">files/ntia/publications/<wbr class="">ianacontract.pdf</a>></div><div class="">[6]: <<a href="https://icann.org/icp/icp-2.htm" target="_blank" class="">https://icann.org/icp/icp-2.<wbr class="">htm</a>></div><div class="">[7]: <<a href="https://aso.icann.org/about/aso-icann/" target="_blank" class="">https://aso.icann.org/about/<wbr class="">aso-icann/</a>></div></div></div></blockquote><div><br class=""></div>Yes… This is an ICANN document that was created as part of its performance of the</div><div>IANA functions contract when that contract was being issued by NTIA.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="">...those public information are the base of my </div><div class="">assertion...again, i admit that both the two </div><div class="">directions could be proved to be true.</div></div></div></blockquote><div><br class=""></div>ICANN is now awarded the IANA functions contract with respect to internet number</div><div>resources by the empowered community which consists (for this purpose) of the</div><div>NRO EC.</div><div><br class=""></div><div>ICANN performs the IANA functions for internet number resources according to the</div><div>policies developed through the global policy development process of the ASO,</div><div>under the administrative guidance of the ASO AC. The ASO AC is a synonym</div><div>for the NRO NC and the global policy development process is managed by each</div><div>of the five RIR communities passing identical policy through their respective</div><div>PDPs and then forwarding that to the ASO AC for submission to ICANN.</div><div>(this is an oversimplification, but the rest is not material to this discussion).</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class=""><div class="">But, icymi, *our* concern was about what Owen </div><div class="">said, regarding ICANN. So, the same kind of </div><div class="">thinking developed through nra.help...</div></div></div></blockquote><div><br class=""></div>I chose an unfortunately charged term “puppet” to talk about the fact that ICANN</div><div>does not have authority over the RIRs, but, rather the RIRs have authority over</div><div>ICANN even though addresses flow from ICANN’s main pool to the RIR’s</div><div>individual pools. The control structure is very much that ICANN performs</div><div>the actions (with respect to internet number resources) that the RIRs tell it to.</div><div><br class=""></div><div>So while Mike (and others) don’t like my use of the word “puppet”, the reality is</div><div>that it is the NRO that pulls ICANNs strings with respect to Internet Number</div><div>Resources and even Mike has stated that it is a distinction without a difference.</div><div><br class=""></div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class=""><div class="">Hope this clarifies, something.</div></div></div></blockquote><div><br class=""></div>I hope you now have the clarity you seek.</div><div><br class=""></div><div>Owen</div><div><br class=""></div><br class=""></body></html>