apnic-resource-policies.txt		apnic-resource-policies-DRAFT-v14.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: 013		Version: 014
	Date of original publication: 05 March 2015		Date of original publication: 05 March 2015
	Date of this version: 20 July 2023		Date of this version: TBA
	Review scheduled: n/a		Review scheduled: n/a
	Obsoletes: apnic-127-v012		Obsoletes: apnic-127-v013
	Status: Active		Status: Draft
	Comments: Implements prop-145, 147, prop-150, prop-151		Comments: Implements prop-155
	-------------------------------------------------------------------------------------------		-------------------------------------------------------------------------------------------
	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. Address space		2.1. Address space
	2.2. Autonomous System (AS)		2.2. Autonomous System (AS)
	skipping to change at line 104 ¶		skipping to change at line 104 ¶
	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
	11.2.3. Conditions on the recipient of the transfer		11.2.3. Conditions on the recipient of the transfer
	11.3. Transfer of Historical Internet resources		11.3. Transfer of Historical Internet resources
	11.3.1. Transfer procedure		11.3.1. Transfer procedure
	11.3.2. Policies applicable to transferred Historical resources		11.3.2. Policies applicable to transferred Historical resources
	12.0. ASN Transfers		12.0. ASN Transfers
	12.1. Transfers of ASNs between APNIC resource holders		12.1. Transfers of ASNs between APNIC resource holders
	12.1.1. Conditions on resource		12.1.1. Conditions on resource
	12.1.2. Conditions on source of the transfer		12.1.2. Conditions on source of the transfer
	12.1.3. Conditions on recipient of the transfer		12.1.3. Conditions on recipient of the transfer
	12.2. Inter-RIR ASN transfers		12.2. Inter-RIR ASN transfers
	12.2.1. Conditions on the space to be transferred		12.2.1. Conditions on the space to be transferred
	12.2.2. Conditions on the source of the transfer		12.2.2. Conditions on the source of the transfer
	12.2.3. Conditions on the recipient of the transfer		12.2.3. Conditions on the recipient of the transfer
	13.0. IPv6 Transfers		13.0. IPv6 Transfers
			13.1. Provider Independent (PI) IPv6 assignment
	14.0. Mergers & Acquisitions		14.0. Mergers & Acquisitions
	14.1. Updating registration details		14.1. Updating registration details
	14.2. Effect on membership agreement		14.2. Effect on membership agreement
	14.3. Consequences for allocations		14.3. Consequences for allocations
	15. Appendix A: HD-Ratio		15. Appendix A: HD-Ratio
	Part 1: Policy Environment		Part 1: Policy Environment
	1.0. Introduction		1.0. Introduction
	skipping to change at line 869 ¶		skipping to change at line 873 ¶
	* Regional Internet Registry (RIRs); and		* Regional Internet Registry (RIRs); and
	* National Internet Registry (NIRs).		* National Internet Registry (NIRs).
	Assignments to critical infrastructure are available only to the actual operators of the network infrastructure performing such functions. Registrar organizations which do not actually host the network housing the registry infrastructure, will not be eligible for an assignment under this policy.		Assignments to critical infrastructure are available only to the actual operators of the network infrastructure performing such functions. Registrar organizations which do not actually host the network housing the registry infrastructure, will not be eligible for an assignment under this policy.
	The maximum assignment made under these terms is /32 per account holder.		The maximum assignment made under these terms is /32 per account holder.
	9.1.3. IPv6 for Internet Exchange Points		9.1.3. IPv6 for Internet Exchange Points
	Internet Exchange Points are eligible to receive a portable assignment from APNIC to be used exclusively to connect the IXP participant devices to the Exchange Point.		Internet Exchange Points are eligible to receive a portable assignment from APNIC to be used exclusively to connect the IXP participant devices to the Exchange Point.
	The minimum assignment made under these terms is /48.		The minimum assignment made under these terms is /48.
	Global routability of the portable assignment is left to the discretion of the IXP and its participants.		Global routability of the portable assignment is left to the discretion of the IXP and its participants.
	9.1.4. Provider Independent IPv6 assignment		9.1.4. Provider Independent (PI) IPv6 assignment
	Requests for Provider Independent assignments must include a detailed plan of intended usage of the proposed address block over at least the 12 months following the allocation.		Applicants who can commit to using and advertizing the IPv6 address space within twelve (12) months from the date of their assignment are eligible for an IPv6 Provider Independent delegation.
	9.1.4.1. Initial assignment		9.1.4.1. Initial assignment
	Applicants are eligible for an IPv6 Provider Independent delegation if they are able to demonstrate a valid reason that an assignment from their ISP, or LIR, is not suitable. For guidelines on what will be considered a valid technical or other reason, see "APNIC guidelines for IPv6 allocation and assignment requests".		The initial IPv6 PI assignment to eligible applicants is /48.
	http://www.apnic.net/ipv6-guidelines
	The minimum size of the assignment is a /48 per end-site. The considerations of Section 5.2.3.3 Assignment of multiple /48s to a single end-site, must be followed if multiple /48s are requested.
	http://www.apnic.net/ipv6-guidelines
	9.1.4.2. Subsequent assignment		9.1.4.2. Subsequent assignment
	Subsequent Provider Independent assignments may be delegated to account holders that are able to demonstrate		For additional IPv6 PI address space requirements exceeding /48, account holders must follow the Section 9.2, "Subsequent assignments," in APNIC guidelines for IPv6 allocation and assignment requests.
	* why an additional portable assignment is required and why an assignment from an ISP or other LIR cannot be used for this purpose;
	* that the use of the initial provider independent delegation generated the minimum possible number of global routing announcements and the maximum aggregation of that block; and,		https://www.apnic.net/about-apnic/corporate-documents/documents/resource-guidelines/ipv6-guidelines/#PI-subsequent
	* how the subsequent assignment will be managed to minimize the growth of the global IPv6 routing table.
			Subsequent IPv6 PI assignments requests will be evaluated based on the account holders demonstrated need and adherence to IPv6 policies.
	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
	An applicant is eligible for an ASN assignment if:		An applicant is eligible for an ASN assignment if:
	* the network is currently multihomed, or		* the network is currently multihomed, or
	* has the need to interconnect with other AS.		* has the need to interconnect with other AS.
	An applicant will also be eligible if the requestor can demonstrate that will meet the above criteria upon receiving an ASN (or within a reasonably short time thereafter).		An applicant will also be eligible if the requestor can demonstrate that will meet the above criteria upon receiving an ASN (or within a reasonably short time thereafter).
	skipping to change at line 1056 ¶		skipping to change at line 1058 ¶
	The conditions on the source of the transfer will be defined by the RIR where the source organization holds an account. This means:		The conditions on the source of the transfer will be defined by the RIR where the source organization holds an account. This means:
	* For transfers from an APNIC source, the source entity must be the currently registered resource holder of the resource, and not be involved in any dispute as to the status of those resources.		* For transfers from an APNIC source, the source entity must be the currently registered resource holder of the resource, and not be involved in any dispute as to the status of those resources.
	* Where the source is in another region, the conditions on the source as defined in the counterpart RIR's transfer policy at the time of the transfer will apply.		* Where the source is in another region, the conditions on the source as defined in the counterpart RIR's transfer policy at the time of the transfer will apply.
	12.2.3. Conditions on the recipient of the transfer		12.2.3. Conditions on the recipient of the transfer
	The conditions on the recipient of the transfer will be defined by the RIR where the recipient holds an account. This means:		The conditions on the recipient of the transfer will be defined by the RIR where the recipient holds an account. This means:
	* 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.		* 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.
	* 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.		* 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.
	13.0. IPv6 Transfers		13.0. IPv6 Transfers
	APNIC will only recognize the transfer or IPv6 addresses as the result of Merger & Acquisition activity.		APNIC will only recognize the transfer of IPv6 addresses as the result of Merger & Acquisition activity.
			13.1 Provider Independent (PI) IPv6 assignment
			The IPv6 PI address space delegated under Section 9.1.4 will be non-transferable. If this PI address space is not used or is no longer needed, it must be returned to APNIC.
	14.0. Mergers & Acquisitions		14.0. Mergers & Acquisitions
	APNIC will process and record the transfer of ASNs, IPv6, and IPv4 resources as the result of merger or acquisition.		APNIC will process and record the transfer of ASNs, IPv6, and IPv4 resources as the result of merger or acquisition.
	Addresses delegated from the 103/8 IPv4 free pool cannot be transferred for a minimum of five years after the original delegation.		Addresses delegated from the 103/8 IPv4 free pool cannot be transferred for a minimum of five years after the original delegation.
	The following conditions and consequences apply:
			The following conditions and consequences apply:
	14.1. Updating registration details		14.1. Updating registration details
	If an LIR 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 LIR changes name, then the LIR must provide to APNIC relevant legal documentation supporting the name change.		If an LIR 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 LIR changes name, then the LIR must provide to APNIC relevant legal documentation supporting the name change.
	14.2. Effect on membership agreement		14.2. Effect on membership agreement
	If an LIR change 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 LIR becomes a subsidiary of another entity, and the infrastructures of the respective entities remain fully independent, then the membership agreement may continue.		If an LIR change 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 LIR becomes a subsidiary of another entity, and the infrastructures of the respective entities remain fully independent, then the membership agreement may continue.
	14.3. Consequences for allocations		14.3. Consequences for allocations
	Following ownership change of an LIR, 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.		Following ownership change of an LIR, 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.
	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 LIR that is effectively subsumed.		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 LIR that is effectively subsumed.
	When assessing the status of allocations, APNIC requires full disclosure of all address space held by all of the entities in question. If full disclosure is not made, then APNIC will consider any allocations to be invalid and will require that they be returned.		When assessing the status of allocations, APNIC requires full disclosure of all address space held by all of the entities in question. If full disclosure is not made, then APNIC will consider any allocations to be invalid and will require that they be returned.
End of changes. 12 change blocks.
	17 lines changed or deleted		22 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/