 |
Maintainer Registration Form #[MAINTAINER TEMPLATE]# |
|
To register a maintainer in the database or to change its data, submit an application with form #[MAINTAINER TEMPLATE]# to RIPN. Application preparation rules are set out in document "General rules for making applications". Below is a detailed description of each #[MAINTAINER TEMPLATE]# field (information in all fields should be entered in English, unless specified otherwise): Unique maintainer identifier - word made of Latin capital letters, figures and dashes, not coinciding with other maintainer identifiers registered in RIPN database. The identifier should end with -MNT-RIPN characters and contain not more than 64 characters. Unique maintainer identifier is selected by the Applicant. You
can check if the identifier is unique with Use of unique maintainer identifiers from RIPE database (European Center for IP net development) is not allowed. [Mandatory] [Single] [Read-Only] [Open] Example:
Any brief description of the maintainer. [Optional] [Multiple] [Read-Write] [Open] Example:
Organization or person, which supports this technical support service. If the object has already been registered in RIPN database, its unique identifier assigned during registration is specified in this field. If the object has not yet been registered in RIPN database, the application should contain its TEMPLATE. In this case, the name of the organization is specified in this field ("org" field in the ORGANIZATION TEMPLATE) or the name of the person (" person" field in the PERSON TEMPLATE). The submitted PERSON TEMPLATE should contain filled in "person-r", "p-addr", "passport", "birht-date" fields. Use of unique person identifiers from InteNIC and RIPE databases is not allowed in this field. [Mandatory] [Single] [Read-Only] [Open] Example:
Representative of technical support service, contact person for technical questions. If the object has already been registered in RIPN database, its unique identifier assigned during registration is specified in this field. If the object has not yet been registered in RIPN database, the application should contain its TEMPLATE. In this case, the name of the person ("person" field in the PERSON TEMPLATE) is specified in this field. Use of unique person identifiers from InterNIC or RIPE databases is allowed only in those cases when the data includes the E-mail address of the person. This field can contain information on several representatives of technical support service. [Mandatory] [Multiple] [Read-Write] [Open] Example:
E-mail address used for forwarding all object update requests that failed authorization for objects covered by the given maintainer. [Mandatory] [Multiple] [Read-Write] [Hidden] Example:
E-mail address used for forwarding notifications of all updates in RIPN database objects, supported by the given maintainer. [Mandatory] [Multiple] [Read-Write] [Hidden] Example:
The field that establishes authorization scheme. MAIL-FROM <e-mail> - non necessary authorization by
e-mail; Authorization is possible: by password only, or by password and e-mail simultaneously. Upon receipt of application for change of data in the object that has reference to technical support service, the sender's address is compared with the addresses specified in "auth" fields of maintainer description and "passwd" field in the application is compared with the passwords specified in "auth" fields of maintainer description. The changes will be accepted only in those cases when the senders address and "passwd" field in the application coincide with one of the addresses and one of the passwords, specified in "auth" field of the maintainer description. Thus, when authorization is effected both by e-mail address and by password, an application with the right password sent from the wrong e-mail address will not be accepted. The password should be given in the template in not coded form. [Mandatory] [Multiple] [Read-Write] [Hidden] Example:
Any comments, 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] Unique identifier of the maintainer responsible for correctness of information on given object in RIPN database. Can point to itself - for its registration must be used MAINTAINER TEMPLATE. [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 documents in RIPN database, this field should always have the value "RIPN". [Mandatory] [Single] [Read-Only] [Open] Example:
Sample of #[MAINTAINER TEMPLATE]# completion mntner: NTIME1-MNT-RIPN Template description includes the following parameters for each field in the template:
|
