You are here: Home > Publications > RIPE Document Store > Internet Exchange Point Assignment Request Form

Changes to Internet Exchange Point Assignment Request Form

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-575: ripe-460: IPv6 Internet Exchange Point Points Assignment Request Form
delete: <p> delete: <strong> 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 delete: <a class="external-link" href="https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" title=""> here delete: </a> . delete: </strong> delete: </p> delete: <p> To request resources from the RIPE NCC, members should now use the request forms in the delete: <a class="external-link" href="https://lirportal.ripe.net/" target="_self" title=""> LIR Portal delete: </a> . delete: </p> delete: <p> The delete: <a class="external-link" href="https://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self" title=""> Resource Request API delete: </a> and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms. delete: </p> delete: <p> delete: </p>

 % IPv6  Internet Exchange Point  Points  Assignment Request Form insert: <br /> 

% RIPE NCC members (LIRs) and Direct Assignment Users can use this delete: <br /> % form insert: <br />
% to request an IPv4/IPv6 IPv6 Assignment for an Internet Exchange delete: <br /> % Point (IXP). insert: <br />
% Please see delete: <a data-val="6c9f9e3b-3b03-45e7-a758-311bc9237f97" href="resolveuid/6c9f9e3b-3b03-45e7-a758-311bc9237f97" data-linktype="internal" class="internal-link"> ripe-576 delete: </a> ripe-461 for instructions on how to delete: <br /> % complete this form.
%
% Please note that the End User should have a signed "End User
% Assignment Agreement" with either the sponsoring LIR delete: <br /> % or the RIPE NCC.


#[GENERAL INFORMATION]#
delete: <br /> request-type: ixp-assign delete: <br /> form-version: 1.0 delete: <br /> %
% Please add your RegID.
insert: <br />
request-type: ipv6-for-ixp insert: <br />
form-version: 1.2 insert: <br />
x-ncc-regid:
insert: <br />
#[REQUESTER TEMPLATE]# insert: <br />
% insert: <br />
% Please add your contact details. insert: <br />
insert: <br />
name: insert: <br />
phone: insert: <br />
fax-no: insert: <br />
e-mail: insert: <br />
nic-hdl:

#[OVERVIEW OF ORGANISATION]# ORGANISATION TEMPLATE]#

% Is this request being sent by a sponsoring LIR on behalf of an insert: <br />
% End delete: <br /> % User? (Yes/No) insert: <br />

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 insert: <br />
% "Contractual delete: <br /> % Requirements for Provider Independent Resource Holders insert: <br />
% in the RIPE delete: <br /> % NCC Service Region". (Yes/No)
insert: <br />
confirmation:
insert: <br />
%
% Which IXP will use the requested address space?
% Please include the IXP's membership policy. insert: <br />
insert: <br />
org-description:

