------------------------------------------------------------------- APNIC Document identity Title: APNIC Person Template Description Short title: person-template-descr Document ref: APNIC-025 Version: 001 Date of original publication: 1 September 1995 Date of this version: 1 September 1995 Review scheduled: n/a Obsoletes: APNIC-017 Status: Expired Comments: n/a -------------------------------------------------------------------- APNIC Person Template Description Issued: September 1, 1995 Expires: January 31, 1996 This document describes the PERSON template used in several APNIC application forms. As such, this document should be used as a companion to the document accompanying the application forms. For each different person specified in an application form, please complete a separate PERSON template. If a PERSON template has already been submitted AND no changes are necessary to that template, there is no need to submit a new template. In addition, most application forms contain two PERSON templates, intending to correspond to the technical and administrative contacts for the object. If a single person is acting in both roles, there is no need to duplicate the information. APNIC application forms are structured as a series of records, where each record is composed of a series of tag: value pairs. As APNIC application forms are generally processed by machine, some aspects for an application form's format should not be altered. These aspects include lines beginning with #[ and the strings that compose the tags (e.g., the word before the colon). Altering these parts of an application form will likely lead to unpredictable results. When completing a template, please fill in the appropriate information (in type written English). Note that if you have blank fields, you may either remove them from the form or leave them blank when you submit your application. With a few exceptions, fields in the APNIC database are case insensitive. Please fill in the fields with proper capitalization and formatting, APNIC will provide none. It should be noted that information provided in a PERSON template will be entered into the APNIC Registration database which is provided to the Internet community as an aide to the diagnosis and resolution of network related issues. As such, it is imperative that the information maintained within the APNIC Registration database should be kept as up to date as possible. If you have any questions regarding this template or any other aspect of APNIC application forms, please contact APNIC at hostmaster@apnic.net. Person Template Tag Descriptions --------------------------------- person: Please give the full name of the person this template will represent. If you have provided in the person's name in a contact field of another template (e.g., the admin-c or tech-c fields of the NETWORK template), the names must be written identically to those provided in the fields. Please do not use formal titles like `Dr' or `Prof.' or `Sir' as the words which comprise a name is indexed and there are many people with the same titles. In addition, please do not add periods between the names or initials and list the name as you would be addressed in a letter salutation (e.g., given name followed by family name or family name followed by given name depending on the custom in your country). Example: person: John E Doe address: Please complete with the full postal address, and write as you would for ordinary international postal mail using one line for each part of the address as shown below. Please use multiple lines, with the last line containing the country (either the country name or the ISO-3166 2 letter country code). Example: address: Terabit Labs Inc. address: Industrial Estate North address: North Perpendicular Road 12 address: NL-1234 Northtown address: Niue phone: Please give the work telephone number of the person specified above as it would be dialed internationally (without the prefix necessary to reach an international line). Please specify the telephone number with "+ ". If an extension is necessary, add "ext ". Most countries should drop the leading zero when specifying their area code. More than one telephone number is fine. Each telephone number should be put on a separate line and written in order of the most appropriate number for the person to the least. Example: phone: +81 20 1233 4676 phone: +81 20 1233 4677 ext 4711 fax-no: Please complete with the facsimile number of the person as it would be dialed internationally (without the prefix necessary to reach an international line). Please specify the telephone number with "+ ". Most countries should drop the leading zero when specifying their area code. More than one facsimile number is fine. Each facsimile number should be put on a separate line and written in order of the most appropriate to the least. Example: fax-no: +81 20 1233 4678 e-mail: Please supply the appropriate electronic mail address for the person. Please ensure that this is a valid RFC-822 address with a fully qualified domain name. If you do NOT have e-mail connectivity, please leave this field blank or delete it from the template. Example: e-mail: johndoe@terabit.na nic-hdl: A NIC Handle is a unique identifer used within the APNIC database to differentiate between people with the same names. It is also used by preference for the fields which reference this person in other templates such as the admin-c: and tech-c: fields of the NETWORK template. NIC handles are assigned by registries -- if you do not have one, please do not make one up, APNIC will provide you with one. If you have an APNIC NIC handle, but do not remember it, please make a note of this in the COMMENTS section of the application form you are submitting. If you have a NIC handle assigned by another registry, e.g., InterNIC, please provide a full person template anyway -- the regional registries are currently investigating ways in which information such as this can be shared, but no solution has yet been implemented. If you do not have a NIC handle, please leave the field blank -- DO NOT put 'Please Assign' or similar for this field. Example: nic-hdl: JD0401-JP changed: Please indicate the email address of the person who is completing the template, followed by the current date in the format of YYMMDD (YY is the last 2 digits of the current year, MM is the month and DD is the day, all values 0 filled). If you do not have email connectivity please leave blank and it will be filled in for you. Do not put "Please Assign" or similar for this field. Example: changed: johndoe@terabit.na 950225 notify: Please provide a electronic mailbox of who should be notified when this record changes. This can be useful if more than one person manage the same object. When a record is altered, either through the action of APNIC staff or via the database update mechanisms described in APNIC-019, an advisory email will be sent by the database system. If the update is not appropriate, you should immediately contact the APNIC database manager apnic-dbm@apnic.net. The format of this field is one RFC822 electronic mail address per line. Although multiple lines are allowed, usage should be kept to a minimum. Please put 'dbmon@apnic.net' into this field if you do not wish to be notified of changes. If you specify a mailbox other than dbmon@apnic.net, be sure that the person at the other end of the mailbox understands what the update advisories mean. Example: notify: dbmon@apnic.net mnt-by: Please provide the APNIC allocated maintainer ID. The maintainer ID provides some level of control over who can update an object protected by a mnt-by: field. If you do not have a maintainer ID, you may either leave this field blank or apply for one using the APNIC Maintainer Object Request form found at: ftp://archive.apnic.net/apnic/docs/apnic-026.txt There can be zero or more mnt-by: tags per NETWORK template, however each maintainer object specified must already exist in the APNIC Registration Database. Example: mnt-by: MAINT-FOO-JP source: Source of the information. For the purposes of APNIC forms, it will always be APNIC. This is information which is always required in the database, so it has been added to the forms already. Example: source: APNIC Acknowledgements ---------------- This document in derived in large part from documents written by the staff of the European Registry, RIPE-NCC .