Help guide for ASN requests

How to complete the APNIC Autonomous System Number Request Form

#[REQUESTOR TEMPLATE]#

 

name
Name of person making request
Provide the full name of the person completing the request form. APNIC will use this name for any correspondence regarding the progress of this request.
email
Email address of person making request
Provide the email address of the person completing the request form. APNIC will use this address for any correspondence regarding the progress of this request.
acct-name
APNIC account 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.

Example:

acct-name: GLOBALTRANSIT-JP

 

org-relationship
Relationship to organization
The relationship attribute describes the relationship of the person completing the request form to the organization intending to use the AS number.Common values for this field are: employee, officer, manager, or consultant.

 

 #[AUTONOMOUS SYSTEM TEMPLATE]#

 

prefix
Address prefixes to be announced
The prefix attribute identifies the IP address prefixes you plan to announce within the AS number you are requesting.Note: please separate multiple prefixes using commas.

Example:

prefix: 202.8.224.0/19, 203.7.225.0/20
date
Date the Autonomous System will be implemented

The date attribute identifies the date of implementation of your internet’s exterior gateway protocol.

Example:

date: 25/10/2002
peer-as-contacts
Peering contacts

The peer-as-contacts attribute identifies 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) Definition/explanation
Autonomous System number as-number The Autonomous System (AS) number of the peer network.
Peer organization peer-org The name of the organization to which you are peering.
Contact name at peer organization peer-contact The name of a contact person at that organization who can verify the peering arrangement
Peer contact phone number peer-phone The phone number of the peer-contact. Please use the format:

+<international code>-<area/city code>
-<exchange>-<subscriber>
Peer contact email peer-email The email address of the peer-contact.

Example:

peer-as-contacts: 1234, STARISP, JON STAR, 
+60-20-1233-4676, john@starisp.com
 #[AUT-NUM TEMPLATE]#

 

as-name
Autonomous System name

Please provide a short but meaningfully descriptive name for this autonomous system. The as-name is used mainly for administrative purposes such as consistency checking of the Internet Registry.

The autonomous system name should be a single word of less than 25 capital characters or a hyphen (‘-‘).

Please use an Autonomous System name that relates to the organization requesting the AS number.

Example:

as-name: GLOBALTRANSIT-AS-JP

 

descr
Description of organization
The description of organization (descr) should be a brief description of the organization that will be using the AS number. This attribute should include the organization’s
name, the organization’s type of business, and the location of the organization.This attribute should not be used to contain any advertising information.

Please limit the descr attribute to no more than five lines.

Example:

descr: Global Transit Inc.
descr: Transit AS
descr: Content Service Provider
descr: Tokyo
country
ISO 3166 code

The country attribute should contain the most appropriate two-letter ISO 3166 code for the organization requesting the AS number.

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.

Example:

country: JP
import
Import policy

The import attribute can be used to describe routing information your AS will accept from neighboring Autonomous Systems. Please include at least two import statements in your request for an AS number.
Information in the import attribute must use the following format (using multiple lines as necessary).

Example:

import: from <peering-1> [action <action-1>]
 accept <filter>
Attribute (long) Attribute (short) Definition/explanation
Import from peer AS peering-1 Use this to identify the neighboring AS from which you will be receiving routing information.

If you choose to use the import attribute, you must include the statement:

from <peering -1>
Import action action-1 Use this to specify the action to execute while importing routes at the AS peer.

If you choose to use the import attribute, it is optional to include:

[action <action -1>]
AS policy filter filter Use this to define the AS policy filter.

A policy filter is a logical expression which you apply to a set of routes to return a subset of these routes. The policy filter can match routes using any BGP path attributes.

If you choose to use the import attribute, you must include the statement:

accept <filter>

Example:

import: from AS9386
 action pref=100;
 accept ANY

For more information, see RFC 2622, section 6.2.

default
Default routing

The default attribute can be used to describe default routing policies. If you will be using a peer as a default for your network, please provide an indication of how default routing will be done.

Information in the default attribute must use the following format (using multiple lines as necessary):

default: to <peering> [action <action>]
 [networks <filter>]
Attribute (long) Attribute (short) Definition/explanation
Default peer peering Use this to indicate the AS (and the router if present) being defaulted to.

If you choose to use the default attribute, you must include the statement:

to <peering>
Default action action Optional.

Use this to specify various attributes of defaulting. For example, you may use this to specify a relative preference if multiple defaults are included.

If you choose to use the default attribute, it is optional to include:

[action <action>]
Network policy filter filter Use this to specify the policy filter.

A router only uses the default policy if it received the routes matched by filter from this peer.

If you choose to use the export attribute, you must include the statement:

networks <filter>

Example:

default: to AS9386
 action pref=10;
 networks ANY

For more information, see RFC 2622, section 6.5.

remarks
Remarks

The remarks attribute can be used for any remarks about the aut-num that cannot be expressed in any of the other attributes. Remarks should be only be included if they provides extra information to
users of the database.

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

Example:

remarks: For routing problems with this ASN
contact the admin-c
admin-c
Administrative contacts

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

  • For residential networks or users, the IR’s technical contact may be registered as admin-c.
  • 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:

admin-c: 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 attribute.

tech-c
Technical contacts

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:

tech-c: 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 attribute.

notify
Notification of object changes

The notify attribute contains an e-mail address to which notifications of changes to the object should be sent. Use this attribute to assist in object maintenance by listing email addresses of people who should be
notified of any changes or attempted changes to this object.

Note: Do not use the notify attribute as a network contact address.

Example:

notify: johndoe@globaltransit.co.jp
mnt-by
Maintainer object

The mnt-by attribute references your maintainer object, which is a database object used to authorise updates to the APNIC database. If your database details are protected by a maintainer object, then only persons
with access to the security information of that maintainer object will be able to change details.

You must create a maintainer object to prevent unathorized updates of your aut-num object.

In the absence of mnt-routes or mnt-lower attributes, this can be used to authorise the creation of route objects that refer to this AS number in the origin attribute.

Example:

mnt-by: MAINT-JP-GLOBALTRANSIT
mnt-routes
Maintainer for route objects

The mnt-routes attribute references a object that can be used to authorise the creation of route objects that refer to this AS number in the origin attribute.

This attribute is optional.

Example:

mnt-lower: MAINT-JP-GLOBAL

 

Additional information
The additional information area is used to provide more information on any unclear aspects of your request.If you are an APNIC Member, are you requesting this AS number on behalf of a customer? If yes, do you agree to return the AS number to APNIC if your customer ceases to receive connectivity from you?

Note: if you do not agree, APNIC cannot approve your request.

If you are an APNIC Non-Member or requesting an AS number for your own network, you may leave this section blank.