<div dir="auto"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 31, 2017 at 12:39 PM, Alan Barrett <span dir="ltr"><<a href="mailto:alan.barrett@afrinic.net" target="_blank">alan.barrett@afrinic.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="m_-5805387322357970349m_-3454443274868871386gmail-m_58914299128395811m_4948272609750985334m_-4996482076122422400gmail-"><br>
> On 25 Aug 2017, at 16:02, Noah <<a href="mailto:noah@neo.co.tz" target="_blank">noah@neo.co.tz</a>> wrote:<br>
> We should get the Legal Counsel to also look at the matter and advise. Too sensitive.<br>
<br>
</span>The legal adviser has provided advice to me on many occasions. When I try to summarise his advice, I may make mistakes in minor details, but I am not making a mistake about the main point: The current RSA prohibits transfers (except for mergers and acquisitions), and removing that prohibition will require changing the RSA.<br></blockquote><div><br></div><div dir="auto"><br></div><div>Remove the prohibitions to transfers to allow only specific transfers which are "IPv4 Resources transfer <b>within</b> the AFRINIC Region". <br></div><div dir="auto"><br></div><div dir="auto"><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="m_-5805387322357970349m_-3454443274868871386gmail-m_58914299128395811m_4948272609750985334m_-4996482076122422400gmail-"><br>
> RSA is the contractual agreement which introduce and enforce policies and has clearly solved cases of conflict between itself and policies.<br>
> What I am trying to say is that we have to be mindful of the fact that the policies supersede the RSA which depends on them and as much as we members are subjected to the RSA, policies reign supreme.<br>
<br>
</span>The policies express the will of the community. The RSA is a legal agreement. If the will of the community conflicts with the RSA, then the community will expext the RSA to be changed. That’s what’s about to happen.<br></blockquote><div><br></div><div dir="auto"><br></div>The changes have to be specific to the will of the community in this case "IPv4 Resources transfer within the AFRINIC Region" and not generic transfer or any other transfers. <br><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="m_-5805387322357970349m_-3454443274868871386gmail-m_58914299128395811m_4948272609750985334m_-4996482076122422400gmail-"><br>
>> The RSA also has a clause that says "except in the event of The Applicant becoming the subject of merger and/or acquisition proceedings, the transfer of number resources is strictly prohibited”. Even if there’s a policy that allows transfers, the RSA prohibits transfers, and the member has agreed to follow the RSA, so the member may not make a transfer.<br>
><br>
> This is not valid if the RSA is subject to policies. If policies say member can transfer, then policy overrides any provisions of the RSA with regards to this aspect.<br>
<br>
</span>“This agreement is subject to policies” means “policies can add additional restrictions”; it does not mean that policies can remove restrictions.<br></blockquote><div><br></div><div dir="auto"><br></div><div>I am not sure I understood your statement above and disclaimer: 'as much as am not a lawyer', and others in the community could advice but "<b>subject to</b>" means... <span style="background-color:rgb(255,255,255);color:rgb(51,51,51);font-family:"open sans",sans-serif;font-size:17px">conditional and being dependent upon something... see [1] [2] </span></div><div dir="auto"><br></div><div>Therefore IMHO, RSA is subject to policies and that would mean in this case, subject to specifically the ratified policies only, and for this case the AFPUB-2016-V4-003 "IPv4 Resources transfer within the AFRINIC Region". <br></div><div><br></div><div>So the modification and wording of the updated RSA, ref: transfers , should be specific to this policy to avoid creating loopholes using the word "transfer" as the only tranfers allowed per policy will be Intra/within/inside Afrinic service region and nothing else.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="m_-5805387322357970349m_-3454443274868871386gmail-m_58914299128395811m_4948272609750985334m_-4996482076122422400gmail-"><br>
> In fact, how is this different from the current situation?<br>
><br>
> 1. RSA set default rules ( prohibits transfers) and bind members to policies<br>
> 2. Members sign RSA<br>
> 3. RSA states Policies supremacy<br>
> 4. Policy allows certain transfer (intra region only) and states rules and conditions<br>
<br>
</span>But your point 3 does not apply. Perhaps it might be useful to say something like that in a future version of the RSA, but it’s not in the current RSA.<br>
<div class="m_-5805387322357970349m_-3454443274868871386gmail-m_58914299128395811m_4948272609750985334m_-4996482076122422400gmail-HOEnZb"><div class="m_-5805387322357970349m_-3454443274868871386gmail-m_58914299128395811m_4948272609750985334m_-4996482076122422400gmail-h5"><br></div></div></blockquote><br></div><div class="gmail_quote">Why future versions of RSA. If current is being updated to reflect other changes, then add that there.<br></div><br></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra">Noah<br></div><div class="gmail_extra" dir="auto"><br></div><div class="gmail_extra" dir="auto"><div dir="auto" style="font-family:sans-serif">[1] <a href="https://definitions.uslegal.com/s/subject-to/">https://definitions.uslegal.<wbr>com/s/subject-to/</a></div><div dir="auto" style="font-family:sans-serif"><br></div><div dir="auto" style="font-family:sans-serif">[2] <a href="http://thelawdictionary.org/subject-to/">http://thelawdictionary.org/subject-to/</a><br></div><br></div></div></div>