Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] Revised Proposal | Resource Transfer Policy (Draft-2)

Fernando Frediani fhfrediani at gmail.com
Thu Aug 20 03:09:10 UTC 2020


I have the same view that the proposal is not yet well worded and it is
not correct to impose policies of the receiving RIR to the source
transfers, which should be bound to the origin RIR. The policies that
matter most at the end are the ones of the destination RIR where the
resources will be registered after the transfer is successful.
Also in 5.7.3.2 it is not correct to allow the source entities to remain
eligible to receive further IPv4 form AfriNic. It the source entity is
giving up space it means it doesn't need anymore and it it is not
correct that it can receive more space from AfriNic at least at some
point in time.

Lastly one thing that lacks is the publishing of the successful
transfers by AfriNic in order to give publicity to all community.

Regards
Fernando


On 18/08/2020 16:30, Owen DeLong wrote:

> None of the changes address any of my previous comments, so they all

> still stand and are included

> here by reference.

>

> In this version 5.7.3.1 is irrational

>

> In every other RIR, the source of a transfer is required to be in

> compliance with the policies of the source RIR.

> It does not make sense to impose the policies of the receiving RIR on

> the source of a transfer.

>

> 5.7.4.1 is absurdly worded as a meandering run-on sentence. Instead, I

> propose:

>

> 5.7.4.1Transfer recipients in the AFRINIC region must demonstrate

> need according to existing

>

> AFRINIC policies in the same manner as if the resources

> were to be received from

> the AFRINIC free pool. Transfer recipients in another RIR

> must comply with the

> recipient policies of that RIR.

>

>

> 5.7.4.3 is bolded, yet it contains the exact same language as the

> existing policy.

>

> 5.7.5 attempts to invent a new process wheel and is overly specific

> about the actions required. I suggest

> that we leave this issue to staff as an implementation detail and

> business practice and that they work

> with the other RIRs which have well established and well functioning

> processes for these transfers

> already. There is no need to reinvent the wheel. It is perfectly round

> and rolls nicely in 4 RIRs already.

>

> Owen

>

>> On Aug 18, 2020, at 00:57 , Moses Serugo <moses.serugo at gmail.com

>> <mailto:moses.serugo at gmail.com>> wrote:

>>

>> Hello PDWG Members,

>>

>> We have received a new version of policy Proposal - Resource Transfer

>> Policy (Draft-2)/AFPUB-2019-V4-003-DRAFT02from authors Anthony

>> Ikechukwu Ubah and Taiwo Oyewande. The proposal contents are

>> published at: https://afrinic.net/policy/proposals/2019-v4-003-d2

>>

>> Please take some time to go through the proposal contents and provide

>> your feedback.

>>

>> Regards,

>>

>> Moses Serugo

>>

>> PDWG  Co-Chair.

>> _______________________________________________

>> RPD mailing list

>> RPD at afrinic.net <mailto:RPD at afrinic.net>

>> https://lists.afrinic.net/mailman/listinfo/rpd

>

>

> _______________________________________________

> RPD mailing list

> RPD at afrinic.net

> https://lists.afrinic.net/mailman/listinfo/rpd

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20200820/5f5f2eb1/attachment-0001.html>


More information about the RPD mailing list