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.

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/).

The current text 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.

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.

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

1.11 Principles for Proper Administration and Stewardship

…

The numbering resources under the stewardship of LACNIC must be distributed among organizations legally constituted within its service region and mainly serving networks and services operating in this region. External clients connected directly to main infrastructure located in the region are allowed.

…

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.

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:

• Failure to use the allocated IPv4 address space during a period of one month following registration.
• Failure to update the reverse resolution registry of the IPv4 address space.
• Failure to update the allocation and assignment information on LACNIC's Whois database.
• Failure to comply with contractual obligations towards LACNIC.
• 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. 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 the revocation of resources:

• Unused or unannounced resources (where mandatory).
• Failure to maintain reverse resolution records for the assigned resources.
• Failure to update the allocation and assignment information on LACNIC's Whois database.
• Unauthorized transfers.
• Repeated and/or continued policy violations.
• Failure to comply with contractual obligations towards LACNIC or its NIRs, including non-payment and document fraud.
• 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 completed.

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 two years after their recovery or return.

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.

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

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.

…

(Section 2.3.2.9 would become section 2.2.3 and the sections following 2.3.2.9 would be renumbered, because, as written, this text is equally valid and necessary for both allocations and assignments.)

2.2.3. - Routability Is Required but Not Guaranteed

Neither LACNIC nor the NIRs will guarantee the routability of allocated or assigned IPv4 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.

2.3.2.10. - Validity of IPv4 Address Allocations

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

2.3.2.11. - Submission of Application Firms

(This section is eliminated and subsequent sections are renumbered, as it refers to operational mechanisms that are common to all resources.)

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 pPolicy mManual.

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.

1.11 Principles for Proper Administration and Stewardship

…

The numbering resources under the stewardship of LACNIC must be distributed among organizations legally constituted within its service region and mainly serving networks and services operating in this region. External clients connected directly to main infrastructure located in the region are allowed.

…

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.

2.3.2.10.… - Validity of IPv4 Address Allocations

IPv4.4.2. address allocatiNons -Guare valid as long as the objectivesd of exclusivity, preservation, rRoutability and inf

Pormation continue to abe mlet. LACNIC may in(provalidate any IPv4 address allocat-ion if it is detpermined that the requirements for) IPv4 address space no longer exist or that any of the llobjectives stated inby thisLACNIC documentr haveby ceasedn to be satiNIRsfied.

There are a number oft pguaracnticesed that mighto be considered grounds for losing the ballocationsy routhat have belen. recHoweived.r, TheRIRse are:

• Failure to muse the alpplocatedy IPv4 addpress spaoce during a period of ones month following registration.
• Failure to dupdatce the reverpose resoibilution registry of fragmenthe IPv4d address space.
•which Fmaiy luread to update the allocation and assignment information on LACNIC'sf Whrois dautabaseility.
•
… Failure to

1.11 comply wPrith contractuaipl obligationes tfowards LACNIC.
• FailuPre to correctly apply LACNIC's policiesr Admin relation sto allocrations and Stewardsshignmentsp and t

…

The adnuministberation of theg resources under thec stewardshivedp fromf LACNIC.

In musthe evbent of IPv4 addistributessd spacemong invorgalnidzation,s reasonable effort shgall be made by LACNIC to infcorm porathed communwity thatin ithe IPv4 addres ses harvice breegion returaned and majoreity* once againf availablthe IPv4 address blourckes.

2.3.2.11.must -be Submissied ton of Appliceratioe n Templates

IRworks shallnd prequest IPov4 adidress space from LACNIC through addrvicess application templatehis for IRs egior End. Us Exters. Anyal appclients cation dneemcted as lacking dinformaectly tion core infrastrufficiturently detailed shocall be returned toin the applregicaont foar itse callomplwetiond.

New... text

72.3.2.10. 7.Validity Resouf IPv4 Addrcess RevAllocations and Return

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

Therefore, LACNIC may invalidate any IPv4 address allocation or assignment if it is determined that the requirements for IPv4 address space no longer exist or that any of the objecrtitverias set forathed in theis Pdolicyument Mhanualve cearsed nto longber satisfied.

