Guide to the APNIC IPv6 Allocation Request Form (text version)

Additional information area

The additional information area allows you to provide other information that may be helpful for your request.

Other details you may need to provide in additional information

If your organisation has published information online about its proposed IPv6 services, please provide a URL where APNIC view that information.

You are not required to provide a public link to your network services plan; however, if it is available, it may help to provide APNIC a better understanding of your request.

Please provide a network diagram showing your IPv6 network. In your diagram, please indicate approximate deployment dates for planned infrastructure and estimates of the IPv6 address space to be assigned in each part of the network.

Under the IPv6 allocation policy, you are required to demonstrate that you have a plan for making at least 200 assignments to other organisations within two years. Your network diagram must support this requirement.

An example of a network diagram is provided below.

You can send your diagram in one of the following formats: ASCII, JPEG, GIF, PostScript, PDF, Visio, MS Word, or MS PowerPoint.

If your organisation has an existing allocation from APNIC or an NIR, and chooses this option to justify the allocation, please outline the following:

list of existing IPv4 allocation(s) made by APNIC or an NIR
confirm the commitment to make IPv6 assignments and/or sub-allocations
agree to announce the IPv6 allocation in the routing table within 2 years

Please note that historical IP ranges do not meet the criteria of being an existing allocation from APNIC or an NIR.

If you are requesting an initial allocation greater than the /32 minimum allocation, please provide details of your IPv4 network here. This information is separate from the IPv6 customer network details provided in the "IPv6 Usage Template".

You should provide information regarding your existing IPv4 network services and projected IPv6 services in the following format:

<service>, <ports>, <ipv4-static>, <ipv4-dynamic>, <ipv6-static>, <ipv6-dynamic>

Attribute (long)	Attribute (short)	Definition/explanation
Service	service	List the type of service provided, eg. ADSL, dial-up, cable. Fill out a new line for each type of service provided. Example: ADSL
Number of ports	ports	List the number of ports provided for this service. Example: 65000
Number of static IPv4 customers	ipv4-static	List the number of customers to whom you currently provide static IPv4 addresses. Example: 10000
Number of dynamic IPv4 customers	ipv4-dynamic	List the number of customers to whom you currently provide dynamic IPv4 addresses. Example: 10000
Number of static IPv6 customers	ipv6-static	List the number of customers to whom you plan to provide static IPv6 addresses. Example: 10000
Number of dynamic IPv6 customers	ipv6-dynamic	List the number of customers to whom you plan to provide dynamic IPv6 addresses. Example: 10000

Important notes on the existing network field

The IPv6 allocation policy allows the extent of existing IPv4 infrastructure to be considered when the amount of address space requested exceeds the minimum allocation size (/32). If you are simply requesting a /32 address range, then you do not need to provide any IPv4 information here.

Example:

existing-network: ADSL, 20000, 10000, 5000, 10000, 5000

existing-network: Cable, 65536, 20000, 500, 20000, 500

existing-network: Dial-up, 120, 60, 300, 60, 300

Do you have any additional comments?

Only provide additional comments here if you feel that any aspects of your application may not be clear from the information provided above.

Example of a network diagram:

Diagram