- Legend
- Added
- Deleted
This document contains instructions for LIRs on how to complete the “IPv6 Internet Exchange Points Assignment Request Form Link: https://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html ”. "Internet Exchange Point Assignment Request Form".
The instructions are based on the “ following policy documents:
- General Information Link: #general
- Requester Template Link: #requester
- Overview of Organisation Template Link: #overview
- User Template Link: #user
- Member Peering Information Template Link: #peering
- Current Address Space Usage Template Link: #current
- Addressing Plan Link: #plan
- Supplemental Comments Link: #comments
- Supporting Documentation Link: #documentation
- Database Template(s) Link: #database
- End of Request Link: #end
General Information
#[GENERAL INFORMATION]#
%
% Please add your RegID.
request-type: ipv6-for-ixp
form-version: 1.2ixp-assign
form-version: 1.0
x-ncc-regid: nl.bluelight
Please do not change the value of the “request-type:” and “form-version:” "request-type:" and "form-version:" fields.
Enter your Registry Identifier (RegID) in the “x-ncc-regid:” "x-ncc-regid:" field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact <[email protected]>.
Requester Template
#[REQUESTER TEMPLATE]#
%
% Please add your contact details.
name: John Smith
phone: +123 45 678910
fax-no: +123 45 678911
email: [email protected]
nic-hdl: HOHO1-RIPE
Enter your contact details in the requester template. You must be a registered contact for the LIR. The LIR Portal Link: https://lirportal.ripe.net/ contains a list of registered contacts for your LIR.
Please use the international dialling codes (for example, +31 for the Netherlands,) in the “phone:” and “fax-no:” fields.
Enter your NIC handle, if you have one, in the “nic-hdl:” field.
Overview of Organisation Template#[OVERVIEW OF ORGANISATION TEMPLATE]#
%
%
% Is this request being sent by a sponsoring LIR on behalf of an
% End
%
end-user-of-sponsoring-lir: Yes
% If yes, please confirm that the "End User Assignment Agreement"
% contains all of the elements listed in paragraph 2.0 of
% "Contractual
%
% in the RIPE
%
confirmation: Yes
%
% Which IXP will use the requested address space?
% Please include the IXP's membership policy.
org-description: Ruritania IXP. The joining requirements are online at
http://www.rurixp.ripe.net/join_us.htmlIf this request is sent for an End User of a sponsoring LIR,
org-description: Ruritania IXP LtdIf you are an LIR sending this request on behalf of an End User,"Yes" in the "end-user-of-sponsoring-lir" field.
If you answered 'Yes' "Yes" you should also confirm that all of the elements of paragraph 2.0 of “Contractual "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region Link: /publications/docs/ripe-452/ ” Region" are listed in the 'End User Assignment Agreement' “End User Assignment Agreement” that is signed by the End User and the sponsoring LIR. PI assignments can only be made to End Users if there is a signed 'End User Assignment Agreement' between the sponsoring LIR and For all assignments that are requested through a sponsoring LIR for an End User, we need to receive a copy of the "End User Assignment Agreement" and the company registration papers of the End User.
You can find an example agreement at at http://www.ripe.net/ripe/docs/lir-end-user-agreement.html Link: /manage-ips-and-asns/resource-management/number-resources/independent-resources/independent-assignment-request-and-maintenance-agreement/ . at:
https://www.ripe.net/lir-services/resource-management/direct-assignments/independent-assignment-request-and-maintenance-agreement Link: /manage-ips-and-asns/resource-management/number-resources/independent-resources/independent-assignment-request-and-maintenance-agreement/
You can send us an agreement in your local language or use the English version.
If this request is sent by a Direct Assignment User, you answer 'No' "No" to the above two questions. Direct Assignment Users have already signed an 'End User Assignment Agreement' "End User Assignment Agreement" with the RIPE NCC. If the request is for an LIR, you should also answer with
'No'.In the “org-description:” "No".In the “org-description:”
organisation operating as an Internet Exchange Point (IXP). Please include references which show that the organisation operates as an IXP and that the requirements to join the IXP are open and clear. You can add a URL or attach a document which contains this information.User Template
#[USER TEMPLATE]#
%IXP requesting the assignment(s).
Overview of the User#[OVERVIEW OF THE USER]#
% Who is the contact person for this IXP?
name: Fred Bloggs
organisation: Ruritania IXP
country: NN
phone:+123 45 678910
Name: Fred Bloggs
Organisation: Ruritania IXP
Country: NN
Phone:
fax-no: +123 45 678911
email:[email protected]
Email:
Enter the legal name and primary location of the organisation in the “organisation:” and “country:” “organisation:” and “country:” fields.
Please use international dialling dialing codes (for example, +31 for the Netherlands,) in the
“phone:” and “fax-no:” fields.
Member Peering Information Template
#[MEMBER PEERING INFORMATION TEMPLATE]#
%
% If the IXP has an online list of members, please add the
% URL below.
member-peering-list: http://www.rurixp.ripe.net/members.html
% If you will include this list as an attachment, please
% enter "Yes" below.
member-peering-attached:
% Please add the contact details for three of these members.
organisation-1: Bluelight B.V.
as-number-1: AS65444
e-mail-1: [email protected]
organisation-2: Bank of Ruritania Inc.
as-number-2: AS65333
e-mail-2: [email protected]
organisation-3: Ruritania Telecom
as-number-3: AS65222
e-mail-3: [email protected]
% If possible, please add the URL of a looking glass where
% we can verify this information:
looking-glass: http://www.rurixp.ripe.net/looking-glass.cgi
You must provide a list of the IXP's members. If this list is online, please add the URL of the IXP's website in the “member-peering-list:” field. If you attach the list to your request, enter ‘yes' in the “member-peering-attached:” field.
Enter the organisation name, Autonomous System (AS) number and the contact e-mail address for three of the IXPs members.
If possible, add the URL of a looking glass in the "looking glass:" field so we can verify this information.
CurrentTemplate#[CURRENT ADDRESS SPACE USAGE TEMPLATE]#
%
% 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: 192.0.2.0/24 to nl.bluelight in 1 month.
% If the IXP has any IPv6 assignments, please list them below.
subnet: none
subnet-ipv6: None
Please specify address prefixes using slash notation (for example, y:y:y::/yy). You can repeat the “subnet:” “subnet-ipv4 or subnet-ipv6:” field as many times as needed.
Addressing Plan
#[ADDRESSING PLAN]#
%
% When
If there is any address space assigned that they will be returned, list each prefix in separate "address-space-returned" fields. The maximum renumbering is 180 days. You can use the following syntax: <x.x.x.x/xx> in <time period> for this field.
IPv4 Address Space Usage#[IPv4 ADDRESS SPACE USAGE]#will the IXP use the requested
% HowIPv4address space?
%ADDRESSING PLAN
% Subnet Immediate Intermediate Entire Purpose
% size (/nn) Requirement Requirement Period
subnet: /27 16 24 32 Network Infrastructure
subnet: /24,/26 272 296 320 Members connections
totals: /24,/26,/27 /24,/27 /24,/26 /24,/26,/27
number-of-subnets:2
The addressing plan shows how the End User will use the requested address space.
You can repeat the "subnet" row as many times as needed. Delete any empty "subnet" fields before you send the request.
In the "Subnet size (/nn)" column, enter a slash notation prefix for each subnet. Each entry should be large enough to contain the number of addresses needed for that subnet over the next time period.
In order to demonstrate the predicted growth of your network, you must provide an estimate of the address space you will require over three distinct periods: Immediate, Intermediate and the Entire period. These columns can either contain numbers (for example, 256) or slash notation prefixes (for example, /24).
In the "Purpose" column, write a short description of each subnet. If needed, you can write a more detailed description in the "Supplemental Comments" section at the end of this form.
In the "totals" row, add the totals of each column. The total of the "Subnet size (/nn)" column should be the total amount of address space you are requesting for this assignment.
In the "number-of-subnets" field, enter the total number of subnets listed in the addressing plan.
IPv6 Address Space Usage#[IPv6 ADDRESS SPACE USAGE]#
% How will the IXP use the requested IPv6 address space?
% ADDRESSING PLAN
% Subnet Within Within WithinPurpose
% size (/nn) 3 months 1 year 2 years Purpose
subnet: /64 x - - *see supplemental
subnet: /64Network Infrastructurex - - comments section
subnet: /55Members connections*
The addressing plan shows when the IXP plans to use the address space.
Enter the size of each subnet in the “Subnet size (/nn)” “Subnet size (/nn)” column. Please specify the size using IPv6 slash notation (for example, /48). You can repeat the “subnet:” “subnet:” field as many times as needed.
In the “Purpose” “Purpose” column, write a short description for each subnet. If needed, you can write a more detailed description in the “Insert Supplemental Comments” “Insert Supplemental Comments” section at the end of the form.
Complete the remaining columns with a cross (x) or a dash (-). For example, if you will use a subnet within three months, enter a cross in the “Within 3 months” “Within 3 months” column and a dash in both the “Within 1 year” and “Within 2 years” “Within 1 year” and “Within 2 years” columns.
Supplemental Comments
#[SUPPLEMENTAL COMMENTS]#
%
% Please add more information if you think it will help
% us understand this request.
We will have 2 separate subnets. One for our 30 banking members who
require secure transactions, and one for our 200 regular ISP
members. Each member will use a /128.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.
Ruritania IXP has 62 IXP members, and add approximately six new members every month. Each member's connection requires one /30.
The IXP network consists of three routers (three IPs), three switches (three IPs) and two firewalls (eight IPs). Two more routers and switches will be added next month.
We would like to return the current /24 used for our peering LAN and receive one /23 IXP assignment to renumber current members and connect new members.The joining requirements are online at: http://www.rurixp.ripe.net/join_us.html Link: http://www.rurixp.ripe.net/join_us.html
You can use this space for additional information that you think will be helpful for us when we evaluate your request.
A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs.
Supporting Documentation
#[SUPPORTING DOCUMENTATION]#
%
% If this request is being sent by a sponsoring LIR on behalf of
% ananEnd User, please attach a copy of the signed
%
% "End User AssignmentAgreement" and the company registration papers
%
% of the End User.
% You can also attach a network diagram or other supporting documentation.
%
% Have you attached any files/documents to this request? (Yes/No)
file-attached: Yes
For each IPv6 IXP assignment that is requested through a sponsoring LIR for an End User, IXP, we need to receive a copy of 'End User Assignment Agreement' “End User Assignment Agreement” and the company registration papers of the End User.
If this request is for an LIR or a “Direct Assignment User”, “Direct Assignment User”, you do not have to attach a copy of 'End User Assignment Agreement' “End User Assignment Agreement” and company registration papers.
A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs.
Database Template(s)
#[DATABASE TEMPLATE(S)]#inet6num:
%
% Please complete all of the fields below.
Database Templates#[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: RURIXP
descr: Ruritania IXPLtd
country: NL
org: ORG-Bb2-RIPE
admin-c: HOHO1-RIPE
tech-c: HOHO1-RIPE
status: ASSIGNEDHOHO15-RIPE
tech-c: HOHO15-RIPE
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-lower: RIPE-NCC-END-MNT
mnt-by: SANTA-MNT
mnt-domains: SANTA-MNT
mnt-routes: SANTA-MNT
changed: [email protected]
source: RIPE
Leave the “inet6num:” field
#[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: RURIXP
descr: Ruritania IXP Ltd
country: NL
org: ORG-Bb2-RIPE
admin-c: HOHO15-RIPE
tech-c: HOHO15-RIPE
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-lower: RIPE-NCC-END-MNT
mnt-by: SANTA-MNT
mnt-domains: SANTA-MNT
mnt-routes: SANTA-MNT
changed: [email protected]
source: RIPE
If the IXP is requesting IPv4 and IPv6, please complete all templates. If not, you should complete the relevant template(s) and delete the rest when sending the request.
(the RIPE NCC) will complete it.The “netname:” will choose the address range.The “netname:”
Enter the legal name of the organisation operating the IXP in the “descr:” “descr:” field.
Enter the ISO country code of the organisation in the “country:” “country:” field.
Enter the org-ID of the organisation object in the “org:” “org:” field. You can create organisation objects using 'webupdates'.
Person and role objects contain information about people. Each object has a unique NIC handle (nic-hdl). You can create person and role objects using webupdates.
The nic-hdl of the role or person object entered in the “admin-c:” “admin-c:” field should be for someone who has administrative responsibilities for the network.
The nic-hdl of the role or person object entered in the “tech-c:” “tech-c:” field should be for someone who has technical knowledge of the network.
The “status:” “status:” field must be ASSIGNED . PI.
Maintainers protect objects in the RIPE Whois Database. They contain the information needed to authorise creation, deletion or modification of these objects. You can create maintainers using the 'Maintainer Editor' (https://lirportal.ripe.net Link: https://lirportal.ripe.net “Maintainer Editor” (https://lirportal.ripe.net Link: https://lirportal.ripe.net/ ).
One of the “mnt-by:” “mnt-by:” fields must be RIPE-NCC-END-MNT. RIPE-NCC-END-MNT. Enter the IXP's maintainer in the other “mnt-by:” “mnt-by:” field. The IXP will be able to update the inet6num inetnum/inet6num object using webupdates.
The “mnt-lower:” “mnt-lower:” field must be
RIPE-NCC-END-MNT.The “mnt-domains:” RIPE-NCC-END-MNT.The “mnt-domains:”
The “mnt-routes:” “mnt-routes:” field shows which maintainer authorises the creation of route6 route/route6 objects for the assignment.
All of the objects that you enter in the template must already exist in the RIPE
Whois Database.The “changed:” Database.The “changed:”
[email protected].The “source:” [email protected] “source:”
End of Request
#[END of REQUEST]#
Best Regards,
John Smith,
Best Regards,Jan Janssen,Bluelight Admin
Please write your full name below the “#[END of REQUEST]# ” header. "#[END of REQUEST]#" header.