You are here: Home > Publications > RIPE Document Store > RIPE Internet Network Numbers Template

Changes to RIPE Internet Network Numbers Template

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-048: RIPE Internet Network Numbers Template ripe-454: This obsolete document contains instructions for LIRs on how to complete the "Provider Independent (PI) Assignment Request Form".
delete: <p style="text-align: left; "> RIPE Internet Network Numbers Template delete: <br /> delete: <br /> D.Karrenberg delete: <br /> delete: <br /> Aug 1992 delete: <br /> delete: <br /> delete: <br /> delete: <br /> To whom it may concern, delete: <br /> delete: <br /> The RIPE Network Coordination Centre now handles all requests insert: <p>

This document contains instructions for IP delete: <br /> network numbers from European organisations. Our aim is to provide a delete: <br /> rapid and efficient service to all European organisations. As this is delete: <br /> a recent initiative, procedures for handling network number requests are delete: <br /> in the process of being established. Therefore we apologise in advance delete: <br /> for any duplication of effort that may be required by you due to new delete: <br /> forms and templates. As the European NIC, we require different delete: <br /> information to that required by the US and for it to be presented in a delete: <br /> format which is both easy for you LIRs on how to complete and the " insert: <a href="http://www.ripe.net/publications/docs/pi-requestform.html"> Provider Independent (PI) Assignment Request Form insert: </a> ". insert: </p>

insert: <p>

The instructions are based on the " insert: <a href="http://www.ripe.net/publications/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for us to process. the RIPE region insert: </a> ". insert: </p>

insert: <ul> insert: <hr />
insert: <p>

  insert: </p>

insert: <h2>

insert: <a id="info" name="info"> insert: </a> General Information insert: </h2>

insert: <blockquote>
insert: <pre>
 #[GENERAL INFORMATION]# % % Please add your RegID. request-type:  insert: <strong>  pi-ipv4  insert: </strong>  form-version:  insert: <strong>  1.1  insert: </strong>  x-ncc-regid:  insert: <strong>  insert: <span class="arial-small">  nl.bluelight  insert: </span>  insert: </strong>  insert: </pre> 
insert: </blockquote>
insert: <p>

Please do not change the value of the " insert: <span class="pre"> request-type: insert: </span> " and " insert: <span class="pre"> form-version: insert: </span> " fields. insert: </p>

insert: <p>

Enter your Registry Identifier (RegID) in the " insert: <span class="pre"> x-ncc-regid insert: </span> :" field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact insert: <a href="mailto:ncc@ripe.net"> ncc@ripe.net insert: </a> . insert: </p>

insert: <h2>

insert: <a id="user" name="user"> insert: </a> Address Space User insert: </h2>

insert: <blockquote>
insert: <pre>
 #[ADDRESS SPACE USER]# % % Who will use the requested address space?  
Before your application legal-organisation-name: insert: <strong> North SantaBank insert: </strong> organisation-location: insert: <strong> Santa City, NN insert: </strong> website-if-available: insert: <strong> http://www.nsb.nn insert: </strong> insert: <br />
% Is this request being sent by a sponsoring LIR on behalf of % an End User? (Yes/No) insert: <br />
end-user-of-sponsoring-lir: insert: <strong> Yes insert: </strong> insert: <br />
% 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) insert: <br />
confirmation: insert: <strong> Yes insert: </strong> insert: <br />
% Does this End User already have address space that can be processed any further, you used for % this assignment? (Yes/No) insert: <br />
space-available: insert: <strong> No insert: </strong> insert: </pre>
insert: </blockquote>
insert: <p>

Enter the legal name and primary location of the organisation that will need to delete: <br /> complete the enclosed templates and return them to the appropriate delete: <br /> organisation responsible for issuing IP network numbers. In most cases delete: <br /> use this will be your IP service provider or the RIPE NCC. Before delete: <br /> completion of the template, please be sure to read the following text delete: <br /> and examples carefully which will guide you. delete: <br /> delete: <br /> A new classless IP addressing scheme called CIDR PI address space in the "legal-organisation-name" and "organisation-location" fields. If this End User has recently been delete: <br /> adopted to cope with routing table growth and address space exhaustion delete: <br /> problems in the Internet. Under a website, enter the URL in the "website-if-available" field. Otherwise, enter "none" in this scheme it is beneficial for delete: <br /> everyone to get their network numbers allocated via their respective delete: <br /> IP service providers. Your IP service provider is the organisation delete: <br /> providing external connectivity to your network. field. insert: </p>

