![]() |
![]() |
You're here: Home » Resource services |
Network templateThe 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 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 field should include the location of the organisation and enough detail to distinguish it from other organisations. This field should not be used to contain any advertising information. Please limit the descr field to no more than five lines. Example: descr: SparkyNet, Sdn Bhd descr: Internet Service Provider descr: Pinang, Malaysia ISO 3166 code (country)The country attribute should contain the most appropriate two-letter ISO 3166 code for the organisation that will be using the 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. Example: country: MY 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:
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. 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. Remarks (remarks)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: Production IPv6 network servicing commercial clients in Jakarta Changed by (changed)The changed attribute is used to record the e-mail address of the person completing or updating this template, followed by the corresponding date. The date should be in the format of YYYYMMDD (YYYY - year, MM - month, and DD - day, all values 0 filled). You should provide exactly one changed attribute per network template. Example: changed: ahmad.ali@sparkynet.com.my 20020225 Maintainer object (mnt-lower)A maintainer object 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 creation of assignment objects within your IP address range. You should enter this in the correct maintainer object format. Example: mnt-lower: MAINT-AP-SPARKY Top | Guide to the APNIC IPv6 Allocation 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 ![]() |