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

This document contains instructions for LIRs on how to complete the “ insert: <a class="external-link" href="https://www.ripe.net/ripe/docs/ipv6request-exchangepoint.html" target="_self" title=""> IPv6 Internet Exchange Points Assignment Request Form insert: </a> ”. insert: 

insert: 

The instructions are based on the “ insert: <a href="https://www.ripe.net/publications/docs/ipv6-policy.html"> IPv6 Address Allocation and Assignment Policy insert: </a> ”. insert: 

insert: <hr />

insert: <ul>

insert: <li>

insert: <a href="#general"> General Information insert: </a> insert: </li>

insert: <li>

insert: <a href="#requester"> Requester Template insert: </a> insert: </li>

insert: <li>

insert: <a href="#overview"> Overview of Organisation Template insert: </a> insert: </li>

insert: <li>

insert: <a href="#user"> User Template insert: </a> insert: </li>

insert: <li>

insert: <a href="#peering"> Member Peering Information Template insert: </a> insert: </li>

insert: <li>

insert: <a href="#current"> Current Address Space Usage Template insert: </a> insert: </li>

insert: <li>

insert: <a href="#plan"> Addressing Plan insert: </a> insert: </li>

insert: <li>

insert: <a href="#comments"> Supplemental Comments insert: </a> insert: </li>

insert: <li>

insert: <a href="#documentation"> Supporting Documentation insert: </a> insert: </li>

insert: <li>

insert: <a href="#database"> Database Template(s) insert: </a> insert: </li>

insert: <li>

insert: <a href="#end"> End of Request insert: </a> insert: </li>

insert: </ul>

insert: <hr />

insert: 

insert: <a name="general"> insert: </a> insert: 

insert: <h2>

General Information insert: `</h2>`

insert: <pre>

 #[GENERAL INFORMATION]#  insert: <br /> 
 %  insert: <br /> 
 % Please add your RegID.  insert: <br /> 
 request-type: ipv6-for-ixp  insert: <br /> 
 form-version: 1.2  insert: <br /> 
 x-ncc-regid:  insert: <b>  nl.bluelight  insert: </b>  insert: </pre>

insert: 

Please do not change the value of the “ insert: <tt> request-type: insert: </tt> ” and “ insert: <tt> form-version: insert: </tt> ” fields. insert: 

insert: 

Enter your Registry Identifier (RegID) in the “ insert: <tt> x-ncc-regid: insert: </tt> ” field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact <[email protected]>. insert: 

insert: 

insert: <a name="requester"> insert: </a> insert: 

insert: <h2>

Requester Template insert: `</h2>`

insert: <pre>

 #[REQUESTER TEMPLATE]#  insert: <br /> 
 %  insert: <br /> 
 % Please add your contact details.  insert: <br /> 
 name:  insert: <b>  John Smith  insert: </b>  insert: <br /> 
 phone:  insert: <b>  +123 45 678910  insert: </b>  insert: <br /> 
 fax-no:  insert: <b>  +123 45 678911  insert: </b>  insert: <br /> 
 email:  insert: <b>  [email protected]  insert: </b>  insert: <br /> 
 nic-hdl:  insert: <b>  HOHO1-RIPE  insert: </b>  insert: </pre>

insert: 

Enter your contact details in the requester template. You must be a registered contact for the LIR. insert: <a href="https://lirportal.ripe.net/"> The LIR Portal insert: </a> contains a list of registered contacts for your LIR. insert: 

insert: 

Please use the international dialling codes (for example, +31 for the Netherlands,) in the “ insert: <tt> phone: insert: </tt> ” and “ insert: <tt> fax-no: insert: </tt> ” fields. insert: 

insert: 

Enter your NIC handle, if you have one, in the “ insert: <tt> nic-hdl: insert: </tt> ” field. insert: 

insert: 

insert: <a name="overview"> insert: </a> insert: 

insert: <h2>

Overview of Organisation Template insert: `</h2>`

insert: <pre>

 #[OVERVIEW OF ORGANISATION TEMPLATE]#  insert: <br /> 
 %  insert: <br /> 
 % Is this request being sent by a sponsoring LIR on behalf of an  insert: <br /> 
 % End User? (Yes/No)  insert: <br /> 
 insert: <br /> 
 end-user-of-sponsoring-lir:  insert: <b>  Yes  insert: </b>  insert: <br /> 
 insert: <br /> 
 % If yes, please confirm that the "End User Assignment Agreement"  insert: <br /> 
 % contains all of the elements listed in paragraph 2.0 of  insert: <br /> 
 % "Contractual Requirements for Provider Independent Resource Holders  insert: <br /> 
 % in the RIPE NCC Service Region". (Yes/No)  insert: <br /> 
 insert: <br /> 
 confirmation:  insert: <b>  Yes  insert: </b>  insert: <br /> 
 insert: <br /> 
 %  insert: <br /> 
 % Which IXP will use the requested address space?  insert: <br /> 
 % Please include the IXP's membership policy.  insert: <br /> 
 insert: <br /> 
 org-description:  insert: <b>  Ruritania IXP. The joining requirements are online at  insert: </b>  insert: <br /> 
 insert: <b>  http://www.rurixp.ripe.net/join_us.html  insert: </b>  insert: </pre>

