You are here: Home > Publications > RIPE Document Store > Internet Exchange Point Request Supporting Notes

Changes to Internet Exchange Point Request Supporting Notes

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-565: This document contains instructions for LIRs on how to complete the "Internet ripe-372: Supporting Notes For The IPv6 Internet Exchange Point Points Assignment Request Form". Form

This document contains instructions for LIRs on how to complete the "Internet Exchange Point Assignment Request Form". delete: </p> delete: <p> The instructions are based on the following policy documents: delete: </p> delete: <ol> delete: <li> delete: <a href="http://www.ripe.net/ripe/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region delete: </a> delete: </li> delete: <li> delete: <a href="http://www.ripe.net/ripe/docs/ripe-523"> IPv6 Address Allocation and Assignment Policy delete: </a> delete: </li> delete: <li> delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> delete: </li> delete: </ol> delete: <h2> General Information delete: </h2> delete: <pre class="pre"> #[GENERAL INFORMATION]# delete: <br /> delete: <br /> % Please add your RegID. delete: <br /> request-type: ixp-assign delete: <br /> form-version: 1.0 delete: <br /> x-ncc-regid: delete: <b> nl.bluelight delete: </b> delete: </pre> delete: <p> Please do not change the value of the "request-type:" and "form-version:" fields. delete: </p> delete: <p> Enter your Registry Identifier (RegID) in the "x-ncc-regid:" field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> . delete: </p> delete: <p> delete: </p> delete: <h3> delete: <b> Overview of Organisation delete: </b> delete: </h3> delete: <pre> #[OVERVIEW OF ORGANISATION]# delete: <br /> delete: <br /> % Is this request being sent by a sponsoring LIR on behalf of an End delete: <br /> % User? (Yes/No) delete: <br /> end-user-of-sponsoring-lir: delete: <b> Yes delete: </b> delete: <br /> % If yes, please confirm that the "End User Assignment Agreement" delete: <br /> % contains all of the elements listed in paragraph 2.0 of "Contractual delete: <br /> % Requirements for Provider Independent Resource Holders in the RIPE delete: <br /> % NCC Service Region". (Yes/No) delete: <br /> confirmation: delete: <b> Yes delete: </b> delete: <br /> % Which IXP will use the requested address space? delete: <br /> org-description: delete: <b> Ruritania IXP Ltd delete: </b> delete: </pre> delete: <p class="PreformattedText"> delete: <br /> If you are an LIR sending this request on behalf of an End User, you should answer "Yes" in the "end-user-of-sponsoring-lir" field. delete: <br /> delete: <br /> If you answered "Yes" you should also confirm that all of the elements of paragraph 2.0 of "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" are listed in the “End User Assignment Agreement” that is signed by the End User and the sponsoring LIR. delete: </p> delete: <p class="PreformattedText"> delete: </p> delete: <p class="PreformattedText"> 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. delete: <br /> delete: <br /> You can find an example agreement at: delete: <br /> delete: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> https://www.ripe.net/lir-services/resource-management/direct-assignments/independent-assignment-request-and-maintenance-agreement delete: </a> delete: <br /> delete: <br /> You can send us an agreement in your local language or use the English version. delete: <br /> delete: <br /> If this request is sent by a Direct Assignment User, you answer "No" to the above two questions. Direct Assignment Users have already signed an "End User Assignment Agreement" with the RIPE NCC. If the request is for an LIR, you should also answer with "No". delete: </p> delete: <p class="PreformattedText"> delete: </p> delete: <p class="PreformattedText"> In the “org-description:” field, write a short description of the IXP requesting the assignment(s). delete: </p> delete: <p class="PreformattedText"> delete: </p> delete: <h3> delete: <b> Overview of the User delete: </b> delete: </h3> delete: <pre class="mceContentBody documentContent"> #[OVERVIEW OF THE USER]# delete: <br /> delete: <br /> % Who is the contact person for this IXP? delete: <br /> Name: delete: <b> Fred Bloggs delete: </b> delete: <br /> Organisation: delete: <b> Ruritania IXP delete: </b> delete: <br /> Country: delete: <b> NN delete: </b> delete: <br /> Phone: delete: <b> +123 45 678910 delete: </b> delete: <br /> Email: delete: <b> fred@rurixp.ripe.net delete: </b> delete: </pre> delete: <p> Enter the legal name and primary location of the organisation in the “organisation:” and “country:” fields. delete: </p> delete: <p> Please use international dialing codes (for example, +31 for the Netherlands,) in the “phone:”field. delete: </p> delete: <p> delete: </p> delete: <h3> delete: <b> Existing Address Space Usage delete: </b> delete: </h3> delete: <pre> #[EXISTING 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: <b> 192.0.2.0/24 to nl.bluelight in 1 month. delete: </b> delete: <br /> % If the IXP has any IPv6 assignments, list them below. delete: <br /> subnet-ipv6: delete: <b> None delete: </b> delete: </pre> delete: <p> Please specify address prefixes using slash notation (for example, y:y:y::/yy). You can repeat the “subnet-ipv4 or subnet-ipv6:” field as many times as needed. delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: </p> delete: <h3> delete: <b> IPv4 Address Space Usage delete: </b> delete: </h3> delete: <pre> #[IPv4 ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % How will the IXP use the requested IPv4 address space? delete: <br /> % ADDRESSING PLAN delete: <br /> % Subnet Immediate Intermediate Entire Purpose delete: <br /> % size (/nn) Requirement Requirement Period delete: <br /> subnet delete: <b> : /27 16 24 32 Network Infrastructure delete: <br /> delete: </b> subnet delete: <b> : /24,/26 272 296 320 Members connections delete: <br /> delete: </b> delete: <br /> totals delete: <b> : /24,/26,/27 /24,/27 /24,/26 /24,/26,/27 delete: </b> delete: <br /> number-of-subnets: delete: <b> 2 delete: </b> delete: </pre> delete: <p> The addressing plan shows how the End User will use the requested address space. delete: </p> delete: <p> You can repeat the "subnet" row as many times as needed. Delete any empty "subnet" fields before you send the request. delete: </p> delete: <p> 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. delete: </p> delete: <p> 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). delete: </p> delete: <p> 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. delete: </p> delete: <p> 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. delete: <br /> delete: <br /> In the "number-of-subnets" field, enter the total number of subnets listed in the addressing plan. delete: </p> delete: <p> delete: </p> delete: <h3> delete: <b> IPv6 Address Space Usage delete: </b> delete: </h3> delete: <pre class="mceContentBody documentContent"> #[IPv6 ADDRESS SPACE USAGE]# delete: <br /> delete: <br /> % How will the IXP use the requested IPv6 address space? delete: <br /> % ADDRESSING PLAN delete: <br /> % Subnet Within Within Within Purpose delete: <br /> % size (/nn) 3 months 1 year 2 years delete: <b> delete: <br /> subnet: /64 x - - Network Infrastructure delete: <br /> subnet: /55 x - - Members connections* delete: </b> delete: </pre> delete: <p class="PreformattedText"> delete: </p> delete: <p> The addressing plan shows when the IXP plans to use the address space. delete: </p> delete: <p> Enter the size of each subnet in the “Subnet size (/nn)” column. Please specify the size using IPv6 slash notation (for example, /48). You can repeat the “subnet:” field as many times as needed. delete: </p> delete: <p> In the “Purpose” column, write a short description for each subnet. If needed, you can write a more detailed description in the “Insert Supplemental Comments” section at the end of the form. delete: </p> delete: <p> 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” column and a dash in both the “Within 1 year” and “Within 2 years” columns. delete: </p> delete: <p> delete: </p> delete: <h3> delete: <b> Supplemental Comments delete: </b> delete: </h3> delete: <pre> #[SUPPLEMENTAL COMMENTS]# delete: <br /> delete: <br /> % Please add more information if you think it will help us understand delete: <br /> % 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: </pre> delete: <p class="PreformattedText"> delete: <b> Ruritania IXP has 62 IXP members, and add approximately six new members every month. Each member's connection requires one /30. delete: <br /> 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. delete: <br /> 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. delete: </b> delete: </p> delete: <pre> delete: <b> The joining requirements are online at: delete: </b> delete: <a href="http://www.rurixp.ripe.net/join_us.html"> http://www.rurixp.ripe.net/join_us.html delete: </a> delete: </pre> delete: <p class="PreformattedText"> delete: </p> delete: <p> You can use this space for additional information that you think will be helpful for us when we evaluate your request. delete: </p> delete: <p> A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. delete: </p> delete: <p> delete: </p> delete: <h3> delete: <b> Supporting Documentation delete: </b> delete: </h3> delete: <pre> #[SUPPORTING DOCUMENTATION]# delete: <br /> delete: <br /> % If this request is being sent by a sponsoring LIR on behalf of an delete: <br /> % End User, please attach a copy of the signed "End User Assignment delete: <br /> % Agreement" and the company registration papers of the End User. delete: <br /> delete: <br /> % Have you attached any files/documents to this request? (Yes/No) delete: <br /> file-attached: delete: <b> Yes delete: </b> delete: </pre> delete: <p> For each assignment that is requested through a sponsoring LIR for an IXP, we need to receive a copy of “End User Assignment Agreement” and the company registration papers of the End User. delete: </p> delete: <p> If this request is for an LIR or a “Direct Assignment User”, you do not have to attach a copy of “End User Assignment Agreement” and company registration papers. delete: </p> delete: <h3> delete: </h3> delete: <h3> delete: <b> Database Templates delete: </b> delete: </h3> delete: <pre class="mceContentBody documentContent"> #[IPv4 DATABASE TEMPLATE]# delete: <br /> delete: <br /> % If you are requesting IPv4, 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: <leave empty> delete: <b> delete: <br /> delete: </b> netname: delete: <b> RURIXP delete: </b> delete: <br /> descr: delete: <b> Ruritania IXP Ltd delete: </b> delete: <br /> country: delete: <b> NL delete: </b> delete: <br /> org: delete: <b> ORG-Bb2-RIPE delete: </b> delete: <br /> admin-c: delete: <b> HOHO15-RIPE delete: </b> delete: <br /> tech-c: delete: <b> HOHO15-RIPE delete: </b> 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: delete: <b> SANTA-MNT delete: </b> delete: <br /> mnt-domains: delete: <b> SANTA-MNT delete: </b> delete: <br /> mnt-routes: delete: <b> SANTA-MNT delete: </b> delete: <br /> changed: hostmaster@ripe.net delete: <br /> source: RIPE delete: <br /> delete: <br /> #[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: delete: <b> RURIXP delete: </b> delete: <br /> descr: delete: <b> Ruritania IXP Ltd delete: </b> delete: <br /> country: delete: <b> NL delete: </b> delete: <br /> org: delete: <b> ORG-Bb2-RIPE delete: </b> delete: <br /> admin-c: delete: <b> HOHO15-RIPE delete: </b> delete: <br /> tech-c: delete: <b> HOHO15-RIPE delete: </b> 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: delete: <b> SANTA-MNT delete: </b> delete: <br /> mnt-domains: delete: <b> SANTA-MNT delete: </b> delete: <br /> mnt-routes: delete: <b> SANTA-MNT delete: </b> delete: <br /> changed: hostmaster@ripe.net delete: <br /> source: RIPE delete: </pre> delete: <p class="PreformattedText"> 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. delete: </p> delete: <p> Leave the "inetnum/inet6num" fields empty as we will choose the address range. delete: </p> delete: <p> The “netname:” should be a short, descriptive name for the network and should reflect the name of the organisation operating the IXP. delete: </p> delete: <p> Enter the legal name of the organisation operating the IXP in the “descr:” field. delete: </p> delete: <p> Enter the ISO country code of the organisation in the “country:” field. delete: </p> delete: <p> Enter the org-ID of the delete: <b> organisation delete: </b> object in the “org:” field. You can create delete: <b> organisation delete: </b> objects using 'webupdates'. delete: </p> delete: <p> delete: <b> Person delete: </b> and delete: <b> role delete: </b> objects contain information about people. Each object has a unique NIC handle (nic-hdl). You can create delete: <b> person delete: </b> and delete: <b> role delete: </b> objects using webupdates. delete: </p> delete: <p> The nic-hdl of the delete: <b> role delete: </b> or delete: <b> person delete: </b> object entered in the “admin-c:” field should be for someone who has administrative responsibilities for the network. delete: </p> delete: <p> The nic-hdl of the delete: <b> role delete: </b> or delete: <b> person delete: </b> object entered in the “tech-c:” field should be for someone who has technical knowledge of the network. delete: </p> delete: <p> The “status:” field must be ASSIGNED PI. delete: </p> delete: <p> Maintainers protect objects in the RIPE Database. They contain the information needed to authorise creation, deletion or modification of these objects. You can create maintainers using the “Maintainer Editor” ( delete: <a href="https://lirportal.ripe.net/"> https://lirportal.ripe.net delete: </a> ). delete: </p> delete: <p> One of the “mnt-by:” fields must be RIPE-NCC-END-MNT. Enter the IXP's maintainer in the other “mnt-by:” field. The IXP will be able to update the delete: <b> inetnum/inet6num delete: </b> object using webupdates. delete: </p> delete: <p> The “mnt-lower:” field must be RIPE-NCC-END-MNT. delete: </p> delete: <p> The “mnt-domains:” field shows which maintainer authorises the creation of delete: <b> domain delete: </b> objects for the assignment. delete: </p> delete: <p> The “mnt-routes:” field shows which maintainer authorises the creation of delete: <b> route/route6 delete: </b> objects for the assignment. delete: </p> delete: <p> All of the objects that you enter in the template must already exist in the RIPE Database. delete: </p> delete: <p> The “changed:” field must be hostmaster@ripe.net. delete: </p> delete: <p> The “source:” field must be RIPE. delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> End of Request delete: </b> delete: </p> delete: <p class="PreformattedText"> Best Regards, delete: </p> delete: <p class="PreformattedText"> Jan Janssen, Bluelight Admin delete: </p> delete: <p> Please write your full name below the "#[END of REQUEST]#" header. delete: </p>

Supporting Notes For The IPv6 Internet Exchange Point Points Assignment Request Supporting Notes Form
RIPE Documents Search