delete: <br /> #[OVERVIEW OF THE USER]# delete: <br /> #[USER TEMPLATE]# insert: <br />
%
% Who is the contact person for this IXP?
Name: delete: <br /> Organisation: delete: <br /> Country: delete: <br /> Phone: delete: <br /> E-mail: delete: <br /> delete: <br /> delete: <br /> #[EXISTING insert: <br />
name: insert: <br />
organisation: insert: <br />
country: insert: <br />
phone: insert: <br />
fax-no: insert: <br />
e-mail: insert: <br />
insert: <br />
#[MEMBER PEERING INFORMATION TEMPLATE]# insert: <br />
% insert: <br />
% If the IXP has an online list of members, please add the URL below. insert: <br />
insert: <br />
member-peering-list: insert: <br />
insert: <br />
% If you will include this list as an attachment, please enter "Yes" insert: <br />
% below. insert: <br />
insert: <br />
member-peering-attached: insert: <br />
insert: <br />
% Please add the contact details for three of these members. insert: <br />
insert: <br />
organisation-1: insert: <br />
as-number-1: insert: <br />
e-mail-1: insert: <br />
insert: <br />
organisation-2: insert: <br />
as-number-2: insert: <br />
e-mail-2: insert: <br />
insert: <br />
organisation-3: insert: <br />
as-number-3: insert: <br />
e-mail-3: insert: <br />
insert: <br />
% If possible, please add the URL of a looking glass where we can verify insert: <br />
% this information: insert: <br />
insert: <br />
looking-glass: insert: <br />
insert: <br />
#[CURRENT ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % If the IXP has any IPv4 ranges(s) for their peering LAN, list them delete: <br /> % below. If any such space is being returned, then the return date delete: <br /> % should be specified. delete: <br /> subnet-ipv4: delete: <br /> USAGE TEMPLATE]# insert: <br />
%
% If the IXP has any IPv6 assignments, please list them below.
subnet-ipv6: delete: <br /> delete: <br /> delete: <br /> delete: <br /> % The next two sections (IPv4 and IPv6) will give us an overview of delete: <br /> % the detailed usage of the resources. Please fill in only the delete: <br /> % relevant section as per the resource being requested and remove the delete: <br /> % section that is not applicable. delete: <br /> delete: <br /> delete: <br /> #[IPv4 ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % How insert: <br />
subnet: insert: <br />
subnet: insert: <br />
insert: <br />
#[ADDRESSING PLAN]# insert: <br />
% insert: <br />
% When will the IXP use the requested IPv4 address space? delete: <br /> % delete: <br /> % ADDRESSING PLAN delete: <br /> % delete: <br /> % Subnet Immediate Intermediate Entire Purpose delete: <br /> % size (/nn) Requirement Requirement Period delete: <br /> subnet: delete: <br /> delete: <br /> totals: delete: <br /> number-of-subnets: delete: <br /> delete: <br /> #[IPv6 ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % How will the IXP use the requested IPv6 address space? delete: <br /> % delete: <br /> % ADDRESSING PLAN
%
% Subnet Within Within Within Purpose
% size (/nn) 3 months 1 year 2 years Purpose insert: <br />
insert: <br />
subnet:
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 delete: <br /> % supporting documentation. If the IXP has an online list of members, delete: <br /> % please add the URL below. delete: <br /> delete: <br /> <add more information> insert: <br />
insert: <br />



#[SUPPORTING DOCUMENTATION]#
%
% If this request is being sent by a sponsoring LIR on behalf of insert: <br />
% an delete: <br /> % End User, please User,please attach a copy of the signed insert: <br />
% "End User Assignment delete: <br /> % Agreement" and the company registration papers insert: <br />
% of the End User.
% You can also attach a network diagram or other supporting documentation. insert: <br />
%
% Have you attached any files/documents to this request? (Yes/No)
insert: <br />
file-attached:


#[IPv4 DATABASE TEMPLATE]# delete: <br /> delete: <br /> % If you are requesting IPv4, #[DATABASE TEMPLATE(S)]# insert: <br />
% insert: <br />
% Please complete this IPv4 database template. delete: <br /> % If you are not requesting IPv4, please remove this IPv4 database delete: <br /> % template. delete: <br /> delete: <br /> inetnum: all of the fields below. insert: <br />
insert: <br />
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>
notify: <add email address> insert: <br />
changed: hostmaster@ripe.net
source: RIPE


#[IPv6 DATABASE TEMPLATE]# delete: <br /> delete: <br /> % If you are requesting IPv6, complete this IPv6 database template. delete: <br /> % If you are not requesting IPv6, please remove this IPv6 database delete: <br /> % template. delete: <br /> delete: <br /> inet6num: <leave empty> delete: <br /> netname: <add netname> delete: <br /> descr: <add IXP organisation name> delete: <br /> country: <add country code> delete: <br /> org: <add org-ID> delete: <br /> admin-c: <add nic-hdl of administrative contact> delete: <br /> tech-c: <add nic-hdl of technical contact> delete: <br /> status: ASSIGNED PI delete: <br /> mnt-by: RIPE-NCC-END-MNT delete: <br /> mnt-lower: RIPE-NCC-END-MNT delete: <br /> mnt-by: <add mntner name> delete: <br /> mnt-routes: <add mntner name> delete: <br /> mnt-domains: <add mntner name> delete: <br /> changed: hostmaster@ripe.net delete: <br /> source: RIPE delete: <br /> delete: <br /> #[END of REQUEST]# delete: <br />

IPv6 Internet Exchange Point Points Assignment Request Form
RIPE Documents Search