Update to “Resource Recovery and Return” and consistency with the rest of the Manual

Original Language Español Date Published 12/07/2019 Last Modified 24/09/2019
Last Call for Comments Period Does not apply Date Ratified Does not apply Implementation Date Does not apply
Status Under discussion Download TXT PDF XML DOCX
See other versions 1.0 2.0 (compare)

Authors

Name: Jordi Palet Martinez
Email: jordi.palet@theipv6company.com
Organization: The IPv6 Company

Proposal Data

Policy Type: LACNIC
Id: LAC-2019-9
Last version: 2
Presented at: LACNIC 32 Presentations:

Summary

This proposal updates section 7 of the Policy Manual to “Resource Revocation and Return.” Discrepancies in the current wording are eliminated and consistency with the terminology used in the Service Agreement is introduced, clarifying that it applies to repeated and/or continued violations of the policies as well as to cases of fraud and non-payment.

Other items of the manual are also revised to avoid duplications and maintain consistency, avoiding the unnecessary revocation of resources in cases already noted as “problematic” on the list of potential improvements to existing policies (items 1, 8 and 10, see https://www.lacnic.net/561/1/lacnic/).

Rationale

The current text of Section 7 does not properly specify how to act in case of repeated policy violations. The wording is ambiguous and appears to be limited to non-payment.

Because they are not nearing exhaustion, it is reasonable not to immediately include returned IPv6 and ASN resources in the pool of available resources. Nevertheless, it would be convenient for such resources to be automatically added to the pool of available resources after a certain period of time (to allow operators to create the necessary filters, clean up the resources, etc.), thus avoiding the accumulation of resources in different pools that would require new policies.

In addition to introducing several editorial changes and unifying duplicate texts, or texts that is currently included for IPv4 bur also affects IPv6, the proposal clarifies different aspects, which might also be understood as editorial changes, and solves several items on the list of potential improvements.

Text

Current text

7. 7. Resource Recovery and Return

7.1. Resource Recovery

Seeking to achieve an efficient utilization of the resources assigned to the LAC region, LACNIC shall attempt to recover resources in order to re-assign them to organizations.

If there is evidence to suggest that the assigned resources are possibly not being utilized or are being incorrectly utilized, LACNIC shall verify with the organization that received the assignment whether the resource is being properly utilized.

The following are some of the evidences that LACNIC may use to initiate the resource recovery process:

• Lack of visibility of the resource on the global routing table.
• Breach of LACNIC policies.
• Breach of the provisions of the registration service agreement or other legal agreements between the organization hold ing the resource and LACNIC or one of its NIRs.
• Evidence that an organization has disappeared and its blocks have not been transferred. • Unauthorized transfers under the provisions of the policies.

The resource recovery process begins once LACNIC is in possession of the evidence mentioned above.

LACNIC shall attempt to contact the organization and rectify the situation.

Certain organizations exist that may have assignments that are being used but are not visible on the global routing table. If the organization can justify that this is the case, LACNIC shall consider this sufficient and the resource recovery process shall end.

If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months. During this period the organization may rectify the situation with LACNIC.

Two months after the resources are published, LACNIC shall proceed to delete the NS records pointing to the authoritative nameservers of the resources involved. This information may be recovered once the organization contacts LACNIC or the corresponding NIR.

If three months after the resources are published the organization has not rectified the situation, the resources shall be recovered and the records of the holders of these resources shall be removed from LACNIC’s database.

In those cases where the revocation of resources involves essential strategic infrastructure that is necessary for operating the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LACNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extraordinary situation is detected.

LACNIC shall publish the resources that have been recovered so that the routing filters may be modified.

LACNIC shall frequently attempt to identify resources that are capable of being recovered.

Any IPv4 resources recovered under this policy may only be assigned under the guidelines set forth in item 11.1 of the Policy Manual.

Assignment of recovered IPv4 resources will begin when, for the first time, it is not possible to perform an assignment from the IPv4 special reserve pool. Resources having an earlier recovery date shall be assigned first. Recovered IPv6 and ASN resources shall not be assigned until a new policy defines the appropriate time.

7.2. Resource Return

IPv4 resources returned under this policy may only be assigned under the guidelines set forth in section 11.1 of the Policy Manual. Assignment of returned IPv4 resources will begin when, for the first time, it is not possible to perform an assignment from the IPv4 special reserve pool. Resources having an earlier return date shall be assigned first. Returned IPv6 and ASN resources shall not be assigned until a new policy defines the appropriate time to do so.

2.3.2.9. Non-Guaranteed Routability

Portable (provider-independent) IPv4 addresses allocated by LACNIC or by an NIRs are not guaranteed to be globally routable.

These problems shall be solved between the holders of the IPv4 addresses involved and their connectivity provider or providers. In those cases deemed necessary, LACNIC shall provide the necessary guidance.

4.4.2. Non-Guaranteed Routability

Portable (provider-independent) IPv4 addresses allocated by LACNIC or by an NIRs are not guaranteed to be globally routable. However, RIRs must apply procedures that reduce the possibility of fragmented address space which may lead to a loss of routability.

1.11 Principles for Proper Administration and Stewardship

The numbering resources under the stewardship of LACNIC must be distributed among organizations legally incorporated within its service region and a majority* of the resources must be used to operate networks and provide services in this region. External clients connected directly to core infrastructure located in the region are allowed.

...

2.3.2.10. Validity of IPv4 Address Allocations

IPv4 address allocations are valid as long as the objectives of exclusivity, preservation, routability and information continue to be met. LACNIC may invalidate any IPv4 address allocation if it is determined that the requirements for IPv4 address space no longer exist or that any of the objectives stated in this document have ceased to be satisfied.

There are a number of practices that might be considered grounds for losing the allocations that have been received. These are:
o Failure to use the allocated IPv4 address space during a period of one month following registration.
o Failure to update the reverse resolution registry of the IPv4 address space.
o Failure to update the allocation and assignment information on LACNIC's Whois database.
o Failure to comply with contractual obligations towards LACNIC.
o Failure to correctly apply LACNIC's policies in relation to allocations and assignments and the administration of the resources received from LACNIC.

In the event of IPv4 address space invalidation, reasonable effort shall be made by LACNIC to inform the community that the IPv4 addresses have been returned and are once again available IPv4 address blocks.

2.3.2.11. Submission of Application Templates

IRs shall request IPv4 address space from LACNIC through address application templates for IRs or End Users. Any application deemed as lacking information or insufficiently detailed shall be returned to the applicant for its completion.

New text

7. Resource Revocation and Return

Resource allocations and assignments will remain valid as long as the objectives of exclusivity, preservation, routability, information, and the rest of the policies in general continue to be met.

Therefore, LACNIC may invalidate any allocation or assignment if it is determined that the requirements no longer exist or that the criteria set forth in the Policy Manual are no longer satisfied.

The following may be considered grounds for resource revocation:
o Unused or unannounced resources (where mandatory).
o Failure to maintain reverse resolution records for the assigned resources.
o Failure to update the allocation and assignment information on the whois database managed by LACNIC or the NIRs, as applicable.
o Unauthorized transfers.
o Repeated and/or continued policy violations.
o Failure to comply with contractual obligations towards LACNIC or its NIRs, including non-payment and document fraud.
o Organizations that have disappeared or fail to respond.

When the violation has been caused by a third party, without the knowledge of the organization receiving the resources, and if it is evident that there is no collusion or negligence on the part of said organization, the revocation process will not be initiated.

7.1. Resource Revocation Process

To ensure the efficient utilization of regional resources, LACNIC will verify that the organizations receiving resources are using such resources correctly. This will be done automatically whenever possible and more exhaustively when there is evidence to suggest that certain resources are not being used properly.

Once the evidence has been detected and confirmed, the resource recovery process will include the following steps:

a) LACNIC shall attempt to contact the organization and rectify the situation.

