------------------------------------------------------------------- APNIC Document identity Title: APNIC IP Address Reassignment Form Short title: address-reassign-request Document ref: APNIC-027 Version: 001 Date of original publication: 1 September 1995 Date of this version: 1 September 1995 Review scheduled: n/a Obsoletes: APNIC-019 Status: Obsolete Comments: Obsoleted by APNIC-034 -------------------------------------------------------------------- APNIC IP Address Reassignment Form Issued: September 1, 1995 Expires: January 31, 1996 Please see comments at the bottom of this form regarding how to complete this application. Note that this form is parsed by machine and modification of lines starting with #[ or the field names will likely result in strange errors being returned to you and your request not being processed. After completing this form, please submit it via email to: ip-reassign@rs.apnic.net or in type written English via fax (discouraged) to: +81-3-5276-6239 or in type written English via postal mail (as a last resort) to: Asia Pacific Network Information Center c/o The United Nations University 53-70, Jingumae 5-Chome, Shibuya-ku, Tokyo 150, Japan If you have any questions, you may contact us via email at hostmaster@apnic.net (preferred), fax at the above number, postal mail at the above address or via telephone at +81-3-5276-3973. Note that we do not accept IP reassignments via telephone. Please allow up to one month for processing fax or postal mail requests. Electronic requests will be processed immediately. If you do not receive a response from the APNIC Database system within 24 hours, please contact the APNIC database administrator at apnic-dbm@apnic.net. NOTE: IT IS NOT NECESSARY TO INCLUDE THIS HEADER NOR THE INSTRUCTIONS AT THE BOTTOM OF THIS FORM WITH YOUR APPLICATION. - - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - - #[NETWORK TEMPLATE V3.0]# inetnum: netname: descr: descr: country: admin-c: tech-c: rev-srv: remarks: notify: dbmon@apnic.net mnt-by: changed: source: APNIC #[PERSON TEMPLATE V3.0]# person: address: address: phone: fax-no: e-mail: nic-hdl: remarks: notify: dbmon@apnic.net mnt-by: changed: source: APNIC #[PERSON TEMPLATE V3.0]# person: address: address: phone: fax-no: e-mail: nic-hdl: remarks: notify: dbmon@apnic.net mnt-by: changed: source: APNIC #[TEMPLATES END]# - - - - - - - - - - - - - - CUT HERE - - - - - - - - - - - - - - - - - Instructions For Completing This Form ------------------------------------- In order to keep the APNIC whois registry up to date, APNIC uses the "RIPE database" software provided by the European Internet registry RIPE-NCC. This software allows service providers to submit database reassignment information via email with nearly instantaneous turn around. However, since the reassignment mechanism is automated, even small syntax errors will result in your reassignment not being processed, thus please insure you have read and understood the NETWORK and PERSON template documents, APNIC-024 and APNIC-025. For details on how to fill out the network template, please see ftp://archive.apnic.net/apnic/docs/apnic-024.txt. For details on how to fill out the person template, please see ftp://archive.apnic.net/apnic/docs/apnic-025.txt. IF YOU HAVE AN APNIC ISSUED NIC HANDLE, PLEASE USE IT INSTEAD OF FILLING IN THE REST OF THE PERSON TEMPLATE. If you have filled in NIC handles for the admin-c and tech-c fields of the NETWORK template and no aspect of the person's contact information has changed, you do NOT need to complete the PERSON templates -- please leave the fields blank. Reassignment Procedure ---------------------- The automated reassigment procedure is broken down into three steps, namely: 1) filling in the reassignment form, if necessary obtaining new NIC handles for the contacts and using those new NIC handles for the admin-c: and tech-c: tags. 2) submitting the reassignment form to ip-reassign@rs.apnic.net 3) receiving the response from the automated server The first step will entail supplying values for (at a minimum) all mandatory fields. As person names are not unique, it is necessary to obtain a unique key for persons in the APNIC database. This unique key is known as the NIC Handle. If an administrative or technical contact is being added to the APNIC registration database for the first time, you will need to obtain an APNIC NIC handle for the contact. Before obtaining an APNIC NIC handle, please attempt to verify the person has not already had a NIC handle assigned by querying the APNIC database via your WHOIS command. If the person truly does not have a NIC handle, then you can use your finger commmand (or telnet to port 79) to rs.apnic.net, querying the person's first name, their last name, and the country they are from separated by periods. For example, if you need to allocate a handle for John Doe of Japan, you can issue the following command: finger john.doe.jp@rs.apnic.net The APNIC finger server will find the next available NIC handle in the format JDn-JP (where 'n' is some number) and reserve that handle for one week. If you do not submit your reassignment within one week, the NIC handle reserved will be returned to the 'free pool'. PLEASE INSURE YOU SUBMIT THE REASSIGNMENT WITHIN ONE WEEK AFTER RESERVING THE NIC HANDLE. For more information on the APNIC Registration Services finger ser- vice, you can issue the following command: finger help@rs.apnic.net Step two requires you to copy the reassignment form you filled in during step one into a mail file and then to submit the file to ip-reassign@rs.apnic.net The template will be scanned for syntax errors and, if no errors are found, the appropriate changes will be immediately made to the APNIC Registration database. Note that all updates are logged within APNIC to insure that erroneous or malicious updates can be detected and corrected. After submitting your template via email, you should receive back a response from the database server. If any errors were detected in your submission, no changes will be made to the APNIC Registration database and you will need to submit your application again. If non-fatal errors are detected, the database software will flag the errors as 'warnings' and return your template. Note however that warnings are only advisory and your update will be accepted in the database (perhaps with some modifications as noted in the warning message(s)). It is recommended that in future submissions you correct the specific problems which generated the warnings prior to submitting a new update. If no errors or warnings are detected in your template, a short confirmation message will be returned. If you believe your submission was rejected erroneously or you have any questions regarding your submission, please contact APNIC at apnic-dbm@apnic.net. Acknowledgements ---------------- This document in derived in large part from documents written by the staff of the European Registry, RIPE-NCC .