Supporting Notes for the IPv4 Additional Allocation Request Form
Filiz Bican,
Emma Bretherick,
Laura Cobley
Document ID: ripe-277
Date: 20 August 2003
See also: ripe-276
Contents
* Introduction
* Supporting Notes for the Request Form Templates
* Example
* References
Introduction
This document contains instructions for completing the "IPv4
Additional 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 Additional Allocation Request Form" can be found at:
http://www.ripe.net/ripe/docs/add-allocation.html
You should use this form if you have already received an IPv4
allocation and about 80% of it has been used in valid IPv4 assignments
registered in the RIPE Database. Supporting Notes for the Request
Form Templates
#[GENERAL INFORMATION]#
request-type: ipv4-add-alloc
form-version: 1.0
x-ncc-regid:
Please do not alter the value of the 'request-type' or 'form-version'
fields.
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
#[OVERALL USAGE TEMPLATE]#
%
% Please provide information about your current
% allocation(s).
% Prefix Usage % Number Free Total
alloc:
Please repeat the "alloc" field for each of your allocation blocks.
In the "Prefix" column please specify the allocation block using CIDR
(slash) notation (i.e. x.x.x.x/xx).
In the "Usage %" column please enter the percentage of address space
from the allocation block that has been assigned and registered in the
RIPE Database.
In the "Number" column please enter the number of addresses that are
in use.
In the "Free" column please enter the number of addresses that are
unassigned.
In the "Total" column please enter the total number of addresses
within the allocation block.
%
% You may find it easier to use the "asused_public" program
% to prepare this information. The "asused_public" program
% can be found at:
%
% ftp://ftp.ripe.net/tools/asused-latest.tar.gz
%
#[ALLOCATION USAGE TEMPLATE]#
%
% In this section, please list all the assignments you made
% from your LAST allocation. Again, you may want to generate
% this list with the "asused_public" program.
%
% Assignments
% Size
% Inetnum in CIDR Date Netname
Please only list the assignments made from the last allocation block
received by your LIR.
In the "Inetnum" field please enter the range of address space
assigned, shown in the same format as the "inetnum:" attribute of the
inetnum object in the RIPE Database (i.e. x.x.x.x " x.x.x.x).
In the "Size in CIDR" column please enter the size of the assignment
in slash notation.
In the "Date" column please enter the date the assignment was
registered in the RIPE Database. This should correspond to the date in
the first "changed:" attribute of the inetnum object.
In the "Netname" column please enter the netname of the
assignment. This should correspond to the "netname:" attribute of the
inetnum object in the RIPE Database.
#[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-add-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
#[OVERALL USAGE TEMPLATE]#
%
% Please provide information about your current
% allocation(s).
% Prefix Usage % Number Free Total
alloc: 192.168/20 78.1% 3200 896 4096
alloc: 192.168.16/20 79.4% 3266 830 4096
%
% You may find it easier to use the "asused_public" program
% to prepare this information. The "asused_public" program
% can be found at:
%
% ftp://ftp.ripe.net/tools/asused-latest.tar.gz
%
#[ALLOCATION USAGE TEMPLATE]#
%
% In this section, please list all the assignments you made
% from your LAST allocation. Again, you may want to generate
% this list with the "asused_public" program.
%
% Assignments
% Size
% Inetnum in CIDR Date Netname
192.168.16.0 - 192.168.23.255 /21 20021008 XMAS-SERVICE-LAN
192.168.24.0 - 192.168.27.255 /22 20030111 NN-OFFICE-LAN
192.168.28.0 - 192.168.28.127 /25 20030426 POLAR-CITY
#[INSERT SUPPLEMENTAL COMMENTS]#
%
% Please add any supplementary information that you think
% may facilitate the evaluation of this request below.
Please note that the network "POLAR-CITY"
was originally approved as "POLARCITY"
Please update your internal files accordingly.
#[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 Reference Manual
http://www.ripe.net/ripe/docs/databaseref-manual.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/