b) If the situation cannot be rectified, LACNIC shall publish the resources that are to be recovered for a maximum of three months.

During this period, the organization may rectify the situation with LACNIC.

c) In all other cases, two months after the resources are published, LACNIC shall proceed to delete the NS records pointing to the authoritative nameservers of the resources involved This information may be recovered once the organization reestablishes contact with LACNIC or with the corresponding NIR.

d) If three months after the resources are published the organization has not rectified the situation, the resources shall be recovered and the records of the holders of these resources shall be removed from LACNIC’s database.

e) All other provisions specified in the Registration Services Agreement and Bylaws shall apply.

7.2. Exceptions

When the revocation of resources involves essential strategic infrastructure that is necessary for the operation of the Internet in the region, or in exceptional situations such as natural disasters or political instability, the LACNIC Board of Directors may extend the resource revocation period, with prior assessment by the LACNIC Staff once such an exceptional situation is detected.

7.3. Resource Return

Resource recipients may return the resources to LACNIC, in full or in part, at any time.

If all the resources are returned, all the other provisions specified in the Registration Services Agreement and Bylaws shall apply.

7.4. Publishing Recovered and Returned Resources

LACNIC shall publish the resources that have been recovered or returned so that the corresponding routing filters may be updated.

7.5. Use of Recovered or Returned Resources

