Aut-num template

The aut-num template is used to provide information about the Autonomous System in the APNIC Whois Database.

Attributes in aut-num template:

as-name
descr
country
import
export
default
remarks
admin-c
tech-c
notify
mnt-by
mnt-routes

Autonomous System name (as-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 organisation requesting the AS number.

Example:

as-name: GLOBALTRANSIT-AS-JP

Top

Description of organisation (descr)

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

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

Top

ISO 3166 code (country)

The country attribute should contain the most appropriate two-letter ISO 3166 code for the organisation 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

Top

Import policy (import)

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.1.

Top

Export policy (export)

The export attribute can be used to describe generated routing information sent to peer Autonomous Systems.

Please include at least two export statements in your request for an AS number.

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

Example:

export:  to <peering-1> [action <action-1>]
         announce <filter>

Attribute (long)	Attribute (short)	Definition/explanation
Export to peer AS	peering-1	Use this to identify the AS of your peer to which you will be supplying routing information. If you choose to use the export attribute, you must include the statement: from <peering -1>
Export action	action-1	Use this to specify the action to be executed while exporting routes at the AS peer. If you choose to use the export 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 will apply to the AS you are requesting. As you have not yet been allocated an AS number, please use the value THIS-AS to specify routes from your AS. If you choose to use the export attribute, you must include the statement: announce <filter>

Example:

export:  to AS9444
         announce THIS-AS

For more information, see RFC 2622, section 6.2.

Top

Default routing (default)

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.

Top

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

Top

Administrative contacts (admin-c)

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.

Top

Technical contacts (tech-c)

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.

Top

Notification of object changes (notify)

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

Top

Maintainer object (mnt-by)

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 unauthorised 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

Top

Maintainer for route objects (mnt-routes)

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

Top | Guide to the APNIC AS Number Request Form (text version)