Supporting Notes for the IPv4 First Allocation Request Form
Filiz Yilmaz Bican,
Emma Bretherick,
Agata Peszkowska,
Ingrid Wijte
Document ID: ripe-312
Date: 26 April 2004
Obsoletes: ripe-236, ripe-273
See also ripe-311
_________________________________________________________________
Contents
Introduction
Supporting Notes for the Request Form Templates
Example
References
Introduction
This document contains instructions for completing the 'IPv4 First Allocation Request
Form'. It is a tool for gathering the information necessary to evaluate the request and to
ensure that the same guidelines are applied to each request. Where necessary, the RIPE
NCC will ask for additional information.
The 'IPv4 First Allocation Request Form' can be found at:
http://www.ripe.net/ripe/docs/first-allocation.html
This form should be sent following the submission of 'Provider Aggregatable (PA)
Assignment Request Form(s)' found at:
http://www.ripe.net/ripe/docs/iprequestform.html
Supporting Notes for the Request Form Templates
#[GENERAL INFORMATION]#
request-type: ipv4-first-alloc
form-version: 1.1
Please do not alter the value of the 'request-type' and 'form-version' fields.
x-ncc-regid:
The Registry Identifier (RegID) must be included in every message sent to
<hostmaster@ripe.net>. It is used to identify the Local Internet Registry (LIR). It has the
following format:
<country code>.<organisation name>
Warning: Requests sent to the RIPE NCC that lack a proper RegID (x-ncc-regid) will
bounce back to the sender.
#[REQUESTER TEMPLATE]#
%
% Please enter the details of the person at your Local
% Internet Registry (LIR) who is submitting this request.
name:
phone:
fax-no:
e-mail:
nic-hdl:
A nic-handle (nic-hdl) is a unique identifier for a person or a role object.
It is generated by the database when creating the object. It has the following format:
<initials>[number]-RIPE
For example:
HOHO15-RIPE
More information can be found at:
http://www.ripe.net/ripe/docs/databaseref-manual.html
#[CURRENT ADDRESS SPACE]#
%
% Does the organisation (LIR) that is submitting this
% request have address space in use for infrastructure
% Enter "Yes" or "No".
current-address:
If your organisation already has IP address space please state "Yes" (this does not
include address space for customers' networks).
#[CURRENT ADDRESS SPACE PREFIX TEMPLATE]#
%
% If you have answered "Yes" to the question above please
% list prefixes currently used.
%
actual-prefix:
Please repeat the 'actual-prefix:' field for all subnets currently in use by your organisation.
In the 'actual-prefix' field please enter the actual prefixes in CIDR (slash) notation that you
are currently using (i.e. x.x.x.x/xx).
#[DATABASE TEMPLATE(S)]#
%
% Please fill in the necessary details below so that the
% Hostmaster can create an inetnum object after allocating
% a block to you. If it is necessary to create a maintainer object
% please include that template too.
inetnum:
netname:
descr: [Provider / Enterprise] Local Registry
descr: *specify the name of the LIR's organisation*
country: *specify the country code*
org: *specify org ID here*
admin-c: *insert nic-handle of administrative contact*
tech-c: *insert nic-handle of technical contact*
status: ALLOCATED PA
mnt-by: RIPE-NCC-HM-MNT
mnt-lower: *specify mntner name here*
mnt-routes:*specify mntner name here*
notify: *specify e-mail address*
changed: hostmaster@ripe.net
source: RIPE
The "inetnum:" attribute (the IPv4 network range) should be left blank. It will be chosen by
the RIPE NCC from the available IPv4 address space allocated to it by the Internet
Assigned Numbers Authority (IANA).
The "netname:" attribute should be left blank. It will be chosen by the RIPE NCC.
The first "descr:" attribute will always indicate that this network is allocated to either a
Provider or an Enterprise LIR. In the second "descr:" attribute enter the registered/legal
organisation name of the LIR.
The "country:" attribute describes the country or countries the network will operate in. If
the network is multi-national a "#" can be used to allow multiple ISO country codes to be
listed using a single "country:" attribute.
For example:
country: NL # ES IT
The "org:" attribute should specify the Org ID for the organisation that will use the address
space. This object must be created in advance.
The "admin-c:" attribute contains the nic-hdl for the administrative contact person at the
LIR. This person should be administratively responsible for the network. A role object nic-
hdl can also be used in this attribute.
The "tech-c:" attribute contains the nic-hdl for the technical contact person at the LIR. This
person should have technical knowledge of the network and will preferably be working on-
site. A role object nic-hdl can also be used in this attribute.
The "status:" attribute must be ALLOCATED PA.
The "mnt-by:" attribute must be RIPE-NCC-HM-MNT.
The "mnt-lower:" and "mnt-routes:" attributes provide hierarchical authentication. They
authenticate the creation of more specific inetnum objects or route objects within the
allocation block. The LIR's maintainer must be referenced here.
The "notify:" attribute specifies the e-mail address that will receive notifications of any
changes made to the object.
The "changed:" attribute must be hostmaster@ripe.net.
The "source:" attribute must be RIPE.
If you already have a maintainer there is no need to complete the mntner template below.
mntner: *specify mntner name here*
descr: *descriptive comments*
admin-c: *insert nic-handle of administrative contact*
tech-c: *insert nic-handle of technical contact*
upd-to: *specify e-mail address*
mnt-nfy: *specify e-mail address*
auth: *specify authorisation*
mnt-by: *specify mntner name here*
referral-by: RIPE-DBM-MNT
changed: hostmaster@ripe.net
source: RIPE
The "mntner:" attribute should reflect the LIR's organisation name.
The "descr:" attribute should be used to give a short description of the object.
For example:
"Maintainer for objects of <organisation name>"
The "upd-to:" attribute specifies the e-mail address that will be notified of all failed
attempts to modify objects protected by the maintainer.
The "mnt-nfy:" attribute specifies the e-mail address that will be notified of all successful
updates to objects protected by the maintainer.
The "auth:" attribute specifies the authentication scheme you have chosen to protect your
objects. The different schemes can be found at:
http://www.ripe.net/ripencc/pub-services/db/security.html
PGP cannot be used as authentication when creating a maintainer. If you wish to use
PGP you must choose another authentication and then modify the object after its creation.
In the "mnt-by:" attribute you should enter the name of the maintainer protecting this
object. Usually this will be the same value as the "mntner:" attribute, as the object will
protect itself.
The "referral-by:" attribute must be RIPE-DBM-MNT.
The "changed:" attribute must be hostmaster@ripe.net.
The "source:" attribute must be RIPE.
#[INSERT SUPPLEMENTAL COMMENTS]#
%
% Please add any supplementary information that you think
% may facilitate the evaluation of this request below.
%
% Please give an explanation of how much address space you
% expect to assign within the next three months. This information
% will facilitate the evaluation of your first allocation size.
You may also use this area/space for any additional comments you feel are important and
did not fit within the previous templates.
#[END OF REQUEST]#
Please insert your signature in plain text (with your full name) after the above header. The
Robot will not process any information included here.
Example
#[GENERAL INFORMATION]#
request-type: ipv4-first-alloc
form-version: 1.1
x-ncc-regid: nn.santa
#[REQUESTER TEMPLATE]#
%
% Please enter the details of the person at your Local Internet
% Registry (LIR) who is submitting this request.
name: Santa Claus
phone: +999 555 5555
fax-no: +999 555 5556
e-mail: santa.claus@nowhere.nn
nic-hdl: HOHO15-RIPE
#[CURRENT ADDRESS SPACE]#
%
% Does the organisation (LIR) that is submitting this
% request have address space in use for infrastructure
% Enter "Yes" or "No".
current-address: Yes
#[CURRENT ADDRESS SPACE USAGE TEMPLATE]#
%
% If you have answered "Yes" to the question above please
% list prefixes currently used.
%
actual-prefix: 193.1.193.0/26
actual-prefix: 193.1.193.64/27
actual-prefix: 193.1.193.96/27
actual-prefix: 193.1.193.128/25
actual-prefix: 193.1.193.0/24
#[DATABASE TEMPLATE(S)]#
%
% Please fill in the necessary details below so that the
% Hostmaster can create an inetnum object after allocating
% a block to you. If it is necessary to create a maintainer object
% please include that template too.
inetnum:
netname:
descr: Provider Local Registry
descr: Santa's Workshop Inc.
country: NN
org: ORG-SANT1-RIPE
admin-c: HOHO15-RIPE
tech-c: HOHO15-RIPE
status: ALLOCATED PA
mnt-by: RIPE-NCC-HM-MNT
mnt-lower: SANTA-MNT
mnt-routes: SANTA-MNT
notify: ripe-notify@nowhere.nn
changed: hostmaster@ripe.net
source: RIPE
mntner: SANTA-MNT
descr: Santa's Workshop Inc. Maintainer
admin-c: HOHO15-RIPE
tech-c: HOHO15-RIPE
upd-to: santa@nowhere.nn
mnt-nfy: role@nowhere.nn
auth: MD5-PW $1$rHVeTQ7w$wywuM6zU2zZhA9HfDu4o4/
mnt-by: SANTA-MNT
referral-by: RIPE-DBM-MNT
changed: hostmaster@ripe.net
source: RIPE
# [INSERT SUPPLEMENTAL COMMENTS]#
%
% Please add any supplementary information that you think
% may facilitate the evaluation of this request below.
%
% Please give an explanation of how much address space you
% expect to assign within the next three months. This information
% will facilitate the evaluation of your first allocation size.
All current address space listed will be returned to nn.teleco (our previous provider) three
months after we receive an allocation.
We expect to assign a /23 and a /24 for our own infrastructure and a further /23 for
customers within the first three months.
#[END of REQUEST]#
Best Regards,
Santa Claus
Network Administrator
Santa's Workshop Inc.
References
IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region
http://www.ripe.net/ripe/docs/ipv4-policies.html
RIPE Database User Manual: Getting Started
http://www.ripe.net/ripe/docs/db-start.html
Smallest RIPE NCC Allocation / Assignment Sizes
http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html
RIPE NCC LIR Portal
https://lirportal.ripe.net/