You are here: Home > Publications > RIPE Document Store > Supporting Notes for the IPv6 Provider Independent (PI) Assignment Request Form

Changes to Supporting Notes for the IPv6 Provider Independent (PI) Assignment Request Form

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-483: This document contains instructions ripe-468: Supporting Notes for LIRs on how to complete the "IPv6 IPv6 Provider Independent (PI) Assignment Request Form". Form

This document contains instructions for LIRs on how to complete the " delete: <a href="http://ripe.net/ripe/docs/ipv6-pi.html"> IPv6 Provider Independent (PI) Assignment Request Form delete: </a> ". delete: </p> delete: <p> The instructions are based on the " delete: <a href="http://www.ripe.net/ripe/docs/ipv6-policy.html"> IPv6 Address Allocation and Assignment Policy delete: </a> ". delete: </p> delete: <ul> delete: <li> delete: <a href="#info"> General Information delete: </a> delete: </li> delete: <li> delete: <a href="#user"> Address Space User delete: </a> delete: </li> delete: <li> delete: <a href="#initial"> Initial Information delete: </a> delete: </li> delete: <li> delete: <a href="#plan"> Addressing Plan delete: </a> delete: </li> delete: <li> delete: <a href="#equipment"> Equipment Description delete: </a> delete: </li> delete: <li> delete: <a href="#network"> Network Description delete: </a> delete: </li> delete: <li> delete: <a href="#peering"> Peering Contacts delete: </a> delete: </li> delete: <li> delete: <a href="#diagram"> Network Diagram 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: <h2> delete: <a name="info"> delete: </a> General Information delete: </h2> delete: <pre> #[GENERAL INFORMATION]# delete: <br /> % delete: <br /> % Please add your RegID. delete: <br /> delete: <br /> request-type: pi-ipv6 delete: <br /> form-version: 1.0 delete: <br /> x-ncc-regid: delete: <b> nl.bluelight delete: </b> delete: <br /> 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 ncc@ripe.net. delete: </p> delete: <h2> delete: <a name="user"> delete: </a> Address Space User delete: </h2> delete: <pre> #[ADDRESS SPACE USER]# delete: <br /> % delete: <br /> % Who will use the requested address space? delete: <br /> delete: <br /> delete: <br /> legal-organisation-name: delete: <b> North SantaBank delete: </b> delete: <br /> organisation-location: delete: <b> Santa City, NN delete: </b> delete: <br /> website-if-available: delete: <b> http://www.nsb.nn delete: </b> delete: <br /> delete: <br /> delete: <br /> % Is this request being sent by a sponsoring LIR on behalf of delete: <br /> % an End User? (Yes/No) delete: <br /> delete: <br /> end-user-of-sponsoring-lir: delete: <b> Yes delete: </b> delete: <br /> delete: <br /> % If yes, 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 /> % Also 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 delete: <br /> % RIPE NCC Service Region".(Yes/No) delete: <br /> delete: <br /> confirmation: delete: <b> Yes delete: </b> delete: <br /> delete: <br /> % Does this End User already have address space that can be used for delete: <br /> % this assignment? (Yes/No) delete: <br /> delete: <br /> space-available: delete: <b> No delete: </b> delete: <br /> delete: </pre> delete: <p> Enter the legal name and primary location of the organisation that will use this IPv6 PI address space in the "legal-organisation-name" and "organisation-location" fields. If this End User has a website, enter the URL in the "website-if-available" field. Otherwise, enter "none" in this field. delete: <br /> 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. IPv6 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: <br /> delete: <br /> For each IPv6 PI 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: <br /> delete: <br /> You can find an example agreement online: delete: </p> delete: <p> You can find an example agreement online: delete: </p> delete: <p> delete: <a href="http://www.ripe.net/membership/lir-end-user-agreement.html"> http://www.ripe.net/membership/lir-end-user-agreement.html delete: </a> delete: </p> delete: <p> 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: <br /> delete: <br /> 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: <br /> delete: <br /> If there is any address space assigned to this End User that is not in use, indicate this in the "space-available" field. If you answer "yes", you can explain why the End User needs another assignment of address space in the "Network Description" section. delete: </p> delete: <h2> delete: <a name="initial"> delete: </a> Initial Information delete: </h2> delete: <pre> ##[INITIAL INFORMATION]# delete: <br /> % delete: <br /> % Why is PI address space required rather than PA address space? delete: <br /> delete: <br /> why-pi: delete: <b> North SantaBank will be multihomed. delete: </b> delete: <br /> delete: <br /> % Is the End User requesting extra address space for routing and/or delete: <br /> % administrative reasons? (Yes/No) delete: <br /> delete: <br /> routing-reasons: delete: <b> No delete: </b> delete: <br /> delete: <br /> % Have you made the End User aware of the consequences and disadvantages delete: <br /> % of PI address space? (Yes/No) delete: <br /> delete: <br /> confirmation: delete: <b> Yes. delete: </b> delete: <br /> delete: </pre> delete: <p> In the "why-pi:" field, explain why PA address space cannot be used for this assignment. delete: </p> delete: <p> You cannot request a larger assignment of address space than needed as conservation is one of the most important goals of the Internet Registry System. You can state whether you are requesting more address space than needed in the "routing-reasons:" field. delete: </p> delete: <p> You must ensure that the End User understands and accepts that PI address space may be more difficult or more expensive to route than PA address space and then confirm this in the "confirmation:" field. delete: </p> delete: <h2> delete: <a name="plan"> delete: </a> Addressing Plan delete: </h2> delete: <pre> #[ADDRESSING PLAN]# delete: <br /> % delete: <br /> % When will the End User use this IPv6 PI assignment? delete: <br /> delete: <br /> % delete: <br /> % Subnet Within Within Within delete: <br /> % size (/nn) 3 months 1 year 2 years Purpose delete: <br /> delete: <br /> subnet: delete: <b> /48 x - - Office LAN delete: </b> delete: <br /> delete: <br /> number-of-subnets: delete: <b> 1 delete: </b> delete: <br /> delete: <br /> % Will the End User return any address space? delete: <br /> delete: <br /> address-space-returned: delete: <b> no delete: </b> delete: <br /> 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> Enter the size of each subnet in the "Subnet size (/nn)" column. Please specify the size using IPv6 slash notation (for example, /48). 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 "Network Description" section of this 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> In the "number-of-subnets" field, enter the total number of subnets listed in the addressing plan. delete: </p> delete: <p> The smallest IPv6 PI assignment size issued by the RIPE NCC is /48 delete: </p> delete: <p> If there is any address space assigned to the End User that they will return, list each prefix in separate "address-space-returned" fields. The expected time for renumbering is three months. You can use the following syntax: <IP range> to <which LIR/ISP> in <time period> for this field. delete: </p> delete: <h2> delete: <a name="equipment"> delete: </a> Equipment Description delete: </h2> delete: <pre> #[EQUIPMENT DESCRIPTION]# delete: <br /> % delete: <br /> % What equipment will be used and how will it use the requested delete: <br /> % address space? delete: <br /> delete: <br /> equipment-name: delete: <b> Switches delete: </b> delete: <br /> manufacturer-name: delete: <b> Cisco delete: </b> delete: <br /> model-number: delete: <b> 25xx delete: </b> delete: <br /> other-data: delete: <b> 5 units delete: </b> delete: <br /> delete: <br /> equipment-name: delete: <b> Servers delete: </b> delete: <br /> manufacturer-name: delete: <b> HP delete: </b> delete: <br /> model-number: delete: <b> various delete: </b> delete: <br /> other-data: delete: <b> 10 units delete: </b> delete: <br /> delete: <br /> equipment-name: delete: <b> Workstations delete: </b> delete: <br /> manufacturer-name: delete: <b> Dell delete: </b> delete: <br /> model-number: delete: <b> GX150 delete: </b> delete: <br /> other-data: delete: <b> 20 units delete: </b> delete: <br /> delete: <br /> equipment-name: delete: <b> Routers delete: </b> delete: <br /> manufacturer-name: delete: <b> Cisco delete: </b> delete: <br /> model-number: delete: <b> 3825 delete: </b> delete: <br /> other-data: delete: <b> 2 units delete: </b> delete: </pre> delete: <p> delete: <br /> delete: <br /> delete: </p> delete: <p> The equipment description will help us to understand the requirements listed in the addressing plan and can be repeated as many times as needed. Leave an empty line before each new "equipment-name" field. delete: </p> delete: <p> In the "equipment-name" field, enter the type of equipment requiring address space from this assignment. delete: </p> delete: <p> Enter the vendor name and model number for the piece of equipment in the "manufacturer-name" and "model-number" fields. delete: </p> delete: <p> If you have any more information about how this piece of equipment will use the requested address space, add this in the "other-data" field. delete: </p> delete: <h2> delete: <a name="network"> delete: </a> Network Description delete: </h2> delete: <pre> #[NETWORK DESCRIPTION]# delete: <br /> % delete: <br /> % Please add more information if you think it will help us understand delete: <br /> % this request. If the End User is requesting more than a /48 please delete: <br /> % explain why: delete: <br /> delete: <br /> delete: <b> North SantaBank has an office in Santa City that will be multihomed. delete: </b> delete: <br /> delete: </pre> delete: <p> You can use this space for additional information that you think will be helpful for us (RIPE NCC) when we evaluate your request. A clearer understanding of the network and its addressing needs can help us to evaluate your request more quickly. delete: </p> delete: <p> delete: <br /> delete: <br /> delete: </p> delete: <h2> delete: <a name="peering"> delete: </a> Peering Contacts delete: </h2> delete: <pre> #[PEERING CONTACTS]# delete: <br /> % delete: <br /> % Please list the Autonomous System numbers and email contact addresses delete: <br /> % of the peering partners for the requested IPv6 PI assignment delete: <br /> delete: <br /> peering: delete: <b> AS##### noddy@grottoinvestments.nn delete: </b> delete: <br /> peering: delete: <b> AS##### mary@northernbanking.nn delete: </b> delete: <br /> delete: </pre> delete: <p> Organisations that require an IPv6 PI assignment must be multi-homed. Therefore you must list the Autonomous System numbers and contact email addresses of at least two peering partners in the "peering:" fields. You can repeat the "peering:" field as many times as needed. delete: </p> delete: <p> delete: <br /> delete: <br /> delete: </p> delete: <h2> delete: <a id="diagram" name="diagram"> delete: </a> Network Diagram delete: </h2> delete: <pre> #[NETWORK DIAGRAM]# delete: <br /> % delete: <br /> % You can attach a network diagram or other supporting documentation, delete: <br /> % particularly if the End User is requesting more than a /48 delete: <br /> % delete: <br /> % Have you attached any files/documents to this request? (Yes/No) delete: <br /> delete: <br /> file-attached: delete: <b> Yes delete: </b> delete: <br /> delete: </pre> 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> Supporting documentation is useful if the organisation will require more than /48. delete: </p> delete: <h2> delete: <a name="database"> delete: </a> Database Template(s) delete: </h2> delete: <pre> #[DATABASE TEMPLATE(S)]# delete: <br /> % delete: <br /> % Please complete all of the fields below. delete: <br /> delete: <br /> inet6num: delete: <br /> netname: delete: <b> NSB-NET delete: </b> delete: <br /> descr: delete: <b> North SantaBank delete: </b> delete: <br /> country: delete: <b> NN delete: </b> delete: <br /> org: delete: <b> ORG-NS31-RIPE delete: </b> delete: <br /> admin-c: delete: <b> ACM2-RIPE delete: </b> delete: <br /> tech-c: delete: <b> HOHO1-RIPE delete: </b> delete: <br /> status: delete: <b> ASSIGNED PI delete: </b> delete: <br /> mnt-by: delete: <b> RIPE-NCC-END-MNT delete: </b> delete: <br /> mnt-lower: delete: <b> RIPE-NCC-END-MNT delete: </b> delete: <br /> mnt-by: delete: <b> SANTA-MNT delete: </b> delete: <br /> mnt-routes: delete: <b> SANTA-MNT delete: </b> delete: <br /> mnt-domains: delete: <b> SANTA-MNT delete: </b> delete: <br /> changed: hostmaster@ripe.net delete: <br /> source: RIPE delete: <br /> delete: </pre> delete: <p> Leave the "inet6num" field empty as we will choose the address range. delete: </p> delete: <p> The "netname" should be a short and descriptive name for the network and should reflect the organisation name of the End User. delete: </p> delete: <p> Enter the End User's organisation name in the "descr" field. delete: </p> delete: <p> Use the ISO country code of the End User's location in the "country" field. If the End User is multi-national, repeat the "country" field as many times as needed. Alternatively, you can use EU or ZZ if you do not wish to show the End User's location in the inet6num object. delete: </p> delete: <p> Enter the org-ID of the End User's organisation object in the "org" field. delete: </p> delete: <p> The nic-handle of the role or person object in the "admin-c" field should reflect someone who is administratively responsible for the network. delete: </p> delete: <p> The nic-handle of the role or person object in the "tech-c" field should reflect someone who has technical knowledge of the network. delete: </p> delete: <p> The "status" field must be ASSIGNED PI. delete: </p> delete: <p> The "mnt-by" and "mnt-lower" fields must contain RIPE-NCC-END-MNT. You can put the LIR's or End User's maintainers in separate "mnt-by", "mnt-routes" and "mnt-domains" fields. delete: </p> delete: <p> The "mnt-by" field shows which maintainer authenticates object updates. The "mnt-routes" and "mnt-domains" fields show which maintainers authenticate the creation of route6 and domain objects. delete: </p> delete: <p> The RIPE Database must contain all of the objects that you use. 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: <h2> delete: <a name="end"> delete: </a> End of Request delete: </h2> delete: <pre> Best Regards, delete: <br /> delete: <br /> delete: <b> Jan Janssen, Bluelight Admin delete: </b> delete: <br /> delete: </pre> delete: <p> Please write your full name below the "#[END of REQUEST]#" header. delete: </p>

RIPE Documents Search