diff-apnic-127-v011
| apnic-resource-policies.txt | draft-apnic-127-v012.txt > | |||
|---|---|---|---|---|
| —————————————————————————————– | —————————————————————————————– | |||
| APNIC Document identity | APNIC Document identity | |||
| Title: APNIC Internet Number Resource Policies | Title: APNIC Internet Number Resource Policies | |||
| Short title: apnic-resource-policies | Short title: apnic-resource-policies | |||
| Document ref: APNIC-127 | Document ref: APNIC-127 | |||
| Version: 011 | Version: 012 | |||
| Date of original publication: 05 March 2015 | Date of original publication: 05 March 2015 | |||
| Date of this version: 08 August 2022 | Date of this version: xx December 2022 | |||
| Review scheduled: n/a | Review scheduled: n/a | |||
| Obsoletes: apnic-127-v010 | Obsoletes: apnic-127-v011 | |||
| Status: Active | Status: Draft | |||
| Comments: Implements prop-142, 143, 144 and minor editorial changes | Comments: Implements prop-146 | |||
| ——————————————————————————————- | ——————————————————————————————- | |||
| Table of Contents | Table of Contents | |||
| Part 1: Policy Environment | Part 1: Policy Environment | |||
| 1.0. Introduction | 1.0. Introduction | |||
| 1.1. Scope | 1.1. Scope | |||
| 1.2. Hierarchy of resource distribution | 1.2. Hierarchy of resource distribution | |||
| 2.0. Definitions | 2.0. Definitions | |||
| 2.1. Internet Registry (IR) | 2.1. Internet Registry (IR) | |||
| 2.2. Address space | 2.2. Address space | |||
| skipping to change at line 393 ¶ | skipping to change at line 393 ¶ | |||
| will be the legitimate holder of the resources to be transferred. Where the recipient is in the | will be the legitimate holder of the resources to be transferred. Where the recipient is in the | |||
| APNIC region, the recipient must be a current APNIC account holder. Where the recipient is from | APNIC region, the recipient must be a current APNIC account holder. Where the recipient is from | |||
| another RIR region, it must be that RIR’s equivalent to the “Recipient” as defined here. | another RIR region, it must be that RIR’s equivalent to the “Recipient” as defined here. | |||
| 3.0. Policy framework | 3.0. Policy framework | |||
| IP address space and other number resources are public resources which must be managed in a prudent | IP address space and other number resources are public resources which must be managed in a prudent | |||
| manner with regards to the long-term interests of the Internet. Responsible management involves | manner with regards to the long-term interests of the Internet. Responsible management involves | |||
| balancing a set of sometimes competing goals. The following are the goals relevant to Internet | balancing a set of sometimes competing goals. The following are the goals relevant to Internet | |||
| number policy. | number policy. | |||
| This document is intended to help IRs perform their role in consistent and equitable ways. IRs must | ||||
| maintain full documentation of and transparency within the decision-making process. | ||||
| 3.1. Goals of resource management | 3.1. Goals of resource management | |||
| The goals described here were formulated by the Internet community and reflect the mutual interest | The goals described here were formulated by the Internet community and reflect the mutual interest | |||
| of all members of that community in ensuring that the Internet can function and grow to the maximum | of all members of that community in ensuring that the Internet can function and grow to the maximum | |||
| extent possible. | extent possible. | |||
| It is APNIC’s primary duty, as a custodian of a public resource, to ensure these goals are met within | It is APNIC’s primary duty, as a custodian of a public resource, to ensure these goals are met within | |||
| the Asia Pacific region. APNIC does this by providing guidance and leadership in developing and | the Asia Pacific region. APNIC does this by providing guidance and leadership in developing and | |||
| implementing responsible policies and practices. | implementing responsible policies and practices. | |||
| It is the responsibility of every NIR and LIR to also ensure these goals are met within their | It is the responsibility of every NIR and LIR to also ensure these goals are met within their | |||
| skipping to change at line 443 ¶ | skipping to change at line 446 ¶ | |||
| the address space is aggregated by the LIR within a minimum number of routes announcements | the address space is aggregated by the LIR within a minimum number of routes announcements | |||
| (preferably one). | (preferably one). | |||
| LIRs must only delegate addresses to customers who will be using those addresses in relation to | LIRs must only delegate addresses to customers who will be using those addresses in relation to | |||
| network connectivity services provided by the LIR. | network connectivity services provided by the LIR. | |||
| LIRs are expected to enter into agreements with their customers specifying that the end-user will | LIRs are expected to enter into agreements with their customers specifying that the end-user will | |||
| hold the addresses only for so long as the end-user remains a customer of that LIR. Such agreements | hold the addresses only for so long as the end-user remains a customer of that LIR. Such agreements | |||
| should also be consistent with the license under which the address space is being used by the LIR. | should also be consistent with the license under which the address space is being used by the LIR. | |||
| 3.1.4. No guarantee of contiguous delegations | 3.1.4. Contiguous delegations | |||
| RIRs should apply practices that maximize the potential for subsequent allocations to be made | RIRs should apply practices that maximize the potential for subsequent allocations to be made | |||
| contiguous with past allocations currently held. However, there can be no guarantee of contiguous | contiguous with past allocations currently held. However, there can be no guarantee of contiguous | |||
| allocation. | allocation. | |||
| APNIC will attempt to make any subsequent delegations contiguous with previous delegations but | APNIC will attempt to make any subsequent delegations contiguous with previous delegations but | |||
| cannot guarantee that this will be possible. | cannot guarantee that this will be possible. | |||
| 3.1.5. Conservation | 3.1.5. Conservation | |||
| To maximize the lifetime of the available resource, address space must be distributed according to | To maximize the lifetime of the available resource, address space must be distributed according to | |||
| actual need and for immediate use. Stockpiling address space and maintaining reservations are contrary | actual need and for immediate use. Stockpiling address space and maintaining reservations are contrary | |||
| skipping to change at line 475 ¶ | skipping to change at line 478 ¶ | |||
| All policies and practices relating to the use of public address space should apply fairly and equitably | All policies and practices relating to the use of public address space should apply fairly and equitably | |||
| to all existing and potential members of the Internet community, regardless of their location, nationality, | to all existing and potential members of the Internet community, regardless of their location, nationality, | |||
| size, or any other factor. | size, or any other factor. | |||
| 3.1.7. Minimized Overhead | 3.1.7. Minimized Overhead | |||
| It is desirable to minimize the overhead associated with obtaining address space. Overhead includes the | It is desirable to minimize the overhead associated with obtaining address space. Overhead includes the | |||
| need to go back to RIRs for additional space too frequently. There is overhead associated with managing | need to go back to RIRs for additional space too frequently. There is overhead associated with managing | |||
| address space that grows through a number of small successive incremental expansions rather than through | address space that grows through a number of small successive incremental expansions rather than through | |||
| fewer, but larger, expansions. | fewer, but larger, expansions. | |||
| 3.1.8. Conflict of goals | ||||
| The goals described above will often conflict with each other, or with the needs of individual IRs or | ||||
| end-users. All IRs evaluating requests for address space must make judgments, seeking to balance the | ||||
| needs of the applicant with the needs of the Internet community. | ||||
| This document is intended to help IRs perform their role in consistent and equitable ways. IRs must | ||||
| maintain full documentation of and transparency within the decision-making process. | ||||
| In IPv6 address policy, the goal of aggregation is considered to be the most important. | ||||
| 3.2. Policy Environment | 3.2. Policy Environment | |||
| Apart from the goals described above, other factors influence the APNIC policy environment. These other | Apart from the goals described above, other factors influence the APNIC policy environment. These other | |||
| factors include the expectations of the Internet community, current administrative structures, and | factors include the expectations of the Internet community, current administrative structures, and | |||
| technological constraints. | technological constraints. | |||
| The policy environment may change quickly or in unpredictable ways, so APNIC, on behalf of its account | The policy environment may change quickly or in unpredictable ways, so APNIC, on behalf of its account | |||
| holders, must monitor any changes and communicate any policy implications. | holders, must monitor any changes and communicate any policy implications. | |||
| This section describes the factors in the current operating environment that has been most important in | This section describes the factors in the current operating environment that has been most important in | |||
| determining current APNIC policies. | determining current APNIC policies. | |||
| End of changes. 6 change blocks. | ||||
| 16 lines changed or deleted | 9 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||