insert: 

If this request is sent for an End User of a sponsoring LIR, you should answer 'Yes' in the “ insert: <tt> end-user-of-sponsoring-lir insert: </tt> ” field. insert: 

insert: 

If you answered 'Yes' you should also confirm that all of the elements of paragraph 2.0 of “ insert: <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 insert: </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. insert: 

insert: 

You can find an example agreement at at insert: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/ripe/docs/lir-end-user-agreement.html insert: </a> . insert:  
You can send us an agreement in your local language or use the English version. insert: 

insert: 

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'. insert: 

insert: 

In the “ insert: <tt> org-description: insert: </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. insert: 

insert: 

insert: <a name="user"> insert: </a> insert: 

insert: <h2>

User Template insert: `</h2>`

insert: <pre>

 #[USER TEMPLATE]#  insert: <br /> 
 %  insert: <br /> 
 % Who is the contact person for this IXP?  insert: <br /> 
 insert: <br /> 
 name:  insert: <b>  Fred Bloggs  insert: </b>  insert: <br /> 
 organisation:  insert: <b>  Ruritania IXP  insert: </b>  insert: <br /> 
 country:  insert: <b>  NN  insert: </b>  insert: <br /> 
 phone:  insert: <b>  +123 45 678910  insert: </b>  insert: <br /> 
 fax-no:  insert: <b>  +123 45 678911  insert: </b>  insert: <br /> 
 email:  insert: <b>  [email protected]  insert: </b>  insert: </pre>

insert: 

Enter the legal name and primary location of the organisation in the “ insert: <tt> organisation: insert: </tt> ” and “ insert: <tt> country: insert: </tt> ” fields. insert: 

insert: 

Please use international dialling codes (for example, +31 for the Netherlands,) in the “ insert: <tt> phone: insert: </tt> ” and “ insert: <tt> fax-no: insert: </tt> ” fields. insert: 

insert: 

insert: <a name="peering"> insert: </a> insert: 

insert: <h2>

Member Peering Information Template insert: `</h2>`

insert: <pre>

 #[MEMBER PEERING INFORMATION TEMPLATE]#  insert: <br /> 
 %  insert: <br /> 
 % If the IXP has an online list of members, please add the  insert: <br /> 
 % URL below.  insert: <br /> 
 insert: <br /> 
 insert: <b>  member-peering-list: http://www.rurixp.ripe.net/members.html  insert: </b>  insert: <br /> 
 insert: <br /> 
 % If you will include this list as an attachment, please  insert: <br /> 
 % enter "Yes" 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: <b>  Bluelight B.V.  insert: </b>  insert: <br /> 
 as-number-1:  insert: <b>  AS65444  insert: </b>  insert: <br /> 
 e-mail-1:  insert: <b>  [email protected]  insert: </b>  insert: <br /> 
 insert: <br /> 
 organisation-2:  insert: <b>  Bank of Ruritania Inc.  insert: </b>  insert: <br /> 
 as-number-2:  insert: <b>  AS65333  insert: </b>  insert: <br /> 
 e-mail-2:  insert: <b>  [email protected]  insert: </b>  insert: <br /> 
 insert: <br /> 
 organisation-3:  insert: <b>  Ruritania Telecom  insert: </b>  insert: <br /> 
 as-number-3:  insert: <b>  AS65222  insert: </b>  insert: <br /> 
 e-mail-3:  insert: <b>  [email protected]  insert: </b>  insert: <br /> 
 insert: <br /> 
 % If possible, please add the URL of a looking glass where  insert: <br /> 
 % we can verify this information:  insert: <br /> 
 insert: <br /> 
 insert: <b>  looking-glass: http://www.rurixp.ripe.net/looking-glass.cgi  insert: </b>  insert: </pre>

insert: 

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 “ insert: <tt> member-peering-list: insert: </tt> ” field. If you attach the list to your request, enter ‘yes' in the “ insert: <tt> member-peering-attached: insert: </tt> ” field. insert: 

insert: 

Enter the organisation name, Autonomous System (AS) number and the contact e-mail address for three of the IXPs members. insert: 

insert: 

If possible, add the URL of a looking glass in the "looking glass:" field so we can verify this information. insert: 

insert: 

insert: <a name="current"> insert: </a> insert: 