insert: <p>

If you are planning delete: <br /> an LIR sending this request on behalf of an End User, you should answer ‘Yes' in the “end-user-of-sponsoring-lir” field. insert: </p>

insert: <p>

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 connect End Users if there is a signed 'End User Assignment Agreement' between the sponsoring LIR and the End User. insert: </p>

insert: <p>

You can find an example agreement online. insert: </p>

insert: <p>

You can send us an agreement in your network local language or use the English version. insert: </p>

insert: <p>

If this request is sent by a Direct Assignment User, you answer “No” to other networks outside your organisation in delete: <br /> the foreseeable future we strongly urge 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: </p>

insert: <p>

If there is any address space assigned to get numbers allocated delete: <br /> from your current or prospective IP service provider. Alternatively, if delete: <br /> this End User that is not likely, then 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 insert: </p>

insert: <h2>

insert: <a id="initial" name="initial"> insert: </a> Initial Information insert: </h2>

insert: <blockquote>
insert: <pre>
 #[INITIAL INFORMATION]# % % Why is PI address space required rather than PA address % space?  insert: </pre> 
insert: <pre>
 why-pi:  insert: <strong>  insert: <span class="arial-small">  North SantaBank  will be allocated  multihomed. We cannot use PA address space because our uplinks do not allow their address space to be announced by other Autonomous Systems.  insert: </span>  insert: </strong>  insert: </pre> 
insert: <pre>
 % Is the End User requesting extra address space for routing % and/or administrative reasons? (Yes/No)  insert: </pre> 
insert: <pre>
 routing-reasons:  insert: <strong>  insert: <span class="arial-small">  No.  insert: </span>  insert: </strong>  insert: </pre> 
insert: <pre>
 % Have you made the End User aware of the consequences and % disadvantages of PI address space? (Yes/No)  insert: </pre> 
insert: <pre>
 confirmation:  insert: <strong>  insert: <span class="arial-small">  Yes.  insert: </span>  insert: </strong>  insert: </pre> 
insert: </blockquote>
insert: <p>

In the " insert: <span class="pre"> why-pi: insert: </span> " 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. insert: </p>

insert: <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 " insert: <span class="pre"> routing-reasons: insert: </span> " field. insert: </p>

insert: <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 " insert: <span class="pre"> confirmation: insert: </span> " 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". insert: </p>

insert: <h2>

insert: <a id="plan" name="plan"> insert: </a> Addressing Plan insert: </h2>

insert: <blockquote>
insert: <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  insert: </pre> 
insert: <pre>
 subnet:  insert: <strong>  /26 32 64 64  insert: <span class="arial-small">  Employee VPN Access  insert: </span>  insert: </strong>  subnet:  insert: <strong>  /26 18 34 64  insert: <span class="arial-small">  Financial Services  insert: </span>  insert: </strong>  subnet:  insert: <strong>  /26 22 30 60  insert: <span class="arial-small">  Workstations  insert: </span>  insert: </strong>  subnet:  insert: <strong>  /27 11 15 28  insert: <span class="arial-small">  Public Services  insert: </span>  insert: </strong>  subnet:  insert: <strong>  /27 7 18 30  insert: <span class="arial-small">  Operations  insert: </span>  insert: </strong>  subnet:  insert: <strong>  /24 176 192 240  insert: <span class="arial-small">  Branch Offices  insert: </span>  insert: </strong>  totals:  insert: <strong>  /23 266 353 486  insert: </strong>  insert: </pre> 
insert: <pre>
 number-of-subnets:  insert: <strong>  6  insert: </strong>  insert: </pre> 
insert: <pre>
 % Will the End User return any address space?  insert: </pre> 
insert: <pre>
 address-space-returned:  insert: <strong>  insert: <span class="arial-small">  85.118.187/24 to nl.bluelight in 3 months  insert: </span>  insert: </strong>  insert: </pre> 
insert: </blockquote>
insert: <p>

The addressing plan shows how the End User will use the requested address space. insert: </p>

insert: <p>

You can repeat the " insert: <span class="pre"> subnet: insert: </span> " row as many times as needed. Delete any empty " insert: <span class="pre"> subnet: insert: </span> " fields before you send the request. insert: </p>

insert: <p>

In the " insert: <span class="pre"> Subnet size (/nn): insert: </span> " column, enter a slash notation prefix for each subnet. Each entry should be large enough to contain the number from of addresses needed for that subnet over the next two years. insert: </p>

