This RIPE Document is available in ASCII and PDF

This document explains how to complete the ENUM Request Form Link: https://www.ripe.net/publications/docs/enum-request.html .

The form and these supporting notes are based on the "IAB Instructions to the RIPE NCC Regarding Operation of the Domain e164.arpa ("ENUM") Link: /manage-ips-and-asns/dns/enum/iab-instructions/ ",

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

Send your completed form to enum-request@ripe.net Link: mailto:enum-request@ripe.net .

Preparation Link: #prep
General Information Link: #general
Requester Details Link: #requester
Organisation Details Link: #org-details
Database Template Link: #template
Supplemental Comments Link: #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:"). You can create person and role objects using webupdates Link: https://www.db.ripe.net/fcgi-bin/webupdates.pl .

Enter "AUTO-1" in the "nic-hdl:" field.

When you receive the message "Create SUCCEEDED: [person] XYZ-RIPE", make a note of your new NIC handle (XYZ-RIPE). You will need it later.

2. Mntner Object

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. You can create mntner objects using webupdates Link: https://www.db.ripe.net/fcgi-bin/webupdates.pl .

Choose a name for your mntner object and enter it in the "mntner:", "mnt-by:" and "referral-by:" fields.

Enter the NIC handle of your person/role object in the "admin-c:" field.

For information about choosing authentication schemes for the "auth:" attribute, see "Protecting your data in the RIPE Database Link: resolveuid/44f2f3493809d218a196b447cdba4db5 ".

If you have chosen MD5-PW or CRYPT-PW for your authentication scheme, you can use the Crypt CGI interface Link: https://www.ripe.net/cgi-bin/crypt.cgi to encrypt your password.

3. Organisation Object

Organisation objects contain information about organisations. Each object has a unique organisation ID ("organisation:"). You can create organisation objects using webupdates Link: https://www.db.ripe.net/fcgi-bin/webupdates.pl .

Enter "AUTO-1" in the "organisation:" field.

Enter "NON-REGISTRY" in the "org-type:" field.

Enter the name of your mntner object in the "mnt-ref:" and "mnt-by:" fields.

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

When you receive the message "Create SUCCEEDED: [organisation] ORG-XYZ-RIPE", make a note of the new organisation ID (ORG-XYZ-RIPE). You will need it later.

You should now have:

• at least one person/role object
• one mntner object
• one organisation object

You can use these in the ENUM Request Form Link: https://www.ripe.net/publications/docs/enum-request.html .

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:  john@bluelight.ripe.net

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: hostmaster@ripe.net
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 Link: ftp://ftp.ripe.net/rfc/rfc1912.txt .

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

The "changed:" field must be hostmaster@ripe.net.

The "source:" field must be RIPE.

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]#