APNIC Home APNIC Home

You're here:  Home » Info & FAQ » APNIC FAQs

Guide to the APNIC Portable Assignment Request Form

Before you start

The APNIC Portable Assignment Request Form will lead LIRs through the steps required to request IPv4 or IPv6 portable assignments for:

Portable assignment

IP address type

Multihoming

IPv4 or IPv6

Internet Exchange Point

IPv4 or IPv6

Critical infrastructure

IPv4 or IPv6

Important:

  • For each type of request, you must submit a separate request form.
  • APNIC members and non-members may use this form.

If you do not yet have an APNIC account name or have forgotten your account name, please contact admin@apnic.net before completing this form.

How to get help

Click where you see Help for specific help with this form. Learn about the parser that checks all email and web-based IP requests at Using the Parser/Validator on the Request Form.

Saving your work

You can save your work on this form at any time by clicking on the "Save" button at the bottom of the page you are working on. All the details you have entered will be securely saved on APNIC's server.

You will be asked to create a password that is to be used for returning to your saved work.

When you save your work, you will be emailed a URL which will allow you to access the information you have saved and continue to complete the request.

Please note, your details will be held on the APNIC server for a maximum of 14 days.

The 9 steps to requesting a portable assignment from APNIC:

1. Application information
2. Type of portable assignment
3. Contact details
4. Network name
5.1 Multihoming - network connectivity
5.2 Multihoming - Address space to be returned
5.3 IXP details
5.4 IX member details
5.5 Critical infrastructure details
6. Existing network infrastructure information
7. Future network plan

7.1 Future network plan (IPv4)
7.2 Future network plan for (IPv6)
8. Additional information
9. Confirm details

TopTop   CloseClose

1. Applicant information

APNIC will use these contact details for all correspondence relating to this request.

TopTop   Top9 steps   CloseClose

Your name

You should ensure you are a registered contact for this organisation. If you are not already a registered contact, then you will need to be "introduced" to APNIC.

How to get introduced

  • Current contacts can use MyAPNIC to add new contacts.
  • The current registered contact can send an email to APNIC introducing the new contact's name and email address; or
  • If the registered contact has left the organisation, APNIC will need a fax on the organisation's letterhead stating the names, email addresses, and NIC-handles (if possible) of the new contacts. The fax must be signed by an authorised person, such as a director or manager.

TopTop   Top9 steps   CloseClose

Your email address

APNIC will use this address for any correspondence regarding the progress of this request.

Note: APNIC strongly discourages requests from free web-based email accounts such as Hotmail or Yahoo. If the organisation making the request does not yet have the infrastructure for its own email accounts, you may submit a request using a free email account and contact APNIC as soon as the organisation sets up its own email system.

TopTop   Top9 steps   CloseClose

APNIC account name

If you do not know your APNIC account name, please contact admin@apnic.net. You will need to provide details of the name and location of your organisation.

Example:

SPARKYNET-MY

TopTop   Top9 steps   CloseClose

Your relationship to organisation applying for resources

Please choose the most appropriate item from the drop down list to describe your relationship to the organisation requesting the resources.

TopTop   Top9 steps   CloseClose

Password

The password you create for this request is used to return to any work you save on the APNIC server. This password should consist of 8 alphanumeric characters.

After you save your work, you will be emailed a URL. When visiting that URL you must correctly enter your password in order to access the information you have entered.

TopTop   Top9 steps   CloseClose

2. Type of portable assignment

The details you enter here will specify what type of second opinion you are requesting.

IP version requested

The APNIC Portable Assignment Request Form can be used to request an IPv4 or IPv6 address range.

For each version of IP address, you must submit a separate form.

TopTop   Top9 steps   CloseClose

Type of portable assignment requested

The type of portable assignment requested (assign-type) field describes the criteria under which you wish to apply for a portable assignment. There are three options for this attribute:

Option

Availability

Description

Multihoming

IPv4 and IPv6

Organisations seeking an IPv4 multihoming assignment must meet the criteria described in "Policies for Address Space Management in the Asia Pacific Region".

In particular, an organisation is eligible to receive a portable assignment from APNIC if it:

  • is currently multihomed with provider-based addresses, or
  • demonstrates a plan to multihome within one month (IPv4 only) or three months (IPv6 only); and
  • agrees to renumber out of previously assigned address space.