IPv4 resources will be added at the “end” of the pool in use at the moment of their recovery or return, and will be used in the order in which they have been added to the pool.

IPv6 and ASN resources will be added to their respective pools in force two years after their recovery or return.

However, LACNIC may use these resources differently, applying best best practices to optimize compliance with the provisions of section 2 of RFC7020. For example, if 16-bit ASNs are recovered or returned.”

(Sections 2.3.2.9 and 4.4.2 are unified and replaced by Section 1.12 and all affected sections are renumbered, as the resulting text is equally valid and necessary for allocations and assignments and for IPv4 and IPv6 addresses.)

1.11. Non-Guaranteed Routability

Neither LACNIC nor the NIRs will guarantee the routability of allocated or assigned addresses.

Resource recipients are responsible for negotiating such routability with their connectivity providers. LACNIC shall provide the corresponding guidance when necessary.

However, allocated or assigned resources must be announced within a maximum of 90 days, except in those cases where the need not to announce the resources is justified.

RIRs must apply operational procedures that reduce the possibility of fragmentation of the address space to minimize the risk of loss of routability.

(Section 4.4.2 is eliminated and subsequent sections are renumbered.)

1.12 Principles for Proper Administration and Stewardship

The numbering resources under the stewardship of LACNIC must be allocated to organizations legally incorporated within its service region and a majority* of the resources must be used to operate networks and provide services in this region. External clients connected directly to core infrastructure located in the region are allowed.

* “Majority” is understood to mean more than 50%.

Upon obtaining any type of resources from LACNIC or from the corresponding NIR, any legacy resources held by the recipient will no longer be considered legacy resources.

(This section is eliminated and the following sections are renumbered, as the text has become the introduction of section 7, for all resources.)

(This section becomes the last of section 1 and subsequent sections are renumbered, as they are mechanisms that apply to any type of resources.)

1.13. Resource Requests

Resource requests to LACNIC or to the corresponding NIRs will be made under the systems in force.

Any request that is considered incomplete will be returned to the applicant with the appropriate instructions so that it can be completed.

Additional Information

-

Timetable

-

References

• APNIC: Closure and recovery. https://www.apnic.net/community/policy/resources#4.2.-Closure-and-recovery
• ARIN: Resource Review. https://www.arin.net/participate/policy/nrpm/#12-resource-review
• RIPE: Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources. https://www.ripe.net/publications/docs/ripe-716

Public Comments by LACNIC Staff

LACNIC STAFF´S IMPACT ANALYSIS - Proposal LAC-2019-9 - versión 2

Interpretación de la propuesta por el staff de LACNIC
------------------------------------------------------

Aplicación de la propuesta
--------------------------
Esta propuesta se aplicaría a los casos de revocación y devolución de recursos.

Modificación del texto actual
Se modifican las secciones del manual de políticas:
- 7. Recuperación y devolución de recursos
- 7.1. Proceso de Revocación de recursos
- 7.2. Excepcionalidad
- 7.3. Devolución de recursos
- 7.4. Publicación de los recursos
- 7.5. Uso de recursos recuperados o devueltos
- 1.11 Principios para una buena administración/custodia
- las secciones 2.3.2.9. y 4.4.2 se unifican y se fusionan en la sección 1.11. Ruteabilidad no garantizada y se renumeran el resto de las secciones.
- Se elimina la sección 2.3.2.10. Validez de las distribuciones de direcciones IPv4 y se agrega en la sección 7. Además, se renumeran las secciones siguientes.
- Se mueve la sección 2.3.2.11. Envío del formulario de solicitud (y se renumeran las siguientes) a la sección 1.13. Solicitud de recursos.

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)

