You are here: Home > Publications > RIPE Document Store > Supporting Notes for the IPv6 Internet Exchange Points Assignment Request Form

Changes to Supporting Notes for the IPv6 Internet Exchange Points Assignment Request Form

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-461: This document contains instructions for LIRs on how to complete the “IPv6 ripe-372: Supporting Notes For The IPv6 Internet Exchange Points Assignment Request Form”. Form

This document contains instructions for LIRs on how to complete the “ delete: <a class="external-link" href="https://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html" target="_self" title=""> IPv6 Internet Exchange Points Assignment Request Form delete: </a> ”. delete:  delete:  The instructions are based on the “ delete: <a href="https://www.ripe.net/publications/docs/ipv6-policy.html"> IPv6 Address Allocation and Assignment Policy delete: </a> ”. delete:  delete: <hr /> delete: <ul> delete: <li> delete: <a href="#general"> General Information delete: </a> delete: </li> delete: <li> delete: <a href="#requester"> Requester Template delete: </a> delete: </li> delete: <li> delete: <a href="#overview"> Overview of Organisation Template delete: </a> delete: </li> delete: <li> delete: <a href="#user"> User Template delete: </a> delete: </li> delete: <li> delete: <a href="#peering"> Member Peering Information Template delete: </a> delete: </li> delete: <li> delete: <a href="#current"> Current Address Space Usage Template delete: </a> delete: </li> delete: <li> delete: <a href="#plan"> Addressing Plan delete: </a> delete: </li> delete: <li> delete: <a href="#comments"> Supplemental Comments delete: </a> delete: </li> delete: <li> delete: <a href="#documentation"> Supporting Documentation delete: </a> delete: </li> delete: <li> delete: <a href="#database"> Database Template(s) delete: </a> delete: </li> delete: <li> delete: <a href="#end"> End of Request delete: </a> delete: </li> delete: </ul> delete: <hr /> delete:  delete: <a name="general"> delete: </a> delete:  delete: <h2> General Information delete: </h2> delete: <pre> #[GENERAL INFORMATION]# delete:   % delete:   % Please add your RegID. delete:   request-type: ipv6-for-ixp delete:   form-version: 1.2 delete:   x-ncc-regid: delete:  nl.bluelight delete:  delete: </pre> delete:  Please do not change the value of the “ delete: <tt> request-type: delete: </tt> ” and “ delete: <tt> form-version: delete: </tt> ” fields. delete:  delete:  Enter your Registry Identifier (RegID) in the “ delete: <tt> x-ncc-regid: delete: </tt> ” field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact <[email protected]>. delete:  delete:  delete: <a name="requester"> delete: </a> delete:  delete: <h2> Requester Template delete: </h2> delete: <pre> #[REQUESTER TEMPLATE]# delete:   % delete:   % Please add your contact details. delete:   name: delete:  John Smith delete:  delete:   phone: delete:  +123 45 678910 delete:  delete:   fax-no: delete:  +123 45 678911 delete:  delete:   email: delete:  [email protected] delete:  delete:   nic-hdl: delete:  HOHO1-RIPE delete:  delete: </pre> delete:  Enter your contact details in the requester template. You must be a registered contact for the LIR. delete: <a href="https://lirportal.ripe.net/"> The LIR Portal delete: </a> contains a list of registered contacts for your LIR. delete:  delete:  Please use the international dialling codes (for example, +31 for the Netherlands,) in the “ delete: <tt> phone: delete: </tt> ” and “ delete: <tt> fax-no: delete: </tt> ” fields. delete:  delete:  Enter your NIC handle, if you have one, in the “ delete: <tt> nic-hdl: delete: </tt> ” field. delete:  delete:  delete: <a name="overview"> delete: </a> delete:  delete: <h2> Overview of Organisation Template delete: </h2> delete: <pre> #[OVERVIEW OF ORGANISATION TEMPLATE]# delete:   % delete:   % Is this request being sent by a sponsoring LIR on behalf of an delete:   % End User? (Yes/No) delete:   delete:   end-user-of-sponsoring-lir: delete:  Yes delete:  delete:   delete:   % If yes, please confirm that the "End User Assignment Agreement" delete:   % contains all of the elements listed in paragraph 2.0 of delete:   % "Contractual Requirements for Provider Independent Resource Holders delete:   % in the RIPE NCC Service Region". (Yes/No) delete:   delete:   confirmation: delete:  Yes delete:  delete:   delete:   % delete:   % Which IXP will use the requested address space? delete:   % Please include the IXP's membership policy. delete:   delete:   org-description: delete:  Ruritania IXP. The joining requirements are online at delete:  delete:   delete:  http://www.rurixp.ripe.net/join_us.html delete:  delete: </pre> delete:  If this request is sent for an End User of a sponsoring LIR, you should answer 'Yes' in the “ delete: <tt> end-user-of-sponsoring-lir delete: </tt> ” field. delete:  delete:  If you answered 'Yes' you should also confirm that all of the elements of paragraph 2.0 of “ delete: <a data-val="b4db2a127586d02986acbcc4f1cf8651" href="resolveuid/b4db2a127586d02986acbcc4f1cf8651" data-linktype="internal" class="internal-link"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> ” are listed in the '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 the End User. delete:  delete:  You can find an example agreement at at delete: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/ripe/docs/lir-end-user-agreement.html delete: </a> . delete:   You can send us an agreement in your local language or use the English version. delete:  delete:  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:  delete:  In the “ delete: <tt> org-description: delete: </tt> ” field, write a short description of the 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. delete:  delete:  delete: <a name="user"> delete: </a> delete:  delete: <h2> User Template delete: </h2> delete: <pre> #[USER TEMPLATE]# delete:   % delete:   % Who is the contact person for this IXP? delete:   delete:   name: delete:  Fred Bloggs delete:  delete:   organisation: delete:  Ruritania IXP delete:  delete:   country: delete:  NN delete:  delete:   phone: delete:  +123 45 678910 delete:  delete:   fax-no: delete:  +123 45 678911 delete:  delete:   email: delete:  [email protected] delete:  delete: </pre> delete:  Enter the legal name and primary location of the organisation in the “ delete: <tt> organisation: delete: </tt> ” and “ delete: <tt> country: delete: </tt> ” fields. delete:  delete:  Please use international dialling codes (for example, +31 for the Netherlands,) in the “ delete: <tt> phone: delete: </tt> ” and “ delete: <tt> fax-no: delete: </tt> ” fields. delete:  delete:  delete: <a name="peering"> delete: </a> delete:  delete: <h2> Member Peering Information Template delete: </h2> delete: <pre> #[MEMBER PEERING INFORMATION TEMPLATE]# delete:   % delete:   % If the IXP has an online list of members, please add the delete:   % URL below. delete:   delete:   delete:  member-peering-list: http://www.rurixp.ripe.net/members.html delete:  delete:   delete:   % If you will include this list as an attachment, please delete:   % enter "Yes" below. delete:   delete:   member-peering-attached: delete:   delete:   % Please add the contact details for three of these members. delete:   delete:   organisation-1: delete:  Bluelight B.V. delete:  delete:   as-number-1: delete:  AS65444 delete:  delete:   e-mail-1: delete:  [email protected] delete:  delete:   delete:   organisation-2: delete:  Bank of Ruritania Inc. delete:  delete:   as-number-2: delete:  AS65333 delete:  delete:   e-mail-2: delete:  [email protected] delete:  delete:   delete:   organisation-3: delete:  Ruritania Telecom delete:  delete:   as-number-3: delete:  AS65222 delete:  delete:   e-mail-3: delete:  [email protected] delete:  delete:   delete:   % If possible, please add the URL of a looking glass where delete:   % we can verify this information: delete:   delete:   delete:  looking-glass: http://www.rurixp.ripe.net/looking-glass.cgi delete:  delete: </pre> delete:  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 “ delete: <tt> member-peering-list: delete: </tt> ” field. If you attach the list to your request, enter ‘yes' in the “ delete: <tt> member-peering-attached: delete: </tt> ” field. delete:  delete:  Enter the organisation name, Autonomous System (AS) number and the contact e-mail address for three of the IXPs members. delete:  delete:  If possible, add the URL of a looking glass in the "looking glass:" field so we can verify this information. delete:  delete:  delete: <a name="current"> delete: </a> delete:  delete: <h2> Current Address Space Usage Template delete: </h2> delete: <pre> #[CURRENT ADDRESS SPACE USAGE TEMPLATE]# delete:   % delete:   % If the IXP has any IPv6 assignments, please list them below. delete:   subnet: delete:  none delete:  delete: </pre> delete:  Please specify address prefixes using slash notation (for example, y:y:y::/yy). You can repeat the “ delete: <tt> subnet: delete: </tt> ” field as many times as needed. delete:  delete:  delete: <a name="plan"> delete: </a> delete:  delete: <h2> Addressing Plan delete: </h2> delete: <pre> #[ADDRESSING PLAN]# delete:   % delete:   % When will the IXP use the requested address space? delete:   % delete:   % Subnet Within Within Within delete:   % size (/nn) 3 months 1 year 2 years Purpose delete:   subnet: delete:  /64 x - - *see supplemental delete:  delete:   subnet: delete:  /64 x - - comments section delete:  delete: </pre> delete:  The addressing plan shows when the IXP plans to use the address space. delete:  delete:  Enter the size of each subnet in the “ delete: <tt> Subnet size (/nn) delete: </tt> ” column. Please specify the size using IPv6 slash notation (for example, /48). You can repeat the “ delete: <tt> subnet: delete: </tt> ” field as many times as needed. delete:  delete:  In the “ delete: <tt> Purpose delete: </tt> ” column, write a short description for each subnet. If needed, you can write a more detailed description in the “ delete: <tt> Insert Supplemental Comments delete: </tt> ” section at the end of the form. delete:  delete:  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 “ delete: <tt> Within 3 months delete: </tt> ” column and a dash in both the “ delete: <tt> Within 1 year delete: </tt> ” and “ delete: <tt> Within 2 years delete: </tt> ” columns. delete:  delete:  delete: <a name="comments"> delete: </a> delete:  delete: <h2> Supplemental Comments delete: </h2> delete: <pre> #[SUPPLEMENTAL COMMENTS]# delete:   % delete:   % Please add more information if you think it will help delete:   % us understand this request. delete:   delete:   delete:  We will have 2 separate subnets. One for our 30 banking members who delete:   require secure transactions, and one for our 200 regular ISP delete:   members. Each member will use a /128. delete:  delete: </pre> delete:  You can use this space for additional information that you think will be helpful for us when we evaluate your request. delete:  delete:  delete: <a name="documentation"> delete: </a> delete:  delete: <h2> Supporting Documentation delete: </h2> delete: <pre> #[SUPPORTING DOCUMENTATION]# delete:   % delete:   % If this request is being sent by a sponsoring LIR on behalf of delete:   % an End User, please attach a copy of the signed delete:   % "End User Assignment Agreement" and the company registration papers delete:   % of the End User. delete:   % You can also attach a network diagram or other supporting documentation. delete:   % delete:   % Have you attached any files/documents to this request? (Yes/No) delete:   delete:   file-attached: delete:  Yes delete:  delete: </pre> delete:  For each IPv6 IXP assignment that is requested through a sponsoring LIR for an End User, we need to receive a copy of 'End User Assignment Agreement' and the company registration papers of the End User. delete:  delete:  If this request is for an LIR or a “ delete: <tt> Direct Assignment User delete: </tt> ”, you do not have to attach a copy of 'End User Assignment Agreement' and company registration papers. delete:  delete:  A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. delete:  delete:  delete: <a name="database"> delete: </a> delete:  delete: <h2> Database Template(s) delete: </h2> delete: <pre> #[DATABASE TEMPLATE(S)]# delete:   % delete:   % Please complete all of the fields below. delete: </pre> delete: <pre> inet6num: delete:   netname: delete:  RURIXP delete:  delete:   descr: delete:  Ruritania IXP delete:  delete:   country: delete:  NL delete:  delete:   org: delete:  ORG-Bb2-RIPE delete:  delete:   admin-c: delete:  HOHO1-RIPE delete:  delete:   tech-c: delete:  HOHO1-RIPE delete:  delete:   status: ASSIGNED delete:   mnt-by: RIPE-NCC-END-MNT delete:   mnt-lower: RIPE-NCC-END-MNT delete:   mnt-by: delete:  SANTA-MNT delete:  delete:   mnt-domains: delete:  SANTA-MNT delete:  delete:   mnt-routes: delete:  SANTA-MNT delete:  delete:   changed: [email protected] delete:   source: RIPE delete: </pre> delete:  Leave the “ delete: <tt> inet6num: delete: </tt> ” field empty as we (the RIPE NCC) will complete it. delete:  delete:  The “ delete: <tt> netname: delete: </tt> ” should be a short, descriptive name for the network and should reflect the name of the organisation operating the IXP. delete:  delete:  Enter the legal name of the organisation operating the IXP in the “ delete: <tt> descr: delete: </tt> ” field. delete:  delete:  Enter the ISO country code of the organisation in the “ delete: <tt> country: delete: </tt> ” field. delete:  delete:  Enter the org-ID of the delete:  organisation delete:  object in the “ delete: <tt> org: delete: </tt> ” field. You can create delete:  organisation delete:  objects using 'webupdates'. delete:  delete:  delete:  Person delete:  and delete:  role delete:  objects contain information about people. Each object has a unique NIC handle (nic-hdl). You can create delete:  person delete:  and delete:  role delete:  objects using webupdates. delete:  delete:  The nic-hdl of the delete:  role delete:  or delete:  person delete:  object entered in the “ delete: <tt> admin-c: delete: </tt> ” field should be for someone who has administrative responsibilities for the network. delete:  delete:  The nic-hdl of the delete:  role delete:  or delete:  person delete:  object entered in the “ delete: <tt> tech-c: delete: </tt> ” field should be for someone who has technical knowledge of the network. delete:  delete:  The “ delete: <tt> status: delete: </tt> ” field must be delete: <tt> ASSIGNED delete: </tt> . delete:  delete:  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' ( delete: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net delete: </a> ). delete:  delete:  One of the “ delete: <tt> mnt-by: delete: </tt> ” fields must be delete: <tt> RIPE-NCC-END-MNT delete: </tt> . Enter the IXP's maintainer in the other “ delete: <tt> mnt-by: delete: </tt> ” field. The IXP will be able to update the delete:  inet6num delete:  object using webupdates. delete:  delete:  The “ delete: <tt> mnt-lower: delete: </tt> ” field must be delete: <tt> RIPE-NCC-END-MNT delete: </tt> . delete:  delete:  The “ delete: <tt> mnt-domains: delete: </tt> ” field shows which maintainer authorises the creation of delete:  domain delete:  objects for the assignment. delete:  delete:  The “ delete: <tt> mnt-routes: delete: </tt> ” field shows which maintainer authorises the creation of delete:  route6 delete:  objects for the assignment. delete:  delete:  All of the objects that you enter in the template must already exist in the RIPE Whois Database. delete:  delete:  The “ delete: <tt> changed: delete: </tt> ” field must be delete: <tt> [email protected] delete: </tt> . delete:  delete:  The “ delete: <tt> source: delete: </tt> ” field must be delete: <tt> RIPE delete: </tt> . delete:  delete:  delete: <a name="end"> delete: </a> delete:  delete: <h2> End of Request delete: </h2> delete: <pre> #[END of REQUEST]# delete:   delete:   delete:  Best Regards, delete:   John Smith, Bluelight Admin delete:  delete: </pre> delete:  Please write your full name below the “ delete: <tt> #[END of REQUEST]# delete: </tt> ” header. delete: 