If you choose this option, you must complete the following templates ONLY in your request:

  • Requestor
  • Portable assignment
  • Network
  • Technical
  • Multihoming
  • Additional information

Note: registrar organisations not hosting the network that houses the registry infrastructure are not eligible for an assignment under this policy.

IXP

IPv4 and IPv6

Internet Exchange Points are eligible to receive a portable assignment from APNIC to be used exclusively to connect the IXP participant devices to the Exchange Point. IXPs may request the following assignment sizes:

  • IPv4 - a minimum assignment of /24
  • IPv6 - a minimum assignment of /48

APNIC may make multiple assignments of these sizes, where justified.

If you choose this option, you must complete the following templates ONLY in your request:

  • Requestor
  • Portable assignment
  • Network
  • Technical
  • Internet Exchange Point
  • Additional information

Critical infrastructure

IPv4 and IPv6

Organisations seeking assignment for critical infrastructure must be an actual operator of the network infrastructure performing the following functions:

  • root domain name system (DNS) server
  • global top level domain (gTLD) DNS server
  • country code TLD (ccTLDs) DNS server
  • Regional Internet Registry (RIRs)
  • National Internet Registry (NIRs)

These organisations are entitled to request the following assignment sizes:

  • IPv4 - a minimum assignment of /24
  • IPv6 - a maximum assignment of /32 per operator

If you choose this option, you must complete the following templates ONLY in your request:

  • Requestor
  • Portable assignment
  • Network
  • Technical
  • Critical infrastructure
  • Additional information

TopTop   Top9 steps   CloseClose

3. Contact details

The details you enter here will be used as the network contact and security information for the address allocation.

Administrative contacts (NIC-handles)

An administrative contact (admin-c) must be someone who is physically located at the site of the network, subject to the following exception:

  • For networks in exceptional circumstances that make it impractical to maintain an on-site administrative contact, an off-site person may be registered as the admin-c.

You may specify more than one admin-c for the network.

You should enter these contacts in the NIC-handle (person object) format.

Example:

KX9-AP

If these contacts do not yet have valid NIC handles, please create them before submitting this form (this process may take 15-20 minutes).

APNIC recommends that you consider using role objectsfor this field.

TopTop   Top9 steps   CloseClose

Technical contacts (NIC-handles)

A technical contact (tech-c) must be a person responsible for the day-to-day operation of the network, but does not need to be physically located at the site of the network. You may specify more than one tech-c for the network.

You should enter these contacts in the NIC-handle (person object) format.

Example:

KX9-AP

If these contacts do not yet have valid NIC-handles, please create them before submitting this form (this process may take 15-20 minutes).

APNIC recommends that you consider using role objects for this field.

TopTop   Top9 steps   CloseClose

Maintainer to control route objects

This attribute is optional for networks requesting IPv4 address space under the multihoming and critical infrastructure criteria. Do not use this attribute for IXP requests.

If you plan to register your IPv4 routing information in the APNIC Routing Registry at any time in the future, please specify the maintainer that will be authorised to create a route object for your requested address space.

You should enter this in the correct maintainer object format.

Example:

MAINT-AP-SPARKY

TopTop   Top9 steps   CloseClose

4. Network name

The details you provide here will be used to identify the proposed network in the APNIC Whois Database.

Name of network

The network name (netname) should be a short, but meaningful name for this network. It is used mainly for administrative purposes such as consistency checking. Please use a network name that identifies the network and relates to the organisation that is requesting the address space.

The network name should be a single word of less than 25 capital alphanumeric characters.

TopTop   Top9 steps   CloseClose

Description of organisation

The description of organisation (descr) should be a brief description of the organisation that will be using the address space. This attribute should include the organisation's name, the organisation's type of business, and the location of the organisation.

This field should not be used to contain any advertising information.

Please limit this field to no more than five lines.

TopTop   Top9 steps   CloseClose

ISO 3166 code

The ISO 3166 code field should contain the two-letter ISO 3166 code that is appropriate for the organisation requesting the address space.

In cases where the more than one country or economy may be appropriate, please use the ISO 3166 code for the country or economy where the administrative contact is located.

