 |
Person Registration Form #[PERSON TEMPLATE]# |
|
To register a person in the database or to change the data related to a person, please submit an application to RIPN with #[PERSON TEMPLATE]# form enclosed. An application may contain one or several #[PERSON TEMPLATE]# forms with data regarding specified person(s). Application preparation rules are set out in "General rules for preparing applications". Below is a detailed description of each field in #[DOMAIN TEMPLATE]# (information in all fields should be entered in English unless specified otherwise): First name, First letter of second name and last name (without full stops) of the registered person. [Mandatory] [Single] [Read-Only] [Open] Пример:
First, second, last name of the person being registered according to passport data. Completion of this field is mandatory for those persons to whom the domain is registered. Information in this field should be entered in Russian (for non-russian persons - in English). [Optional] [Single] [Read-Only] [Hidden] Example:
List of passport data (separated by commas): - series; Completion of this field is mandatory for those persons to whom the personal domain is registered. Information in this field should be entered in Russian (for non-russian persons - in English). [Optional] [Multiple] [Read-Only] [Hidden] Example:
Date of birth. Designated with figures separated by commas in the following order: day, month, year. Completion of this field is mandatory for those persons to whom the personal domain is registered. Information in this field should be entered in Russian (for non-russian persons - in English). [Optional] [Single] [Read-Only] [Hidden] Example:
Contact address. Intended to be output through a commonly available database. [Optional] [Multiple] [Read-Write] [Open] Example:
Postal address of the person being registered. Completion of this field is mandatory for those persons to whom the personal domain is registered. This address will be used for any notifications and official documents. Information in this field should be entered in Russian (for non-russian persons - in English). [Optional] [Multiple] [Read-Write] [Hidden] Example:
Contact phone(s). Phone number should be indicated with international code and city code, without brackets or dashes. Codes and phone number should be separated by spaces. Information regarding each phone number should be represented as a separate line. [Mandatory] [Multiple] [Read-Write] [Open] Example:
Fax number(s). All information inclusion instructions for the field "phone" are applicable to the field "fax-no" as well. [Optional] [Multiple] [Read-Write] [Open] Example:
e-mail address of the person being registered in RFC-822 format. [Mandatory] [Multiple] [Read-Write] [Open] Example:
Unique person identifier (NIC-handle). Unique person identifier can be selected by the Applicant, failing this it is created automatically when object information is entered in the database ("action" field in the application has NEW value or is missing). If when entering information in the database "nic-hdl" field is left void, the identifier will be automatically made of the first capital letters of first, second and last names ("person" field) with addition of index numbers and obligatory characters a person identifier should end with: -RIPN. If, when object information is entered in the database the name selected by you, with obligatory characters for the end of person identifier: -RIPN, is specified in "nic-hdl" field, the unique identifier will be created by adding the index number to the name of your identifier (index number is added in cases when the specified name is already present in the database). Identifier value is reported to Applicant's and maintainer's e-mail addresses. Make sure "nic-hdl" field is always filled in during future updates or collections of complete data of the person (UPDATE or GET values of "action" field in the application) as it will be used for identification. If on the registered person the domain will not be delegated hereinafter, the use of the person unique identifiers from InterNIC or RIPE data bases is possible. The field should contain not more than 64 characters. [Optional] [Single] [Read-Only] [Open] Example:
Any textual comments, notes. [Optional] [Multiple] [Read-Write] [Open] Any comments, notes for use by RIPN. Information in this field should be entered in Russian (for non-russian organization - in English). [Optional] [Multiple] [Read-Write] [Hidden] Reference to the unique identifier of the maintainer responsible for the correctness of data related to the person in RIPN database - You must use #[MAINTAINER TEMPLATE]# for its registration. [Mandatory] [Single] [Read-Write] [Open] Example:
mnt-ch: The field is used only if the technical support in "mnt-by" field must be changed. [Optional] [Single] [Read-Write] [Open] Example:
Information source. For the documents stored in RIPN database, this field shall always have RIPN value. [Mandatory] [Single] [Read-Only] [Open] Example:
Sample of #[PERSON TEMPLATE]# form completion person: Sidor S Sidorov Template description includes the following parameters for each field in the template:
|
