Part 4: ASN Policy
- ¶ 4 Leave a comment on paragraph 4 0
- it is currently multihomed, or
- has the need to interconnect with another AS.
¶ 5 Leave a comment on paragraph 5 0 An organization will also be eligible if it can demonstrate that it will meet the above criteria upon receiving an ASN (or within a reasonably short time thereafter).
¶ 6 Leave a comment on paragraph 6 0 Requests for ASNs under these criteria will be evaluated using the guidelines described in RFC1930 ‘Guidelines for the creation, selection and registration of an Autonomous System’ (AS).
¶ 9 Leave a comment on paragraph 9 0 The requesting organization may request an ASN for use in its own network, or for the purposes of providing the ASN to one of its customers, subject to the terms of Sections 12.3. and 12.4. below.
- ¶ 12 Leave a comment on paragraph 12 0
- The requesting organization is responsible for maintaining the registration described in Section 5.3.3.
- The requesting organization is entitled to continue using the ASN, even if they change network peers or service providers.
- ¶ 15 Leave a comment on paragraph 15 0
- The customer that will actually use the ASN must meet the criteria in Section 12.0.
- The requesting organization is responsible for maintaining the registration described in Section 5.3.3. on behalf of the customer.
- If the customer ceases to receive connectivity from the requesting organization it must return the ASN. The requesting organization is expected to enter into an agreement with the customer to this effect.
- Any ASNs returned to the requesting organization must then be returned to APNIC or the relevant NIR.
¶ 17 Leave a comment on paragraph 17 0 On 1 January 2010 APNIC ceased to make any distinction between two-byte only AS Numbers and four-byte only AS numbers, and operates the AS Number assignments from an undifferentiated four-byte AS Number pool.
¶ 20 Leave a comment on paragraph 20 0 Autonomous System Numbers may be transferred in accordance with the following policies. APNIC does not recognize transfers outside this policy and require organizations holding such transfers to return them.
- ¶ 22 Leave a comment on paragraph 22 0
- Current APNIC account holders
- Current APNIC account holders and organizations in other RIR regions
- Organizations through a merger, acquisition, or takeover
- ¶ 27 Leave a comment on paragraph 27 0
- In the range administered by APNIC
- Assigned to a current APNIC account holder
- The ASN will be subject to all current APNIC policies from the time of transfer
¶ 33 Leave a comment on paragraph 33 0 APNIC will recognize inter-RIR ASN transfers only when the counterpart RIR has an inter-RIR transfer policy that permits the transfer of ASNs between APNIC and its own region.
¶ 34 Leave a comment on paragraph 34 0 APNIC will process and record ASN transfer requests between current APNIC account holders and organizations in other RIR regions subject to the following conditions.
¶ 36 Leave a comment on paragraph 36 0 The ASN to be transferred should be under the management of the RIR at which the transfer source holds an account and the authentic holder of the space should match with the source without any disputes.
¶ 39 Leave a comment on paragraph 39 0 For transfers from an APNIC source, the source entity must be the currently registered holder of the resource, and not be involved in any dispute as to the status of those resources.
¶ 43 Leave a comment on paragraph 43 0 For transfers to an APNIC recipient, the recipient entity must be an APNIC account holder and must meet the criteria for the assignment of an ASN. Following the transfer, the resources will be subject to current APNIC policies.
¶ 44 Leave a comment on paragraph 44 0 Where the recipient is in another region, the conditions on the recipient as defined in the counterpart RIR’s transfer policy at the time of the transfer will apply.
¶ 48 Leave a comment on paragraph 48 0 If an organization changes ownership (due to a merger, sale, or takeover), then the new entity must register any changes to its network usage and contact personnel. If the effect of the ownership change is that the name changes, then the organization must provide relevant legal documentation supporting the name change.
¶ 50 Leave a comment on paragraph 50 0 If an organization changes ownership then the new entity should advise APNIC of the change. APNIC membership is not transferable from one entity to another; however, if the effect of the ownership change is that the organization becomes a subsidiary of another entity, and the infrastructures of the respective entities remain fully independent, then the membership agreement may continue.
¶ 52 Leave a comment on paragraph 52 0 Following a change in ownership, APNIC will review the status of any allocations that are held by the new entity or entities, with regard to the practical effect on their infrastructures.
¶ 53 Leave a comment on paragraph 53 0 If the practical effect of ownership change is that the infrastructures are merged, then APNIC will not continue to make separate allocations to both. This situation will invalidate the membership agreement of the organization that is effectively subsumed.
¶ 54 Leave a comment on paragraph 54 0 When assessing the status of ASN assignments, APNIC requires full disclosure of all resources held by all of the entities in question. If full disclosure is not made, then APNIC will consider any delegations to be invalid and will require that they be returned.