TopTop   Top9 steps   CloseClose

Remarks

The remarks field is optional. The remarks field can be used for any remarks about the address space in this network that cannot be expressed in any of the other attributes in the APNIC Whois Database. Remarks should be only be included if they provides extra information to users of the database.

You may use remarks to specify contact details where spam and abuse reports should be sent.

You may use multiple lines, but please keep remarks to a minimum.

TopTop   Top9 steps   CloseClose

5.1 Network connectivity (multihoming)

This section describes aspects of how your network plans to or is currently multihomed.

If this request is not for multihoming portable assignment, then you should skip this section.

TopTop   Top9 steps   CloseClose

Multihoming status (conn-status)

The multihoming status (conn-status) field indicates whether you are currently multihomed or will be multihomed within the next month (IPv4 only) or within the next three months (IPv6 only). The two options for this attribute are:

Option

Description/explanation

Now

The network is currently connected to more than one AS and your routing policy is different from your upstream ISP.

1 month

The network will be multihomed within one month (IPv4 only) or three months (IPv6 only).

TopTop   Top9 steps   CloseClose

Reason for requesting assignment

To justify your request, you must give details of the reason you are requesting portable assignment under multihoming criteria.

TopTop   Top9 steps   CloseClose

Peer AS contact details (peer-as-contacts)

The peer AS contact details (peer-as-contacts) field provides the names and contacts of the Autonomous Systems that your network is peering with now, or plans to peer with within one month.

You must provide details of at least two peers in the following format (using multiple lines as necessary):

<as-number> <peer-org> <peer-contact> <peer-phone> <peer-email>

Attribute (long)

Attribute (short)

Description/explanation

Peer AS number

as-number

Autonomous System (AS) number of your peer network.

Name of peer organisation

peer-org

Name of the organisation to which you are peering.

Peer contact

peer-contact

Name of a contact person at that organisation who can verify the peering arrangement.

Peer phone

peer-phone

Phone number of the peer-contact in the format:

+<country code>-<area/city code>-<exchange>-<subscriber>

Email address

peer-email

Email address of the peer-contact.

How to complete this section

Use the form to build your peer details

  • Use the fields on the left of the form to specify the required elements for each peer AS number.
  • When you have completed the fields, click "Add information" to transfer that information to the text box in the correct format.
  • Repeat this process for each peer AS number.

TopTop   Top9 steps   CloseClose

5.2 Address space to be returned (multihoming)

The section is used to identify any address space you currently hold, which you will be returning if you receive an assignment from APNIC.

If this request is not for a multihoming portable assignment, then you should skip this section.

How to complete this page

  • Use the fields on the left of the form to specify the required elements for each address assignment to be returned.
  • When you have completed the fields, click "Add information" to transfer that assignment information to the text box in the correct format.
  • Repeat this process for each assignment to be returned.

TopTop   Top9 steps   CloseClose

Address space to be returned (ip-return)

You must provide details of all address space you currently hold and will return if you receive a portable assignment from APNIC. Please use the following format:

<address> <prefix-size> <date> <rtn-org> <rtn-contact> <rtn-phone> <rtn-email>

Attribute (long)

Attribute (short)

Description/explanation

Start address of address range to be returned

Address

The start address of the address range to be returned.

Prefix of address range to be returned

prefix

The total prefix to be returned.

Planned date of return

date

Date you plan to return that address range, in the format :

YYYYMMDD

Where:

YYYY - year 
MM - month 
DD - day

All values must be 0 filled.

Organisation space to be returned to

rtn-org

Name of the organisation to which you plan to return that address space

Contact name

rtn-contact

Name of a contact person at that organisation who can verify the details of the return

Contact phone

rtn-phone

Phone number of the return-contact in the format:

Example:

+<country code>-<area/city code>-<exchange>-<subscriber>

Contact email

rtn-email

Email address of the peer-contact

TopTop   Top9 steps   CloseClose

5.3 IXP details (IXP)

This section is used to describe your operations as an IXP.

If this request is not for an IXP portable assignment, then you should skip this section.

Start date of service (service-plan)

The start date of service (service-plan) field specifies when the IX started, or plans to start, offering IX services using the requested address assignment.