insert: <h2>

Current Address Space Usage Template insert: `</h2>`

insert: <pre>

 #[CURRENT ADDRESS SPACE USAGE TEMPLATE]#  insert: <br /> 
 %  insert: <br /> 
 % If the IXP has any IPv6 assignments, please list them below.  insert: <br /> 
 subnet:  insert: <b>  none  insert: </b>  insert: </pre>

insert: 

Please specify address prefixes using slash notation (for example, y:y:y::/yy). You can repeat the “ insert: <tt> subnet: insert: </tt> ” field as many times as needed. insert: 

insert: 

insert: <a name="plan"> insert: </a> insert: 

insert: <h2>

Addressing Plan insert: `</h2>`

insert: <pre>

 #[ADDRESSING PLAN]#  insert: <br /> 
 %  insert: <br /> 
 % When will the IXP use the requested address space?  insert: <br /> 
 %  insert: <br /> 
 % Subnet Within Within Within  insert: <br /> 
 % size (/nn) 3 months 1 year 2 years Purpose  insert: <br /> 
 subnet:  insert: <b>  /64 x - - *see supplemental  insert: </b>  insert: <br /> 
 subnet:  insert: <b>  /64 x - - comments section  insert: </b>  insert: </pre>

insert: 

The addressing plan shows when the IXP plans to use the address space. insert: 

insert: 

Enter the size of each subnet in the “ insert: <tt> Subnet size (/nn) insert: </tt> ” column. Please specify the size using IPv6 slash notation (for example, /48). You can repeat the “ insert: <tt> subnet: insert: </tt> ” field as many times as needed. insert: 

insert: 

In the “ insert: <tt> Purpose insert: </tt> ” column, write a short description for each subnet. If needed, you can write a more detailed description in the “ insert: <tt> Insert Supplemental Comments insert: </tt> ” section at the end of the form. insert: 

insert: 

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 “ insert: <tt> Within 3 months insert: </tt> ” column and a dash in both the “ insert: <tt> Within 1 year insert: </tt> ” and “ insert: <tt> Within 2 years insert: </tt> ” columns. insert: 

insert: 

insert: <a name="comments"> insert: </a> insert: 

insert: <h2>

Supplemental Comments insert: `</h2>`

insert: <pre>

 #[SUPPLEMENTAL COMMENTS]#  insert: <br /> 
 %  insert: <br /> 
 % Please add more information if you think it will help  insert: <br /> 
 % us understand this request.  insert: <br /> 
 insert: <br /> 
 insert: <b>  We will have 2 separate subnets. One for our 30 banking members who  insert: <br /> 
 require secure transactions, and one for our 200 regular ISP  insert: <br /> 
 members. Each member will use a /128.  insert: </b>  insert: </pre>

insert: 

You can use this space for additional information that you think will be helpful for us when we evaluate your request. insert: 

insert: 

insert: <a name="documentation"> insert: </a> insert: 

insert: <h2>

Supporting Documentation insert: `</h2>`

insert: <pre>

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

insert: 

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. insert: 

insert: 

If this request is for an LIR or a “ insert: <tt> Direct Assignment User insert: </tt> ”, you do not have to attach a copy of 'End User Assignment Agreement' and company registration papers. insert: 

insert: 

A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. insert: 

insert: 

insert: <a name="database"> insert: </a> insert: 

insert: <h2>

Database Template(s) insert: `</h2>`

insert: <pre>

 #[DATABASE TEMPLATE(S)]#  insert: <br /> 
 %  insert: <br /> 
 % Please complete all of the fields below.  insert: </pre>

insert: <pre>

 inet6num:  insert: <br /> 
 netname:  insert: <b>  RURIXP  insert: </b>  insert: <br /> 
 descr:  insert: <b>  Ruritania IXP  insert: </b>  insert: <br /> 
 country:  insert: <b>  NL  insert: </b>  insert: <br /> 
 org:  insert: <b>  ORG-Bb2-RIPE  insert: </b>  insert: <br /> 
 admin-c:  insert: <b>  HOHO1-RIPE  insert: </b>  insert: <br /> 
 tech-c:  insert: <b>  HOHO1-RIPE  insert: </b>  insert: <br /> 
 status: ASSIGNED  insert: <br /> 
 mnt-by: RIPE-NCC-END-MNT  insert: <br /> 
 mnt-lower: RIPE-NCC-END-MNT  insert: <br /> 
 mnt-by:  insert: <b>  SANTA-MNT  insert: </b>  insert: <br /> 
 mnt-domains:  insert: <b>  SANTA-MNT  insert: </b>  insert: <br /> 
 mnt-routes:  insert: <b>  SANTA-MNT  insert: </b>  insert: <br /> 
 changed: [email protected]  insert: <br /> 
 source: RIPE  insert: </pre>

