Internet Exchange Point Assignment Request Form

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.

To request resources from the RIPE NCC, members should now use the request forms in the LIR Portal.

The Resource Request API and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms.

% Internet Exchange Point Assignment Request Form
% RIPE NCC members (LIRs) can use this
% form to request an IPv4/IPv6 Assignment for an Internet Exchange
% Point (IXP).  Please see ripe-576 for instructions on how to
% complete this form.
%
% 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]#

request-type: ixp-assign
form-version: 1.0

% Please add your RegID.
x-ncc-regid: 


#[OVERVIEW OF ORGANISATION]#

% 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:

% Which IXP will use the requested address space? 
org-description: 


#[OVERVIEW OF THE USER]#

% Who is the contact person for this IXP?
Name:
Organisation:
Country:
Phone:
E-mail:


#[EXISTING ADDRESS SPACE USAGE]#

% If the IXP has any IPv4 ranges(s) for their peering LAN, list them
% below.  If any such space is being returned, then the return date
% should be specified.
subnet-ipv4:

% If the IXP has any IPv6 assignments, list them below.
subnet-ipv6:



% The next two sections (IPv4 and IPv6) will give us an overview of
% the detailed usage of the resources. Please fill in only the
% relevant section as per the resource being requested and remove the
% section that is not applicable.


#[IPv4 ADDRESS SPACE USAGE]#

% How will the IXP use the requested IPv4 address space? 
%
% ADDRESSING PLAN
% 
%       Subnet       Immediate    Intermediate  Entire   Purpose
%       size (/nn)   Requirement  Requirement   Period
subnet:

totals:
number-of-subnets: 

#[IPv6 ADDRESS SPACE USAGE]#

% How will the IXP use the requested IPv6 address space?
%
% ADDRESSING PLAN
% 
%       Subnet       Within     Within   Within    Purpose
%       size (/nn)   3 months   1 year   2 years   
subnet:


#[SUPPLEMENTAL COMMENTS]#

% 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. If the IXP has an online list of members,
% please add the URL below.

<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.

% Have you attached any files/documents to this request?  (Yes/No)
file-attached:


#[IPv4 DATABASE TEMPLATE]#

% 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 IXP organisation name>
country:       <add country code>
org:           <add org-ID>
admin-c:       <add nic-hdl of administrative contact>
tech-c:        <add nic-hdl 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 


#[IPv6 DATABASE TEMPLATE]#

% 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 IXP organisation name>
country:       <add country code>
org:           <add org-ID>
admin-c:       <add nic-hdl of administrative contact>
tech-c:        <add nic-hdl 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]#