The date should be in the format of YYYYMMDD (YYYY - year, MM - month, and DD - day, all values 0 filled).

TopTop   Top9 steps   CloseClose

IXP policy (ixp-policy)

APNIC must verify that there is a clear and open policy for other organisations to join the Internet Exchange.

The two options for this field are:

  1. Provide the URL where your IXP policy is located.

  2. Upload a text file of your IXP policy.

TopTop   Top9 steps   CloseClose

5.4 IX member details (IXP)

You must provide the details of at least 3 members of your Exchange Point to qualify for an APNIC IXP assignment.

If this request is not for an IXP portable assignment, then you should skip this section.

How to complete this page

Use the form to build your IXP member details:

  • Use the fields on the left of the form to specify the required elements for each IXP member.
  • When you have completed the fields, click "Add information" to transfer that member information to the text box in the correct format.
  • Repeat this process for each member of your IXP.

TopTop   Top9 steps   CloseClose

IX member details (ix-member)

The IX member details (ix-member) field lists the current members of the IXP and their AS number as used at the IX.

If you are not yet operational and have no members, please leave this page blank.

List your IX members in the following format, using multiple lines:

<mem-name> <as-number> <mem-contact> <mem-phone> <mem-email>

Attribute (long)

Attribute (short)

Description/explanation

Member name

mem-name

Name of the IX member

Member AS number

as-num

Autonomous System (AS) number used by that member at the IX.

Contact name

mem-contact

Name of a contact person at that organisation who can verify they are an IX number.

Contact phone

mem-phone

Phone number of the mem-contact in the format:

+<country code>-<area/city code>-<exchange>-<subscriber>

Contact email

mem-email

Email address of the mem-contact.

TopTop   Top9 steps   CloseClose

5.5 Critical infrastructure details

The information you provide in this section is specifically related to your operation as critical Internet infrastructure.

If this request is not for a critical infrastructure portable assignment, then you should skip this section.

TopTop   Top9 steps   CloseClose

Category of critical infrastructure

The category of critical infrastructure (critical-cat) list specifies the type of critical infrastructure your organisation operates.

Options for this field are:

  • Root DNS server
  • Global top level DNS (gTLD) server
  • Country code DNS (ccTLD) server
  • Regional Internet Registry (RIR)
  • National Internet Registry (NIR)

TopTop   Top9 steps   CloseClose

Organisation URL (org-url)

Please provide details of your organisation's website so APNIC can verify your role as critical Internet infrastructure.

TopTop   Top9 steps   CloseClose

6. Existing network infrastructure

This section is used to describe the address assignments you are currently using for your network infrastructure.

If this organisation does not currently hold any IP address space, then you should skip this section.

How to complete this page

There are two options for completing this section:

  1. Use the form to build up your information, line by line
    • Use the fields on the left of the form to specify the required elements for each line.
    • When you have completed the fields, click "Add Information" to transfer that line to the text box in the correct format.
    • Repeat this process for each line required.
  2. Upload a text file
    • If you have a text file on a local drive, which describes this information in the correct format, you may click "Upload Text File"
    • Follow the prompts to locate the file and attach it to this request form;
    • Only text files may be uploaded in this section.

TopTop   Top9 steps   CloseClose

Existing network infrastructure

The existing network infrastructure (infrastructure) field summarises addresses you are currently using for your network infrastructure equipment. If you are applying for IPv6 address space you do not need to document existing IPv4 space you currently use. If you are applying for IPv4 address space, you do not need to document existing IPv6 space you currently use. This field is used by APNIC to establish the patterns of address assignment within this network.

If this organisation does not currently hold any IP address space, then you should skip this section.

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

<address> <prefix-size> <remark>

Attribute (long)

Attribute (short)

Definition/explanation

Actual address

address

The actual start address assigned.

Total prefix size

prefix-size

The total address prefix of the subnet.

Description of subnet

remark

A descriptive remark about this network, including its function and the equipment installed.

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, then you must describe each contiguous part of that network as a separate subnet.
  • 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 prefixes 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.

TopTop   Top9 steps   CloseClose

7. Future network plan

7.1 Future network plan (IPv4)