insert: <p>

In the " insert: <span class="pre"> Within 3 months: insert: </span> ", " insert: <span class="pre"> Within 1 year: insert: </span> " and " insert: <span class="pre"> Within 2 years: insert: </span> " 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). insert: </p>

insert: <p>

In the " insert: <span class="pre"> Purpose: insert: </span> " column, write a different delete: <br /> part of the short description of each subnet. If needed, you can write a more detailed description in the " insert: <span class="pre"> Network Description: insert: </span> " section at the end of this form. insert: </p>

insert: <p>

In the " insert: <span class="pre"> totals: insert: </span> " row, add the totals of each column. The total of the " insert: <span class="pre"> Subnet size (/nn): insert: </span> " column should be the total amount of address space by the RIPE NCC. Please pay careful attention delete: <br /> you are requesting for this assignment. insert: </p>

insert: <p>

In the " insert: <span class="pre"> number-of-subnets: insert: </span> " field, enter the total number of subnets listed in the addressing plan. insert: </p>

insert: <p>

If there is any address space assigned to the End User that they will return, list each prefix in separate " insert: <span class="pre"> address-space-returned: insert: </span> " 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 matter. delete: <br /> delete: <br /> Class A and B network numbers are a scarce resource and some delete: <br /> justification in terms of expected network size and structure field. insert: </p>

insert: <h2>

insert: <a id="equipment" name="equipment"> insert: </a> Equipment Description insert: </h2>

insert: <blockquote>
insert: <pre>
 #[EQUIPMENT DESCRIPTION]# % % What equipment  will be delete: <br /> needed before such a number  used and how will it use the % requested address space?  insert: </pre> 
insert: <pre>
 equipment-name:  insert: <strong>  insert: <span class="arial-small">  Core switches  insert: </span>  insert: </strong>  manufacturer-name:  insert: <strong>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </strong>  model-number:  insert: <strong>  insert: <span class="arial-small">  25xx  insert: </span>  insert: </strong>  other-data:  insert: <strong>  insert: <span class="arial-small">  3 units  insert: </span>  insert: </strong>  insert: </pre> 
insert: <pre>
 equipment-name:  insert: <strong>  insert: <span class="arial-small">  Servers  insert: </span>  insert: </strong>  manufacturer-name:  insert: <strong>  insert: <span class="arial-small">  HP  insert: </span>  insert: </strong>  model-number:  insert: <strong>  insert: <span class="arial-small">  various  insert: </span>  insert: </strong>  other-data:  insert: <strong>  insert: <span class="arial-small">  40 units  insert: </span>  insert: </strong>  insert: </pre> 
insert: <pre>
 equipment-name:  insert: <strong>  insert: <span class="arial-small">  Firewalls  insert: </span>  insert: </strong>  manufacturer-name:  insert: <strong>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </strong>  model-number:  insert: <strong>  insert: <span class="arial-small">  PIX 515 E  insert: </span>  insert: </strong>  other-data:  insert: <strong>  insert: <span class="arial-small">  2 units, 8 IP addresses  insert: </span>  insert: </strong>  insert: </pre> 
insert: <pre>
 equipment-name:  insert: <strong>  insert: <span class="arial-small">  Workstations  insert: </span>  insert: </strong>  manufacturer-name:  insert: <strong>  insert: <span class="arial-small">  Dell  insert: </span>  insert: </strong>  model-number:  insert: <strong>  insert: <span class="arial-small">  GX150  insert: </span>  insert: </strong>  other-data:  insert: <strong>  insert: <span class="arial-small">  22 units, 1 IP address each  insert: </span>  insert: </strong>  insert: </pre> 
insert: <pre>
 equipment-name:  insert: <strong>  insert: <span class="arial-small">  Routers  insert: </span>  insert: </strong>  manufacturer-name:  insert: <strong>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </strong>  model-number:  insert: <strong>  insert: <span class="arial-small">  3825  insert: </span>  insert: </strong>  other-data:  insert: <strong>  insert: <span class="arial-small">  2 units  insert: </span>  insert: </strong>  insert: </pre> 
insert: <pre>
 equipment-name:  insert: <strong>  insert: <span class="arial-small">  Routers  insert: </span>  insert: </strong>  manufacturer-name:  insert: <strong>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </strong>  model-number:  insert: <strong>  insert: <span class="arial-small">  AS5300  insert: </span>  insert: </strong>  other-data:  insert: <strong>  insert: <span class="arial-small">  1 unit, 32 ports  insert: </span>  insert: </strong>  insert: </pre> 