1. Esta propuesta modifica el título de “Recuperación y devolución de recursos” a “Revocación y devolución de recursos".

2. En la sección “7.1. Proceso de revocación de recursos”, de la propuesta:
a. Cuando se indica que “LACNIC verificará con las organizaciones que reciben recursos, el adecuado uso de los mismos, de forma automatizada periódicamente”
i. Al indicar “adecuado uso”, LACNIC interpreta que se refiere al cumplimiento de las políticas.
ii. LACNIC entiende por “forma automatizada”, un proceso que no resulte oneroso para LACNIC y que de manera rápida permita identificar posibles incumplimientos a las políticas.
iii. Se asume que la frecuencia de periódicamente queda a criterio de LACNIC dependiendo del aspecto a monitorear.

Independientemente de cualquier automatización y reiteración de la falla, LACNIC tiene la responsabilidad de utilizar el mejor criterio previo al inicio del proceso revocación.

b. Con respecto a la sección c) de la propuesta, LACNIC interpreta que la eliminación de los NS se realizará solamente si la organización no contesta. Esto se debe a que el autor lo explicó así de acuerdo al espíritu original de esa propuesta. De todas formas, esto no varía de cómo se procede actualmente.

3. En la sección 1.11. Principios de una buena administración/custodia:
La propuesta define qué se entiende como mayoritariamente: “*como más del 50%”, como fue publicado en la lista de mejoras https://www.lacnic.net/561/1/lacnic/.

4. En la sección 2.2.3. se extiende el plazo máximo para anunciar los recursos distribuidos o asignados de 30 a 90 días, como está publicado en la lista de mejoras https://www.lacnic.net/561/1/lacnic/.

5. Actualmente LACNIC revoca por incumplimiento de pago o si se presenta una denuncia con evidencia específica. Estos casos se gestionan sin mayores complicaciones: LACNIC se contacta con la parte involucrada y ésta intenta solucionar el incumplimiento lo más pronto posible. Sin embargo, en la implementación de un proceso de revocación automática LACNIC podría enfrentar litigios de entidades que pierdan recursos y que quieran mantenerlos, sosteniendo que los estarían utilizándolos de manera legítima.

6. La base de datos que utilizará LACNIC para el proceso automatizado dependerá del RIS (Routing Information Service) de RIPE.

7. En situaciones particulares en las que no está definido como actuar, LACNIC actuará de la forma que considere más correcta y conservadora.

8. La propuesta modifica la sección de las prácticas consideradas como causa para la pérdida de direcciones que actualmente aparecen en el manual en la sección “2.3.2.10. Validez de las distribuciones de direcciones IPv4”, y pasan a la sección “7. Revocación y devolución de recursos”. Además, en las prácticas modifica:
a. En el manual actualmente se indica: “No utilizar el espacio de direcciones IPv4 distribuidos en un período de un mes posterior al registro”.
En la propuesta se modifica a “Recursos no utilizados o anunciados (cuando sea obligatorio).”
Luego, en la sección 1.11. de la propuesta se indica que “ los recursos distribuidos o asignados deben ser anunciados en un plazo máximo de 90 días, salvo en aquellos casos en que se justifique la necesidad de no hacerlo”.
En resumen, se modifica el período máximo para que los recursos asignados sean anunciados de 30 a 90 días.
b. El texto actual indica “No cumplir con las obligaciones contractuales con LACNIC” y la propuesta agrega “No cumplir con las obligaciones contractuales con LACNIC o sus NIRs, según corresponda”.
c. La propuesta agrega como otra práctica: “De forma genérica, incumplimientos continuados y/o reiterados de políticas” y “Organizaciones que desaparecieron, o no responden”.
LACNIC interpreta que este punto no significa un cambio en la operativa con la que se tiene actualmente.
d. La propuesta elimina el texto “En el evento de invalidación de espacios de direcciones IPv4, LACNIC hará los esfuerzos para informar a la comunidad que las direcciones IPv4 han sido regresadas a los bloques disponibles de direcciones IPv4”.
e. La propuesta agrega “Cuando el incumplimiento ha sido causado por un tercero, sin conocimiento de la organización que recibe los recursos, y sea evidente que no hay connivencia ni negligencia por parte de dicha organización, no se completará el proceso de revocación”.