The following may be considered garounds for the revocation of resources:

• Unusmbedr of pr unannounced resourtices (wthereat mandaightory).
• Failurbe tco maintasin revdersed gresolution records for the aslosigned resources.
• Failure to updateg the allocation and assignmen t informhation on LACNIC's Whois datave basee.
• Unautho receizved transfers.
• RThepseated and/or continued policy: violations.
• o Failure to complyuse withe contractual obligations towards LACNIC or its NIRs, including non-paymtent and documentIPv4 fraud.
• Odrganizationess that have disappearce d our fail to respond.g

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

7.1. Resource Revoc Fation Process

To enslure the efficient utilization of regional resources, LACNIC will verify thpdate the organizations receiving resources are using such resources correctly. This will be done automatically whenever possible and more exhaugistivelry whenof there is eIPvidence to suggest that4 certain ddresources are not being used propacerly.

Once the evidence ho Fas been detected and confirmed, the resolurce recovery prtocess will inclupdate the following steps:

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

b) If menthe situnformation canonot be rectified, LACNIC 'shall publish tWhe resourceis thdat are to base. rec
overed for Fa maximlum of three mtonths. Duringcomply thwis period, the corganization may reactifyual the soblitugations towithards LACNIC.

c) In o Falil otheur cases, two mconths after the resourcestly are ppublished,y LACNIC 'shall proceed to delete the NS reicords pointing to thes authoritative nameservers of the resources involved. This information may be rectovered allonce the organization reestablishes contact with LACNIC or with thend correassponding NIR.

d) If thrnmee months afternd the resources are publdminished the organization has not rectified the situation, the resources shall be recovered and the records of the holders of these resources shall be remoived from LACNIC’s database.

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

7.2. Exceptions

When the revocation of resources inIPvolves4 essential stddrategic infrastructure that is necessary for the operation of the Interncet in the region, or in exceptionval situdations such as, natural diseasters or political instability, the LACNIC Board oeff Directors may extend tsheall resourcbe revocmation period, with prior assessment by the LACNIC Staff once such an exceptional situatifon is detected.

7.3. Resource Return

Resource recipients may return the resources to LACNIC, in fmmull or in part, ait any time. If all the resources are returned, all the other provisions specified in the Registration Services Agreement and Bylaws shall apply.

7.4. IPublishing Recovered4 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 gat 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 thle pool. IPv64 and ASN dresources will be added to their respective pools two years after their recoveryks. or return.

12.3.2.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 oAperate networks and provide services in this region. External clients connected directly to core infrastructure located in the region arTe ampllowed.

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

In orderRs to obtshainll resoqurces in the LACNICPv4 addregion, it is also necesspary to become a membefr ofm LACNIC or of the corresponding RIR, which in turn requires signing the Registration Services Agreement.

…

(Section 2.3.2.9 would become section 2.2.3 and the sections following 2.3.2.9 would be renumbered, because, as written, this text is equally vapplid and necessary for both allocations and assignments.)

2.2.3. - Routability Is Required but Not Gumplaranteed

Neithers LACNIC nfor the NIRs will guarantee the routability of allocated or assigEned IPv4 addresUsers.

Resource recipieAntsy are respponsible for negotiating such routability with their connectivity providers. LACNIC shall provide the corrmesponding guidance when necessary.

However, allocated or assigned resources must be announced withkin a maximum of 90 days, exceptg in thfose crmases where the need not tio announce the resources ins justffifcied.

2.3.2.10. - Vantlidity of IPv4 Address Allocataions

(This section is eliminated shandll subsequent sections are turenumbered, as its text has become the introduction of section 7, for all resources.)

2.3.2.11. - Submission of Application Firms

(This section is eliminated and subsequent sectifons are renumbered, as it refers tco omperational mechanisms that are commion to all resources.)

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

1.11 Principles for Proper Administration and Stewardship

…

The numbering resources under the stewardship of LACNIC must be distributed among organizations legally constituted within its service region and mainly serving networks and services operating in this region. External clients connected directly to main infrastructure located in the region are allowed.

