<div><div dir="auto"><br></div><br><div class="gmail_quote"><div dir="auto">On Thu, Sep 7, 2017 at 20:53 Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wouldn’t it make the most sense for the RSA to eliminate all language referencing<br>
resource management directly and instead include language to the effect of:<br>
<br>
This RSA is subject to the community developed consensus policies contained in<br>
the consolidated policy manual which is incorporated here by reference. This<br>
agreement shall be considered amended in accordance to each subsequent change<br>
to those policies and the signatories accept in advance all such amendments<br>
as determined appropriate by the consensus of the community and ratified by<br>
the AfriNIC board.<br>
<br>
Please feel free to word-smith or improve upon the general idea above, but I believe<br>
this would create a long-term solution to the issues of the RSA while still preserving<br>
the policy supremacy and keeping the policy control in the hands of the current process.<br>
<br>
Owen</blockquote><div dir="auto"><br></div><div dir="auto">+1</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> On Aug 31, 2017, at 20:10 , David Hilario <<a href="mailto:d.hilario@laruscloudservice.net" target="_blank">d.hilario@laruscloudservice.net</a>> wrote:<br>
><br>
> On 31 August 2017 at 23:18, Noah <<a href="mailto:noah@neo.co.tz" target="_blank">noah@neo.co.tz</a>> wrote:<br>
>><br>
>><br>
>> On Thu, Aug 31, 2017 at 12:39 PM, Alan Barrett <<a href="mailto:alan.barrett@afrinic.net" target="_blank">alan.barrett@afrinic.net</a>><br>
>> wrote:<br>
>>><br>
>>><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.<br>
>>>> Too sensitive.<br>
>>><br>
>>> The legal adviser has provided advice to me on many occasions. When I try<br>
>>> to summarise his advice, I may make mistakes in minor details, but I am not<br>
>>> making a mistake about the main point: The current RSA prohibits transfers<br>
>>> (except for mergers and acquisitions), and removing that prohibition will<br>
>>> require changing the RSA.<br>
>><br>
>><br>
>><br>
>> Remove the prohibitions to transfers to allow only specific transfers which<br>
>> are "IPv4 Resources transfer within the AFRINIC Region".<br>
>><br>
>><br>
>><br>
>>><br>
>>>> RSA is the contractual agreement which introduce and enforce policies<br>
>>>> 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<br>
>>>> the policies supersede the RSA which depends on them and as much as we<br>
>>>> members are subjected to the RSA, policies reign supreme.<br>
>>><br>
>>> The policies express the will of the community. The RSA is a legal<br>
>>> agreement. If the will of the community conflicts with the RSA, then the<br>
>>> community will expext the RSA to be changed. That’s what’s about to happen.<br>
>><br>
>><br>
>><br>
>> The changes have to be specific to the will of the community in this case<br>
>> "IPv4 Resources transfer within the AFRINIC Region" and not generic transfer<br>
>> or any other transfers.<br>
>><br>
>><br>
>>><br>
>>>>> The RSA also has a clause that says "except in the event of The<br>
>>>>> Applicant becoming the subject of merger and/or acquisition proceedings, the<br>
>>>>> transfer of number resources is strictly prohibited”. Even if there’s a<br>
>>>>> policy that allows transfers, the RSA prohibits transfers, and the member<br>
>>>>> 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<br>
>>>> member can transfer, then policy overrides any provisions of the RSA with<br>
>>>> regards to this aspect.<br>
>>><br>
>>> “This agreement is subject to policies” means “policies can add additional<br>
>>> restrictions”; it does not mean that policies can remove restrictions.<br>
>><br>
>><br>
>><br>
>> I am not sure I understood your statement above and disclaimer: 'as much as<br>
>> am not a lawyer', and others in the community could advice but "subject to"<br>
>> means... conditional and being dependent upon something... see [1] [2]<br>
>><br>
>> Therefore IMHO, RSA is subject to policies and that would mean in this case,<br>
>> subject to specifically the ratified policies only, and for this case the<br>
>> AFPUB-2016-V4-003 "IPv4 Resources transfer within the AFRINIC Region".<br>
>><br>
>> So the modification and wording of the updated RSA, ref: transfers , should<br>
>> be specific to this policy to avoid creating loopholes using the word<br>
>> "transfer" as the only tranfers allowed per policy will be<br>
>> Intra/within/inside Afrinic service region and nothing else.<br>
>><br>
>><br>
><br>
> Using this logic, we would still be using the RSA as a resource<br>
> management document and Policy enforcement.<br>
> We would basically never get rid of the initial problem.<br>
><br>
> The RSA being a legal document and not a community document, it should<br>
> only describe the legal premise of signing up with the AFRINIC and not<br>
> get involved into the resource management.<br>
><br>
> Implying that removing this restriction would allow inter-RIR transfer<br>
> is a bit far fetched, plus as far as I know, all RIRs have something<br>
> in the lines that they can only do inter-RIR transfers with RIR who<br>
> have a compatible inter-RIR transfer policy, no policy at AFRINIC,<br>
> means no transfers to or from other RIR.<br>
><br>
> Don't manage resources through the RSA, that would even be<br>
> incompatible with other RIR, manage resources through policies.<br>
><br>
> Following your logic, we would remain in a perpetual problem, and the<br>
> RSA will be in need of updates at any future policy update that<br>
> touches any resource topics that are in the RSA.<br>
><br>
>>><br>
>>>> In fact, how is this different from the current situation?<br>
>>>><br>
>>>> 1. RSA set default rules ( prohibits transfers) and bind members to<br>
>>>> policies<br>
>>>> 2. Members sign RSA<br>
>>>> 3. RSA states Policies supremacy<br>
>>>> 4. Policy allows certain transfer (intra region only) and states rules<br>
>>>> and conditions<br>
>>><br>
>>> But your point 3 does not apply. Perhaps it might be useful to say<br>
>>> something like that in a future version of the RSA, but it’s not in the<br>
>>> current RSA.<br>
>>><br>
>><br>
>> Why future versions of RSA. If current is being updated to reflect other<br>
>> changes, then add that there.<br>
>><br>
>> Cheers,<br>
>> Noah<br>
>><br>
>> [1] <a href="https://definitions.uslegal.com/s/subject-to/" rel="noreferrer" target="_blank">https://definitions.uslegal.com/s/subject-to/</a><br>
>><br>
>> [2] <a href="http://thelawdictionary.org/subject-to/" rel="noreferrer" target="_blank">http://thelawdictionary.org/subject-to/</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> RPD mailing list<br>
>> <a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br>
>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
>><br>
> David Hilario<br>
><br>
> IP Manager<br>
><br>
> Larus Cloud Service Limited<br>
><br>
> p: +852 29888918 m: +359 89 764 1784<br>
> f: +852 29888068<br>
> a: Flat B5, 11/F, TML Tower, No.3 Hoi Shing Road, Tsuen Wan, HKSAR<br>
> w: <a href="http://laruscloudservice.net" rel="noreferrer" target="_blank">laruscloudservice.net</a><br>
> e: <a href="mailto:d.hilario@laruscloudservice.net" target="_blank">d.hilario@laruscloudservice.net</a><br>
><br>
> _______________________________________________<br>
> RPD mailing list<br>
> <a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>--<br>Kind regards.<br>Lu<br><br></div></div></div>