- 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/publications/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.
% Temporary Internet Number Assignment Request Form
% RIPE NCC members (LIRs)and Direct Assignment Userscan use this form to request
% a Temporary Internet Assignment. Please see "Supporting Notes for the Temporary
% Internet Assignment Request Form" for instructions on how to complete this form.
% http://ripe.net/ripe/docs/temp-assign-support Link: http://ripe.net/ripe/docs/temp-assign-support
%
% Please note that an End User should have a signed "Temporary Independent
% Assignment Request and Maintenance Agreement" with a sponsoring LIR.
% http://ripe.net/lir-services/resource-management/temp-assign-agreement
#[GENERAL INFORMATION]#
% Please add your RegID.
request-type: temp-assign
form-version: 1.11.0
x-ncc-regid:
#[ASSIGNMENT USER]#
% Who will use the requested assignment?
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 "Temporary Independent Assignment Request and
% Maintenance 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)
% Please also attach a copy of the signed agreement and the company registration
% papers of the End User.
confirmation:
#[INITIAL INFORMATION]#
% Which type of assignment is the End User requesting? (IPv4/IPv6/ASN)
type-of-assignment:
% Why do you need this temporary assignment?
why:
% The End User should be aware that this resource will be for a specific time
% period and will be automatically de-registered at the end of the approved
% assignment period.
% Please add more information on the purpose (Event/Research) and duration of this
% request.
purpose:
website-if-available:
% The date should be in the following format: yyyymmdd
start-date:
end-date:
% The next three sections (IPv4, IPv6 and ASN) will give us an overview of the
% detailed usage of the resources. Please fill in only the relevant
% sections as per the resource being requested and remove the sections that are not
% applicable.
#[IPv4 section]#
%
% Why is PI address space required rather than PA address space?
why-pi-v4:
% Is the End User requesting extra address space for routing and/or
% administrative reasons? If yes, explain why.
why-routing-v4:
% Please confirm if the End User is aware of the consequences and disadvantages
% of PI address space? (yes/no)
% For details, you can refer to section 8.0 “PA vs. PI Address Space” of the IPv4
% Address Allocation and Assignment Policies.
confirmation-v4:
% ADDRESSING PLAN
% How will the End User use this IPv4 address space?
%
% Subnet Immediate Intermediate Entire Purpose
% size (/nn) Requirement Requirement Period
subnet:
subnet:
totals:
number-of-subnets:
#[IPv6 section]#
%
% Why is PI address space required rather than PA address space?
why-pi-v6:
% Is the End User requesting extra address space for routing and/or
% administrative reasons? If yes, explain why.
why-routing-v6:
% Please confirm if the End User is aware of the consequences and disadvantages
% of PI address space? (yes/no)
% For details, you can refer to section 8.0 “PA vs. PI Address Space” of the IPv4
% Address Allocation and Assignment Policies.
confirmation-v6:
%ADDRESSING PLAN
% How will the End User use this IPv6 address space?
%
% Subnet Immediate Intermediate Entire Purpose
% size (/nn) Requirement Requirement Period
subnet:
subnet:
totals:
%
% Please list the Autonomous System Numbers and email contact addresses
% of the peering partners for the requested IPv6 PI assignment.
peering-v6:
peering-v6:
#[ASN section]#
%[ADDRESS SPACE TO BE ANNOUNCED]%
% If this ASN will originate other prefixes than are requested
% in this request, please list these below.
prefix-asn:
% If you require a 16-bit AS Number instead of a 32-bit AS Number,
% please indicate this below and tell us why. For more information,
% see http://www.ripe.net/news/asn-32-guide.html
as-number-type: 32-bit [change as required]
why-16-bit:
% Please list the Autonomous System Numbers and email contact addresses
% of the peering partners.
peering-asn:
peering-asn:
#[SUPPORTING DOCUMENTATION]#
% Please add more information if you think it will help us understand
% this request. You can attach a network diagram or other relevant
% supporting documentation.
%<add more information>
#[DATABASETEMPLATE IPv4]#
#[ DATABASE
%
% If you are requesting IPv4, complete this IPv4 database template.
% If you are not requesting IPv4, please remove this IPv4 database template.
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
remarks: Temporary assignment
===========================================
Duration of assignment:
===========================================
Start date:
End date:
==========================================
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
#[DATABASETEMPLATE IPv6]#
#[ DATABASE
%
% If you are requesting IPv6, complete this IPv6 database template.
% If you are not requesting IPv6 please remove this IPv6 database template.
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
remarks: Temporary assignment
===========================================
Duration of assignment:
===========================================
Start date:
End date:
==========================================
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
#[DATABASETEMPLATE ASN]#
#[ DATABASE
%
% If you are requesting ASN, complete this ASN database template.
% If you are not requesting ASN, please remove this ASN database template.
aut-num: ASNEW
as-name: <add name for the AS>
descr: <add AS Number User name>
org: <add org-ID>
import: <specify the outgoing routing policy for the first peer>
export: <specify the incoming routing policy for the first peer>
import: <specify the outgoing routing policy for the second peer>
export: <specify the incoming routing policy for the second peer>
admin-c: <add nic-handle of administrative contact>
tech-c: <add nic-handle of technical contact>
remarks: Temporary assignment
===========================================
Duration of assignment:
===========================================
Start date:
End date:
============================================
mnt-by: RIPE-NCC-END-MNT
mnt-by: <add mntner name>
mnt-routes: <add mntner name>
changed: [email protected]
source: RIPE
#[END of REQUEST]#