insert: </blockquote>
insert: <p>

The equipment description will help us to understand the requirements listed in the addressing plan and can be allocated. Class A numbers will only delete: <br /> be assigned to networks which technically need more than 65000 hosts to delete: <br /> be on one network number. A detailed technical justification is needed, delete: <br /> review takes place on a global scale and the allocation process can take delete: <br /> several months. Similarly due to class B scarcity, a reasonable repeated as many times as needed. Leave an empty line before each new " insert: <span class="pre"> equipment-name: insert: </span> " field. insert: </p>

insert: <p>

In the " insert: <span class="pre"> equipment-name: insert: </span> " field, enter the type of equipment requiring address space from this assignment. insert: </p>

insert: <p>

Enter the vendor name and model number delete: <br /> of class C numbers will be assigned over class B. If you can engineer delete: <br /> your network to use multiple class C numbers, it is strongly advised. delete: <br /> Please note that this is contrary to earlier recommendations where it delete: <br /> was recommended to use Bs over multiple Cs due to routing table size delete: <br /> constraints. A one page document detailing the information needed by delete: <br /> the NCC to evaluate requests for class B numbers is available from the delete: <br /> NCC if it is not enclosed with this letter; this document also includes delete: <br /> a list of recommended reading about CIDR and address allocation in delete: <br /> general. delete: <br /> delete: <br /> Appended to this letter is a blank template for IP number registration, delete: <br /> which we would be extremely grateful if you complete and return to the delete: <br /> appropriate organisation responsible for issuing IP network numbers. In delete: <br /> most cases this will be your IP service provider. It may of course also delete: <br /> be the RIPE NCC. delete: <br /> delete: <br /> the piece of equipment in the " insert: <span class="pre"> manufacturer-name: insert: </span> " and " insert: <span class="pre"> model-number insert: </span> :" fields. insert: </p>

insert: <p>

If you have any further queries please do not hesitate more information about how this piece of equipment will use the requested address space, add this in the " insert: <span class="pre"> other-data: insert: </span> " field. insert: </p>

insert: <h2>

insert: <a id="network" name="network"> insert: </a> Network Description insert: </h2>

insert: <blockquote>
insert: <pre>
 #[NETWORK DESCRIPTION]# % % Please add more information if you think it will help us % understand this request.  insert: </pre> 
insert: <pre>
 insert: <strong>  insert: <span class="arial-small">  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.  insert: </span>  insert: </strong>  insert: <strong>  insert: <span class="arial-small">  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  insert: </span>  insert: </strong>  insert: </pre> 
insert: </blockquote>
insert: <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 contact the delete: <br /> NCC. evaluate your request more quickly. insert: </p>

insert: <h2>

insert: <a id="diagram" name="diagram"> insert: </a> Network Diagram insert: </h2>

insert: <blockquote>
insert: <pre>
 #[NETWORK DIAGRAM]# % % Have you attached a network diagram to this request? (Yes/No) diagram-attached:  insert: <strong>  insert: <span class="arial-small">  Yes  insert: </span>  insert: </strong>  insert: </pre> 
insert: </blockquote>
insert: <p>

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

insert: <h2>

insert: <a id="database" name="database"> insert: </a> Database Template(s) insert: </h2>

insert: <blockquote>
insert: <pre>
 #[DATABASE TEMPLATE(S)]# % %  Please note that  complete  all queries should,  of the fields below. inetnum: netname:  insert: <strong>  insert: <span class="arial-small">  NSB-NET  insert: </span>  insert: </strong>  descr:  insert: <strong>  insert: <span class="arial-small">  North SantaBank  insert: </span>  insert: </strong>  country:  insert: <strong>  insert: <span class="arial-small">  NN  insert: </span>  insert: </strong>  org:  insert: <strong>  insert: <span class="arial-small">  ORG-NS31-RIPE  insert: </span>  insert: </strong>  admin-c:  insert: <strong>  insert: <span class="arial-small">  ACM2-RIPE  insert: </span>  insert: </strong>  tech-c:  insert: <strong>  insert: <span class="arial-small">  HOHO1-RIPE  insert: </span>  insert: </strong>  status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-lower: RIPE-NCC-END-MNT mnt-by:  insert: <strong>  insert: <span class="arial-small">  SANTA-MNT  insert: </span>  insert: </strong>  mnt-routes:  insert: <strong>  insert: <span class="arial-small">  SANTA-MNT  insert: </span>  insert: </strong>  mnt-domains:  insert: <strong>  insert: <span class="arial-small">  SANTA-MNT  insert: </span>  insert: </strong>  changed: hostmaster@ripe.net source: RIPE  insert: </pre> 
