Supporting Notes for the IPv4 First Allocation Request Form

Doc-ID: ripe-362
Date: November 2005
Obsoletes: ripe-333

This document contains instructions for LIRs on how to complete the "IPv4 First Allocation Request Form".

The instructions are based on the "IPv4 Address Allocation and Assignment Policy for the RIPE region" .

LIRs should also send one or more "Provider Aggregatable (PA) Assignment Request Forms" for all pending infrastructure and/or customer assignments.

• General Information
• Requester Template
• Current Address Space
• Current Address Space Prefix Template
• Database Template(s)
• Insert Supplemental Comments
• End of Request

General Information

#[GENERAL INFORMATION]#
%
% Please add your RegID.

request-type: ipv4-first-alloc
form-version: 1.1
x-ncc-regid:  nl.bluelight

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

Enter your Registry Identifier (RegID) in the "x-ncc-regid:" field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact <ncc@ripe.net>.

Requester Template

#[REQUESTER TEMPLATE]#
%
% Please add your contact details.

name:    John Smith
phone:   +123 45 678910
fax-no:  +123 45 678911
email:   john@bluelight.ripe.net
nic-hdl: HOHO1-RIPE

Enter your contact details in the requester template. You must be a registered contact for the LIR. The LIR Portal contains the list of registered contacts for your LIR.

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

Enter your NIC handle in the "nic-hdl:" field, if you have one.

Current Address Space

#[CURRENT ADDRESS SPACE]#
%
% Are you currently using any address space? (Yes/No)

current-address: Yes

Enter ‘Yes’ in the "current-address:" field if there is any address space registered to your organisation in the RIPE Whois database.

Current Address Space Prefix Template

#[CURRENT ADDRESS SPACE PREFIX TEMPLATE]#
%
% If yes, which address prefix are you using?

 actual-prefix: 192.0.2.0/24
 actual-prefix: 2001:DB8:5::/48

If you have entered ‘Yes’ in the "Current Address Space" section, please list all of your address space in the "actual-prefix:" field. Please specify address prefixes using slash notation (for example, x.x.x.x/xx or y:y:y::/yy). You can repeat the "actual-prefix:" field as many times as needed.

Database Template(s)

#[DATABASE TEMPLATE(S)]# 
%
% Please complete all of the fields below.

inetnum: 
netname: 
descr:      Bluelight B.V.
country:    NL
org:        ORG-Bb2-RIPE
admin-c:    HOHO1-RIPE
tech-c:     HOHO1-RIPE
status:     ALLOCATED PA
mnt-by:     RIPE-NCC-HM-MNT
mnt-lower:  BLUELIGHT-MNT
mnt-routes: BLUELIGHT-MNT
notify:     john@bluelight.ripe.net
changed:    hostmaster@ripe.net
source:     RIPE

Leave the "inetnum:" and "netname:" fields empty as we (the RIPE NCC) will complete them.

Enter the legal name of the LIR’s organisation in the "descr:" field.

Enter the ISO country code of the LIR’s organisation in the "country:" field.

Enter the org-ID of the LIR’s organisation object in the "org:" field. If you don’t know your LIR’s org-ID, you can find it in the Organisation Object Editor (https://lirportal.ripe.net).

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 (https://www.ripe.net/webupdates).

The nic-hdl of the role or person object in the "admin-c:" field should reflect someone who is administratively responsible for the network.

The nic-hdl of the role or person object in the "tech-c:" field should reflect someone who has technical knowledge of the network.

Maintainers protect objects in the RIPE Whois database. They contain the information needed to authorise creation, deletion or modification of these objects. You can create maintainers using the Maintainer Editor (https://lirportal.ripe.net).

The "mnt-by:" field must be RIPE-NCC-HM-MNT. You will be able to update your allocation object using the Allocation Editor (https://lirportal.ripe.net).

The "mnt-lower:" field shows which maintainer authorises the creation of inetnum objects (i.e. assignments) within the allocation block.

The "mnt-routes:" field shows which maintainer authorises the creation of route objects for the allocation block.

The RIPE Whois database must contain all of the objects that you enter.

We will send an email to the email address in the "notify:" field every time the allocation object is updated.

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

The "source:" field must be RIPE.

Insert Supplemental Comments

#[INSERT SUPPLEMENTAL COMMENTS]#
%
% Please add more information if you have specific

% addressing needs.

We will send one infrastructure request (/24) 
and three customer requests (/27 each) later today. 
This is for all of our immediate addressing needs.

You can use this space for additional information that you think will be helpful for us when we evaluate your request.

End of Request

#[END of REQUEST]#

When you have sent this request form to us, please send separate "Provider Aggregatable (PA) Assignment Request Forms" for all pending infrastructure and customer assignments. Complete one PA Assignment Request form for your infrastructure and additional PA Assignment forms for each organisation you will assign PA address space to. Send each form in a separate email to <hostmaster@ripe.net>.

You will receive a unique ticket number (NCC#xxxxxxxxxx) for each form. We will then evaluate the requests for your first allocation and your first PA assignment(s) at the same time.