9. Respecto a la versión anterior:
a. En la sección 7.5. “Uso de recursos recuperados o devueltos“ se agrega “...Sin embargo, LACNIC podrá utilizar estos recursos de forma diferente, en aplicación de mejores prácticas, para un cumplimiento optimizado de lo indicado en la sección 2 del RFC7020. Por ejemplo, si se recuperan o devuelven ASN de 16 bits”, como se recomendó en el análisis de impacto.
b. En la sección 1.11. Principios para una buena administración/custodia, se agrega “Al obtener cualquier tipo de recursos de LACNIC o el NIR correspondiente, en caso de tener recursos legados, estos dejan de ser considerados legados.”
c. Se fusionan las secciones 2.3.2.9 y 4.4.2 en la sección 1.11. Ruteablidad no garantizada.
i. se agrega: “Los RIRs deben aplicar procedimientos operativos que reduzcan la posibilidad de fragmentación del espacio de direcciones, para minimizar riesgos de pérdida de ruteabilidad.
d. 2.3.2.11 pasa a 1.13 para que involucre a todo tipo de solicitud.

Recomendaciones
--------------------
10. En la sección “7.1. Proceso de revocación de recursos” y “7.3. Devolución de recursos” de la propuesta, se indica: “Se aplicarán el resto de estipulaciones indicadas en el Acuerdo de Servicios de Registro y Estatutos”.

El Manual de Políticas está destinado a la administración de los recursos numéricos de Internet, no entra dentro de su alcance temas con relación a la membresía ni al acuerdo de servicios.

Impacto en el sistema de registro
----------------------------------
Esta propuesta implicaría cambios en los sistemas para generar un mecanismo de validación automática y periódica.

Fuentes oficiales de referencias
--------------------------------

Políticas sobre el contacto de abuso en otros RIRs
--------------------------------------------------

- RIPE
En RIPE las políticas proporcionan algunas reglas de alto nivel para el retorno de los recursos.

En la política IPv4 para recursos a los LIR, se indican los motivos que podrían causar el cirerre de un LIR por RIPE NCC: https://www.ripe.net/publications/docs/ripe-725#9

Para recursos independientes (sin tener contacto directo con RIPE NCC), tienen una política donde se indican algunos de los requisitos contractuales para dichos recursos. El resto de los requisitos están en el contrato.

En base a estas políticas RIPE NCC ha desarrollado un procedimiento de cierre público y cancelación de registro que no es una política sino un procedimiento interno. No solo incluye estos requisitos de política, sino también los requisitos del acuerdo de servicio. Se puede ver parte de este procedimiento en: https://www.ripe.net/publications/docs/ripe-716#b

- APNIC
Las políticas de recuperación y devolución están en el documento de políticas en la sección 4.2 y 4.2.1:
https://www.apnic.net/community/policy/resources#4.2.-Closure-and-recovery

También se puede ver en la sección 8.0: “Durante ese tiempo, si la razón original para la solicitud no sigue siendo válida, los recursos deberán ser retornados a APNIC como se indica en la sección 4.0”.

- ARIN
Tiene un proceso de revocación y devolución de recursos pero no es una política, sino que está publicado como un procedimiento operativo: https://www.arin.net/resources/fees/returns/.

- AFRINIC
No tienen una política para la recuperación de recursos, sino que recuperan recursos para miembros que no pagan, ya que este es un asunto contractual.

Por otra parte, hay referencias a que si el propósito para el cual se solicitaron los recursos ha cambiado, entonces los recursos que ya no son válidos.

LACNIC STAFF´S IMPACT ANALYSIS - Proposal LAC-2019-9 - versión 1

LACNIC Staff's Interpretation of the Proposal
---------------------------------------------

Applicability
-------------
This proposal would apply to resource revocations and returns.

Modifications to the current text
--------------------------------
The proposal seeks to modify the following sections of the Policy Manual:
● 7.7. Resource Recovery and Return
● 7.1. Resource Revocation Process
● 7.2. Exceptions
● 7.3. Resource Return
● 7.4. Publishing Recovered and Returned Resources
● 7.5. Use of Recovered or Returned Resources
● 1.11 Principles for Proper Administration and Stewardship
● Section 2.3.2.9. Non-Guaranteed Routability would become Section 2.2.3 and subsequent sections would be renumbered.
● Section 2.3.2.10. Validity of IPv4 Address Allocations would be eliminated and added to Section 7. Subsequent sections would be renumbered.
● Section 2.3.2.11. Submission of Application Templates would be eliminated, and subsequent sections would be renumbered.