insert: </blockquote>
insert: <p>

Leave the " insert: <span class="pre"> inetnum: insert: </span> " field empty as we will choose the address range. insert: </p>

insert: <p>

The " insert: <span class="pre"> netname: insert: </span> " should be a short and descriptive name for the network and should reflect the organisation name of the End User. insert: </p>

insert: <p>

Enter the End User's organisation name in the " insert: <span class="pre"> descr insert: </span> :" field. insert: </p>

insert: <p>

Use the ISO country code of the End User's location in the " insert: <span class="pre"> country: insert: </span> " field. If the End User is multi-national, repeat the " insert: <span class="pre"> country: insert: </span> " field as many times as needed. Alternatively, you can use EU or ZZ if possible, be made through delete: <br /> e-mail and sent to <hostmaster@ripe.net>. If you do not have access wish to delete: <br /> electronic mail, then we prefer to communicate by fax rather than by delete: <br /> ordinary mail. show the End User's location in the insert: <strong> inetnum insert: </strong> object. insert: </p>

insert: <p>

Enter the org-ID of the End User's organisation object in the " insert: <span class="pre"> org: insert: </span> " field. insert: </p>

insert: <p>

The nic-handle of the role or person object in the " insert: <span class="pre"> admin-c: insert: </span> " field should reflect someone who is administratively responsible for the network. insert: </p>

insert: <p>

The nic-handle of the role or person object in the " insert: <span class="pre"> tech-c: insert: </span> " field should reflect someone who has technical knowledge of the network. insert: </p>

insert: <p>

The " insert: <span class="pre"> status: insert: </span> " field must be ASSIGNED PI . insert: </p>

insert: <p>

The " insert: <span class="pre"> mnt-by: insert: </span> " and " insert: <span class="pre"> mnt-lower: insert: </span> " fields must contain insert: <span class="pre"> RIPE-NCC-END-MNT insert: </span> . You can reach us at: delete: <br /> delete: <br /> Kruislaan 409 Phone: +31 20 592 5065 delete: <br /> NL-1098 SJ Amsterdam Telefax: +31 20 592 5090 delete: <br /> put the LIR's or End User's maintainers in separate " insert: <span class="pre"> mnt-by: insert: </span> ", " insert: <span class="pre"> mnt-routes: insert: </span> " and " insert: <span class="pre"> mnt-domains: insert: </span> " fields. insert: </p>

insert: <p>

The Netherlands delete: <br /> delete: <br /> If we do not hear from you in the near future we will assume " insert: <span class="pre"> mnt-by: insert: </span> " field shows which maintainer authenticates object updates. The " insert: <span class="pre"> mnt-routes: insert: </span> " and " insert: <span class="pre"> mnt-domains: insert: </span> " fields show which maintainers authenticate the creation of route and domain objects. insert: </p>

insert: <p>

The RIPE Database must contain all of the objects that you use. insert: </p>

insert: <p>

The " insert: <span class="pre"> changed: insert: </span> " field must be insert: <span class="pre"> hostmaster@ripe.net insert: </span> . insert: </p>

insert: <p>

The " insert: <span class="pre"> source: insert: </span> " field must be insert: <span class="pre"> RIPE insert: </span> . insert: </p>

insert: <h2>

insert: <a id="end" name="end"> insert: </a> End of Request insert: </h2>

insert: <blockquote>
insert: <pre>
 #[END of REQUEST]#  insert: </pre> 
insert: <pre>
 insert: <strong>  insert: <span class="arial-small">  Best Regards  insert: </span>  ,  
have contacted insert: </strong>
insert: <strong> insert: <span class="arial-small"> Jan Janssen, Bluelight Admin insert: </span> insert: </strong> insert: </pre>
insert: </blockquote>
insert: <p>

Please write your IP service provider. delete: <br /> delete: <br /> Yours sincerely, delete: <br /> delete: <br /> delete: <br /> delete: <br /> The RIPE NCC staff delete: </p> full name below the " insert: <span class="pre"> #[END of REQUEST]# insert: </span> " header. insert: </p>

RIPE Internet Network Numbers Template Supporting Notes for the Provider Independent (PI) Assignment Request Form