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

[rpd] Proposal Update received: AFRINIC Number Resources Transfer Policy

Taiwo Oyewande taiwo.oyewande88 at gmail.com
Wed Nov 20 16:48:42 UTC 2019


Hi Alain,

Thanks for your reply. As you mentioned correctly, I raised this again, the wordings are still not clear and to me, the problem remains unaddressed. Maybe rewording the document will give a better read and understanding.

Kind regards
Taiwo


> On 19 Nov 2019, at 03:16, Owen DeLong <owen at delong.com> wrote:

>

>

>

>> On Nov 18, 2019, at 06:53 , ALAIN AINA via RPD <rpd at afrinic.net> wrote:

>>

>> Hello,

>>

>> Thanks Taiwo for raising this again and thanks to those who contributed to the discussion and proposed text.

>>

>> Raising this again, meant that the answers I provided last time did not have the expected effect.

>>

>> You may remember that in my combined response(*) of 3 September 2019, I provided the following response to issue #7:

>>

>> ######

>> 7- FTTH, Cloud... etc providers no longer able to make assignments without afrinic approval

>>

>> The sub-allocations and assignments by LIRs are not transfers... these organizations do not need approval from AFRINIC to register assignments in the database and the process for sub-allocations is known.

>>

>> This policy does not change these practices

>

> As it is written, it’s not clear that is the case.

>

> Suggest you clean up the language to make this clear in the policy proposal.

>

>> ########

>>

>> This is a proposed transfer policy and not an allocation/assignment policy. As you can see the transfer policy does not amend the current allocation/assignment policies (section 5.0 of the CPM). It only obsoletes section 5.7

>>

>> The text under discussion, shown below, is to explicitly prevent people from considering unapproved private change of right of use and ownership of resources held by members (allocated PA, assigned PI, assigned ASN) and LIR assignments to users (assigned PA) as legitimate transfers.

>>

>> Hope this clarifies

>>

>> -Alain

>>

>>>> In section 2.0: "Number resources are non-transferable and are not assignable to any other organization unless AFRINIC has expressly and in writing approved a request for transfer. AFRINIC is tasked with making prudent decisions on whether to approve the transfer of number resources".

>>

>> (*) https://lists.afrinic.net/pipermail/rpd/2019/009975.html

>>

>>

>>> On 12 Nov 2019, at 15:13, Taiwo Oyewande <taiwo.oyewande88 at gmail.com> wrote:

>>>

>>> Hi all,

>>>

>>> This policy seems unrealistic with the amount of assignments of network resources which takes place daily

>>>

>>> In section 2.0:

>>> "Number resources are non-transferable and are not assignable to any other organization unless AFRINIC has expressly and in writing approved a request for transfer. AFRINIC is tasked with making prudent decisions on whether to approve the transfer of number resources".

>>>

>>> Assignment takes place on a regular basis between business and business, and business and end-user. If all of these assignments need AFRINIC's approval, It will be an herculean task if not impossible for AFRINIC to manage such massive amount of assignment.

>>> For instance, if every assignment approval takes 2-3 days (maybe even way longer!), this means during the "pre-approval period" businesses and end-users will not have the resource they need for daily operations.

>>>

>>> People get IP to assign to customers by its very definition. To be frank, I think this policy is unpractical, thus I hereby oppose it.

>>>

>>> Regards

>>>

>>>

>>> _______________________________________________

>>> RPD mailing list

>>> 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

>

>

> _______________________________________________

> RPD mailing list

> RPD at afrinic.net

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




More information about the RPD mailing list