- Legend
- Added
- Deleted
Please note: all email-based request forms have been archived on the website and are available through the LIR Portal. You can find an announcement about this here Link: https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2014-October/002890.html .
To request resources from the RIPE NCC, members should now use the request forms in the LIR Portal Link: https://lirportal.ripe.net/ .
The Resource Request API Link: https://www.ripe.net/data-tools/developer-documentation/resource-request-api and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms.
% IPv6 PI Assignment Request Form
% RIPE NCC members (LIRs)and Direct Assignment Userscan use this form
% to request an IPv6 PI assignment. Please see
% Supporting Notes for the IPv6 Provider Independent (PI) Assignment
% Request Form for instructions on how to complete this form.
% http://ripe.net/ripe/docs/ipv6-pi-support Link: http://ripe.net/ripe/docs/ipv6-pi-supporthttp://ripe.net/ripe/docs/ipv6-pi-support.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-ipv6
form-version: 1.11.0
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 attach a copy of the signed "End User Assignment
% Agreement" and the company registration papers of the End User.
% Also 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]#
%
% When will the End User use this IPv6 PI assignment?
%
% Subnet Within Within Within
% size (/nn) 3 months 1 year 2 years Purpose
subnet:
% 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. If the End User is requesting more than a /48 please
% explain why:
#[PEERING CONTACTS]#
%
% Please list the Autonomous System numbers and email contact addresses
% of the peering partners for the requested IPv6 PI assignment.
peering:
peering:
#[NETWORK DIAGRAM]#
%
% You can attach a network diagram or other supporting documentation,
% particularly if the End User is requesting more than /48.
%
% Have you attached any files/documents to this request? (Yes/No)
file-attached:
#[DATABASE TEMPLATE(S)]#
%
% Please complete all of the fields below.
inet6num: <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]#