Maintainer Registration Form #[MAINTAINER TEMPLATE]#

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):

mntner:

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
whois -h whois.ripn.net <NAME-MNT-RIPN>
or using Whois services.

Use of unique maintainer identifiers from RIPE database (European Center for IP net development) is not allowed.

[Mandatory] [Single] [Read-Only] [Open]

Example:

mntner: NTIME1-MNT-RIPN

descr:

Any brief description of the maintainer.

[Optional] [Multiple] [Read-Write] [Open]

Example:

descr: JSC Newtime Technical Support

mnt-adm:

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:

mnt-adm: SSS-RIPN

tech-c:

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:

tech-c: VIP311-RIPN

upd-to:

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:

upd-to: noc@newtime.ru

mnt-nfy:

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:

mnt-nfy: noc@newtime.ru

auth:

The field that establishes authorization scheme.

MAIL-FROM <e-mail> - non necessary authorization by e-mail;
CRYPT-PW <passwd> - necessary authorization by password

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:

auth: MAIL-FROM noc@newtime.ru
auth: CRYPT-PW QWERTY123

remark:

Any comments, notes.

[Optional] [Multiple] [Read-Write] [Open]

remark-h:

mnt-by:

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-by: NTIME1-MNT-RIPN

mnt-ch:

source:

Information source

For documents in RIPN database, this field should always have the value "RIPN".

[Mandatory] [Single] [Read-Only] [Open]

Example:

source: RIPN

Sample of #[MAINTAINER TEMPLATE]# completion

mntner: NTIME1-MNT-RIPN
descr: Joint Stock Company Newtime
descr: Technical Support
mnt-adm: NTIME-ORG-RIPN
tech-c: SSS-RIPN
tech-c: Ivan I Ivanov
upd-to: noc@newtime.ru
mnt-nfy: noc@newtime.ru
auth: MAIL-FROM noc@newtime.ru
auth: CRYPT-PW VASYA007
auth: MAIL-FROM vasya@newtime.ru
auth: CRYPT-PW QWERTY123
mnt-by: NTIME1-MNT-RIPN
source: RIPN

Template description includes the following parameters for each field in the template:

• Inclusion requirement:

[Mandatory] - the field is mandatory
[Optional] - the field is optional

• Allowed number of identical fields in a template:

[Single] - only one field is allowed in the template;
[Multiple] - several identical fields are allowed in a template;

• Possibility of updating the field after entering the information in RIPN database:

[Read-only] - the field is protected from changes;

Either changes can not be made without completely re-registering the domain, or RIPN must be contacted at ru-ncc@ripn.net in order to change the data in the field;

[Read-Write] - changes are allowed;

• Field accessibility while working with RIPN database:

[Hidden] - available to the appropriate maintainer services only;
[Open] - generally accessible