This section is used to describe the plans for using the requested IPv4 address space in the network infrastructure over the next year.

If this request relates only to IPv6 address space, then you should skip this section.

How to complete this page

Use the form to build your network plan details:

  • Use the fields on the left of the form to specify the required elements for each assignment to your planned network infrastructure.
  • When you have completed the fields, click "Add information" to transfer that assignment information to the text box in the correct format.
  • Repeat this process for each assignment to your network infrastructure.

TopTop   Top9 steps   CloseClose

Network plan field

IPv4 assignment

The future network plan (network-plan) field summarises the address assignments planned for the organisation's network infrastructure over the coming year. This field is used by APNIC to establish the patterns of address assignment in this network.

You should provide descriptions of all assignments planned for your customer's network in the following format:

<address-prefix> <now/6mo/1yr> <remark>

Attribute (long)

Attribute (short)

Definition/explanation

Prefix length of planned subnet

address-prefix

The prefix length of the subnet your organisation plans to sub-allocate to the customer, as a prefix in slash notation.

Deploy now

now

The IPv4 prefix planned for immediate use.

Deploy within 6 months

6mo

The IPv4 address prefix planned for use after six months.

Deploy within 1 year

1yr

The IPv4 address prefix planned for use after one year.

Detailed description of subnet

remark

A descriptive remark about the plans for this network, including its function and the equipment installed.

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 prefixes in order to convey the actual layout of your network.

TopTop   Top9 steps   CloseClose

7.2 Future network plan (IPv6)

This section is used to describe the plans for using the requested IPV6 address space in the network infrastructure over the next two years.

If this request relates only to IPv4 address space, then you should skip this section.

How to complete this page

Use the form to build your network plan details:

  • Use the fields on the left of the form to specify the required elements for each assignment to your planned network infrastructure.
  • When you have completed the fields, click "Add information" to transfer that assignment information to the text box in the correct format.
  • Repeat this process for each assignment to your network infrastructure.

TopTop   Top9 steps   CloseClose

Network plan field

The future network plan (network-plan) field summarises the address assignments planned for the customer's network infrastructure over the next two years. This field is used by APNIC to establish the patterns of address assignment in this network.

You should provide descriptions of all assignments planned for your customer's network infrastructure in the following format:

network-plan: <address-prefix> <now/1yr/2yr> <remark>

Attribute (long)

Attribute (short)

Definition/explanation

Prefix length of planned subnet

address-prefix

The size of the subnet your organisation plans to assign to the end site, as a prefix in slash notation.

Deploy now

now

The IPv6 prefix planned for immediate use.

Deploy within 1 year

1yr

The IPv6 address prefix planned for use after one year.

Deploy within 2 years

2yr

The IPv6 address prefix planned for use after two years.

Detailed description of subnet

remark

A descriptive remark about the plans for this network, including its function and the equipment installed.

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 prefixes in order to convey the actual layout of your network.

TopTop   Top9 steps   CloseClose

8. Additional information

This section is for you to provide whatever other details you feel may help justify your portable assignment request.

How to complete this page

There are two options for using this section to provide additional comments:

  1. Enter your information directly into the text field
  2. Upload a text file
  • If you have a file on a local drive setting out your additional comments, you may select "Upload file"
  • Follow the prompts to locate the file and have it automatically attached to this request form
  • Only text files may be uploaded in this section

Additional information

The additional information field is used to provide any other information that may help to justify the request for address space.

The information you provide in this field can help APNIC to evaluate your request more rapidly.

In particular, it will help APNIC evaluate the request if you can provide:

  • network topology diagrams
  • additional information on any other aspect of this request you feel may be unclear

9. Confirm details

Please check that the details on the confirmation screen are correct before submitting your completed request to APNIC.

You may use the progress bar to return to any section of this form to amend the details you have provided.

TopTop   Top9 steps   CloseClose

Top  |  Resource services

Home | MyAPNIC | Info & FAQ | Services | Training | Meetings | Membership | Policy | Internet community | Search
Last modified Tuesday, 20-Mar-2007 13:45:57 EST | © 1999 - 2008 APNIC Pty. Ltd.
Comments to: webmaster@apnic.net | Privacy statement | RSS Really Simple Syndication