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

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

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

ripe-454: This obsolete document contains instructions ripe-142: Supporting Notes for LIRs on how to complete the "Provider Independent (PI) Assignment European IP Address Space Request Form". Form

This document contains instructions for LIRs on how to complete the " delete: <a href="http://www.ripe.net/publications/docs/pi-requestform.html"> Provider Independent (PI) Assignment Request Form delete: </a> ". RIPE Document is available in a ASCII and PDF

delete:  The instructions are based on the " delete: <a href="http://www.ripe.net/publications/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for the RIPE 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="#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:  delete:  delete: <h2> delete: <a id="info" name="info"> delete: </a> General Information delete: </h2> delete: <blockquote> delete: <pre> #[GENERAL INFORMATION]# % % Please add your RegID. request-type: delete:  pi-ipv4 delete:  form-version: delete:  1.1 delete:  x-ncc-regid: delete:  delete:  nl.bluelight delete:  delete:  delete: </pre> delete: </blockquote> 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: <h2> delete: <a id="user" name="user"> delete: </a> Address Space User delete: </h2> delete: <blockquote> delete: <pre> #[ADDRESS SPACE USER]# % % Who will use the requested address space? delete:   legal-organisation-name: delete:  North SantaBank delete:  organisation-location: delete:  Santa City, NN delete:  website-if-available: delete:  http://www.nsb.nn delete:  delete:   % Is this request being sent by a sponsoring LIR on behalf of % an End User? (Yes/No) delete:   end-user-of-sponsoring-lir: delete:  Yes delete:  delete:   % If yes, please confirm that the "End User Assignment Agreement" % contains all of the elements listed in paragraph 2.0 of "Contractual % Requirements for Provider Independent Resource Holders in the % RIPE NCC Service Region".(Yes/No) delete:   confirmation: delete:  Yes delete:  delete:   % Does this End User already have address space that can be used for % this assignment? (Yes/No) delete:   space-available: delete:  No delete:  delete: </pre> delete: </blockquote> 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:  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: <h2> delete: <a id="initial" name="initial"> delete: </a> Initial Information delete: </h2> delete: <blockquote> delete: <pre> #[INITIAL INFORMATION]# % % Why is PI address space required rather than PA address % space? delete: </pre> delete: <pre> why-pi: delete:  delete:  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. delete:  delete:  delete: </pre> delete: <pre> % Is the End User requesting extra address space for routing % and/or administrative reasons? (Yes/No) delete: </pre> delete: <pre> routing-reasons: delete:  delete:  No. delete:  delete:  delete: </pre> delete: <pre> % Have you made the End User aware of the consequences and % disadvantages of PI address space? (Yes/No) delete: </pre> delete: <pre> confirmation: delete:  delete:  Yes. delete:  delete:  delete: </pre> delete: </blockquote> 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 Region". delete:  delete: <h2> delete: <a id="plan" name="plan"> delete: </a> Addressing Plan delete: </h2> delete: <blockquote> delete: <pre> #[ADDRESSING PLAN]# % % How will the End User use this address space? % % Subnet size Within Within Within % (/nn) 3 months 1 year 2 years Purpose delete: </pre> delete: <pre> subnet: delete:  /26 32 64 64 delete:  Employee VPN Access delete:  delete:  subnet: delete:  /26 18 34 64 delete:  Financial Services delete:  delete:  subnet: delete:  /26 22 30 60 delete:  Workstations delete:  delete:  subnet: delete:  /27 11 15 28 delete:  Public Services delete:  delete:  subnet: delete:  /27 7 18 30 delete:  Operations delete:  delete:  subnet: delete:  /24 176 192 240 delete:  Branch Offices delete:  delete:  totals: delete:  /23 266 353 486 delete:  delete: </pre> delete: <pre> number-of-subnets: delete:  6 delete:  delete: </pre> delete: <pre> % Will the End User return any address space? delete: </pre> delete: <pre> address-space-returned: delete:  delete:  85.118.187/24 to nl.bluelight in 3 months delete:  delete:  delete: </pre> delete: </blockquote> delete:  The addressing plan shows how the End User will use the requested address space. delete:  delete:  You can repeat the " delete:  subnet: delete:  " row as many times as needed. Delete any empty " delete:  subnet: delete:  " fields before you send the request. delete:  delete:  In the " delete:  Subnet size (/nn): delete:  " 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. delete:  delete:  In the " delete:  Within 3 months: delete:  ", " delete:  Within 1 year: delete:  " and " delete:  Within 2 years: delete:  " 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). delete:  delete:  In the " delete:  Purpose: delete:  " column, write a short description of each subnet. If needed, you can write a more detailed description in the " delete:  Network Description: delete:  " section at the end of this form. delete:  delete:  In the " delete:  totals: delete:  " row, add the totals of each column. The total of the " delete:  Subnet size (/nn): delete:  " column should be the total amount of address space you are requesting for this assignment. delete:  delete:  In the " delete:  number-of-subnets: delete:  " 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 " delete:  address-space-returned: delete:  " 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: <h2> delete: <a id="equipment" name="equipment"> delete: </a> Equipment Description delete: </h2> delete: <blockquote> delete: <pre> #[EQUIPMENT DESCRIPTION]# % % What equipment will be used and how will it use the % requested address space? delete: </pre> delete: <pre> equipment-name: delete:  delete:  Core switches delete:  delete:  manufacturer-name: delete:  delete:  Cisco delete:  delete:  model-number: delete:  delete:  25xx delete:  delete:  other-data: delete:  delete:  3 units delete:  delete:  delete: </pre> delete: <pre> equipment-name: delete:  delete:  Servers delete:  delete:  manufacturer-name: delete:  delete:  HP delete:  delete:  model-number: delete:  delete:  various delete:  delete:  other-data: delete:  delete:  40 units delete:  delete:  delete: </pre> delete: <pre> equipment-name: delete:  delete:  Firewalls delete:  delete:  manufacturer-name: delete:  delete:  Cisco delete:  delete:  model-number: delete:  delete:  PIX 515 E delete:  delete:  other-data: delete:  delete:  2 units, 8 IP addresses delete:  delete:  delete: </pre> delete: <pre> equipment-name: delete:  delete:  Workstations delete:  delete:  manufacturer-name: delete:  delete:  Dell delete:  delete:  model-number: delete:  delete:  GX150 delete:  delete:  other-data: delete:  delete:  22 units, 1 IP address each delete:  delete:  delete: </pre> delete: <pre> equipment-name: delete:  delete:  Routers delete:  delete:  manufacturer-name: delete:  delete:  Cisco delete:  delete:  model-number: delete:  delete:  3825 delete:  delete:  other-data: delete:  delete:  2 units delete:  delete:  delete: </pre> delete: <pre> equipment-name: delete:  delete:  Routers delete:  delete:  manufacturer-name: delete:  delete:  Cisco delete:  delete:  model-number: delete:  delete:  AS5300 delete:  delete:  other-data: delete:  delete:  1 unit, 32 ports delete:  delete:  delete: </pre> delete: </blockquote> 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 " delete:  equipment-name: delete:  " field. delete:  delete:  In the " delete:  equipment-name: delete:  " 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 " delete:  manufacturer-name: delete:  " and " delete:  model-number delete:  :" 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 " delete:  other-data: delete:  " field. delete:  delete: <h2> delete: <a id="network" name="network"> delete: </a> Network Description delete: </h2> delete: <blockquote> delete: <pre> #[NETWORK DESCRIPTION]# % % Please add more information if you think it will help us % understand this request. delete: </pre> delete: <pre> delete:  delete:  We have 11 branches across Santa City linked by corporate fibre channels. We will assign a /28 subnet for each branch. Each branch will have SMTP, WWW, file server, e-banking and dial-up pool. delete:  delete:  delete:  delete:  Public Internet Services: SMTP (2 IP addresses), WWW (6 IP addresses, 2 servers), FTP (1 IP address), DNS (2 IP addresses) Financial Services: 6 servers, 3 IP addresses each. Operations network: Security, Monitoring, VPN, Proxy, DNS delete:  delete:  delete: </pre> delete: </blockquote> 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: <h2> delete: <a id="diagram" name="diagram"> delete: </a> Network Diagram delete: </h2> delete: <blockquote> delete: <pre> #[NETWORK DIAGRAM]# % % Have you attached a network diagram to this request? (Yes/No) diagram-attached: delete:  delete:  Yes delete:  delete:  delete: </pre> delete: </blockquote> delete:  A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. delete:  delete: <h2> delete: <a id="database" name="database"> delete: </a> Database Template(s) delete: </h2> delete: <blockquote> delete: <pre> #[DATABASE TEMPLATE(S)]# % % Please complete all of the fields below. inetnum: netname: delete:  delete:  NSB-NET delete:  delete:  descr: delete:  delete:  North SantaBank delete:  delete:  country: delete:  delete:  NN delete:  delete:  org: delete:  delete:  ORG-NS31-RIPE delete:  delete:  admin-c: delete:  delete:  ACM2-RIPE delete:  delete:  tech-c: delete:  delete:  HOHO1-RIPE delete:  delete:  status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-lower: RIPE-NCC-END-MNT mnt-by: delete:  delete:  SANTA-MNT delete:  delete:  mnt-routes: delete:  delete:  SANTA-MNT delete:  delete:  mnt-domains: delete:  delete:  SANTA-MNT delete:  delete:  changed: [email protected] source: RIPE delete: </pre> delete: </blockquote> delete:  Leave the " delete:  inetnum: delete:  " field empty as we will choose the address range. delete:  delete:  The " delete:  netname: delete:  " 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 " delete:  descr delete:  :" field. delete:  delete:  Use the ISO country code of the End User's location in the " delete:  country: delete:  " field. If the End User is multi-national, repeat the " delete:  country: delete:  " 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 " delete:  org: delete:  " field. delete:  delete:  The nic-handle of the role or person object in the " delete:  admin-c: delete:  " field should reflect someone who is administratively responsible for the network. delete:  delete:  The nic-handle of the role or person object in the " delete:  tech-c: delete:  " field should reflect someone who has technical knowledge of the network. delete:  delete:  The " delete:  status: delete:  " field must be ASSIGNED PI . delete:  delete:  The " delete:  mnt-by: delete:  " and " delete:  mnt-lower: delete:  " fields must contain delete:  RIPE-NCC-END-MNT delete:  . You can put the LIR's or End User's maintainers in separate " delete:  mnt-by: delete:  ", " delete:  mnt-routes: delete:  " and " delete:  mnt-domains: delete:  " fields. delete:  delete:  The " delete:  mnt-by: delete:  " field shows which maintainer authenticates object updates. The " delete:  mnt-routes: delete:  " and " delete:  mnt-domains: delete:  " fields show which maintainers authenticate the creation of route and domain objects. delete:  delete:  The RIPE Database must contain all of the objects that you use. delete:  delete:  The " delete:  changed: delete:  " field must be delete:  [email protected] delete:  . delete:  delete:  The " delete:  source: delete:  " field must be delete:  RIPE delete:  . delete:  delete: <h2> delete: <a id="end" name="end"> delete: </a> End of Request delete: </h2> delete: <blockquote> delete: <pre> #[END of REQUEST]# delete: </pre> delete: <pre> delete:  delete:  Best Regards delete:  , delete:   delete:  delete:  delete:  Jan Janssen, Bluelight Admin delete:  delete:  delete: </pre> delete: </blockquote> delete:  Please write your full name below the " delete:  #[END of REQUEST]# delete:  " header. delete: 

Supporting Notes for the Provider Independent (PI) Assignment European IP Address Space Request Form