Changes to IPv6 Internet Exchange Points Assignment Request Form
Legend | (+) Added | (-) Deleted |
---|---|---|
Changed | Tag Added | Tag Deleted |
insert: <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 insert: <a class="external-link" href="https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" title=""> here insert: </a> . insert: </strong> insert: </p>
insert: <p>To request resources from the RIPE NCC, members should now use the request forms in the insert: <a class="external-link" href="https://lirportal.ripe.net/" target="_self" title=""> LIR Portal insert: </a> . insert: </p>
insert: <p>The insert: <a class="external-link" href="https://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self" title=""> Resource Request API insert: </a> and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms. insert: </p>
insert: <p>insert: </p>
% IPv6 Internet Exchange Points Point Assignment Request Form delete: <br />
% RIPE NCC members (LIRs) and Direct Assignment Users can use this insert: <br />
% form delete: <br /> % to request an IPv6 IPv4/IPv6 Assignment for an Internet Exchange insert: <br />
% Point (IXP). delete: <br /> % Please see ripe-461 insert: <a data-val="6c9f9e3b-3b03-45e7-a758-311bc9237f97" href="resolveuid/6c9f9e3b-3b03-45e7-a758-311bc9237f97" data-linktype="internal" class="internal-link"> ripe-576 insert: </a> for instructions on how to insert: <br />
% complete this form.
%
% Please note that the End User should have a signed "End User
% Assignment Agreement" with either the sponsoring LIR insert: <br />
% or the RIPE NCC.
#[GENERAL INFORMATION]#
% insert: <br />
request-type: ixp-assign insert: <br />
form-version: 1.0 insert: <br />
% Please add your RegID.
delete: <br /> request-type: ipv6-for-ixp delete: <br /> form-version: 1.2 delete: <br /> x-ncc-regid:
delete: <br /> #[REQUESTER TEMPLATE]# delete: <br /> % delete: <br /> % Please add your contact details. delete: <br /> delete: <br /> name: delete: <br /> phone: delete: <br /> fax-no: delete: <br /> e-mail: delete: <br /> nic-hdl:
#[OVERVIEW OF ORGANISATION TEMPLATE]# ORGANISATION]#
% Is this request being sent by a sponsoring LIR on behalf of an delete: <br /> % End insert: <br />
% User? (Yes/No) delete: <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 delete: <br /> % "Contractual insert: <br />
% Requirements for Provider Independent Resource Holders delete: <br /> % in the RIPE insert: <br />
% NCC Service Region". (Yes/No)
delete: <br /> confirmation:
delete: <br /> %
% Which IXP will use the requested address space?
% Please include the IXP's membership policy. delete: <br /> delete: <br /> org-description:
#[USER TEMPLATE]# delete: <br /> % insert: <br />
#[OVERVIEW OF THE USER]# insert: <br />
% Who is the contact person for this IXP?
delete: <br /> name: delete: <br /> organisation: delete: <br /> country: delete: <br /> phone: delete: <br /> fax-no: delete: <br /> e-mail: delete: <br /> delete: <br /> #[MEMBER PEERING INFORMATION TEMPLATE]# delete: <br /> % Name: insert: <br />
Organisation: insert: <br />
Country: insert: <br />
Phone: insert: <br />
E-mail: insert: <br />
insert: <br />
insert: <br />
#[EXISTING ADDRESS SPACE USAGE]# insert: <br />
% If the IXP has an online any IPv4 ranges(s) for their peering LAN, list of members, please add the URL them insert: <br />
% below. delete: <br /> delete: <br /> member-peering-list: delete: <br /> delete: <br /> % If you will include this list as an attachment, please enter "Yes" delete: <br /> % below. delete: <br /> delete: <br /> member-peering-attached: delete: <br /> delete: <br /> % Please add the contact details for three of these members. delete: <br /> delete: <br /> organisation-1: delete: <br /> as-number-1: delete: <br /> e-mail-1: delete: <br /> delete: <br /> organisation-2: delete: <br /> as-number-2: delete: <br /> e-mail-2: delete: <br /> delete: <br /> organisation-3: delete: <br /> as-number-3: delete: <br /> e-mail-3: delete: <br /> delete: <br /> % If possible, please add the URL of a looking glass where we can verify delete: <br /> % this information: delete: <br /> delete: <br /> looking-glass: delete: <br /> delete: <br /> #[CURRENT ADDRESS SPACE USAGE TEMPLATE]# delete: <br /> % If any such space is being returned, then the return date insert: <br />
% should be specified. insert: <br />
subnet-ipv4: insert: <br />
% If the IXP has any IPv6 assignments, please list them below.
delete: <br /> subnet: delete: <br /> subnet: delete: <br /> delete: <br /> #[ADDRESSING PLAN]# delete: <br /> % delete: <br /> % When subnet-ipv6: insert: <br />
insert: <br />
insert: <br />
insert: <br />
% The next two sections (IPv4 and IPv6) will give us an overview of insert: <br />
% the detailed usage of the resources. Please fill in only the insert: <br />
% relevant section as per the resource being requested and remove the insert: <br />
% section that is not applicable. insert: <br />
insert: <br />
insert: <br />
#[IPv4 ADDRESS SPACE USAGE]# insert: <br />
insert: <br />
% How will the IXP use the requested IPv4 address space? insert: <br />
% insert: <br />
% ADDRESSING PLAN insert: <br />
% insert: <br />
% Subnet Immediate Intermediate Entire Purpose insert: <br />
% size (/nn) Requirement Requirement Period insert: <br />
subnet: insert: <br />
insert: <br />
totals: insert: <br />
number-of-subnets: insert: <br />
insert: <br />
#[IPv6 ADDRESS SPACE USAGE]# insert: <br />
insert: <br />
% How will the IXP use the requested IPv6 address space? insert: <br />
% insert: <br />
% ADDRESSING PLAN
%
% Subnet Within Within Within Purpose
% size (/nn) 3 months 1 year 2 years Purpose delete: <br /> delete: <br /> subnet:
subnet:
#[SUPPLEMENTAL COMMENTS]#
%
% Please add more information if you think it will help us understand
% this request. delete: <br /> delete: <br /> You can attach a network diagram or other relevant insert: <br />
% supporting documentation. If the IXP has an online list of members, insert: <br />
% please add the URL below. insert: <br />
insert: <br />
<add more information>
#[SUPPORTING DOCUMENTATION]#
%
% If this request is being sent by a sponsoring LIR on behalf of delete: <br /> % an insert: <br />
% End User,please User, please attach a copy of the signed delete: <br /> % "End User Assignment insert: <br />
% Agreement" and the company registration papers delete: <br /> % of the End User.
% You can also attach a network diagram or other supporting documentation. delete: <br /> %
% Have you attached any files/documents to this request? (Yes/No)
delete: <br /> file-attached:
#[DATABASE TEMPLATE(S)]# delete: <br /> % delete: <br /> % Please #[IPv4 DATABASE TEMPLATE]# insert: <br />
insert: <br />
% If you are requesting IPv4, complete all of the fields below. this IPv4 database template. insert: <br />
% If you are not requesting IPv4, please remove this IPv4 database insert: <br />
% template. insert: <br />
insert: <br />
inetnum: <leave empty> insert: <br />
netname: <add netname> insert: <br />
descr: <add IXP organisation name> insert: <br />
country: <add country code> insert: <br />
org: <add org-ID> insert: <br />
admin-c: <add nic-hdl of administrative contact> insert: <br />
tech-c: <add nic-hdl of technical contact> insert: <br />
status: ASSIGNED PI insert: <br />
mnt-by: RIPE-NCC-END-MNT insert: <br />
mnt-lower: RIPE-NCC-END-MNT insert: <br />
mnt-by: <add mntner name> insert: <br />
mnt-routes: <add mntner name> insert: <br />
mnt-domains: <add mntner name> insert: <br />
changed: [email protected] insert: <br />
source: RIPE insert: <br />
insert: <br />
insert: <br />
#[IPv6 DATABASE TEMPLATE]# insert: <br />
insert: <br />
% If you are requesting IPv6, complete this IPv6 database template. insert: <br />
% If you are not requesting IPv6, please remove this IPv6 database insert: <br />
% 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>
notify: <add email address> delete: <br /> changed: [email protected]
source: RIPE
delete: <br /> #[END of REQUEST]# insert: <br />