Supporting Notes for the IPv4 First Allocation Request Form
Filiz Bican,
Emma Bretherick,
Agata Peszkowska,
Ingrid Wijte
Document ID: ripe-273
Date: 20 August 2003
Obsoletes: ripe-236
See also: ripe-272
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.0
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 automatically 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
#[IPv4 ASSIGNMENT TICKET NUMBERS]#
%
% Please list the details of the PA assignment requests
% that you have sent so far for your customers and/or for
% your own infrastructure.
ticket-ID:
organisation-name:
network-name:
total-immediate:
total-size:
Repeat this template (i.e. all five fields) for all the "Provider
Aggregatable (PA) Assignment Request Forms" that you have submitted to
<hostmaster@ripe.net>. Please leave a blank line between each
template. If you have not submitted any requests, please do so before
submitting this form.
For each request submitted please complete each of the following fields:
In the "ticket-ID" field please enter the ticket number received from
the RIPE NCC for the PA Assignment Request Form.
In the "organisation-name" field please enter the name of the
organisation that will be using the address space as specified in the
same PA Assignment Request Form.
In the "network-name" field please enter the netname as specified in
the same PA Assignment Request Form.
In the "total-immediate" field please enter the total amount of
address space required using CIDR (slash) notation for immediate use
as specified in the same PA Assignment Request Form.
In the "total-size" field please enter the total amount of address
space being requested using CIDR (slash) notation as specified in the
same PA Assignment Request Form.
#[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 USAGE TEMPLATE]#
%
% If you have answered "Yes" to the question above please
% fill in the following template detailing the usage of
% your current address space.
%
% Actual Prefix Current Use Future Use Purpose
subnet:
totals:
Please repeat the "subnet:" field for all subnets currently in use by
your organisation.
In the 'Actual Prefix' column please enter the actual prefixes in CIDR
(slash) notation that you are currently using (i.e. x.x.x.x/xx)
In the 'Current Use' column please enter the amount of address space
in CIDR (slash) notation that you are currently using (i.e. /xx).
In the 'Future Use' column please enter the amount of address space in
CIDR (slash) notation that you plan to use from this subnet in the
future (i.e. /xx).
In the 'Purpose' column please enter a short description of how the
subnet is used.
In the "totals" field please enter the total for each column in CIDR
(slash) notation (i.e. /xx). NOTE: The total given in the 'Actual
Prefix' column should be the total of all subnets in CIDR (slash)
notation (i.e. /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*
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 "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.
You may 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.0
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
#[IPv4 ASSIGNMENT TICKET NUMBERS]#
%
% Please list the details of the PA assignment requests
% that you have sent so far for your customers and/or for
% your own infrastructure.
ticket-ID: NCC#2003062997
organisation-name: Santa's Workshop Inc.
network-name: XMAS-SERVICE-LAN
total-immediate: /23
total-size: /23,/24
ticket-ID: NCC#2003062998
organisation-name: North Pole ISP
network-name: NN-OFFICE-LAN
total-immediate: /24
total-size: /24,/25
ticket-ID: NCC#2003062999
organisation-name: Polar City School
network-name: POLAR-CITY
total-immediate: /25
total-size: /24,/25
#[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
% fill in the following template detailing the usage of
% your current address space.
%
% Actual Prefix Current Use Future Use Purpose
subnet: 193.1.193.0/26 /27 0 Manufacturing devices
subnet: 193.1.193.64/27 /27 0 CAD/CAM stations
subnet: 193.1.193.96/27 /27 0 Manufacturing devices
subnet: 193.1.193.128/25 /25 0 Delivery centre
subnet: 193.1.193.0/24 /25 0 Core network
subnet: 193.1.194.0/23 /23 0 Training centre
subnet: 193.1.196.0/24 /24 0 Guest network
subnet: 193.1.197.0/23 /24 0 Server LAN
totals: /22,/23,/24 /22,/24,/26,/27 0
#[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
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.
All current address space listed will be returned to nn.teleco (our
previous provider) three months after we receive an allocation.
#[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/