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

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

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

ripe-491: This document contains instructions ripe-337: Supporting Notes for LIRs on how to complete the "Provider Provider Independent (PI) Assignment Request Form". Form

This document contains instructions for LIRs on how to complete the " delete: <a href="https://www.ripe.net/publications/docs/pi-requestform.html"> Provider Independent (PI) Assignment Request Form delete: </a> ". delete:  delete:  The instructions are based on the " delete: <a href="https://www.ripe.net/publications/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region delete: </a> ". delete:  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="#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:  delete: <h2> delete: <a name="info"> delete: </a> General Information delete: </h2> delete: <pre> #[GENERAL INFORMATION]# delete:   % delete:   % Please add your RegID. delete:   delete:   request-type: pi-ipv4 delete:   form-version: 1.3 delete:   x-ncc-regid: delete:  nl.bluelight delete:  delete: </pre> delete:  Please do not change the value of the " delete:  request-type: delete:  " and " delete:  form-version: delete:  " fields. delete:  delete:  Enter your Registry Identifier (RegID) in the " delete:  x-ncc-regid delete:  :" field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact delete: <a href="mailto:[email protected]"> [email protected] delete: </a> . delete:  delete:  delete: <a name="user"> delete: </a> delete:  delete: <h2> Address Space User delete: </h2> delete: <pre> #[ADDRESS SPACE USER]# delete:   % delete:   % Who will use the requested address space? delete:   delete:   delete:   legal-organisation-name: delete:  North SantaBank delete:  delete:   organisation-location: delete:  Santa City, NN delete:  delete:   website-if-available: delete:  http://www.nsb.nn delete:  delete:   delete:   delete:   % Is this request being sent by a sponsoring LIR on behalf of delete:   % an 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 "Contractual delete:   % Requirements for Provider Independent Resource Holders in the delete:   % RIPE NCC Service Region".(Yes/No) delete:   delete:   confirmation: delete:  Yes delete:  delete:   delete:   % Does this End User already have address space that can be used for delete:   % this assignment? (Yes/No) delete:   delete:   space-available: delete:  No delete:  delete: </pre> delete:  Enter the legal name and primary location of the organisation that will use this 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:   delete:   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:   delete:   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. 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 online: delete:   delete: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/membership/lir-end-user-agreement.html delete: </a> delete:   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:  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:  delete:  delete:  delete: <h2> delete: <a name="initial"> delete: </a> Initial Information delete: </h2> delete: <pre> #[INITIAL INFORMATION]# delete:   % delete:   delete:   % Why is PI address space required rather than PA address delete:   % space? delete:   delete:   why-pi: delete:  North SantaBank will be multihomed. delete:   We cannot use PA address space because our uplinks do not delete:   allow their address space to be announced by other Autonomous Systems. delete:  delete:   delete:   % Is the End User requesting extra address space for routing delete:   % and/or administrative reasons? (Yes/No) delete:   delete:   routing-reasons: delete:  No. delete:  delete:   delete:   % Have you made the End User aware of the consequences and delete:   % disadvantages of PI address space? (Yes/No) delete:   delete:   confirmation: delete:  Yes. delete:  delete: </pre> delete:  In the " delete:  why-pi: delete:  " field, explain why PA address space cannot be used for this assignment. Remember that you should encourage the use of PA address space where possible. delete:  delete:  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 " delete:  routing-reasons: delete:  " field. delete:  delete:  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 " delete:  confirmation: delete:  " field. You can find more details on the consequences and disadvantages of PI address space in the document "IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region". delete:  delete:  delete: <a name="plan"> delete: </a> delete:  delete: <h2> Addressing Plan delete: </h2> delete: <pre> #[ADDRESSING PLAN]# delete:   % As of 1 January 2010 assignments are for a period of up to 12 months. delete:   % As of 1 July 2010 assignments are for a period of up to 9 months. delete:   % As of 1 January 2011 assignments are for a period of up to 6 months. delete:   % As of 1 July 2011 assignments are for a period of up to 3 months. delete: </pre> delete: <pre> % delete:   % How will the End User use this address space? delete:   % delete: </pre> delete: <pre> % Subnet Immediate Intermediate Entire Purpose delete:   % size (/nn) Requirement Requirement Period delete:   subnet: delete:  /26 32 64 64 Employee VPN Access delete:  delete:   subnet: delete:  /26 18 34 64 Financial Services delete:  delete:   subnet: delete:  /26 22 30 60 Workstations delete:  delete:   subnet: delete:  /27 11 15 28 Public Services delete:  delete:   subnet: delete:  /27 7 18 30 Operations delete:  delete:   subnet: delete:  /24 176 192 240 Branch Offices delete:  delete:   totals: delete:  /23 266 353 486 delete:  delete:   delete: </pre> delete: <pre> number-of-subnets: delete:  6 delete:  delete: </pre> delete:  % Will the End User return any address space? delete:  delete: <pre> address-space-returned: delete:  85.118.187/24 to nl.bluelight in 3 months delete:  delete:   delete: </pre> delete:  The addressing plan shows how the End User will use the requested address space. delete:  delete:  You can repeat the "subnet" row as many times as needed. Delete any empty "subnet" fields before you send the request. delete:  delete:  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:  delete:  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. Your estimates should include interfaces used for hosts, routers, gateways, terminal concentrators and any other machines requiring one or more network interfaces. These columns can either contain numbers (for example, 128) or slash notation prefixes (for example, /25). Multiple slash notation prefixes must be separated by comma(s) with no blank spaces (for example, /25,/27). delete:   Starting on 1 January 2010, a gradual reduction in the assignment period will be applied. As the assignment period changes, so to will the information required: delete:  delete:  Up to 30 June 2010, assignments are for a period of up to 12 months. Therefore, your request should reflect your immediate requirements, predicted requirements for the coming 6 months, and predicted requirements for the coming 12 months. delete:  delete:  As of 1 July 2010, assignments are for a period of up to 9 months. Your request should reflect your immediate requirements, predicted requirements for the coming 6 months, and predicted requirements for delete:   the coming 9 months. delete:  delete:  As of 1 January 2011, assignments are for period of up to 6 months. Your request should reflect your immediate requirements, predicted requirements for the coming 3 months, and predicted requirements for delete:   the coming 6 months. delete:  delete:  As of 1 July 2011, assignments are for a period of up to 3 months. Your request should reflect your immediate requirements, predicted requirements for the coming 2 months, and predicted requirements for the coming 3 months. delete:  delete:  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 at the end of this form. delete:   delete:   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:   delete:   In the "number-of-subnets" field, enter the total number of subnets listed in the addressing plan. delete:   delete:   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: <x.x.x.x/xx> to <which LIR/ISP> in <time period> for this field. delete:  delete:  delete: <a name="equipment"> delete: </a> delete:  delete: <h2> Equipment Description delete: </h2> delete: <pre> #[EQUIPMENT DESCRIPTION]# delete:   % delete:   % What equipment will be used and how will it use the requested delete:   % address space? delete:   delete:   equipment-name: delete:  Core switches delete:  delete:   manufacturer-name: delete:  Cisco delete:  delete:   model-number: delete:  25xx delete:  delete:   other-data: delete:  3 units delete:  delete:   delete:   equipment-name: delete:  Servers delete:  delete:   manufacturer-name: delete:  HP delete:  delete:   model-number: delete:  various delete:  delete:   other-data: delete:  40 units delete:  delete:   delete:   equipment-name: delete:  Firewalls delete:  delete:   manufacturer-name: delete:  Cisco delete:  delete:   model-number: delete:  PIX 515 E delete:  delete:   other-data: delete:  2 units, 8 IP addresses delete:  delete:   delete:   equipment-name: delete:  Workstations delete:  delete:   manufacturer-name: delete:  Dell delete:  delete:   model-number: delete:  GX150 delete:  delete:   other-data: delete:  22 units, 1 IP address each delete:  delete:   delete:   equipment-name: delete:  Routers delete:  delete:   manufacturer-name: delete:  Cisco delete:  delete:   model-number: delete:  3825 delete:  delete:   other-data: delete:  2 units delete:  delete:   delete:   equipment-name: delete:  Routers delete:  delete:   manufacturer-name: delete:  Cisco delete:  delete:   model-number: delete:  AS5300 delete:  delete:   other-data: delete:  1 unit, 32 ports delete:  delete: </pre> delete:  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:   delete:   In the "equipment-name" field, enter the type of equipment requiring address space from this assignment. delete:   delete:   Enter the vendor name and model number for the piece of equipment in the "manufacturer-name" and "model-number" fields. delete:   delete:   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:  delete:  delete: <a name="network"> delete: </a> delete:  delete: <h2> Network Description delete: </h2> delete: <pre> #[NETWORK DESCRIPTION]# delete:   % delete:   % Please add more information if you think it will help us understand delete:   % this request. delete:   delete:   delete:  We have 11 branches across Santa City linked by corporate fibre delete:   channels. We will assign a /28 subnet for each branch. Each branch delete:   will have SMTP, WWW, file server, e-banking and dial-up pool. delete:   delete:   Public Internet Services: SMTP (2 IP addresses), WWW (6 IP addresses, delete:   2 servers), FTP (1 IP address), DNS (2 IP addresses) Financial delete:   Services: 6 servers, 3 IP addresses each. Operations network: delete:   Security, Monitoring, VPN, Proxy, DNS delete:  delete: </pre> delete:  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:  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 "End User Assignment delete:   % Agreement" and the company registration papers of the End User. delete:   % You can also attach a network diagram or other supporting delete:   % 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 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:   delete:   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:   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:   delete:   inetnum: delete:   netname: delete:  NSB-NET delete:  delete:   descr: delete:  North SantaBank delete:  delete:   country: delete:  NN delete:  delete:   org: delete:  ORG-NS31-RIPE delete:  delete:   admin-c: delete:  ACM2-RIPE delete:  delete:   tech-c: delete:  HOHO1-RIPE delete:  delete:   status: delete:  ASSIGNED PI delete:  delete:   mnt-by: delete:  RIPE-NCC-END-MNT delete:  delete:   mnt-lower: delete:  RIPE-NCC-END-MNT delete:  delete:   mnt-by: delete:  SANTA-MNT delete:  delete:   mnt-routes: delete:  SANTA-MNT delete:  delete:   mnt-domains: delete:  SANTA-MNT delete:  delete:   changed: [email protected] delete:   source: RIPE delete: </pre> delete:  Leave the "inetnum" field empty as we will choose the address range. delete:   delete:   The "netname" should be a short and descriptive name for the network and should reflect the organisation name of the End User. delete:   delete:   Enter the End User's organisation name in the "descr" field. delete:   delete:   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 delete:  inetnum delete:  object. delete:   delete:   Enter the org-ID of the End User's organisation object in the "org" field. delete:   delete:   The nic-handle of the delete:  role delete:  or delete:  person delete:  object in the "admin-c" field should reflect someone who is administratively responsible for the network. delete:   delete:   The nic-handle of the delete:  role delete:  or delete:  person delete:  object in the "tech-c" field should reflect someone who has technical knowledge of the network. delete:   delete:   The "status" field must be ASSIGNED PI. delete:   delete:   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:   delete:   The "mnt-by" field shows which maintainer authenticates object updates. The "mnt-routes" and "mnt-domains" fields show which maintainers authenticate the creation of delete:  route delete:  and delete:  domain delete:  objects. delete:   delete:   The RIPE Database must contain all of the objects that you use. delete:   delete:   The "changed" field must be [email protected] delete:   delete:   The "source" field must be RIPE. delete:  delete:  delete: <a name="end"> delete: </a> delete:  delete: <h2> End of Request delete: </h2> delete: <pre> Best Regards, delete:   delete:   Jan Janssen, Bluelight Admin delete: </pre> delete:  Please write your full name below the "#[END of REQUEST]#" header. delete: 