ipv6-guidelines-v010.txt		ipv6-guidelines-draftv011.txt
	--------------------------------------------------------------------		--------------------------------------------------------------------
	APNIC Document identity		APNIC Document identity
	Title: APNIC guidelines for IPv6 allocation and assignment		Title: APNIC guidelines for IPv6 allocation and assignment
	requests		requests
	Short title: ipv6-guidelines		Short title: ipv6-guidelines
	Document ref: APNIC-114		Document ref: APNIC-114
	Version: 010		Version: 011
	Date of original publication: 2 July 2004		Date of original publication: 2 July 2004
	Date of this version: 4 November 2013		Date of this version: xx July 2023
	Review scheduled: n/a		Review scheduled: n/a
	Obsoletes: apnic-114-009		Obsoletes: apnic-114-010
	Status: Active		Status: Draft
	Comments: Re-order document, correct error		Comments: Implements prop-145
	in previous version, and general
	improvements.
	---------------------------------------------------------------------		---------------------------------------------------------------------
	About this document		About this document
	-------------------		-------------------
	These guidelines are intended to complement the document IPv6 address		These guidelines are intended to complement the document IPv6 address
	allocation and assignment policy.		allocation and assignment policy.
	http://www.apnic.net/policy/ipv6-address-policy		http://www.apnic.net/policy/ipv6-address-policy
	These guidelines will be updated from time to time, in consultation with		These guidelines will be updated from time to time, in consultation with
	skipping to change at line 50 ¶		skipping to change at line 48 ¶
	3. Additional guidance		3. Additional guidance
	4. Goals of address space management		4. Goals of address space management
	5. Application of guidelines		5. Application of guidelines
	Section 2: General guidelines		Section 2: General guidelines
	6. Definitions		6. Definitions
	6.1. End Site
	6.2. Multiple Discrete Networks
	7. Sparse Delegation Framework		7. Sparse Delegation Framework
	7.1. Avoiding Fragmentation		7.1. Avoiding Fragmentation
	8. Allocations to LIRs		8. Allocations to LIRs
	8.1. Initial allocation criteria		8.1. Initial allocation criteria
	8.1.1. A plan for 200 assignments		8.1.1. A plan for 200 assignments
	8.1.2. Existing LIRs with IPv4 allocations from APNIC or an		8.1.2. Existing LIRs with IPv4 allocations from APNIC or an
	NIR		NIR
	8.1.3. Initial allocation larger than /32		8.1.3. Initial allocation larger than /32
	skipping to change at line 169 ¶		skipping to change at line 165 ¶
	It is intended that NIRs will either adopt these, or similar, guidelines		It is intended that NIRs will either adopt these, or similar, guidelines
	for their own members.		for their own members.
	Section 2: General guidelines		Section 2: General guidelines
	------------------------------------------------------------------------		------------------------------------------------------------------------
	6. Definitions		6. Definitions
	---------------		---------------
	6.1. End Site		Terms not defined in this document have the meaning given to them in the APNIC
			Definition Document and Policy Document.
	Section 2.9 of "IPv6 address allocation and assignment policy"
	defines an end site as "an end user (subscriber) who has a
	business relationship with a service provider". That section
	also lists some possible business relationships (which would
	normally be found in the contract between the LIR and their
	customer) that typically indicate end sites. End sites do not
	re-assign any of their IP addresses to other organizations.
	Examples:
	Single end site
	- A home or corporate user who has a single contract with a
	service provider for their own device or network.
	- A home or corporate user who has multiple devices to connect
	the Internet, but has only one contract with a service
	provider.
	Multiple sites
	- A home or corporate user who has multiple contracts with one
	or more service providers.
	- A home or corporate user who has multiple separate networks
	that are not connected to each other because each network
	has a different management policy, even if they are in the
	same place (for example, a merged company with independent
	networks).
	6.2. Multiple Discrete Networks
	Where an organization demonstrates a compelling need, or		https://www.apnic.net/about-apnic/corporate-documents/documents/corporate/definitions/
	requirement, to build discrete networks due to regulatory,		https://www.apnic.net/community/policy/resources
	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.
	7. Sparse Delegation Framework		7. Sparse Delegation Framework
	-------------------------------		-------------------------------
	APNIC delegates blocks of IPv6 address space to resource holders		APNIC delegates blocks of IPv6 address space to resource holders
	according to a "sparse delegation" algorithm. This delegation		according to a "sparse delegation" algorithm. This delegation
	process is designed to maximize the growth potential for each		process is designed to maximize the growth potential for each
	delegation by maximizing the distance between them.		delegation by maximizing the distance between them.
	The following illustration shows the order in which a sequence of		The following illustration shows the order in which a sequence of
End of changes. 6 change blocks.
	47 lines changed or deleted		9 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/