You are here: Home > Publications > RIPE Document Store > Supporting Notes for the ENUM Request Form

Changes to Supporting Notes for the ENUM Request Form

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-505: This document explains how to complete the ripe-385: Supporting Notes For The ENUM Request Form. Form

This document explains how to complete the ENUM Request Form .

The form and these supporting notes are based on the " IAB Instructions to the RIPE NCC Regarding Operation of the Domain e164.arpa ("ENUM") ",

Your request and all related communication will be publicly available at:
http://www.ripe.net/enum.

Send your completed form to [email protected] .


Preparation
General Information
Requester Details
Organisation Details
Database Template
Supplemental Comments


Preparation

Before completing the request form, create the following objects in the RIPE Database.

1. Person/Role Object(s)

Person and role objects contain information about people. Each object has a unique NIC handle ("nic-hdl:"). (" insert: <span class="pre"> nic-hdl:" insert: </span> ). You can create insert: <b> person insert: </b> and insert: <b> role insert: </b> objects using insert: <a class="external-link" href="https://www.db.ripe.net/fcgi-bin/webupdates.pl"> webupdates insert: </a> . insert: </p>

insert: <p>

Enter " insert: <span class="pre"> AUTO-1 insert: </span> " in the " insert: <span class="pre"> nic-hdl: insert: </span> " field. insert: </p>

insert: <p>

insert: <img alt="ripe3851.gif" class="image-inline" height="212" src="resolveuid/a92bf8dc80308523ed94561cbcd391e5" title="Create a Person Object" width="348" /> ripe3851.gif insert: </p>

insert: <p>

When you receive the message " insert: <span class="pre"> Create SUCCEEDED: [person] XYZ-RIPE insert: </span> ", make a note of your new NIC handle ( insert: <span class="pre"> XYZ-RIPE insert: </span> ). You will need it later. insert: </p>

insert: <p>

insert: <b> 2. Mntner Object insert: </b>

Mntner objects protect objects in the RIPE Database. They contain the information needed to authorise creation, deletion or modification of the objects that they protect. delete: </p> delete: <p> You can create your first delete: <b> person delete: </b> and mntner objects using delete: <span> delete: <a class="western" href="http://apps.db.ripe.net/startup/"> RIPE Database New User Start-up Form delete: </a> delete: </span> insert: <a class="external-link" href="https://www.db.ripe.net/fcgi-bin/webupdates.pl"> webupdates insert: </a> . delete: </p> delete: <p> Leave the "Nic-hdl:" field empty.

Choose a name for your mntner object and enter it in the "Maintainer name:" " insert: <span class="pre"> mntner: insert: </span> ", " insert: <span class="pre"> mnt-by: insert: </span> " and " insert: <span class="pre"> referral-by: insert: </span> " fields. insert: </p>

insert: <p>

Enter the NIC handle of your insert: <b> person/role insert: </b> object in the " insert: <span class="pre"> admin-c: insert: </span> " field.

delete: <p align="center"> delete: <img align="bottom" alt="screen 1" class="image-inline" height="311" id="graphics2" name="graphics2" src="resolveuid/5844abf1b89a0a22d343e07857d620d3" width="460" /> delete: </p> delete: <p align="center"> delete: <img align="bottom" alt="ENUM Request Form, Screenshot 2" class="image-inline" height="192" id="graphics3" name="graphics3" src="resolveuid/d6c6656414dcf378cdf88942efdd9fc9" width="460" /> delete: </p> delete: <p align="center"> delete: <img align="bottom" alt="ENUM Request Form, Screenshot 3" class="image-inline" height="148" id="graphics4" name="graphics4" src="resolveuid/67aa713884828867f1f13faf75a8684f" width="460" /> delete: </p> delete: <p> When insert: <p>

insert: <img alt="ripe3852.gif" class="image-inline" height="269" src="resolveuid/9d5f0cbf69d3b413e39f5a82910cb7c9" title="Creating a Maintainer Object" width="381" /> ripe3852.gif insert: </p>

insert: <p>

For information about choosing authentication schemes for the " insert: <span class="pre"> auth: insert: </span> " attribute, see " insert: <a data-val="44f2f3493809d218a196b447cdba4db5" href="resolveuid/44f2f3493809d218a196b447cdba4db5" data-linktype="internal" class="internal-link"> Protecting your data in the RIPE Database insert: </a> ". insert: </p>

insert: <p>

If you receive the message " delete: <b> Succeeded! delete: </b> ", make a note of have chosen MD5-PW or CRYPT-PW for your delete: <b> person nic-hdl” delete: </b> and delete: <b> “maintainer name” delete: </b> . You will need them later. delete: </p> delete: <p> You authentication scheme, you can create additional delete: <b> person delete: </b> and delete: <b> role delete: </b> objects and also change the objects you already created using delete: <span> delete: <a class="western external-link" href="https://www.db.ripe.net/fcgi-bin/webupdates.pl"> webupdates delete: </a> delete: </span> . delete: </p> delete: <p> delete: <b> 2. use the insert: <a href="https://www.ripe.net/cgi-bin/crypt.cgi"> Crypt CGI interface insert: </a> to encrypt your password. insert: </p>

insert: <p>

insert: <b> 3. Organisation Object

Organisation objects contain information about organisations. Each object has a unique organisation ID ("organisation:"). (" insert: <span class="pre"> organisation: insert: </span> "). You can create organisation objects using delete: <span> delete: <a class="western external-link" href="https://www.db.ripe.net/fcgi-bin/webupdates.pl"> insert: <a class="external-link" href="https://www.db.ripe.net/fcgi-bin/webupdates.pl"> webupdates delete: </span> .

