Authors | |
---|---|
Name: Jordi Palet Martinez Email: jordi.palet@theipv6company.com Organization: The IPv6 Company |
Name: Jordi Palet Martinez Email: jordi.palet@theipv6company.com Organization: The IPv6 Company |
Summary | |
This proposal updates section 7 of the Policy Manual to “Resource Revocation and Return.” Discrepancies in the current w ording 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 revo cation 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 w ording 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 revo cation 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 (Describe the problem you intend to solve) | |
The current text does not properly specify how to act in case of repeated policy violations. The wording is ambiguous an d 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 th e 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 th e 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 f or IPv4 bur also affects IPv6, the proposal clarifies different aspects, which might also be understood as editorial cha nges, and solves several items on the list of potential improvements. |
Current 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 uti lized, LACNIC shall verify with the organization that received the assignment whether the resource is being properly uti lized. 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 tabl e 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 mo nths 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 authoritativ e 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 opera ting the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LA CNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extra ordinary 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 p olicy 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 an d 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 Pol icy 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 with in its service region and mainly serving networks and services operating in this region. External clients connected dire ctly 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 routa ble. These problems shall be solved between the holders of the IPv4 addresses involved and their connectivity provider or pro viders. 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 c ontinue 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. The se 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 applica tion 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, routabili ty, 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 w ill 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 th ree 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 point ing 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 sha ll 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 Boar d of Directors may extend the resource revocation period, with prior assessment by the LACNIC Staff once such an excepti onal 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 return ed, 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 wit hin its service region and a majority* of the resources must be used to operate networks and provide services in this re gion. 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 correspon ding 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 pro vide 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 comm on to all resources.) |
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 uti lized, LACNIC shall verify with the organization that received the assignment whether the resource is being properly uti lized. 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 h old 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 tabl e. If the organization can justify that this is the case, LACNIC shall consider this sufficient and the resource recover y process shall end. If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three mo nths. 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 authoritativ e 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 opera ting the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LA CNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extra ordinary 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 P olicy 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 an d 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 Pol icy 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. Returne d 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 routa ble. These problems shall be solved between the holders of the IPv4 addresses involved and their connectivity provider or pro viders. 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 routa ble. However, RIRs must apply procedures that reduce the possibility of fragmented address space which may lead to a los s 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 wit hin its service region and a majority* of the resources must be used to operate networks and provide services in this re gion. 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 c ontinue 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. The se 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 t he 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 applic ation deemed as lacking information or insufficiently detailed shall be returned to the applicant for its completion. |
New 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 uti lized, LACNIC shall verify with the organization that received the assignment whether the resource is being properly uti lized. 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 tabl e 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 mo nths 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 authoritativ e 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 opera ting the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LA CNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extra ordinary 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 p olicy 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 an d 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 Pol icy 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 with in its service region and mainly serving networks and services operating in this region. External clients connected dire ctly 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 routa ble. These problems shall be solved between the holders of the IPv4 addresses involved and their connectivity provider or pro viders. 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 c ontinue 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. The se 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 applica tion 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, routabili ty, 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 w ill 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 th ree 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 point ing 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 sha ll 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 Boar d of Directors may extend the resource revocation period, with prior assessment by the LACNIC Staff once such an excepti onal 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 return ed, 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 wit hin its service region and a majority* of the resources must be used to operate networks and provide services in this re gion. 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 correspon ding 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 pro vide 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 comm on to all resources.) |
7. Resource Revocation and Return Resource allocations and assignments will remain valid as long as the objectives of exclusivity, preservation, routabili ty, 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 w ill 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 th ree 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 point ing to the authoritative nameservers of the resources involved This information may be recovered once the organization r eestablishes 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 sha ll 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 Boar d of Directors may extend the resource revocation period, with prior assessment by the LACNIC Staff once such an excepti onal 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 provis ions 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 re sulting 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 pro vide 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 i ts 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 recipie nt 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 sectio n 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 | |
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/pub lications/docs/ripe-716 |
- |
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 |