diff-apnic-127-v006

	apnic-resource-policies.txt	apnic-127-v006-draft.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: 005	Version: 006
	Date of original publication: 5 March 2015	Date of original publication: 5 March 2015

	Date of this version: 20 December 2017	Date of this version: xx April 2019
	Review scheduled: n/a	Review scheduled: n/a

	Obsoletes: apnic-127-v004	Obsoletes: apnic-127-v005
	Status: Active	Status: Draft
	Comments: Implements prop-116, prop-121, and	Comments: Implements prop-125, and prop-127
	prop-122.
	———————————————————————-	———————————————————————-

	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

	skipping to change at line 1281 ¶	skipping to change at line 1281 ¶
	– For residential networks or users, the IR’s technical contact	– For residential networks or users, the IR’s technical contact
	may be registered as the admin-c.	may be registered as the admin-c.
	– For networks in exceptional circumstances that make it	– For networks in exceptional circumstances that make it
	impractical to maintain an on-site administrative contact, an	impractical to maintain an on-site administrative contact, an
	off-site person may be registered as the admin-c.	off-site person may be registered as the admin-c.

	The technical contact (“tech-c”) need not be physically	The technical contact (“tech-c”) need not be physically
	located at the site of the network, but must be a person who	located at the site of the network, but must be a person who
	is responsible for the day-to-day operation of the network.	is responsible for the day-to-day operation of the network.


	In addition, it is mandatory to register an Incident Response	In addition, it is mandatory to register an Incident Response Team (IRT)
	Team (IRT) object for each resource record in the APNIC Whois	object for each resource record in the APNIC Whois Database. Contact
	Database.	addresses listed in the IRT object (email, abuse-mailbox attributes) must
		be regularly monitored and any abuse complaints sent to these contacts must
		be responded to promptly to resolve the complaints.

		APNIC will validate IRT contacts periodically or every six (6) months to
		ensure they are accurate and contactable. Members are required to complete
		these validation checks within fifteen (15) days of receiving the validation
		check email from APNIC. If the IRT contacts fail the validation, APNIC will
		mark the IRT object invalid in the APNIC Whois Database and follow up according
		to relevant policies and procedures. If validation still fails after thirty (30)
		days, the Member will have limited access to MyAPNIC until their IRT contacts are
		validated.

	5.4. Reverse lookup	5.4. Reverse lookup
	——————-	——————-

	5.4.1. Responsibility to maintain IPv4 in-addr.arpa records	5.4.1. Responsibility to maintain IPv4 in-addr.arpa records
	———————————————————–	———————————————————–
	LIRs should maintain in-addr.arpa resource records for their	LIRs should maintain in-addr.arpa resource records for their
	customers’ networks. If a network is not specifically associated	customers’ networks. If a network is not specifically associated
	with an LIR then the in-addra.arpa records should be maintained	with an LIR then the in-addra.arpa records should be maintained
	by either the appropriate NIR or APNIC.	by either the appropriate NIR or APNIC.

	skipping to change at line 1581 ¶	skipping to change at line 1592 ¶
	——————-	——————-

	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	The current minimum delegation size for IPv4 is a /24 (256
	addresses).	addresses).


	Since Friday, 15 April 2011, each APNIC account holder is only	Since Thursday, 28 February 2019, each APNIC account holder
	eligible to receive IPv4 address delegations totalling a maximum /22	is only eligible to receive IPv4 address delegations totalling
	from the APNIC 103/8 IPv4 address pool.	a maximum /23 from the APNIC 103/8 IPv4 address pool.

	On Tuesday, 27 May 2014, each APNIC account holder became eligible	On Tuesday, 27 May 2014, each APNIC account holder became eligible
	to receive additional delegations up to a maximum of /22 address	to receive additional delegations up to a maximum of /22 address
	space from the APNIC non-103/8 Recovered IPv4 address pool.	space from the APNIC non-103/8 Recovered IPv4 address pool.

	Note: Resources may not always be available from the recovered	Note: Resources may not always be available from the recovered
	(non-103/8) address pool. APNIC has created a waiting list for those	(non-103/8) address pool. APNIC has created a waiting list for those
	IPv4 requests that cannot be fulfilled. These requests are fulfilled	IPv4 requests that cannot be fulfilled. These requests are fulfilled
	in order of request, as space becomes available.	in order of request, as space becomes available.


	skipping to change at line 1624 ¶	skipping to change at line 1635 ¶
	– 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
	——————–	——————–
	To be eligible for an initial IPv4 delegation, an LIR must:	To be eligible for an initial IPv4 delegation, an LIR must:

	– Have used a /24 from their upstream provider or demonstrate an	– Have used a /24 from their upstream provider or demonstrate an

	immediate need for a /24,	immediate need for a /24, and
	– Have complied with applicable policies in managing all address	– Have complied with applicable policies in managing all address
	space previously delegated to it (including Historical	space previously delegated to it (including Historical

	delegations), and	delegations).
	– Demonstrate a detailed plan for use of at least a /23 within
	a year

	6.2.2. IPv4 for multihoming	6.2.2. IPv4 for multihoming
	—————————	—————————
	An organization is eligible to receive an IPv4 delegation if:	An organization is eligible to receive an IPv4 delegation if:

	– it is currently multihomed, or	– it is currently multihomed, or
	– it is currently using at least a /24 from its upstream	– it is currently using at least a /24 from its upstream
	provider and intends to be multihomed, or	provider and intends to be multihomed, or
	– it intends to be multihomed, and advertise the prefixes within	– it intends to be multihomed, and advertise the prefixes within
	6 months	6 months

End of changes. 8 change blocks.
	17 lines changed or deleted	26 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/