Enter "AUTO-1" in the "organisation:" " insert: <span class="pre"> AUTO-1 insert: </span> " in the " insert: <span class="pre"> organisation: insert: </span> " field.

Enter "OTHER" in the "org-type:" " insert: <span class="pre"> NON-REGISTRY insert: </span> " in the " insert: <span class="pre"> org-type: insert: </span> " field.

Enter the name of your mntner object in the "mnt-ref:" " insert: <span class="pre"> mnt-ref: insert: </span> " and "mnt-by:" " insert: <span class="pre"> mnt-by: insert: </span> " fields.

Add a "password" field and enter the password for your mntner object in clear-text.

delete: <p align="center"> delete: <img align="bottom" alt="ENUM Request Form, Screenshot 4" class="image-inline" height="534" id="graphics5" name="graphics5" src="resolveuid/a5f9cb21bfe86ab78bd27cc1c6d1a4f3" width="651" /> delete: </p> delete: <p align="justify"> insert: <p>

insert: <img alt="ripe3853.gif" class="image-inline" height="305" src="resolveuid/adc2846e9a9a65f349351f1e0380d3d5" title="Creating an Organisation Object" width="373" /> ripe3853.gif insert: </p>

insert: <p>

When you receive the message "Create " insert: <span class="pre"> Create SUCCEEDED: [organisation] ORG-XYZ-RIPE", ORG-XYZ-RIPE insert: </span> ", make a note of the new organisation ID (ORG-XYZ-RIPE). ( insert: <span class="pre"> ORG-XYZ-RIPE insert: </span> ). You will need it later.

delete: <p align="justify"> insert: <p>

You should now have:

  • delete: <p> at least one person/role delete: </b> object delete: </p> delete: </li> delete: <li> one delete: <b> mntner object
  • one mntner insert: </b> object insert: </li>
  • insert: <li>
  • one insert: <b> organisation object
delete: <p align="justify"> insert: <p>

You can use these in the delete: <span> delete: <a class="western" href="http://www.ripe.net/ripe/docs/enum-request.html"> insert: <a href="https://www.ripe.net/publications/docs/enum-request.html"> ENUM Request Form delete: </span> .

General Information

 #[GENERAL INFORMATION]# 
%
% Please do not change the value of the two fields below.
 request-type: enum 
form-version: 1.0

Do not change the value of the " request-type: " and " form-version: " fields.

Requester Details

 #[REQUESTER DETAILS]# 
%
% Please add your contact details.
 name:   John Smith   
phone: +123 45 678910
fax-no: +123 45 678911
email: [email protected]

Enter your contact details.

Use the international dialling code (for example, +31 for the Netherlands,) in the " phone: " and " fax-no: " fields.

Organisation Details

 #[ORGANISATION DETAILS]# 
%
% Which organisation is requesting the delegation?
 legal-organisation-name:   Arctic Telecom   
organisation-location: Frostlane 1-3, 0135 NN Ice-Valley, Northern Nowhere
website: http://www.arctictelecom.net

Enter the legal name and primary location of the organisation that is requesting the delegation in the " legal-organisation-name: " and " organisation-location: " fields. If this organisation has a website, enter its URL in the " website: " field.

Database Template

 #[DATABASE TEMPLATE]# 
%
% Please complete all of the fields below.
 domain:   9.9.9.8.e164.arpa   
descr: Arctic Telecom
org: ORG-BEI1-RIPE
admin-c: JS6381-RIPE
tech-c: JS6381-RIPE
zone-c: JS6381-RIPE
nserver: iceberg1.arctic-telecom.net
nserver: titanic.penguin.ripe.net
mnt-by: EXAMPLE-MNT
changed: [email protected]
source: RIPE

Enter a fully qualified domain name for the requested delegation in the " domain: " field (without a trailing dot). The domain name consists of the the country's E.164 code, written in reverse, with each digit separated by a dot. For example, the country code "+123" is written as " 3.2.1.e164.arpa ".

Enter the name of your organisation in the " descr: " field.

Enter the organisation ID of your organisation object in the " org: " field.

The NIC handle of the role or person object in the " admin-c: " field should reflect someone who is administratively responsible for the delegation.

The NIC handle of the role or person object in the " tech-c: " and " zone-c: " fields should reflect someone who has technical knowledge of DNS setup of the delegation.

Enter the hostnames of two name servers in the two " nserver: " fields. You can add more " nserver: " fields if needed. You can also add an IP address after a hostname to specify a glue record. Prior to delegation, all name servers should be configured as authoritative for the requested zone in accordance with RFC 1912 .

Enter the name of your mntner object in the " mnt-by: " field.

The " changed: " field must be [email protected] .

The " source: " field must be RIPE .

delete: <a id="comments" name="comments" data-val="a5f9cb21bfe86ab78bd27cc1c6d1a4f3" data-linktype="internal"> insert: <a id="comments" name="comments" data-val="adc2846e9a9a65f349351f1e0380d3d5" data-linktype="internal"> Supplemental Comments

 #[SUPPLEMENTAL COMMENTS]# 
%
% Please add more information if you think it will help us understand
% this request.
  The Ministry of Telecommunications of Northern Nowhere selected Arctic 
Telecom to run the Northern Nowhere ENUM trial. This delegation will allow
Arctic Telecom to conduct field trials of ENUM-enabled technologies in
Northern Nowhere.

You can use this space for additional information that you think will be helpful.

 #[END of REQUEST]# 
Supporting Notes for the For The ENUM Request Form
RIPE Documents Search