insert: 

Leave the “ insert: <tt> inet6num: insert: </tt> ” field empty as we (the RIPE NCC) will complete it. insert: 

insert: 

The “ insert: <tt> netname: insert: </tt> ” should be a short, descriptive name for the network and should reflect the name of the organisation operating the IXP. insert: 

insert: 

Enter the legal name of the organisation operating the IXP in the “ insert: <tt> descr: insert: </tt> ” field. insert: 

insert: 

Enter the ISO country code of the organisation in the “ insert: <tt> country: insert: </tt> ” field. insert: 

insert: 

Enter the org-ID of the insert:  organisation insert:  object in the “ insert: <tt> org: insert: </tt> ” field. You can create insert:  organisation insert:  objects using 'webupdates'. insert: 

insert: 

insert:  Person insert:  and insert:  role insert:  objects contain information about people. Each object has a unique NIC handle (nic-hdl). You can create insert:  person insert:  and insert:  role insert:  objects using webupdates. insert: 

insert: 

The nic-hdl of the insert:  role insert:  or insert:  person insert:  object entered in the “ insert: <tt> admin-c: insert: </tt> ” field should be for someone who has administrative responsibilities for the network. insert: 

insert: 

The nic-hdl of the insert:  role insert:  or insert:  person insert:  object entered in the “ insert: <tt> tech-c: insert: </tt> ” field should be for someone who has technical knowledge of the network. insert: 

insert: 

The “ insert: <tt> status: insert: </tt> ” field must be insert: <tt> ASSIGNED insert: </tt> . insert: 

insert: 

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' ( insert: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net insert: </a> ). insert: 

insert: 

One of the “ insert: <tt> mnt-by: insert: </tt> ” fields must be insert: <tt> RIPE-NCC-END-MNT insert: </tt> . Enter the IXP's maintainer in the other “ insert: <tt> mnt-by: insert: </tt> ” field. The IXP will be able to update the insert:  inet6num insert:  object using webupdates. insert: 

insert: 

The “ insert: <tt> mnt-lower: insert: </tt> ” field must be insert: <tt> RIPE-NCC-END-MNT insert: </tt> . insert: 

insert: 

The “ insert: <tt> mnt-domains: insert: </tt> ” field shows which maintainer authorises the creation of insert:  domain insert:  objects for the assignment. insert: 

insert: 

The “ insert: <tt> mnt-routes: insert: </tt> ” field shows which maintainer authorises the creation of insert:  route6 insert:  objects for the assignment. insert: 

insert: 

All of the objects that you enter in the template must already exist in the RIPE Whois Database. insert: 

insert: 

The “ insert: <tt> changed: insert: </tt> ” field must be insert: <tt> [email protected] insert: </tt> . insert: 

insert: 

The “ insert: <tt> source: insert: </tt> ” field must be insert: <tt> RIPE insert: </tt> . insert: 

insert: 

insert: <a name="end"> insert: </a> insert: 

insert: <h2>

End of Request insert: `</h2>`

insert: <pre>

 #[END of REQUEST]#  insert: <br /> 
 insert: <br /> 
 insert: <b>  Best Regards,  insert: <br /> 
 John Smith, Bluelight Admin  insert: </b>  insert: </pre>

insert: 

Please write your full name below the “ insert: <tt> #[END of REQUEST]# insert: </tt> ” header. insert: 

Supporting Notes For The for the IPv6 Internet Exchange Points Assignment Request Form

RIPE Documents Search

ripe-372

State:

Obsoleted

Updated by:

ripe-461 , ripe-565 , ripe-576

Authors:

RIPE NCC

Date:

April 2006

Download

File:
PDF | 22.0KB

Download

File:
ASCII | 8.0KB

Changes to Supporting Notes For The IPv6 Internet Exchange Points Assignment Request Form

General Information insert: </h2>

Requester Template insert: </h2>

Overview of Organisation Template insert: </h2>

User Template insert: </h2>

Member Peering Information Template insert: </h2>

Current Address Space Usage Template insert: </h2>

Addressing Plan insert: </h2>

Supplemental Comments insert: </h2>

Supporting Documentation insert: </h2>

Database Template(s) insert: </h2>

End of Request insert: </h2>

RIPE Documents Search

ripe-372

General Information insert: `</h2>`

Requester Template insert: `</h2>`

Overview of Organisation Template insert: `</h2>`

User Template insert: `</h2>`

Member Peering Information Template insert: `</h2>`

Current Address Space Usage Template insert: `</h2>`

Addressing Plan insert: `</h2>`

Supplemental Comments insert: `</h2>`

Supporting Documentation insert: `</h2>`

Database Template(s) insert: `</h2>`

End of Request insert: `</h2>`