 |
#[ORGANIZATION TEMPLATE]# |
|
To register an organization that is a legal entity in RIPN database or to update the information on an organization, it is necessary to submit an application with #[ORGANIZATION TEMPLATE]# to RIPN. Application preparation rules are set out in document "General rules for making applications". Below is a detailed description of each field in #[ORGANIZATION TEMPLATE]# (information in all fields should be entered in English, unless specified otherwise): Full name of the organization as specified in its incorporation documents. Includes the legal status and the unabbreviated ame of the organization. [Mandatory] [Multiple] [Read-Only] [Open] Example:
Full name of the organization as specified in its incorporation documents. Includes the legal status and the unabbreviated name of the organization. This information should be identical to that specified in the field "org". Information in this field should be entered in Russian (for non-russian organization - in English). [Mandatory] [Multiple] [Read-Only] [Hidden] Example:
The field contains information on organization codes : INN, OKPO, OKONH . If the organization hasn't representation in Russia and not registered in Russia, this field must be absent. The codes should be listed, separated by spaces, in the following order: INN OKPO OKONH. No reference should be made to code names. A complete list of OKONH codes should not be provided, it is sufficient to include one. The data in this field will be used for billing. This field is mandatory for Russian legal entities. In applications submitted by organizations not registered as legal entities in Russia this field shall be included in the application but remain blank. [Mandatory] [Single] [Read-Only] [Hidden] Example:
The organization's representative responsible for the managerial support of activities related to maintaining the domain (administrative contact) - You must use #[PERSON TEMPLATE]#" for its registration. If an object has already been registered in RIPN database, this field should specify its unique identifier assigned in the process of registration. If an object has not yet been registered in RIPN database, the application should include the registration form for that object. In such cases, this field should specify the name of the person (the field "person" in the person's template). The use of unique person identifiers from InterNIC or RIPE databases is allowed only in those cases when the data includes the person's E-mail address. This field may contain information on several representatives of the organization. [Mandatory] [Multiple] [Read-Write] [Open] Example:
The organization's representative responsible for making domain support payments (the billing-contact). All correspondence regarding payment issues will be addressed to this person - You must use #[PERSON TEMPLATE]#" for its registration. All information inclusion instructions for the field "admin-c" apply to the field "bill-c" as well. [Mandatory] [Multiple] [Read-Write] [Open] Example:
The full registered address of the organization according to its incorporation documents. Information in this field should be entered in Russian (for non-russian organization - in English). [Mandatory] [Multiple] [Read-Only] [Hidden] Example:
Postal address of the organization. The originals of invoices and other official documents will be sent to this address. This field should specify all the information required to ensure reliable delivery of mail to the addressee. In addition to the zip code and the organization's name and postal address, it is desirable to specify the organization's department to which the documents should be delivered, as well as the full name of the organization's representative. Information in this field should be entered in Russian (for non-russian organization - in English). [Mandatory] [Multiple] [Read-Write] [Hidden] Example:
Telephone number(s) of the organization. The telephone number should include the international code and
the area code, without any brackets or dashes. The 觨des and the
telephone number should be separated by spaces. [Mandatory] [Multiple] [Read-Write] [Open] Example:
Fax number(s) of the organization. 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 organization. To ensure a more reliable connection, it is desirable to specify a mailing list address in this field. X.400 and FidoNet addresses should be converted to RFC-822 format. The e-mail address of the organization specified in the field "e-mail" should be used when the organization's representatives specified in fields "admin-c" and "bill-c" can not be contacted. For GEOGRAPHICAL type domains, this field should specify the address of the maintainer responsible for registering third tier domain names in the appropriate geographical domain area. [Mandatory] [Multiple] [Read-Write] [Open] Example:
Unique organization identifier (NIC-handle). A unique organization identifier can either be selected by the Applicant or be created automatically when object information is entered into the database (the field "action" in the application has the value NEW or is not included). If the field "nic-hdl" is left blank when entering the information into the database, the identifier will be created automatically using the first capital letters of words making up the name of the organization (the field "org") with the addition of an index number and the characters whose inclusion is required in the end of any organization's identifier: - ORG-RIPN. If the name selected by you is specified in the field "nic-hdl" while entering the information into the database (including the required characters that must stand in the end of an organization's identifier: - ORG-RIPN) then the unique identifier will be created by adding an index number to your identifier name (the index number is added if the name specified is already present in the database). The value of the identifier is sent to the e-mail addresses of Applicant and the maintainer. Thereafter, when updating the data or obtaining complete information related to the organization (the value of the field "action" in the application is UPDATE or GET), the field "nic-hdl" must be filled in, as identification will be based on the value of this field. The field should contain not more than 64 characters. [Optional] [Single] [Read-Only] [Open] Example:
Any textual comments or notes. [Optional] [Multiple] [Read-Write] [Open] Any comments or notes included for 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 ensuring that RIPN database has the correct information on the organization - 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:
The source of information. For documents in RIPN database, this field should always have the value "RIPN". [Mandatory] [Single] [Read-Only] [Open] Example:
org: Newtime Joint Stock Company Template description includes the following parameters for each field in the template:
|
