Interpretación de la propuesta por el staff de LACNIC
-----------------------------------------------------
Aplicación de la propuesta
---------------------------
Esta propuesta se aplicaría en los casos de fusiones, adquisiciones, reorganizaciones y reubicaciones para organizaciones que tienen asignados ASNs.
Modificación del texto actual
-----------------------------
Se agregaría en el Manual de Políticas una nueva sección 3.3. ASN Fusiones, adquisiciones, reorganizaciones y reubicaciones:
Se recuerda que las políticas de LACNIC no reconocen la venta o transferencia no autorizada de los recursos asignados o distribuidos y considerará tales transferencias inválidas.
Sin embargo, LACNIC procesará y registrará la transferencia de recursos ASN como resultado de fusiones, adquisiciones, reorganizaciones o reubicaciones, ya sean parciales o completas, tanto si se trata de recursos de ISPs o usuarios finales.
Para tramitar dicho cambio y proceder al registro, se deberá proporcionar documentación legal que lo respalde a criterio de LACNIC, por ejemplo:
o Una copia del documento legal que respalda las transferencias de activos.
o Un inventario detallado de todos los activos utilizados por el solicitante con el cual mantendrá en uso el espacio el recurso.
o Una lista de los clientes de la parte solicitante que usa los recursos.
Se deberá justificar también que sigue manteniéndose la necesidad del conjunto de los recursos, obligándose si fuera el caso, al retorno de los excedentes de los mismos o alternativamente a su transferencia a terceras partes, atendiendo a lo que corresponda según las políticas vigentes (3.). En el caso de un retorno, LACNIC determinará las condiciones y plazo.
Comentarios del staff
----------------------
(Los comentarios son observaciones para ayudar a diferenciar los cambios que presenta la propuesta con respecto al texto actual del Manual de Políticas)
Actualmente existe en el Manual de Políticas un texto para uniones y adquisiciones únicamente en la sección “2. Direcciones IPv4”. Si bien a nivel de implementación al realizar una unión o adquisición se fusionan todos los recursos de una organización, LACNIC entiende que con esta propuesta quedará más prolijo y claro en el Manual para cada tipo de recurso.
Esta propuesta es muy similar a la propuesta 2019-2 (para IPv4) y 2019-3 (para IPv6).
Respecto a la versión 2, no cambia el texto de la propuesta. Se agrega en la justificación la aclaración de que "todos los casos son válidos (tanto para intra como inter-RIR).
Recomendaciones
-------------------
En el manual de políticas se describen “las políticas y procedimientos asociados con la distribución, asignación y administración del espacio de direcciones IPv4, IPv6, ASN y la delegación del espacio de resoluciónn inversa asignados a Latinoamérica y el Caribe”. Por ende, LACNIC interpreta que el manual se refiere a políticas dentro de la región. Las políticas que se refieren situaciones particulares fuera de la región, como ser la 2.3.2.18 se lo menciona específicamente. Por lo cual se recomienda mencionar que esta política es inter-RIR en el texto de la propuesta, debido a que la justificación no queda documentada en el manual.
Fuentes oficiales de referencias
---------------------------------
Situación en otros RIRs
----------------------
- RIPE NCC
RIPE NCC no reconoce el término “Inter-RIR merger” y aceptaría todas las transferencias de recursos numéricos siempre que cumplan con las políticas de transferencias en la región correspondiente. Con respecto a las transferencias de recursos de RIPE NCC hacia otra región, RIPE NCC se regirá por las políticas que apliquen a la región a la cual se transferirá el recurso.
Actualmente hay una propuesta en discusión desde marzo del 2017: https://www.ripe.net/publications/docs/ripe-682
- APNIC
APNIC no permite la transferencia de recursos entre RIRs como resultado de “Mergers and acquisitions”.
Actualmente hay una propuesta similar en discusión: https://www.apnic.net/wp-content/uploads/2019/03/prop-130-v001.txt
-ARIN
Actualmente las políticas de ARIN no serían compatibles porque las propuestas son únicamente para fusiones, adquisiciones, reorganizaciones y reubicaciones. Si LACNIC tuviera políticas de transferencia inter-RIR totalmente recíproca con una justificación basada en las necesidades, sería compatible con ARIN. Sin embargo, las restricciones sobre qué tipos de recursos (solo legados, por ejemplo), o tipos de transferencias (solo M&A, por ejemplo), hacen que no sea recíproca política.
ARIN procesa las transferencias Inter-RIR salientes de acuerdo con la Sección 8.4, Transferencias de destinatarios específicos.
-AFRINIC
(a confirmar)
Implementación de la propuesta
--------------------------------
Si esta propuesta llega a consenso podrá ser implementada en forma inmediata para los casos intra-RIR y para los casos inter-RIR será implementada una vez que haya sido implementada la política de transferencias inter-RIR.
ASN Mergers, Acquisitions, Reorganizations and Relocations
Rationale (Describe the problem you intend to solve)The merger, acquisition, reorganization or relocation of companies or parts of companies is a common occurrence in the Internet and technology sector, among operators and other businesses.
This is also true for other types of organizations and sectors, all of them end-users of the RIRs.
These cases are not covered by the existing policy, although they are covered in the case of IPv4. It would not make sense to update IPv4 records but not ASN records for this type of business operations.
This proposal seeks to simplify the text and clarify that all cases are valid. It also proposes leaving the supporting documentation up to the staff, as such documentation will not necessarily be the same in every case.
Likewise, the proposal clarifies that mergers, acquisitions, reorganizations and relocations may be either within the LACNIC service region or between different service regions (intra- and inter-RIR changes).
Current textCurrent text
No such text exists.
---
New text:
Mergers, Acquisitions, Reorganizations or Relocations
LACNIC will process and register any transfer of ASN resources that occurs as a result of a partial or complete, intra- or inter-RIR merger, acquisition, business reorganization or relocation, regardless of whether the resources are held by ISPs or end-users.
To initiate this change and proceed with the registration, legal documentation supporting the operation shall be provided. Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.
New textCurrent text
No such text exists.
---
New text:
Mergers, Acquisitions, Reorganizations or Relocations
LACNIC will process and register any transfer of ASN resources that occurs as a result of a partial or complete, intra- or inter-RIR merger, acquisition, business reorganization or relocation, regardless of whether the resources are held by ISPs or end-users.
To initiate this change and proceed with the registration, legal documentation supporting the operation shall be provided. Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.
Additional informationThe numbering of the proposed text within the corresponding section of the Policy Manual will be decided by LACNIC.
TimetableImmediate implementation
ReferencesSimilar policies with varying levels of “openness” exist in other service regions such as ARIN and RIPE.
In addition, an equivalent policy proposal has been submitted in APNIC and another proposal is being prepared for AfriNIC.
• https://www.ripe.net/publications/docs/ripe-682
• https://www.arin.net/policy/nrpm.html#eight2
-
This proposal establishes the mechanism that allows updating ASN resource records in case of mergers, acquisitions, reorganizations and relocations
Rationale (Describe the problem you intend to solve)The merger, acquisition, reorganization or relocation of companies or parts of companies is a common occurrence in the Internet and technology sector, among both operators and other businesses.
This is also true for other types of organizations and sectors, all of them end-users of the RIRs.
These cases are not covered by the existing policy, although they are covered in the case of IPv4. It would not make sense to update IPv4 records but not ASN records for this type of business operations.
This proposal seeks to simplify the text and clarify that all cases are valid. It also proposes leaving the supporting documentation up to the staff, as such documentation will not necessarily be the same in every case.
Current textCurrent text
No such text exists.
---
New text
Mergers, Acquisitions, Reorganizations or Relocations
Because LACNIC's policies do not recognize the non-authorized sale or transfer of assigned or allocated resources, such transfers will be considered invalid.
Nevertheless, LACNIC will process and register any ASN resource transfer that occurs as a result of a partial or complete merger, acquisition, business reorganization or relocation, regardless of whether the resources are held by an ISP or an end-user.
To initiate this change and proceed with the registration, legal documentation must be submitted which, at the discretion of LACNIC, supports the operation. Examples of such documentation include:
• A copy of the legal document validating the transfer of assets.
• A detailed inventory of all the assets used by the applicant for maintaining the resources in use.
• A list of the applicant's clients using the resources.
The need to maintain all the resources must also be justified, forcing the return of the surplus resources if applicable or, alternatively, the transfer of such surplus resources to third parties under the policies in force (3.). When resources are to be returned, LACNIC will determine the corresponding conditions and deadline.
New textCurrent text
No such text exists.
---
New text
Mergers, Acquisitions, Reorganizations or Relocations
Because LACNIC's policies do not recognize the non-authorized sale or transfer of assigned or allocated resources, such transfers will be considered invalid.
Nevertheless, LACNIC will process and register any ASN resource transfer that occurs as a result of a partial or complete merger, acquisition, business reorganization or relocation, regardless of whether the resources are held by an ISP or an end-user.
To initiate this change and proceed with the registration, legal documentation must be submitted which, at the discretion of LACNIC, supports the operation. Examples of such documentation include:
• A copy of the legal document validating the transfer of assets.
• A detailed inventory of all the assets used by the applicant for maintaining the resources in use.
• A list of the applicant's clients using the resources.
The need to maintain all the resources must also be justified, forcing the return of the surplus resources if applicable or, alternatively, the transfer of such surplus resources to third parties under the policies in force (3.). When resources are to be returned, LACNIC will determine the corresponding conditions and deadline.
Additional informationThe numbering of the proposed text within the corresponding section of the Policy Manual will be decided by LACNIC.
In extreme cases, the non-existence of this policy might result in this issue being taken to the courts if LACNIC refuses to update the registry for any type of resources, and, based on the legislation currently in force in Uruguay, the courts might force LACNIC to modify the registry. We believe that having this policy would avoid this situation and allows maintaining control according to the wishes of the community. It would also avoid legal costs to both parties involved.
TimetableImmediate implementation
ReferencesSimilar policies with varying levels of “openness” exist in other service regions such as ARIN and RIPE.
In addition, an equivalent policy proposal has been submitted in APNIC and another proposal is being prepared for AfriNIC.
• https://www.ripe.net/publications/docs/ripe-682
• https://www.arin.net/policy/nrpm.html#eight2
LACNIC 31 (06/05/2019)
This proposal establishes the mechanism that allows updating ASN resource records in case of mergers, acquisitions, reorganizations and relocations
Rationale (Describe the problem you intend to solve)The merger, acquisition, reorganization or relocation of companies or parts of companies is a common occurrence in the Internet and technology sector, among both operators and other businesses.
This is also true for other types of organizations and sectors, all of them end-users of the RIRs.
These cases are not covered by the existing policy, although they are covered in the case of IPv4. It would not make sense to update IPv4 records but not ASN records for this type of business operations.
This proposal seeks to simplify the text and clarify that it is only for the Intra-RIR case. It also proposes leaving the supporting documentation up to the staff, as such documentation will not necessarily be the same in every case.
Current textNo such text exists.
New textMergers, Acquisitions, Reorganizations or Relocations
Because LACNIC's policies do not recognize the non-authorized sale or transfer of assigned or allocated resources, such transfers will be considered invalid.
Nevertheless, LACNIC will process and register any ASN resource transfer that occurs as a result of a partial or complete merger, acquisition, business reorganization or relocation, regardless of whether the resources are held by an ISP or an end-user.
To initiate this change and proceed with the registration, legal documentation must be submitted which, at the discretion of LACNIC, supports the operation. Examples of such documentation include:
• A copy of the legal document validating the transfer of assets.
• A detailed inventory of all the assets used by the applicant for maintaining the resources in use.
• A list of the applicant's clients using the resources.
The need to maintain all the resources must also be justified, forcing the return of the surplus resources if applicable or, alternatively, the transfer of such surplus resources to third parties under the policies in force (3.). When resources are to be returned, LACNIC will determine the corresponding conditions and deadline.
Additional informationThe numbering of the proposed text within the corresponding section of the Policy Manual will be decided by LACNIC.
In extreme cases, the non-existence of this policy might result in this issue being taken to the courts if LACNIC refuses to update the registry for any type of resources, and, based on the legislation currently in force in Uruguay, the courts might force LACNIC to modify the registry. We believe that having this policy would avoid this situation and allows maintaining control according to the wishes of the community. It would also avoid legal costs to both parties involved.
TimetableImmediate implementation
ReferencesSimilar policies with varying levels of “openness” exist in other service regions such as ARIN and RIPE.
In addition, an equivalent policy proposal has been submitted in APNIC and another proposal is being prepared for AfriNIC.
• https://www.ripe.net/publications/docs/ripe-682
• https://www.arin.net/policy/nrpm.html#eight2
LACNIC 32 (06/10/2019)