…

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.

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:

• Failure to use the allocated IPv4 address space during a period of one month following registration.
• Failure to update the reverse resolution registry of the IPv4 address space.
• Failure to update the allocation and assignment information on LACNIC's Whois database.
• Failure to comply with contractual obligations towards LACNIC.
• 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. 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 the revocation of resources:

• Unused or unannounced resources (where mandatory).
• Failure to maintain reverse resolution records for the assigned resources.
• Failure to update the allocation and assignment information on LACNIC's Whois database.
• Unauthorized transfers.
• Repeated and/or continued policy violations.
• Failure to comply with contractual obligations towards LACNIC or its NIRs, including non-payment and document fraud.
• 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 completed.

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 two years after their recovery or return.

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.

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

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.

…

(Section 2.3.2.9 would become section 2.2.3 and the sections following 2.3.2.9 would be renumbered, because, as written, this text is equally valid and necessary for both allocations and assignments.)

2.2.3. - Routability Is Required but Not Guaranteed

Neither LACNIC nor the NIRs will guarantee the routability of allocated or assigned IPv4 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.

2.3.2.10. - Validity of IPv4 Address Allocations

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

2.3.2.11. - Submission of Application Firms

(This section is eliminated and subsequent sections are renumbered, as it refers to operational mechanisms that are common to all resources.)

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

1.11 Principles for Proper Administration and Stewardship

…

The numbering resources under the stewardship of LACNIC must be distributed among organizations legally constituted within its service region and mainly serving networks and services operating in this region. External clients connected directly to main infrastructure located in the region are allowed.

…

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.

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:

• Failure to use the allocated IPv4 address space during a period of one month following registration.
• Failure to update the reverse resolution registry of the IPv4 address space.
• Failure to update the allocation and assignment information on LACNIC's Whois database.
• Failure to comply with contractual obligations towards LACNIC.
• 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. 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 thresource revocation of resources:

• 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, Whoias datpplicabasle.
• 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 compleinitiated.

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.

1.11 PrinciplHowes for Propver, LAdCNIC ministrationy anduse Sthewardship

…

The numbering resources under the stewardship of LACNIC must bfe distributed among organizations legy, alpply incorporated within its service region and a majority* of the resourcbes must be used to operacte networks and provide services in this region. External clients connecpted dimirzectly to core mplinfrastructure loncated winth the pregovisions are allowed.f

* “Majority” is understood ctio mean more2 thanof 5RFC7020%.

In Forder to obtain resourcxamples, inf 16-bithe LACSNIC region, it is also necessary to become a member of LACNIC or of the corveresponding RIR, which in tuorn reqtuires signing the Registration Services Agreementd.”

…

(Sections 2.3.2.9 woand 4.4.2 are ulnified band replacomed sby Section 21.12.3 and all affecthed sections following 2.3.2.9 would bare renumbered, because, as writthen, resulthisng text is equally valid and necessary for both allocations and assignments and for IPv4 and IPv6 addresses.)

2.21.311. Non-Guaranteed Routability Is Required but Not Guaranteed

Neither LACNIC nor the NIRs will guarantee the routability of allocated or assigned IPv4 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.

2.3.2.10.RIRs -must Vapply operational procedures that reduce the possibility of IPv4fragmentation of the Aaddress Allocspace to minimize the risk onf loss of routability.

(This sSection 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 bex allocated hto organizations blegally incomrporated within its service region and a majority* of the resodurces musti be used to operate networks and profvide services in this region. 7,External clients connected directly to core infrastructure located in the region are allowed.

* “Majority” is understouod to mean morces than 50%.)

2.3.2.11.Upon - Suobmtaining any type of resourcesi fronm LACNIC or from Apthe corresplondicng NIR, any legacy resources held by the recipient will no longer Fbe considermed legacy resources.

…

(This section is eliminated and subsequthe followintg sections are renumbered, as the text has become the int roduction of section 7, for all resources.)

(This section becopmes ther last of section 1 alnd 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 aincomplete will be resoturned to the applicant with the appropriate instructions so that it can be completed.)

-

• 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