<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="auto"><div dir="auto">Andrew <div dir="auto"><br></div><div dir="auto">Routing tables aside :-)</div><div dir="auto"><br></div><div dir="auto">LIR membership 101 requires that one has a business license and another license from a local communications regulatory authority of the country where they are requesting space from. Member services team from AfriNIC always require this before space is allocated/assigned to an entity. <br></div><div dir="auto"><br></div><div dir="auto">The regulators license is required because part of the AfriNIC bylaws
especially section 6.1 states that usage of INR must be for providing
services in the African region.This is the case so that its easier for Afrinic to comply with provisions of the bylaws that state that INR are to used in Africa to support the development of Internet Infrastructure in Africa and this is one of the objectives of Afrinic as an RIR whose vision and missions are;</div><div dir="auto"><br></div><div dir="auto">Our Vision<br>"Be the leading force in growing the internet for Africa's sustainable development"<br><br>Our Mission<br>"To serve the African Community by providing professional and efficient management of Internet number technology usage and development, and promoting Internet self-governance."</div><div dir="auto"><br></div><div>Noah<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 1 Jul 2019, 09:39 Andrew Alston, <<a href="mailto:Andrew.Alston@liquidtelecom.com" rel="noreferrer" target="_blank">Andrew.Alston@liquidtelecom.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="en-KE">
<div class="gmail-m_5640432627521063706m_-1119530443791921186m_-7074239852864492073WordSection1">
<p class="MsoNormal"><span lang="EN-US">Ronald,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">The answer to your question can be found in section 5.5 and 5.6 of the CPM – which makes no mention whatsoever of where space must be utilized. It does however state that you must be
an AFRINIC member to receive space, which is where the requirement that organizations should be domiciled in Africa comes from. This is codified in section 6.1.(i) of the bylaws.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Beyond that – there is no actual policy ever ratified which precludes the use of space off continent outside of soft landing – and that requirement can be found can be found in the soft
landing policy in section 5.4.6.2 of the CPM<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">During the creation of the soft landing policy – there was actually massive debate about that clause – and myself, and others, opposed the clause because it’s actually entirely unverifiable
– and I’ve never liked clauses that impose requirements that cannot be realistically verified. It is virtually impossible to tell where space is actually being utilized<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<ol style="margin-top:0cm" start="1" type="a">
<li class="gmail-m_5640432627521063706m_-1119530443791921186m_-7074239852864492073MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">The BGP tables won’t tell you this – I can have a block of space in Africa that is announced via an African ASN to a non-African
player over a layer 2 link<u></u><u></u></span></li><li class="gmail-m_5640432627521063706m_-1119530443791921186m_-7074239852864492073MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">I can have a block of space in Europe that is announced to an African transit provider in Europe<u></u><u></u></span></li><li class="gmail-m_5640432627521063706m_-1119530443791921186m_-7074239852864492073MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">Latency tells you nothing – VSAT links are common – and VSAT latency can look very much like long haul latency<u></u><u></u></span></li><li class="gmail-m_5640432627521063706m_-1119530443791921186m_-7074239852864492073MsoListParagraph" style="margin-left:0cm"><span lang="EN-US">It’s entirely possible for announce an aggregate link in Africa and actually be using all the space out of the continent by sending
de-aggregates to selective peers that would be not be publicly visible. In the same way – I could be originating the space from routers in Europe while using IGP de-aggregates to bring it back to the continent and there would be no visibility externally of
this.<u></u><u></u></span></li></ol>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">That being said – the clause in 5.4.6.2 is also pretty ambiguous – since I could easily argue that I could number an entire network in Europe or elsewhere without numbering customers
– carry transit across that network and then back into Africa – and state that the space is solely supporting connectivity back to Africa. In the same way I could number an entire branch office off continent and then have that branch office communicating
back to an African branch – and claim the same thing. Hence, I’m not really convinced that 5.4.6.2 is even really realistically enforceable – it is all a matter of perspective.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Just my thoughts<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Andrew<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="en-KE"><u></u> <u></u></span></p>
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(225,225,225) currentcolor currentcolor;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Ronald F. Guilmette <<a href="mailto:rfg@tristatelogic.com" rel="noreferrer noreferrer" target="_blank">rfg@tristatelogic.com</a>>
<br>
<b>Sent:</b> Monday, 1 July 2019 04:31<br>
<b>To:</b> <a href="mailto:rpd@afrinic.net" rel="noreferrer noreferrer" target="_blank">rpd@afrinic.net</a><br>
<b>Subject:</b> [rpd] Legacy holders?<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Sorry all. Just two quick rudimentary questions...<br>
<br>
1)<br>
According to this page:<br>
<br>
<a href="https://afrinic.net/membership/legacy-resource" rel="noreferrer noreferrer" target="_blank">https://afrinic.net/membership/legacy-resource</a><br>
<br>
"There are currently around 350 legacy resources holders<br>
registered in the AFRINIC WHOIS database."<br>
<br>
Is there a simple list of these organizations anywhere? Or does<br>
one have go and do tedious data mining on the entire Afrinic<br>
WHOIS data base in order to just find the names of all of these?<br>
<br>
2)<br>
Within the WHOIS data base what will be the org-type: value<br>
for any one of the legacy organizations?<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" rel="noreferrer noreferrer" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" rel="noreferrer noreferrer" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div></div>
</div></div></div></div>