LACNIC Staff Comments
-------------------------
(Comments are observations intended to help distinguish between the changes presented in the proposal and the current text of the Policy Manual.)

1. This proposal modifies the title “Resource Recovery and Return,” changing it to “Resource Revocation and Return.”

2. The proposal modifies the section describing the practices that are considered grounds for the revocation of addresses, which currently appear in Section “2.3.2.10. Validity of IPv4 Address Allocations” of the Manual. These grounds for revocation would be moved to Section “7. Resource Revocation and Return.” In addition, it modifies the following practices:

a. The manual currently specifies “Failure to use the allocated IPv4 address space during a period of one month following registration.”
The proposal changes this to “Unused or unannounced resources (where mandatory).”
Section 2.2.3 of the proposal specifies that “allocated or assigned resources must be announced within a maximum of 90 days, except in those cases where the need not to announce the resources is justified.”
In short, the maximum period for announcing the assigned resources is increased from 30 to 90 days.

b. The current text specifies “Failure to comply with contractual obligations towards LACNIC.” The proposal expands this to “Failure to comply with contractual obligations towards LACNIC or its NIRs, including non-payment and document fraud.”

c. The proposal adds two items to the list of grounds for the revocation process: “Repeated and/or continued policy violations” and “Organizations that have disappeared or fail to respond.”
LACNIC interprets that this would not involve any operational changes.

d. The proposal eliminates the following text: “In the event of IPv4 address space invalidation, reasonable effort shall be made by LACNIC to inform the community that IPv4 addresses have been returned and are once again available IPv4 address blocks.”
e. The proposal adds that “When the violation has been caused by a third party without the knowledge of the organization receiving the resources, and if it is evident that there is no collusion or negligence on the part of said organization, the revocation process will not be completed.”
We suggest replacing the term “completed” with “initiated.”

3. In section “7.1. Resource Revocation Process” of the proposal:
a. Where the proposal specifies that “LACNIC will verify that the organizations receiving resources are using such resources correctly. This will periodically be done automatically...”
i. LACNIC interprets that the phrase “are using such resources correctly” refers to compliance with the policies.
ii. LACNIC understands “automatically” to mean a process that is not onerous to LACNIC and which will quickly allow identifying potential policy breaches.
iii. It is assumed that the frequency implied by “periodically” will be at the discretion of LACNIC and depend on the aspect to be monitored.

Regardless of any automation or repeated policy breaches, LACNIC is responsible for applying its best criteria prior to initiating a revocation process.

b. As for section c) of the proposal, LACNIC interprets that the NS records will only be eliminated if the organization does not reply. This is what the author explained considering the original spirit of the proposal. In any case, this does not affect the current procedure.

4. Section “7.3. Resource Return” of the proposal specifies that “resources...will be used in the order in which they have been added to the pool.” LACNIC interprets this to mean that the resources with the earliest return date will be assigned first, just as they are currently being assigned.

5. Regarding Section “1.11. Principles for Proper Administration and Stewardship:”
a. The proposal specifies that “a majority” is understood to mean “more than 50%” as published in the list of improvements https://www.lacnic.net/561/1/lacnic/.
b. The proposal specifies that “In order to obtain resources in the LACNIC region, it is also necessary to become a member of LACNIC or of the corresponding RIR, which in turn requires signing the Registration Services Agreement.”
Currently, those who request an ASN are required to sign a contract but are not considered LACNIC members. In any case, they must comply with the LACNIC policies in force.

According to the LACNIC Bylaws, organizations that become members of LACNIC by virtue of receiving resources include only those which receive IP addresses (they do not include organizations that only receive ASNs). According to this section of the proposal, organizations requesting any type of resources —including those receiving exclusively ASNs— must become members of LACNIC. If this proposal is approved, it would be in conflict with the Bylaws.

The Policy Manual should avoid potential conflicts.
LACNIC's membership base is responsible for deciding who is accepted as a member of the organization and who is not, therefore including this text would be inappropriate. If the rationale behind this text is that holders of ASNs should have the same obligations as the others, this is already the case, as they are also required to sign a contract.

