apnic-127-v012.txt   apnic-127-draftv013.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: 012 Version: 013
Date of original publication: 05 March 2015 Date of original publication: 05 March 2015
Date of this version: 22 December 2022 Date of this version: xx June 2023
Review scheduled: n/a Review scheduled: n/a
Obsoletes: apnic-127-v011 Obsoletes: apnic-127-v012
Status: Active Status: Draft
Comments: Implements prop-146 Comments: Implements prop-145, 147, prop-150, prop-151
------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------
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. Address space
2.2. Address space 2.2. Autonomous System (AS)
2.3. Autonomous System (AS) 2.3. Multihomed
2.4. Multihomed 2.4. Usage rate
2.5. Internet resources 2.5. Utilization
2.6. Internet Exchange Point (IXP) 2.6. End-site
2.7. Usage rate 2.7. End-user
2.8. Utilization 2.8. aut-num object
2.9. End-site 2.9. Routing policy
2.10. End-user 2.10. Transfers
2.11. aut-num object 2.11. Multiple Discrete Networks
2.12. Routing policy
2.13. Transfers
3.0. Policy framework 3.0. Policy framework
3.1. Goals of resource management 3.1. Goals of resource management
3.2. Policy Environment 3.2. Policy Environment
3.3. Applicants seeking address space from multiple IRs 3.3. Applicants seeking address space from multiple IRs
4.0. Resource License 4.0. Resource License
4.1. License Renewal 4.1. License Renewal
4.2. Closure and recovery 4.2. Closure and recovery
4.3. Claiming and re-delegating historical resources
5.0. Resource Management 5.0. Resource Management
5.1. How APNIC manages address space 5.1. How APNIC manages address space
5.2. LIR address space management 5.2. LIR address space management
5.3. Registration requirements 5.3. Registration requirements
5.4. Reverse lookup 5.4. Reverse lookup
5.5. Managing Historical resources 5.5. Managing Historical resources
5.6. General requirements for requests 5.6. General requirements for requests
5.7. Experimental allocations policy 5.7. Experimental allocations policy
Part 2: IPv4 Policy Part 2: IPv4 Policy
skipping to change at line 89 skipping to change at line 88
9.1.3. IPv6 for Internet Exchange Points 9.1.3. IPv6 for Internet Exchange Points
9.1.4. Provider Independent IPv6 assignment 9.1.4. Provider Independent IPv6 assignment
Part 4: ASN Policy Part 4: ASN Policy
10.0. ASN assignments 10.0. ASN assignments
10.1. Evaluation of eligibility 10.1. Evaluation of eligibility
10.2. Requesting an ASN 10.2. Requesting an ASN
10.3. Using ASN for own network 10.3. Using ASN for own network
10.4. Providing ASN to customer 10.4. Providing ASN to customer
10.5. Two-byte only and four-byte AS Numbers 10.5. Two-byte only and four-byte AS Numbers
10.6. Route Origin Authorisation (ROA)
10.7. AS-SET
Part 5: Transfer Policy Part 5: Transfer Policy
11.0. IPv4 Transfers 11.0. IPv4 Transfers
11.1. IPv4 transfers within the APNIC region 11.1. IPv4 transfers within the APNIC region
11.1.1. Conditions on the space to be transferred 11.1.1. Conditions on the space to be transferred
11.1.2. Conditions on source of the transfer 11.1.2. Conditions on source of the transfer
11.1.3. Conditions on recipient of the transfer 11.1.3. Conditions on recipient of the transfer
11.2. Inter-RIR IPv4 address transfers 11.2. Inter-RIR IPv4 address transfers
11.2.1. Conditions on the space to be transferred 11.2.1. Conditions on the space to be transferred
11.2.2. Conditions on the source of the transfer 11.2.2. Conditions on the source of the transfer
skipping to change at line 216 skipping to change at line 217
[Figure 1: Diagram of distribution hierarchy] [Figure 1: Diagram of distribution hierarchy]
In this hierarchy, IANA allocates address space to APNIC, to be redistributed throughout the In this hierarchy, IANA allocates address space to APNIC, to be redistributed throughout the
Asia Pacific region. APNIC allocates address space to Internet Registries (IRs) and delegates Asia Pacific region. APNIC allocates address space to Internet Registries (IRs) and delegates
to them the authority to make assignments and allocations. In some cases, APNIC assigns to them the authority to make assignments and allocations. In some cases, APNIC assigns
address space to end users. National and Local IRs allocate and assign address space to address space to end users. National and Local IRs allocate and assign address space to
their account holders under the guidance of APNIC and in accordance with the relevant policies their account holders under the guidance of APNIC and in accordance with the relevant policies
and principals described in this document. and principals described in this document.
2.0. Definitions 2.0. Definitions
The following terms and definitions are used in APNIC documents. Terms not defined in this document have the meaning given to them in the APNIC
Definition Document.
2.1. Internet Registry (IR)
An Internet Registry (IR) is an organization that is responsible for distributing IP address
space to its account holders and for registering those distributions. IRs are classified
according to their primary function and territorial scope within the hierarchical structure
depicted in the figure above.
Internet Registries include:
* APNIC and other Regional Internet Registries (RIRs)
* National Internet Registries (NIRs)
* Local Internet Registries (LIRs).
2.1.1. Regional Internet Registry (RIR)
Regional Internet Registries (RIRs) are established and authorized by their respective regional
communities and recognized by the IANA to serve and represent large geographical regions. Their
primary role is to manage, distribute, and register public Internet address space within their
respective region. There are five RIRs: AFRINIC, APNIC, ARIN, LACNIC, and the RIPE NCC.
2.1.2. National Internet Registry (NIR)
National Internet Registries (NIRs) are established and authorized by their respective regional
communities and recognized by RIRs to delegate address space to their account holders, which are
generally LIRs organized at a national level. NIRs are expected to apply their policies and
procedures fairly and equitably to all account holders of their constituency.
The policies in this document apply to NIRs; however, this document does not describe the entire
roles and responsibilities of NIRs with respect to their formal relationship with APNIC. Such
roles and responsibilities may be described in other documents and agreements including:
* Criteria for the recognition of NIRs in the APNIC region
http://www.apnic.net/policy/nir-criteria
* Operational policies for NIRs in the APNIC region
http://www.apnic.net/policy/operational-policies-nirs
* APNIC and NIR Membership Relationship Agreement
http://www.apnic.net/nir-agreement
2.1.3. Local Internet Registry (LIR)
A Local Internet Registry (LIR) is an IR that primarily assigns address space to the users of
the network services that it provides.
LIRs are generally Internet Service Providers (ISPs) and may assign address space to their own https://www.apnic.net/about-apnic/corporate-documents/documents/corporate/definitions/
network infrastructure and to users of their network services. An LIR's customers may be other
"downstream" ISPs, which further assign address space to their own customers.
2.2. Address space 2.1. Address space
In this document, address space means public unicast IP address ranges, which include IP Address space refers to public unicast IP address ranges such as IP version 4 (IPv4)
version 4 (IPv4) and IP version 6 (IPv6). and IP version 6 (IPv6).
2.2.1. Delegated address space 2.1.1. Delegated address space
APNIC "delegates" addresses to its account holders. These delegations can be for use on their APNIC "delegates" addresses to its account holders. These delegations can be for use on their
own infrastructure (an "assignment") or for subsequent delegation by the requestors to its own infrastructure (an "assignment") or for subsequent delegation by the requestors to its
customers (an "allocation"). customers (an "allocation").
2.2.2. Allocated address space 2.1.2. Allocated address space
Allocated address space is address space that is distributed to IRs or other account holders Allocated address space is address space that is distributed to IRs or other account holders
for the purpose of subsequent distribution by them. for the purpose of subsequent distribution by them.
2.2.3. Assigned address space 2.1.3. Assigned address space
Assigned address space is address space that is delegated to an LIR, or end-user, for exclusive Assigned address space is address space that is delegated to an LIR, or end-user, for exclusive
use within the Internet infrastructure they operate. use within the Internet infrastructure they operate.
2.3. Autonomous System (AS) 2.2. Autonomous System (AS)
An Autonomous System (AS) is a connected group of one or more IP prefixes run by one or more An Autonomous System (AS) is a connected group of one or more IP prefixes run by one or more
network operators under a single and clearly defined routing policy. network operators under a single and clearly defined routing policy.
2.3.1. Autonomous System Number (ASN) 2.2.1. Autonomous System Number (ASN)
An Autonomous System Number (ASN) is a unique two- or four-byte number associated with an AS. An Autonomous System Number (ASN) is a unique two- or four-byte number associated with an AS.
The ASN is used as an identifier to allow the AS to exchange dynamic routing information with The ASN is used as an identifier to allow the AS to exchange dynamic routing information with
other Autonomous Systems. other Autonomous Systems.
2.4. Multihomed 2.3. Multihomed
Multihoming is a way of connecting an autonomous network to the public Internet through more Multihoming is a way of connecting an autonomous network to the public Internet through more
than one AS. than one AS.
2.5. Internet resources 2.4. Usage rate
Internet resources are public IPv4 and IPv6 address numbers, Autonomous System Numbers, and
reverse DNS delegations.
2.5.1. Current resources
Current resources are Internet resources registered by APNIC under explicit policies and
agreements.
2.5.2. Historical resources
Historical resources are Internet resources registered under early registry policies without
formal agreements and include:
* Registrations transferred to APNIC as part of the AUNIC to APNIC migration
o Some historical resource registrations have been inherited by APNIC from the former AUNIC
address registry.
o A list of resources transferred to APNIC as part of the migration is available on the APNIC
website at: http://www.apnic.net/aunic
* Registrations transferred as part of the Early Registration Transfer (ERX) project
o Most historical registrations were initially made by the global registries that predated
ARIN, such as DDN-NIC, SRI-NIC, and InterNIC. ARIN inherited these registrations
automatically when it was established. Historical registrations made to organizations in
the APNIC region were transferred to APNIC during 2003 and 2004 as part of the RIRs' Early
Registration Transfer (ERX) project.
o A list of resources transferred to APNIC as part of the ERX project is available at:
http://www.apnic.net/erx
* Historical APNIC resources
o Historical APNIC resources were delegated to organizations by APNIC prior to the introduction
of a Membership structure. These resources have always been registered in the APNIC Whois
Database, but if the resource holder did not become an APNIC Member at any time after the
introduction of the Membership structure, the resources were not made subject to current
APNIC policies.
2.6. Internet Exchange Point (IXP)
An Internet Exchange Point (IX or IXP) is a layer 1 and layer 2 network structure that
interconnects three or more Autonomous Systems (AS) for the purpose of Internet traffic
interchange.
2.7. Usage rate
Usage rate is the rate at which the LIR made delegations from relevant past address space, Usage rate is the rate at which the LIR made delegations from relevant past address space,
including Historical delegations. including Historical delegations.
2.8. Utilization 2.5. Utilization
Utilization is a measure of IPv6 address usage where "utilization" is only measured in terms Utilization is a measure of IPv6 address usage where "utilization" is only measured in terms
of the bits to the left of the /56 boundary. In other words, utilization refers to the of the bits to the left of the /56 boundary. In other words, utilization refers to the
delegation of /56s to end sites, and not the number of addresses assigned within individual /56s delegation of /56s to end sites, and not the number of addresses assigned within individual /56s
at those end sites. at those end sites.
2.8.1. HD-Ratio 2.5.1. HD-Ratio
The HD-Ratio is a way of measuring the efficiency of address assignment [RFC 3194]. It is an The HD-Ratio is a way of measuring the efficiency of address assignment [RFC 3194]. It is an
adaptation of the H-Ratio originally defined in [RFC1715] and is expressed as follows: adaptation of the H-Ratio originally defined in [RFC1715] and is expressed as follows:
Log (number of allocated objects) Log (number of allocated objects)
HD = ------------------------------------------------------------- HD = -------------------------------------------------------------
Log (maximum number of allocatable objects) Log (maximum number of allocatable objects)
where (in the case of this document) the objects are IPv6 site addresses (/56s) assigned from where (in the case of this document) the objects are IPv6 site addresses (/56s) assigned from
an IPv6 prefix of a given size. an IPv6 prefix of a given size.
2.9. End-site 2.6. End-site
An end site is defined as the location of an end-user who has a business or legal relationship An end site is defined as the location of an end-user who has a business or legal relationship
(same or associated entities) with a service provider that involves: (same or associated entities) with a service provider that involves:
* that service provider assigning address space to the end-user location * that service provider assigning address space to the end-user location
* that service provider providing transit service for the end-user location to other sites * that service provider providing transit service for the end-user location to other sites
* that service provider carrying the end-user's location traffic * that service provider carrying the end-user's location traffic
* that service provider advertising an aggregate prefix route that contains the end-user's * that service provider advertising an aggregate prefix route that contains the end-user's
location assignment location assignment
2.10. End-user 2.7. End-user
Service subscriber or customer of an LIR. Service subscriber or customer of an LIR.
2.11. aut-num object 2.8. aut-num object
An aut-num object is an object in the Whois database used to register ASN assignment details. An aut-num object is an object in the Whois database used to register ASN assignment details.
For the purposes of this document, aut-num object also refers to the ASN registration objects For the purposes of this document, aut-num object also refers to the ASN registration objects
in NIR databases. in NIR databases.
2.12. Routing policy 2.9. Routing policy
The routing policy of an AS is a description of how network prefixes are exchanged between that The routing policy of an AS is a description of how network prefixes are exchanged between that
AS and other Autonomous Systems. AS and other Autonomous Systems.
2.13. Transfers 2.10. Transfers
Resource transfers involve the re-allocation of current address blocks (or ASNs), or the Resource transfers involve the re-allocation of current address blocks (or ASNs), or the
re-allocation of historical resources claimed and transferred to an APNIC account holder. re-allocation of historical resources claimed and transferred to an APNIC account holder.
2.13.1. Counterpart RIR 2.10.1. Counterpart RIR
A counterpart RIR is the Regional Internet Registry that APNIC transfers resources to, or from, A counterpart RIR is the Regional Internet Registry that APNIC transfers resources to, or from,
in an inter-RIR transfer. in an inter-RIR transfer.
2.13.2. Source 2.10.2. Source
The source in a resource transfer is the organization which, prior to the transfer, is the The source in a resource transfer is the organization which, prior to the transfer, is the
legitimate holder of the resources to be transferred. Where the source is in the APNIC region, legitimate holder of the resources to be transferred. Where the source is in the APNIC region,
the source must be a current APNIC account holder, except in the case of an Historical resource the source must be a current APNIC account holder, except in the case of an Historical resource
transfer. Where the source is from another RIR region, it must be that RIR's equivalent to transfer. Where the source is from another RIR region, it must be that RIR's equivalent to
the "Source" as defined here. the "Source" as defined here.
2.13.3. Recipient 2.10.3. Recipient
The recipient in a resource transfer is the organization which, after the transfer is completed, The recipient in a resource transfer is the organization which, after the transfer is completed,
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.
2.11. Multiple Discrete Networks
Where an organization demonstrates a compelling need, or requirement, to build discrete networks
due to regulatory, geographic, or operational reasons and these networks are advertised either
internally, or externally, the network may be defined by APNIC as being composed of discrete networks.
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 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. maintain full documentation of and transparency within the decision-making process.
3.1. Goals of resource management 3.1. Goals of resource management
skipping to change at line 602 skipping to change at line 534
A resource delegation is valid only while the original criteria on which it was made remains valid. If a delegation becomes invalid, then the resource must be returned to the appropriate IR. A resource delegation is valid only while the original criteria on which it was made remains valid. If a delegation becomes invalid, then the resource must be returned to the appropriate IR.
An allocation or assignment becomes invalid if it is: An allocation or assignment becomes invalid if it is:
* Made for a specific purpose that no longer exists, or * Made for a specific purpose that no longer exists, or
* Based on information that is later found to be false or incomplete. * Based on information that is later found to be false or incomplete.
4.2. Closure and recovery 4.2. Closure and recovery
If an LIR holding APNIC address space ceases to provide Internet connectivity services, all of its address space must be returned to APNIC. It is the responsibility of the LIR (or any liquidator or administrator appointed to wind up the account holder's business) to advise all of its customers that address space will be returned to APNIC, and that renumbering into new address space will be necessary. If an LIR holding APNIC address space ceases to provide Internet connectivity services, all of its address space must be returned to APNIC. It is the responsibility of the LIR (or any liquidator or administrator appointed to wind up the account holder's business) to advise all of its customers that address space will be returned to APNIC, and that renumbering into new address space will be necessary.
In the case that a new LIR takes over the business or infrastructure of the closed LIR, the existing address space may be transferred to the new LIR, however such a transfer is subject to re-examination by APNIC and may be treated as a new address request process. In the case that a new LIR takes over the business or infrastructure of the closed LIR, the existing address space may be transferred to the new LIR, however such a transfer is subject to re-examination by APNIC and may be treated as a new address request process.
4.2.1. Recovery of unused historical resources 4.3. Claiming and re-delegating historical resources
A significant number of historical resources registered in the APNIC Whois Database are not announced to the global routing table. Historical resources that are no longer published in the APNIC Whois Database and are placed in reserved status because of EC resolution 2021-09 of 22 February 2021 (https://www.apnic.net/wp-content/uploads/2021/06/FINAL_merged_EC_meeting_minutes20210222_0304_public_final.pdf), can be claimed by the custodians within 12 months of the date they were marked as reserved.
To recover these globally un-routed resources and place them back in the free pool for re-delegation, APNIC will contact networks responsible for historical address space in the APNIC region that has not been globally routed since 1 January 1998. After 12 months, these resources will be placed in the free pool for re-delegation.
To recover un-routed historical AS numbers, APNIC will contact networks responsible for resources not globally used for a reasonable period of time. Any historical resources marked as reserved and/or reclaimed by APNIC due to account closures will lose their historical status and become current resources for re-delegation.
5.0. Resource Management 5.0. Resource Management
All NIRs and LIRs that receive address space from APNIC (either directly or indirectly) must adopt delegation policies that are consistent with the policies described in this document. All NIRs and LIRs that receive address space from APNIC (either directly or indirectly) must adopt delegation policies that are consistent with the policies described in this document.
NIRs and LIRs must ensure that address space for which they are responsible is only allocated or assigned subject to agreements consistent with the license provisions in this document. NIRs and LIRs must ensure that address space for which they are responsible is only allocated or assigned subject to agreements consistent with the license provisions in this document.
Also, NIRs must, wherever possible, apply slow start policies to their own account holders in a manner consistent with the way APNIC applies such policies. Also, NIRs must, wherever possible, apply slow start policies to their own account holders in a manner consistent with the way APNIC applies such policies.
5.1. How APNIC manages address space 5.1. How APNIC manages address space
skipping to change at line 798 skipping to change at line 730
5.7.5. Fees for experimental allocations 5.7.5. Fees for experimental allocations
Experimental allocations are available to APNIC account holders only. Experimental allocations are available to APNIC account holders only.
New applicants wishing to receive experimental allocation will need to become an APNIC account holder. If you are already a member of APNIC, then you do not have to pay anything extra for an experimental allocation. Also, the experimental allocation will not be counted in calculating the account holder's membership tier. New applicants wishing to receive experimental allocation will need to become an APNIC account holder. If you are already a member of APNIC, then you do not have to pay anything extra for an experimental allocation. Also, the experimental allocation will not be counted in calculating the account holder's membership tier.
Part 2: IPv4 Policy Part 2: IPv4 Policy
6.0. Initial IPv4 delegations 6.0. Initial IPv4 delegations
6.1. Minimum and maximum IPv4 delegations 6.1. Minimum and maximum IPv4 delegations
The current minimum delegation size for IPv4 is a /24 (256 addresses). The current minimum delegation size for IPv4 is a /24 (256 addresses).
Since Thursday, 28 February 2019, each APNIC account holder is only eligible to receive IPv4 address delegations totalling a maximum /23 from the APNIC 103/8 IPv4 address pool. Since Thursday, 28 February 2019, each APNIC account holder is only eligible to receive IPv4 address delegations totalling a maximum /23 from the APNIC 103/8 IPv4 address pool.
On Tuesday, 2 July 2019, non-103/8 resources waiting list was abolished and only new APNIC account holders are eligible to receive IPv4 delegation from the remaining IPv4 pool.
On Tuesday, 2 July 2019, the waiting list for non-103/8 resources was abolished and recovered non-103/8 resources will be considered the same as 103/8 addresses in the remaining IPv4 pool for delegations according to the current policy.
Note: A waiting list will be created once APNIC runs out of all IPv4 addresses. Any requests received from the new applicants for IPv4 resources will be put on this waiting list on a first come first request. APNIC will maintain one IPv4 pool for all recovered as well as IANA delegated address space and this pool will be used to provide IPv4 resources to the waiting list requests. Note: A waiting list will be created once APNIC runs out of all IPv4 addresses. Any requests received from the new applicants for IPv4 resources will be put on this waiting list on a first come first request. APNIC will maintain one IPv4 pool for all recovered as well as IANA delegated address space and this pool will be used to provide IPv4 resources to the waiting list requests.
To receive delegations from this pool, they must demonstrate their eligibility by meeting the criteria specified below. To receive delegations from this pool, they must demonstrate their eligibility by meeting the criteria specified below.
6.2. IPv4 request criteria 6.2. IPv4 request criteria
To qualify for an IPv4 address delegation from APNIC, requestors must demonstrate their eligibility under one of the following four criteria. To qualify for an IPv4 address delegation from APNIC, requestors must demonstrate their eligibility under one of the following four criteria.
* IPv4 for LIRs * IPv4 for LIRs
* IPv4 for multihoming * IPv4 for multihoming
* IPv4 for critical infrastructure * IPv4 for critical infrastructure
* IPv4 for Internet Exchange Points * IPv4 for Internet Exchange Points
6.2.1. IPv4 for LIRs 6.2.1. IPv4 for LIRs
skipping to change at line 982 skipping to change at line 918
3. If the customer ceases to receive connectivity from the requesting account holder it must return the ASN. The requesting account holder is expected to enter into an agreement with the customer to this effect. 3. If the customer ceases to receive connectivity from the requesting account holder it must return the ASN. The requesting account holder is expected to enter into an agreement with the customer to this effect.
4. Any ASNs returned to the requesting account holder must then be returned to APNIC or the relevant NIR. 4. Any ASNs returned to the requesting account holder must then be returned to APNIC or the relevant NIR.
5. Alternatively, the same ASN could be registered: 5. Alternatively, the same ASN could be registered:
* via transfer to another APNIC member (upstream provider connecting that customer), or * via transfer to another APNIC member (upstream provider connecting that customer), or
* directly by the customer in cases when they become an APNIC/NIR member and receives * directly by the customer in cases when they become an APNIC/NIR member and receives
* that ASN via transfer. * that ASN via transfer.
10.5. Two-byte only and four-byte AS Numbers 10.5. Two-byte only and four-byte AS Numbers
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. 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.
10.6. ROA/whois object with Private, Reserved and Unallocated (reserved/available) Origin ASN
The origin AS can only be from the IANA specified range and must not contain any IANA unallocated ASN and/or an ASN from:
- 23456 # AS_TRANS RFC6793
- 64496-64511 # Reserved for use in docs and code RFC5398
- 64512-65534 # Reserved for Private Use RFC6996
- 65535 # Reserved RFC7300
- 65536-65551 # Reserved for use in docs and code RFC5398
- 65552-131071 # Reserved
- 4200000000-4294967294 # Reserved for Private Use RFC6996
- 4294967295 # Reserved RFC7300
APNIC account holders are not permitted from creating ROAs with the above-mentioned ASN, Any existing ROAs with these ASN will not be automatically renewed and deleted after notifying the account holder.
AS0 (zero) is also a Reserved ASN (RFC7607) but will be exempted from this restriction as AS0 is reserved by the IANA such that it may be used to identify non-routed networks (RFC6483 Sec 4).
If the Origin ASN has been marked as unallocated (reserved/available) or from the above-mentioned ASN list, APNIC will notify the account holder to update the ROA with a valid ASN.
Same policy applies to corresponding ROAs for route/route6 whois objects.
10.7. AS-SET
An as-set (RFC 2622 Section 5.1) provides a way to document the relationship between ASes which can then be publicly verified. RFC2622 further defines 2 categories for as-set which can be Hierarchical or Non Hierarchical. A hierarchical set name is a sequence of set names and AS numbers separated by colons.
Non hierarchical as-set pose a security issue where any one can create an as-set without any authentication or authorisation. Since many peering filters are based on as-set, creating a blank as-set or as-set with wrong members can cause automated filters to apply empty prefix-filters to BGP session.
To prevent account holders from creating as-sets that already exist in other IRR databases, APNIC account holders are only permitted to create hierarchical as-sets. At least one component of such a name must be an actual set name. All the set name components of an hierarchical name has to be of the same type.
Any non hierarchical as-set can not be used as a parent to create a hierarchical as-set and this will not be allowed.
Part 5: Transfer Policy Part 5: Transfer Policy
11.0. IPv4 Transfers 11.0. IPv4 Transfers
IPv4 addresses 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 to the appropriate IR. IPv4 addresses 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 to the appropriate IR.
The goal of the APNIC transfer policy is to help distribute IPv4 addresses from those who no longer need the addresses, to those that need the addresses, but cannot obtain them from the free pool. The goal of the APNIC transfer policy is to help distribute IPv4 addresses from those who no longer need the addresses, to those that need the addresses, but cannot obtain them from the free pool.
APNIC recognizes there will be situations where IPv4 resources may be transferred between: APNIC recognizes there will be situations where IPv4 resources may be transferred between:
* Current APNIC account holders * Current APNIC account holders
* Current APNIC account holders and organizations in other RIR regions * Current APNIC account holders and organizations in other RIR regions
* Holders of Historical IPv4 addresses without an APNIC account to current APNIC account holders * Holders of Historical IPv4 addresses without an APNIC account to current APNIC account holders
* Organizations through a merger, acquisition, or takeover. * Organizations through a merger, acquisition, or takeover.
 End of changes. 34 change blocks. 
120 lines changed or deleted 87 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/