Supporting Notes for the Provider Independent (PI) Assignment Request Form RIPE NCC Document-ID: ripe-357 Date: October 2005 Obsolete: ripe-337 This document contains instructions for LIRs on how to complete the "Provider Independent (PI) Assignment Request Form" http://www.ripe.net/ripe/docs/pi-request.html. The instructions are based on the "IPv4 Address Allocation and Assignment Policy for the RIPE region" http://www.ripe.net/ripe/docs/ipv4-policies.html. General Information Address Space User Initial Information Addressing Plan Equipment Description Network Description Network Diagram Database Template(s) End of Request General Information #[GENERAL INFORMATION]# % % Please add your RegID. request-type: pi-ipv4 form-version: 1.1 x-ncc-regid: nl.bluelight Please do not change the value of the "request-type" and "form-version" fields. Enter your Registry Identifier (RegID) in the "x-ncc-regid" field. RegIDs have the following format: .. If you do not know your RegID, please contact . Address Space User #[ADDRESS SPACE USER]# % % Who will use the requested address space? legal-organisation-name: North SantaBank organisation-location: Santa City, NN website-if-available: http://www.nsb.nn % Does this End User already have address space that can be % used for this assignment? (Yes/No) space-available: No 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. 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. Initial Information #[INITIAL INFORMATION]# % % Why is PI address space required rather than PA address % space? why-pi: North SantaBank will be multihomed. We cannot use PA address space because our uplinks do not allow their address space to be announced by other Autonomous Systems. % Is the End User requesting extra address space for routing % and/or administrative reasons? (Yes/No) routing-reasons: No. % Have you made the End User aware of the consequences and % disadvantages of PI address space? (Yes/No) confirmation: Yes. In the "why-pi" 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. 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. 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. You can find more details on the consequences and disadvantages of PI address space in the "IPv4 Address Allocation and Assignment Policy for the RIPE region" (see above for url). Addressing Plan #[ADDRESSING PLAN]# % % How will the End User use this address space? % % Subnet size Within Within Within % (/nn) 3 months 1 year 2 years Purpose subnet: /26 32 64 64 Employee VPN Access subnet: /26 18 34 64 Financial Services subnet: /26 22 30 60 Workstations subnet: /27 11 15 28 Public Services subnet: /27 7 18 30 Operations subnet: /24 176 192 240 Branch Offices totals: /23 266 353 486 number-of-subnets: 6 % Will the End User return any address space? address-space-returned: 85.118.187/24 to nl.bluelight in 3 months The addressing plan shows how the End User will use the requested address space. You can repeat the "subnet" row as many times as needed. Delete any empty "subnet" fields before you send the request. 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 two years. In the "Within 3 months", "Within 1 year" and "Within 2 years" columns, enter the number of addresses needed immediately for each subnet, and the estimated need for the next two years. You can change the time periods if needed. 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). 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. 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. In the "number-of-subnets" field, enter the total number of subnets listed in the addressing plan. 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: to in