6. In section 2.2.3, the maximum period for announcing allocated or assigned resources is extended from 30 to 90 days, as specified in the list of improvements https://www.lacnic.net/561/1/lacnic/.

Recommendations
-------------------

7. Sections “7.1. Resource Revocation Process” and “7.3. Resource Return” of the proposal specify that “All other provisions specified in the Registration Services Agreement and Bylaws shall apply.”

Because the Policy Manual is intended to govern the administration of Internet number resources, any matter relating to membership requirements or service agreements is outside its scope.

8. Section “7.3. Resource Return” of the proposal specifies a time frame (2 years) for incorporating recovered and returned IPv6 and ASN resources to their respective pools, while the Manual currently specifies that this time frame is yet to be defined.
We suggest specifying when LACNIC would be expected to start using this pool.

9. Section 7.5 of the proposal states that “IPv4 resources will be added at the “end” of the pool in use at the moment of their recovery or return and will be used in the order in which they have been added to the pool.”

LACNIC interprets that this does not modify the process that is currently being applied. However, the staff believes that it would be good to add a reference to item 2), section 2. of RFC 7020 so as to consider maintaining the hierarchical distribution of addresses in a way that permits their aggregation to the greatest extent possible.

10. We recommend maintaining the text in subsection “2.3.2. Aspects to Consider in Relation to IPv4 Address Administration” instead of “2.2. IPv4 Address Space and the Internet Registry System” as proposed, as maintaining the current text of the manual means that it is equally valid and necessary for both allocations and assignments.

11. Section “1.11. Principles for Proper Administration and Stewardship” of the proposal specifies that “In order to obtain resources in the LACNIC region, it is also necessary to become a member of LACNIC or of the corresponding RIR, which in turn requires signing the Registration Services Agreement.”

Currently, those who apply for ASNs are required to sign a contract but are not considered LACNIC members. In any case, they must comply with the LACNIC policies in force.

According to the LACNIC Bylaws, organizations that become members of LACNIC by virtue of receiving resources include only those which receive IP addresses (they do not include organizations that only receive ASNs). According to this section of the proposal, organizations requesting any type of resources —including those receiving exclusively ASNs— must become members of LACNIC. If this proposal is approved, it would be in conflict with the bylaws.

The Policy Manual should avoid conflicts with the Bylaws. LACNIC’s membership base is responsible for the Bylaws. Matters such as who is granted membership status is outside the scope of the Policy Manual. If the goal of this proposal is for all holders of number resources to have the same obligations, it should be noted that this is already the case, as they are also required to sign a membership contract.

Impact of the policy on the registry system
-------------------------------------------
This proposal would involve changes to LACNIC's systems, i.e. developing an automatic and periodic validation mechanism.
Official Sources:

Policies in force in the other RIRs

- RIPE
The policies in force in the RIPE region provide certain high-level rules determining when resources must be returned.

The IPv4 address allocation and assignment policy specifies the reasons why the RIPE NCC may close an LIR: https://www.ripe.net/publications/docs/ripe-725#9

In the case of independent Internet number resources (no direct contact with the RIPE NCC), the registry has a policy in place which specifies some of the contractual requirements that such resources must meet. The remaining requirements are contained in the corresponding contract.

Based on these policies, the RIPE NCC has developed a procedure for the closure of members and the deregistration of Internet resources (not a policy but an internal procedure). It includes not only these policy requirements but also the requirements contained in the service agreement. This procedure is available at: https://www.ripe.net/publications/docs/ripe-716#b

- APNIC
The policies that apply to resource recovery and returns are included in sections 4.2 and 4.2.1 of their policy document:
https://www.apnic.net/community/policy/resources#4.2.-Closure-and-recovery

This is also addressed in Section 8.0: “During that time, if the reason for the original request is no longer valid, the resources must be returned to APNIC as required in Section 4.0.”

- ARIN:
ARIN has a process for resource revocation and returns, not in the form of a policy but in the form of an operating procedure: https://www.arin.net/resources/fees/returns/.

- AFRINIC
There is no resource recovery policy in place in the AFRINIC region. Instead, the registry proceeds to recover the resources of members who do not pay (a contractual obligation).

In addition, there are references that state that if the purpose for which the resources were requested has changed the resources are no longer valid.

Privacy Policy