{excuse the late response, please!}<div>Dear AfriNIC's Community, <br><br>Le lundi 2 août 2021, Mike Silber <<a href="mailto:silber.mike@gmail.com" target="_blank">silber.mike@gmail.com</a>> a écrit :<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">Hi Sylvain<div><br></div></div></blockquote><div><br></div><div>Hi Mike,</div><div>Thanks for your email, brother.</div><div> </div><div>...i, first, have to apologize as my tone was </div><div>not as usual. But it was not directed to an </div><div>individual; but rather, it was another [*] general </div><div>call to do what i did to learn more about the RIR </div><div>system history [1][2] & the IN Registry system.</div><div>__</div><div>[*]: <<a href="https://lists.afrinic.net/pipermail/rpd/2021/013404.html" target="_blank">https://lists.afrinic.net/<wbr>pipermail/rpd/2021/013404.html</a><wbr>></div><div>[1]: <<a href="https://nro.net/about/rirs/the-internet-registry-system/rir-history/" target="_blank">https://nro.net/about/rirs/<wbr>the-internet-registry-system/<wbr>rir-history/</a>></div><div>[2]: <<a href="https://nro.net/about/history-of-the-nro/" target="_blank">https://nro.net/about/<wbr>history-of-the-nro/</a>></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div>I respectfully disagree.</div><div><br></div></div></blockquote><div><br></div><div>...yes! your plain rights.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div>ICANN is a convenience through which the RIR’s operate.</div><div><br></div></div></blockquote><div><br></div><div>...it's a bit difficult to disambiguate ICANN's </div><div>relationships...it's easy to think the contrary </div><div>true [3] :-/ i share more on it below, please.</div><div>__</div><div>[3]: Open Letter to ICANN from the Regional Internet Registries, 6 NOV 2003</div><div><<a href="https://www.nro.net/open-letter-to-icann-from-the-regional-internet-registries/" target="_blank">https://www.nro.net/open-<wbr>letter-to-icann-from-the-<wbr>regional-internet-registries/</a>></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div>The rest of the NRO recognised AfriNIC and could have done so without ICANN involvement - had they so chosen. </div><div><br></div></div></blockquote><div><br></div><div>...in 2005.</div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div>As it is - the NRO fulfils the role of ASO within ICANN and it could terminate the ASO / NRO nexus at any time with little to no impact. </div><div><br></div></div></blockquote><div><br></div><div>...yes! ASO AC (1999) := NRO NC (2003)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div>Did you miss this in RFC 7020:</div><div><br></div></div></blockquote><div><br></div><div>Maybe other parts...</div><div>...not the text below!</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><pre style="font-size:13.333333015441895px;margin-top:0px;margin-bottom:0px">The Internet Assigned Numbers Authority (IANA) *is a role, not an</pre></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div><pre style="font-size:13.333333015441895px;margin-top:0px;margin-bottom:0px"> organization*. For the Internet Numbers Registry System, the IANA
role manages the top of the IP address and AS number allocation
hierarchies. 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",</pre><pre style="font-size:13.333333015441895px;margin-top:0px;margin-bottom:0px"><br></pre></div></div></blockquote><div><br></div><div>...documented through RFC2860, in june 2000: </div><div><br></div><div><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px"><span style="display:inline;white-space:pre-wrap;font-size:1em;font-weight:bold">Memorandum of Understanding Concerning the Technical</span>
<span style="display:inline;white-space:pre-wrap;font-size:1em;font-weight:bold">Work of the Internet Assigned Numbers Authority</span></pre></div><div><<a href="https://tools.ietf.org/html/rfc2860" target="_blank">https://tools.ietf.org/html/r<wbr>fc2860</a>></div><div><br></div><div>...in that MoU, IETF and ICANN agreed that <pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px"> The IANA will assign and register Internet protocol parameters... </pre></div><div><br></div><div>Those parameters include IP addresses & ASN</div><div>...with the DNS root zone, particularly the arpa. </div><div>zone.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div><pre style="font-size:13.333333015441895px;margin-top:0px;margin-bottom:0px"><br></pre><pre style="font-size:13.333333015441895px;margin-top:0px;margin-bottom:0px"> which
was signed and ratified in March 2000</pre><div><br></div><div>It is the RIRs who chose ICANN and not the other way around.</div></div></div></blockquote><div><br></div><div> </div><div>...i would have asked you to, please, elaborate,</div><div>but i think, i could be satisfied by the content of </div><div>the NRO MoU [4]. </div><div>It shows a full attempt of independence...</div><div>__</div><div>[4]: <<a href="https://www.nro.net/nro-memorandum-of-understanding/" target="_blank">https://www.nro.net/nro-memor<wbr>andum-of-understanding/</a>></div><div><br></div><div>...but, did they chose IANA? the role, sure :-)</div><div><br></div><div><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px">[<a>ASOMOU</a>] ICANN, "ICANN Address Supporting Organization (ASO) MoU",
October 2004,
<<a href="http://archive.icann.org/en/aso/aso-mou-29oct04.htm" target="_blank">http://archive.icann.org/en/a<wbr>so/aso-mou-29oct04.htm</a>>.
</pre></div><div><br></div><div>...the companion RFC of RFC7020 is RFC7249:</div><div><br></div><div><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px"><span style="display:inline;white-space:pre-wrap;font-size:1em;font-weight:bold">Internet Numbers Registries</span></pre></div><div><<a href="https://tools.ietf.org/html/rfc7249" target="_blank">https://tools.ietf.org/html/r<wbr>fc7249</a>><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px"><br></pre><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px">~°~</pre><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px"><pre style="margin-top:0px;margin-bottom:0px">Abstract
<a href="https://datatracker.ietf.org/doc/html/rfc7020" target="_blank">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">~°~</pre></div><div><br></div><div>...i don't think we need to go back to the time </div><div>when the IANA technical function was fully under </div><div>US DoC/NTIA contract [5]...permit me to paste the </div><div>below portion of text, from RFC7020, to conclude:</div><div><br></div><div>~°~</div><div>[...]</div><div><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px">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">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">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">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">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">ICANNASN</a>].</pre></div><div>[...]</div><div>~°~</div><div><br></div><div>It cites a MoU between ICANN & IETF/IAB about </div><div>IANA role; back in march 2000; NRO was created </div><div>on 24 october 2003 [4]. But ICP-2 [6] has been </div><div>ratified by ICANN on 04 june 2001, so LACNIC </div><div>enjoyed it first in 2002, then AfriNIC in 2005...</div><div>...ASO AC (1999) [7] predates NRO NC (2003).</div><div>__</div><div>[5]: <<a href="https://www.ntia.doc.gov/files/ntia/publications/ianacontract.pdf" target="_blank">https://www.ntia.doc.gov/<wbr>files/ntia/publications/<wbr>ianacontract.pdf</a>></div><div>[6]: <<a href="https://icann.org/icp/icp-2.htm" target="_blank">https://icann.org/icp/icp-2.<wbr>htm</a>></div><div>[7]: <<a href="https://aso.icann.org/about/aso-icann/" target="_blank">https://aso.icann.org/about/<wbr>aso-icann/</a>></div><div><br></div><div><br></div><div>...those public information are the base of my </div><div>assertion...again, i admit that both the two </div><div>directions could be proved to be true.</div><div><br></div><div>But, icymi, *our* concern was about what Owen </div><div>said, regarding ICANN. So, the same kind of </div><div>thinking developed through nra.help...</div><div><br></div><div>Hope this clarifies, something.</div><div><br></div><div>Shalom, </div><div>--sb.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><div><div>Mike</div><div><br><blockquote type="cite"><div>On 2 Aug 2021, at 14:49, Sylvain Baya <<a href="mailto:abscoco@gmail.com" target="_blank">abscoco@gmail.com</a>> wrote:</div><br><div>Dear AfriNIC's Community, <br><br>Le lundi 2 août 2021, Noah <<a href="mailto:noah@neo.co.tz" target="_blank">noah@neo.co.tz</a>> a écrit :<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi Mike<div dir="auto"><br></div></div></blockquote><div><br></div><div>Hi Noah, </div><div><br></div><div>Thanks for your email, brother!</div><div><br></div><div>...it's time to learn about the RIR system's history.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto">Thank you for your reply and opinion on the matter.</div><div dir="auto"><br></div><div dir="auto">I am personally offended by Owens choice of words against ICANN.</div><div dir="auto"><br></div><div dir="auto">The existence of an RIR is only possible through ICANN ICP-2 and for him to refer to ICANN as a puppet is offending.</div><div dir="auto"><br></div><div dir="auto">AFRINIC would not have existed without the ICANN structures.</div></div></blockquote><div><br></div><div><br></div><div>Exact!</div><div><br></div><div>For those who need an anchor to start with, </div><div>please look at RFC7020:</div><div><br></div><div><pre style="font-size:10.6667px;margin-top:0px;margin-bottom:0px"><span style="display:inline;white-space:pre-wrap;font-size:1em;font-weight:bold">The Internet Numbers Registry System</span></pre></div><div><<a href="https://tools.ietf.org/html/rfc7020" target="_blank">https://tools.ietf.org/html/r<wbr>fc7020</a>></div><div><br></div><div>Shalom,</div><div>--sb.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto">[...]</div></div></blockquote></div></blockquote></div><br></div></div></blockquote>
</div>
<br><br>-- <br>--<p>Best Regards !<br>__<br>baya.sylvain[AT cmNOG DOT cm]|<<a href="https://cmnog.cm/dokuwiki/Structure">https://cmnog.cm/dokuwiki/Structure</a>><br>Subscribe to Mailing List: <<a href="https://lists.cmnog.cm/mailman/listinfo/cmnog/">https://lists.cmnog.cm/mailman/listinfo/cmnog/</a>><br>__<br>#LASAINTEBIBLE|#Romains15:33«Que LE #DIEU de #Paix soit avec vous tous! #Amen!»<br>#MaPrière est que tu naisses de nouveau. #Chrétiennement<br>«Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!»(#Psaumes42:2)<br><br></p>