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

[rpd] Inter-RIR transfer Policy

JORDI PALET MARTINEZ jordi.palet at consulintel.es
Thu Oct 22 13:27:14 UTC 2020


This requires a clarification …. (as author of LACNIC policy).



In order to allow reciprocity with all the regions in LACNIC only “incoming” legacy lose the legacy status. In the outgoing direction, it is up to the other RIR policies, as it should be.



https://politicas.lacnic.net/politicas/detail/id/LAC-2019-1/language/en



You can see the text in English at (note that may be translation mistakes, the original text valid in LACNIC is always the Spanish version in case of discrepancies):



2.3.2.18.10.- Legacy resources transferred into the LACNIC region will no longer be considered legacy resources.





I’m taking the opportunity to respond to Jako. *All* what you’re are asking for is already in the other policy proposal, with a language that is clear and has been confirmed as reciprocal and compatible by the other RIRs:



https://www.afrinic.net/policy/proposals/2019-ipv4-002-d4?lang=en-GB#proposal



The discussion against was based on:
The ASN part (5.7.4), despite that it was included in order to conform with the staff PIER, which was asking for that. So, we want to follow staff recommendations or not? I’m fine if we make the ASN a totally different proposal, no issue.
Provisions for suspensions, which was requested by the community in the previous version. In my opinion this was not needed at all, because the board can do that according to the bylaws, but the community asked to have explicit. Then some guys in the community said, it not needed. This is part of the problem, we are not “stable” in our own community views.


If we remove both of those points, then we have exactly what is needed. That’s why it is very unfair that the chairs allowed changes in only one of the 3 proposals, if doing similar “editorial changes” (in the view of the chairs) could have also accommodated the consensus.



That’s why it is unfair to allow changes in the last call to one of the proposals and not the others. If you declare the consensus on the 3 proposals depending on the last call changes, what will be the result?



Regards,

Jordi

@jordipalet







El 22/10/20 15:12, "Fernando Frediani" <fhfrediani at gmail.com> escribió:



On 22/10/2020 07:16, Jaco Kroon wrote:

2. Other RIRs (ARIN as I understand) allow legacy space to retain legacy status, and as such, in order to allow outbound transfers of legacy space to those RIRs we must allow those transfers to retain legacy status.

In LACNIC IP space looses its legacy status and still it is perfectly possible to transfer in and out from ARIN. That's not a justification to keep this historical mistake of the internet still alive.

Fernando



_______________________________________________
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



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20201022/22f73474/attachment-0001.html>


More information about the RPD mailing list