ISP Technical template
The ISP Technical template is used to provide details of your current network and your future network plans.
APNIC account name (acct-name)
The acct-name attribute should contain your unique APNIC account name.
If you do not have an account name but wish to become an APNIC member, please see APNIC membership information.
If you are an APNIC member, but have forgotten your account name, please contact admin@apnic.net . You will need to provide details of the name and location of your organisation.
Note, IPv4 allocations are available only to current APNIC members. APNIC will not accept resource request forms be accepted without a completed account field, and requests will not be processed until required fees have been paid.
Example:
SPARKYNET-ID
Top
Internet connectivity type (connectivity)
The connectivity attribute describes you intend to connect the network to the Internet.
The three options for this field are:
- PEERING-POINT (meaning the network will connect to a neutral Internet exchange point at which three or more service providers share a common "layer 2 infrastructure" to exchange traffic)
- SERVICE-PROVIDER (meaning the network will connect to an Internet service provider)
- OTHER (meaning the network will connect to an organisation that is neither a peering point nor a service provider. If the OTHER option is selected then a description of the connection method should be included in the additional comments field)
You may select more than one option for this field. Use a separate line for each option.
Example:
connectivity: PEERING-POINT
Top
Connection provider (conn-provider)
The conn-provider attribute identifies the organisations which will provide Internet connection to this network.
If you indicated either PEERING-POINT or SERVICE-PROVIDER in the connectivity attribute, then list the names of all relevant organisations (one per line).
If you indicated OTHER in the connectivity field, then provide a brief description of the type of connection and the name of any relevant organisations.
Example:
conn-provider: MAE-West
Top
All zeroes subnet configuration (all-0s-subnets)
The all-0s-subnet attribute notes whether your network can support "all zeros" subnets.
Acceptable entries for this attribute are:
- YES (meaning your network can support "all zeroes")
- NO (meaning your network cannot support "all zeroes")
If you answer NO, please provide an explanation in the Additional Questions template. Note that all major router vendors can support all zeros subnets although it may be necessary to alter the default configuration to do so.
Example:
all-0s-subnets: YES
Top
All ones subnet configuration (all-1s-subnets)
The all-1s-subnet attribute notes whether your network can support "all ones" subnets.
Acceptable entries for this attribute are:
- YES (meaning your network can support "all ones")
- NO (meaning your network cannot support "all ones")
If you answer NO, please provide an explanation in the Additional Questions template. Note that all major router vendors can support all ones subnets although it may be necessary to alter the default configuration to do so.
Example:
all-1s-subnets: YES
Top
Supernetting (supernets)
The supernets attribute notes whether your network can support supernetting, meaning you are able to aggregate multiple contiguous networks into a single routing announcement.
Acceptable entries for this attribute are:
- YES (meaning your network can support supernetting)
- NO (meaning your network cannot support supernetting)
If you answer NO, please provide an explanation in the Additional Questions template.
Example:
supernets: YES
Top
Subnetting (subnets)
The subnets attribute notes whether your network can support subnetting, meaning you are able to separately route parts of a single routing prefix.
Acceptable entries for this attribute are:
- YES (meaning your network can support subnetting)
- NO (meaning your network cannot support subnetting)
If you answer NO, please provide an explanation in the Additional Questions template.
Note, APNIC assumes that ISPs will create subnets of their allocated address space to make assignments to their infrastructure and to customers. ISPs that do not follow this practice will be asked for justification when they apply for additional address space.
Example:
subnets: YES
Top
Customer network assignments (cust-network)
The cust-network attribute summarises past 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 addresses in the past, please leave this section blank.
If you have assigned networks to customers, you must provide the assignment information for those networks in the following format (using multiple lines as necessary):
<netname> <address> <mask> <hinit/h6mo/h1yr sinit/s6mo/s1yr date>
Attribute (long) |
Attribute (short) |
Definition/explanation |
Netname |
netname |
The name you assigned to each customers' network, as found in the APNIC database. Please note, the netname should relate to the customer that will be using the address space. |
Address |
address |
The starting address of the network assigned to the customer, in dotted decimal format.
Example:
255.255.248.0 |
Mask |
mask |
The subnet mask of the network, in dotted decimal format. |
Hosts now |
hinit |
The estimated initial number of devices on the network assigned to the customer. |
Hosts in 6 months |
h6mo |
The estimated number of devices on the network assigned to the customer in 6 months from now. |
Hosts in 1 year |
h1yr |
The estimated number of devices on the network assigned to the customer in 1 year from now. |
Subnets now |
sinit |
The estimated initial number of subnets on the network assigned to the customer. |
Subnets in 6 months |
s6mo |
The estimated number of subnets on the network assigned to the customer in 6 months from now. |
Subnets in 1 year |
s1yr |
The estimated number of subnets on the network assigned to the customer in 1 year from now. |
Date assigned |
date |
The date the assignment was made to the customer in YYYYMMDD format. |
Important notes on the cust-network attribute
- It is important that this field be specified correctly as APNIC evaluates future allocations on the basis of past assignment history.
- Please enter the netname exactly as it appears in the assignment details registered in the APNIC Whois database.
- If you have assigned a network to a customer in a non-CIDR fashion (that is, where there is no single subnet mask which can describe the subnet), then you must describe each contiguous part of that network as a separate subnet, repeating the network name as necessary.
- APNIC considers the sum of the addresses described in the cust-network field and the infrastructure field to be the total amount of address space used by this network. Organisations are not eligible to receive additional allocations unless they have used at least 80 percent of their total address space from previous allocations.
Example:
cust-network: FOO-AP 202.12.28.0 255.255.255.128 10/15/80 1/1/2 19960501
cust-network: BAR-AP 202.12.28.128 255.255.255.128 60/70/100 2/3/4 19960515
Top
Network Infrastructure (infrastructure)
The infrastructure attribute summarises the 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:
<address> <mask> <connect> <max> <hinit/h6mo/h1yr> <remark>
Attribute (long) |
Attribute (short) |
Definition/explanation |
Address |
address |
The starting address of the specific network assigned to your infrastructure, in dotted decimal format.
Example:
255.255.248.0 |
Mask |
mask |
The subnet mask of this network, in dotted decimal format. |
Connection type |
connect |
The type of connection this network has with the Internet.The options are:NO, if this network will not be connected to the Internet. PART, if this network will be transiently connected to the Internet (such as a dial-up connection). YES, if this network will be permanently connected to the Internet. |
Maximum hosts |
max |
The maximum number of usable host addresses possible on this network.Note, you should subtract two addresses for the "all 0s" host part and the "all 1s" broadcast address. |
Hosts now |
hinit |
The number of devices initially planned or currently installed on this network. |
Hosts in 6 months |
h6mo |
The number of devices planned for this network in 6 months from now. |
Hosts in 1 year |
h1yr |
The number of devices planned for this network in 1 year from now. |
Description of subnet |
remark |
A descriptive remark about the function of this network.
Example:
DIALUP PORTS |
Important notes on the infrastructure field
- Do not use the infrastructure field to describe networks which you are not yet using.
- If you have assigned addresses to your network infrastructure in a non-CIDR fashion (that is, where there is no single subnet mask which can describe the subnet), then you must describe each contiguous part of that network as a separate subnet, (including the use of 255.255.255.255 masks to define single hosts).
- In your device estimates, be sure to include all devices which need globally unique IP numbers, including PCs, workstations, servers, printers, and routers.
- Be sure to specify valid network numbers and associated network masks in order to convey the actual layout of your network.
- Use the remarks section to be as descriptive as possible about the way the IP addresses are being deployed for each subnet.
- APNIC considers the sum of the addresses described in the cust-network field and the infrastructure field to be the total amount of address space used in this network. Organisations are not eligible to receive additional allocations unless they have used at least 80 percent of their total address space from previous allocations.
Example:
infrastructure: 202.12.28.0 255.255.255.192 YES 62 12/24/48 servers
infrastructure: 202.12.28.64 255.255.255.192 PART 62 30/40/50 dialup ports
infrastructure: 202.12.28.128 255.255.255.128 NO 126 60/100/110 admin
Top
Cable bootstrap criteria (cable-bootstrap)
The cable-bootstrap attribute indicates whether you wish to have your request evaluated under the simplified bootstrap evaluation criteria for new cable or DSL services.
APNIC offers special evaluation criteria for requests relating to cable or DSL services. If you choose to have your request evaluated under the bootstrap criteria, the size of your allocation will allow you to assign a /24 to each CMTS in your network.
If you think an allocation of this size will not be sufficient for your needs, then you should answer NO to this question and complete the more detailed Future Network Plan in the network-plan attribute.
Acceptable entries for this attribute are:
- YES (meaning you are requesting address space to use in a new cable or DSL service and you do want your request evaluated under the bootstrap criteria)
- NO (meaning you are requesting address space to use in a new cable or DSL service but you do not want your request evaluated under the bootstrap criteria)
- N/A (meaning you are not requesting address space to use in a new cable or DSL service)
If you answer NO, please provide an explanation in the Additional Questions template.
Note, APNIC assumes that ISPs will create subnets of their allocated address space to make assignments to their infrastructure and to customers. ISPs that do not follow this practice will be asked for justification when they apply for additional address space.
Example:
cable-bootstrap: YES
Top
New cable/DSL equipment list (cable-list)
The cable-list attribute describes the equipment to be used in the deployment of a new cable or DSL service.
If you entered YES in the cable-bootstrap attribute, then you must provide an equipment list in this attribute.
If you entered NO in the cable-bootstrap attribute, then you should enter N/A (not applicable).
If you entered YES in the cable-bootstrap attribute, you must provide details of your CMTS equipment at each Head-end in the following format (using multiple lines as necessary):
<location> <make> <model> <quantity>
- location is the geographical location of the Head-end
- make is the manufacturer or brand of equipment
- model is the specific model number or name of the equipment
- quantity is the number of units of that equipment at that location
Example:
network-plan: Auckland Nortel CM100 10
Top
Future network plan (network-plan)
The network-plan attribute summarises the address assignments planned for the organisation's network infrastructure over the coming year. It is not used for planned customer assignments.
This field is used by APNIC to establish the patterns of address assignment in this network.
If you will be using any of the allocated addresses in a network that you have not described in the cable-list attribute, then you must provide a detailed network plan in the following format (using multiple lines as necessary):
<address> <mask> <connect> <max> <hinit/h6mo/h1yr> <remark>
Attribute (long) |
Attribute (short) |
Definition/explanation |
Address |
address |
The starting address of the network to be assigned to your infrastructure, in dotted decimal format.
Example:
255.255.248.0 |
Mask |
mask |
The subnet mask planned for this network, in dotted decimal format. |
Connection type |
connect |
The type of Internet connection planned for this network.The options are:NO, if this network will not be connected to the Internet. PART, if this network will be transiently connected to the Internet (such as a dial-up connection). YES, if this network will be permanently connected to the Internet. |
Maximum hosts |
max |
The maximum number of usable host addresses possible on this planned network.Note, 2 addresses should be subtracted for the "all 0s" host part and the "all 1s" broadcast address. |
Hosts now |
hinit |
The number of devices planned to be initially installed on this network. |
Hosts in 6 months |
h6mo |
The number of devices planned for this network in 6 months from now. |
Hosts in 1 year |
h1yr |
The number of devices planned for this network in 1 year from now. |
Detailed description of subnet |
remark |
A descriptive remark about this network. |
Important notes on the network-plan field
- In your device estimates, be sure to include all planned devices which will need globally unique IP numbers, including PCs, workstations, servers, printers, and routers.
- Be sure to specify valid network numbers and associated network masks in order to convey the actual layout of your network.
- APNIC expects that some portion (perhaps even all) of the address space you are requesting is planned to be pooled for customer assignments. Therefore, it is not necessary to specify that addresses will be assigned to customers.
Example:
network-plan: 0.0.0.0 255.255.255.240 YES 14 1/5/11 support group
network-plan: 0.0.0.16 255.255.255.240 YES 14 4/8/8 customer svc
Top | Guide to the APNIC ISP Request Form
| 
