APNIC Home APNIC Home

You're here:  Home » Resource services

Network template

The network template is used to identify the proposed network in the APNIC Whois Database.

Attributes in Network template:

Network name (netname)

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

Example:

netname: SPARKYNET

Top

Description of organisation (descr)

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 attribute should not be used to contain any advertising information.

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

Example:

descr: SparkyNet, Sdn Bhd
descr: Internet Service Provider
descr: Pinang, Malaysia

Top

ISO 3166 code (country)

The country attribute should contain the most appropriate two-letter ISO 3166 code for the organisation that will use the address space.

In cases where 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: MY

Top

Administrative contacts (admin-c)

The admin-c attribute references the person object for a administrative contact, who must be someone who is physically located at the site of the network, subject to the following exceptions:

  • For residential networks or users, the Internet Registry's (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)

The tech-c attribute references the person object for a technical contact, who 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

The tech-c attribute references the person object for a technical contact, who 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.

Top

Remarks (remarks)

This attribute is optional. The remarks attribute can be used for any remarks about the address space in this network 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: Send abuse reports to abuse@example.com

Top

Maintainer controlling route creation (mnt-routes)

This attribute is optional for networks requesting IPv4 address space under the multihoming and critical infrastructure criteria.

Note: please 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:

mnt-routes: MAINT-AP-SPARKY

If you do not yet have a suitable maintainer, please create a maintainer object before submitting this form (it may take up to two days for your maintainer to be generated).

Top  |  Guide to the APNIC Portable Assignment Request Form


Home | MyAPNIC | Info & FAQ | Services | Training | Meetings | Membership | Policy | Internet community | Search
Last modified Friday, 01-Jul-2005 12:18:21 EST | © 1999 - 2008 APNIC Pty. Ltd.
Comments to: webmaster@apnic.net | Privacy statement | RSS Really Simple Syndication