IPv6 Usage template

The IPv6 Usage template is used to provide details of your current network and your future network plans.

Attributes in Network template:

services:
cust-types:
cust-network:
infrastructure:
network-plan:

Types of service offered (services)

The types of services offered (services) attribute lists the types of network services to be offered in the IPv6 network. This information is useful for APNIC to understand the type of network that is being planned.

Common values for this field are: leased line, dial up, facilities management, web hosting, VOIP, and transit. Please describe the services as briefly as possible.

Example:

services: leased line, dial up, web hosting

Top

Types of customer (cust-types)

The types of customer (cust-types) attribute lists the types of customer that will be provided services from this network.

Common values for this field are: residential, small office, business, education, government, ISP. Please describe the types of customer as briefly as possible.

Example:

cust-type: residential, small office, business, ISP

Top

Customer network assignments (cust-network)

The cust-network attribute summarises past IPv6 assignments made to customers of this network. This field is used by APNIC to establish the patterns of address assignment in this network.

If you have not been allocated any IPv6 addresses in the past, please leave this section blank.

If you have assigned IPv6 networks to customers, you must provide the assignment information for those networks in the following format (using multiple lines as necessary):

<subnet-size> <netname>

Attribute (long)

Attribute (short)

Definition/explanation

Size of customer subnet

subnet-size

The size of the subnet assigned to the customer, as a prefix in slash notation.

Example:

/48

Name of customer subnet

netname

The name you assigned to this customer's network, as found in the APNIC database.

Important notes on the cust-network attribute

Do not list IPv4 assignments in this attribute.
Please enter the netname exactly as it appears in the assignment details registered in the APNIC Whois database.
APNIC considers the sum of the addresses described in both the cust-network field and the infrastructure field when evaluating the address utilisation of an organisation. This is used to determine whether that organisation qualifies for a subsequent allocation.

Example:

cust-network: /48 FOONET-AP
cust-network: /48 BARNET-AP

Top

Network Infrastructure (infrastructure)

The infrastructure attribute summarises the IPv6 address assignments made to the organisation's network infrastructure. These addresses are not used for customer assignments.

This field is used by APNIC to establish the patterns of address assignment within this network.

You should provide descriptions of all assignments made to your network infrastructure in the following format:

<subnet-size> <descr>

Attribute (long)

Attribute (short)

Definition/explanation

Size of infrastructure subnet

subnet-size

The size of the subnet assigned to the infrastructure, as a prefix in slash notation.

Example:

/48

Description of infrastructure subnet

descr

A brief description of this element of your infrastructure.

Important notes on the infrastructure attribute

Do not list IPv4 assignments in this attribute.
Do not use the infrastructure field to describe networks which you are not yet using.
APNIC considers the sum of the addresses described in both the cust-network field and the infrastructure field when evaluating the address utilisation of an organisation. This is used to determine whether that organisation qualifies for a subsequent allocation.

Example:

infrastructure: /58   2 routers, 32 serial ports,16 FastEthernet ports, 3 ATM ports (Backbone)
infrastructure: /64 Internal LAN for Head office
infrastructure: /62   LANs of branch Offices
infrastructure: /48   Network Segment for DMZ POP

Top

Future network plan (network-plan)

The network-plan attribute summarises the address assignments planned for the organisation's network infrastructure, for up to two years. If specific customer assignments are known then they may also be included here.

This field is used by APNIC to evaluate whether the organisation has a realistic plan for making at least 200 assignments to other organisations within two years.

You should provide details of your future network plan in the following format (using multiple lines as necessary):

<subnet-size> <now/1yr/2yr> <descr>

Attribute (long)	Attribute (short)	Definition/explanation
Size of planned subnet	subnet-size	The size of the planned subnet assignment, as a prefix in slash notation. Example: /48
Deploy now	now	Use this value if you plan to make the assignment to this subnet upon receiving an IPv6 allocation.
Deploy within 1 year	1yr	Use this value if you plan to make the assignment to this subnet within one year of receiving an IPv6 allocation.
Deploy within 2 years	2yr	Use this value if you plan to make the assignment to this subnet within two years of receiving an IPv6 allocation.
Description of assignment	decsr	A brief description of this planned assignment. Example: Web hosting facility

Important notes on the network-plan attribute

Do not list IPv4 assignments in this attribute.
APNIC will use the information provided in this attribute to determine whether the network you are planning appears to be capable of supporting at least 200 customer assignments within two years. It is not necessary for you to list all of those customer assignments.

Example:

network-plan: /50  /56,/56,/50 Head Office Lan (Support, marketing, sales etc)
network-plan: /64  /64,/64,/64 100 FreeBSD servers for web and mail hosting
network-plan: /48  /48,/48,/48 8x7600 Series ACME router for Mabuhay POP

Top | Guide to the APNIC IPv6 Allocation Request Form