.
European IP Address Space Request Form
____________________________________________________
European IP Address Space Request Form
Document ID: ripe-137
Obsoletes: ripe-129
See also: ripe-136, ripe-138
Overview
This document contains the set of templates to be
used when submitting an IP assignment request. This
set of forms must be used by Internet Service
Providers when submitting a request to the RIPE NCC.
It may also be used by ISPs to collect information
from those managing the networks that will use the
address space. Instructions for filling out the tem-
plates are found in the accompanying document "Sup-
porting This RIPE document has been obsoleted due to the RIPE NCC reaching the last /8 of IPv4 address space. Link: /about-us/news/ripe-ncc-begins-to-allocate-ipv4-address-space-from-the-last-8/
% Provider Independent (PI) Assignment Request Form
% RIPE NCC members (LIRs) and Direct Assignment Users can use this form
% to request a PI assignment. Please see "Supporting Notes for the European IP Address Space
Request Form (ripe-138).
Internet Service Providers: Submit the form via e-
mail to "<[email protected]>." (If the ISP is not
a Local Internet Registry, the form should be sub-
mitted to the upstream provider.)
Network Administrators: Send the form to the Inter-
net Service Provider from which you received it.
Warning (If submitted to the RIPE NCC):
Requests that are sent to the RIPE NCC which
lack a proper registry ID will be returned to
the sender. Further, any modifications to the
templates may result in a delay in handling.
____________________________________________________
ripe-137.txt Page 1
European IP Address Space Request Form
____________________________________________________
I. General Information
#[OVERVIEW OF ORGANIZATION TEMPLATE]#
#[REQUESTER TEMPLATE]#
reg-ID:
name:
organisation:
country:
phone:
fax: (optional)
e-mail:
#[USER TEMPLATE]#
name:
organisation:
country:
phone:
fax: (optional)
e-mail:
#[CURRENT ADDRESS SPACE USAGE TEMPLATE]#
Addresses Used
Prefix Subnet Mask Size Current 1-yr 2-yr Description
____________________________________________________
ripe-137.txt Page 2
European IP Address Space Request Form
____________________________________________________
II. The Request
#[REQUEST OVERVIEW TEMPLATE]#
request-size:
addresses-immediate:
addresses-year-1:
addresses-year-2:
subnets-immediate:
subnets-year-1:
subnets-year-2:
inet-connect:
country-net:
private-considered:
request-refused:
PI-requested:
address-space-returned:
#[ADDRESSING PLAN TEMPLATE]#
Relative Addresses Used
Prefix# Subnet Mask Size Immediate 1yr 2yr Description
____________________________________________________
ripe-137.txt Page 3
European IP Address Space Request Form
____________________________________________________
III. Database Information
#[NETWORK TEMPLATE]#
netname:
descr:
descr:
descr:
descr:
country:
admin-c:
tech-c:
changed:
source: RIPE
#[PERSON TEMPLATE]#
person:
address:
address:
address:
address:
address:
address:
phone:
fax:
nic-hdl:
changed:
source: RIPE
#[TEMPLATES END]#
____________________________________________________
ripe-137.txt Page 4
European IP Address Space Request Form
____________________________________________________
IV. Optional Information:
____________________________________________________
ripe-137.txt Page 5
% Provider Independent (PI) Assignment Request Form" for instructions on
% how to complete this form.
% http://www.ripe.net/ripe/docs/pi-requestsupport.html
%
% Please note that the End User should have a signed "End User
% Assignment Agreement" with either the sponsoring LIR or the RIPE NCC.
#[GENERAL INFORMATION]#
%
% Please add your RegID.
request-type: pi-ipv4
form-version: 1.3
x-ncc-regid:
#[ADDRESS SPACE USER]#
%
% Who will use the requested address space?
legal-organisation-name:
organisation-location:
website-if-available:
% Is this request being sent by a sponsoring LIR on behalf of
% an End User? (Yes/No)
end-user-of-sponsoring-lir:
% If yes, please confirm that the "End User Assignment Agreement"
% contains all of the elements listed in paragraph 2.0 of "Contractual
% Requirements for Provider Independent Resource Holders in the
% RIPE NCC Service Region".(Yes/No)
confirmation:
% Does this End User already have address space that can be used for
% this assignment? (Yes/No)
space-available:
#[INITIAL INFORMATION]#
%
% Why is PI address space required rather than PA address space?
why-pi:
% Is the End User requesting extra address space for routing and/or
% administrative reasons? (Yes/No)
routing-reasons:
% Is the End User aware of the consequences and disadvantages
% of PI address space? (Yes/No)
confirmation:
#[ADDRESSING PLAN]#
% As of 1 January 2010 assignments are for a period of up to 12 months.
% As of 1 July 2010 assignments are for a period of up to 9 months.
% As of 1 January 2011 assignments are for a period of up to 6 months.
% As of 1 July 2011 assignments are for a period of up to 3 months.%
% How will the End User use this address space?
%
% Subnet Immediate Intermediate Entire Purpose
% size (/nn) Requirement Requirement Period
subnet:
subnet:
totals:
number-of-subnets:
% Will the End User return any address space?
address-space-returned:
#[EQUIPMENT DESCRIPTION]#
%
% What equipment will be used and how will it use the requested
% address space?
equipment-name:
manufacturer-name:
model-number:
other-data:
equipment-name:
manufacturer-name:
model-number:
other-data:
#[NETWORK DESCRIPTION]#
%
% Please add more information if you think it will help us understand
% this request.
<add more information>
#[SUPPORTING DOCUMENTATION]#
%
% If this request is being sent by a sponsoring LIR on behalf of
% an End User, please attach a copy of the signed "End User Assignment
% Agreement" and the company registration papers of the End User.
% You can also attach a network diagram or other supporting
% documentation.
%
% Have you attached any files/documents to this request? (Yes/No)
file-attached:
#[DATABASE TEMPLATE(S)]#
%
% Please complete all of the fields below.
inetnum: <leave empty>
netname: <add netname>
descr: <add End User organisation name>
country: <add country code>
org: <add org-ID>
admin-c: <add nic-handle of administrative contact>
tech-c: <add nic-handle of technical contact>
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-lower: RIPE-NCC-END-MNT
mnt-by: <add mntner name>
mnt-routes: <add mntner name>
mnt-domains: <add mntner name>
changed: [email protected]
source: RIPE
#[END of REQUEST]#