Supporting Notes for the IPv4 First Allocation Request Form
RIPE NCC
Document ID: ripe-236
Date: 14 June 2002
See also ripe-235
_________________________________________________________________
Contents
* Introduction
* Supporting Notes for the Request Form Templates
* Example of a First Allocation Request Form
* References
Introduction
This document contains supporting notes for the set of templates to
be used when submitting an "IPv4 First Allocation Request Form".
It should be noted that since August 2000 the minimum allocation
size issued by RIPE NCC is /20 (4096 IPv4 addresses).
This set of templates should be sent following the submission of
one or more IPv4 address space request forms found at:
http://www.ripe.net/ripe/docs/iprequestform.html.
You may choose to use the clean templates provided in the "IPv4
First Allocation Request Form" document which is located at:
http://www.ripe.net/ripe/docs/first-allocation.html#templates
Warning:
Requests sent to the RIPE NCC that lack a proper Registry
Identifier (X-NCC-RegID) will be returned to the sender. Please
include the Registry Identifier in the header of the message or at
the top of this form. Additionally, modifying the templates is
likely to delay the request.
Supporting Notes for the Request Form Templates
X-NCC-RegID:
The Registry Identifier must be included in every message sent to
<hostmaster@ripe.net>. It is used to identify the Local Internet
Registry. More information about the registry identifier can be
found in the RIPE Document "Guidelines for Setting Up a Local
Internet Registry at the RIPE NCC" at:
http://www.ripe.net/ripe/docs/new-lir.html
#[OVERVIEW OF ORGANISATION TEMPLATE]#
Please enter a short description of the organisation requesting the
IPv4 allocation.
#[REQUESTER TEMPLATE]#
Please enter the details of the person at your Local Internet
Registry (LIR) who is submitting this request.
name:
organisation:
country:
phone:
fax-no:
e-mail:
#[IPv4 ASSIGNMENT TICKET NUMBERS]#
In this section, please list the ticket numbers for all the IPv4
address space request forms your New LIR has submitted to
<hostmaster@ripe.net>.
Members need to demonstrate the usage or need for at least a /22
(1024 IPv4 addresses) within three months. For this reason the list
needs to contain tickets that equate to assignments of a /22 or
more.
Organisations using a /22 or fewer addresses are required to
renumber those networks into the new allocation.
Ticket Number Organisation Name Netname Size CIDR
#[NETWORK TEMPLATE]#
This template contains the network object (inetnum) that will
describe your allocation.
inetnum: *leave empty*
netname: *leave empty*
descr: [Provider / Enterprise] Local Registry
descr: Name of LIR's organisation
country: *specify the country*
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 LIR mntner name*
mnt-routes:*specify LIR mntner name*
notify: *specify e-mail address*
changed: hostmaster@ripe.net
source: RIPE
The "inetnum:" attribute value (the IPv4 network prefix) should be
left blank. It will be chosen by the RIPE NCC from the available
IPv4 address space allocated to the RIPE NCC by the Internet
Assigned Numbers Authority (IANA).
The "netname:" will always be selected by the RIPE NCC. LIRs cannot
select their own "netname:" for the inetnum describing their
allocation. However, they must select their own netnames for any
assignments they register as inetnum objects in the RIPE Whois
Database.
The "descr:" attributes will always indicate that this network is
allocated to either a Provider or an Enterprise LIR. However, the
LIR can add additional "descr:" attributes which will be included
in the object entered into the RIPE Database.
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 country codes to be listed using a single
"country:" attribute.
The "admin-c:" and "tech-c:" are the contacts for the allocation at
the LIR. For more information please refer to the supporting notes
of the IPv4 address space request form found at:
http://www.ripe.net/ripe/docs/iprequestsupport.html#toc12
If the LIR has a role object it might want to reference this in the
"admin-c:" and "tech-c:" attributes. Role objects are an efficient
way of managing to contact information for groups of people.
The "status:" attribute will generally be <ALLOCATED PA>.
The "mnt-by:" attribute will always have a value of
<RIPE-NCC-HM-MNT>.
The "mnt-lower:" and "mnt-routes:" attributes provide hierarchical
authentication. That is, they authenticate the creation of route
objects or more specific inetnum objects under the allocation
inetnum object, thus preventing the unauthorised creation of
objects.
It is essential that the LIR has their own maintainer referenced in
these attributes. Where the LIR does not already have a maintainer
they should complete and include the maintainer template below. The
RIPE NCC will then create the maintainer for the LIR and reference
it in the inetnum object.
The "notify:" attribute should specify the e-mail address that will
receive notifications of any changes made to the allocation inetnum
object.
The "changed:" attribute will always be set to
<hostmaster@ripe.net>.
All objects within the RIPE Whois Database have <RIPE> as a fixed
value for the "source:" attribute.
#[MAINTAINER TEMPLATE]#
mntner: [mandatory] [single] [primary/look-up key]
descr: [mandatory] [multiple] [ ]
admin-c: [mandatory] [multiple] [inverse key]
tech-c: [optional] [multiple] [inverse key]
upd-to: [mandatory] [multiple] [inverse key]
mnt-nfy: [optional] [multiple] [inverse key]
auth: [mandatory] [multiple] [ ]
remarks: [optional] [multiple] [ ]
notify: [optional] [multiple] [inverse key]
mnt-by: [mandatory] [multiple] [inverse key]
referral-by: [mandatory] [single] [inverse key]
changed: [mandatory] [multiple] [ ]
source: [mandatory] [single] [ ]
#[TEMPLATES END]#
_________________________________________________________________
Example Request Form (Completed)
Please enter your Registry ID here.
X-NCC-RegID: nn.nowhere
#[OVERVIEW OF ORGANISATION TEMPLATE]#
Northern Nowhere Internet is an ISP serving the Christmastown
Community in the barren wastes of the arctic north. We are located
in Christmas town and peer at the XMAS-IX. We provide GPRS, Cable,
DSL, Leaded Line, Co-location and other Internet services.
#[REQUESTER TEMPLATE]#
name: Santa Claus
organisation: Northern Nowhere Internet
country: NN
phone: +999 555 5555
fax-no: +999 555 5556
e-mail: santa.claus@nowhere.nn
#[IPv4 ASSIGNMENT TICKET NUMBERS]#
Ticket Number Organisation Name Netname Size CIDR
NCC#2002010002 NN Internet XMAS-SERVICE-LAN 768 /23,/24
NCC#2002010001 NN Internet NN-OFFICE-LAN 384 /24,/25
NCC#2002010004 NN Internet NN-P2P-LINKS 384 /24,/25
#[NETWORK TEMPLATE]#
inetnum:
netname:
descr: Provider Local Registry
descr: Northern Nowhere Internet
The Barren Arctic's Premiere
Internet Service Provider
country: NN
admin-c: HOHO-RIPE
tech-c: HOHO-RIPE
status: ALLOCATED PA
mnt-by: RIPE-NCC-HM-MNT
mnt-lower: EXAMPLE-MNT
mnt-routes: EXAMPLE-MNT
notify: ripe-notify@nowhere.nn
changed: hostmaster@ripe.net
source: RIPE
#[MAINTAINER TEMPLATE]#
mntner: EXAMPLE-MNT
descr: Sample maintainer for example
admin-c: SWK1-RIPE
tech-c: RD132-RIPE
upd-to: ripe-dbm@ripe.net
mnt-nfy: ripe-dbm@ripe.net
auth: CRYPT-PW JgR64/DAbBfn6
notify: ripe-dbm@ripe.net
mnt-by: EXAMPLE-MNT
referral-by: RIPE-DBM-MNT
changed: ripe-dbm@ripe.net 20020508
source: RIPE
#[TEMPLATES END]#
_________________________________________________________________
References
More information on "Smallest RIPE NCC Allocation / Assignment
Sizes" is avilable from our web site at:
http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html
Information on renumbering IPv4 networks is available in "Network
Renumbering Overview: Why would I want it and what is it anyway?"
which is available from our FTP site at:
ftp://ftp.ripe.net/rfc/rfc2071.txt
Additionally, "Router Renumbering Guide" might be useful to some
organisations and is available from our FTP site at:
ftp://ftp.ripe.net/rfc/rfc2072.txt
More information about mainatiners is available from the RIPE
Database and the "RIPE Database Reference Manual":
<http://www.ripe.net/perl/whois?-vmntner>
<http://www.ripe.net/ripe/docs/databaseref-manual.html>
Information about person and role objects is available at:
<http://www.ripe.net/perl/whois?-vperson>
<http://www.ripe.net/perl/whois?-vrole>