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-537: This document contains instructions for LIRs on how to complete the "Provider Independent (PI) Assignment Request Form".
delete: <p style="text-align: left; "> insert: <p class="p1">

insert: <a data-val="046f7e54-4540-4541-adff-aceeea440a2f" href="resolveuid/046f7e54-4540-4541-adff-aceeea440a2f" data-linktype="internal" class="internal-link"> This RIPE Internet document has been obsoleted due to the RIPE NCC reaching the last /8 of IPv4 address space. insert: </a> insert: </p>

insert: <p>

This document contains instructions for LIRs on how to complete the " insert: <a href="https://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="https://www.ripe.net/publications/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region insert: </a> ". insert: </p>

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

insert: <a> insert: <strong> insert: </strong> insert: </a> insert: </p>

insert: <h2>

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

insert: <pre>
 #[GENERAL INFORMATION]#  insert: <br /> 
% insert: <br />
% Please add your RegID. insert: <br />
insert: <br />
request-type: pi-ipv4 insert: <br />
form-version: 1.3 insert: <br />
x-ncc-regid: insert: <strong> nl.bluelight insert: </strong> insert: </pre>
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: <p>

insert: <a name="user"> insert: </a> insert: </p>

insert: <h2>

Address Space User insert: </h2>

insert: <pre>
 #[ADDRESS SPACE USER]#  insert: <br /> 
% insert: <br />
% Who will use the requested address space? insert: <br />
insert: <br />
insert: <br />
legal-organisation-name: insert: <strong> North SantaBank insert: </strong> insert: <br />
organisation-location: insert: <strong> Santa City, NN insert: </strong> insert: <br />
website-if-available: insert: <strong> http://www.nsb.nn insert: </strong> insert: <br />
insert: <br />
insert: <br />
% Is this request being sent by a sponsoring LIR on behalf of insert: <br />
% an End User? (Yes/No) insert: <br />
insert: <br />
end-user-of-sponsoring-lir: insert: <strong> Yes insert: </strong> insert: <br />
insert: <br />
% If yes, please confirm that the "End User Assignment Agreement" insert: <br />
% contains all of the elements listed in paragraph 2.0 of "Contractual insert: <br />
% Requirements for Provider Independent Resource Holders in the insert: <br />
% RIPE Network Coordination Centre now handles all requests 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 NCC Service Region".(Yes/No) insert: <br />
insert: <br />
confirmation: insert: <strong> Yes insert: </strong> insert: <br />
insert: <br />
% Does 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 End User already have address space 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 to complete and for us to process. delete: <br /> Before your application can be processed any further, you used for insert: <br />
% this assignment? (Yes/No) insert: <br />
insert: <br />
space-available: insert: <strong> No insert: </strong> insert: </pre>
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: <br />
insert: <br />
If you are planning delete: <br /> to connect an LIR sending this request on behalf of an End User, you should answer "Yes" in the "end-user-of-sponsoring-lir" field. insert: <br />
insert: <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. 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. insert: <br />
insert: <br />
You can find an example agreement online: insert: <br />
insert: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/membership/lir-end-user-agreement.html insert: </a> insert: <br />
insert: <br />
You can send us an agreement in your network to other networks outside your organisation in delete: <br /> the foreseeable future we strongly urge local language or use the English version. insert: <br />
insert: <br />
If this request is sent by a Direct Assignment User, you to get numbers allocated delete: <br /> from your current or prospective IP service provider. Alternatively, if delete: <br /> 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". insert: </p>

insert: <p>

If there is any address space assigned to this End User that is not likely, 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: <p>

insert: </p>

insert: <h2>

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

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

The RIPE NCC will assign additional IPv4 addresses to an End User in order to make the assignment size a multiple of a /24 if the End User demonstrates the intent to announce this address space for the purpose of multihoming to two or more Autonomous Systems (AS) which the End User does not own or control. Cumulatively, no more than 255 additional IPv4 addresses may be assigned to any particular End User for the purposes outlined above. 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 NCC Service Region". insert: </p>

insert: <p>

insert: <a name="plan"> insert: </a> insert: </p>

insert: <h2>

Addressing Plan insert: </h2>

insert: <pre>
 #[ADDRESSING PLAN]#  insert: <br /> 
% As of 1 January 2010 assignments are for a period of up to 12 months. insert: <br />
% As of 1 July 2010 assignments are for a period of up to 9 months. insert: <br />
% As of 1 January 2011 assignments are for a period of up to 6 months. insert: <br />
% As of 1 July 2011 assignments are for a period of up to 3 months. insert: </pre>
insert: <pre>
 %  insert: <br /> 
% How will the End User use this address space? insert: <br />
% insert: </pre>
insert: <pre>
 % Subnet Immediate Intermediate Entire Purpose  insert: <br /> 
% size (/nn) Requirement Requirement Period insert: <br />
subnet: insert: <strong> /26 32 64 64 Employee VPN Access insert: </strong> insert: <br />
subnet: insert: <strong> /26 18 34 64 Financial Services insert: </strong> insert: <br />
subnet: insert: <strong> /26 22 30 60 Workstations insert: </strong> insert: <br />
subnet: insert: <strong> /27 11 15 28 Public Services insert: </strong> insert: <br />
subnet: insert: <strong> /27 7 18 30 Operations insert: </strong> insert: <br />
subnet: insert: <strong> /24 176 192 240 Branch Offices insert: </strong> insert: <br />
totals: insert: <strong> /23 266 353 486 insert: </strong> insert: <br />
insert: </pre>
insert: <pre>
 number-of-subnets:  insert: <strong>  6  insert: </strong>  insert: </pre> 
insert: <p>

% Will the End User return any address space? insert: </p>

insert: <pre>
 address-space-returned:  insert: <strong>  85.118.187/24 to nl.bluelight in 3 months  insert: </strong>  insert: <br /> 
insert: </pre>
insert: <p>

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

insert: <p>

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

insert: <p>

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. insert: </p>

insert: <p>

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 allocated separated by comma(s) with no blank spaces (for example, /25,/27). insert: <br />
Starting on 1 January 2010, a number from a different delete: <br /> part of the address space by the RIPE NCC. Please pay careful attention delete: <br /> to 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 gradual reduction in the assignment period will be delete: <br /> needed before such applied. As the assignment period changes, so to will the information required: insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

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 insert: <br />
the coming 9 months. insert: </p>

insert: <p>

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 insert: <br />
the coming 6 months. insert: </p>

insert: <p>

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. insert: </p>

insert: <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 at the end of this form. insert: <br />
insert: <br />
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. insert: <br />
insert: <br />
In the "number-of-subnets" field, enter the total number of subnets listed in the addressing plan. insert: <br />
insert: <br />
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. insert: </p>

insert: <p>

insert: <a name="equipment"> insert: </a> insert: </p>

insert: <h2>

Equipment Description insert: </h2>

insert: <pre>
 #[EQUIPMENT DESCRIPTION]#  insert: <br /> 
% insert: <br />
% What equipment will be used and how will it use the requested insert: <br />
% address space? insert: <br />
insert: <br />
equipment-name: insert: <strong> Core switches insert: </strong> insert: <br />
manufacturer-name: insert: <strong> Cisco insert: </strong> insert: <br />
model-number: insert: <strong> 25xx insert: </strong> insert: <br />
other-data: insert: <strong> 3 units insert: </strong> insert: <br />
insert: <br />
equipment-name: insert: <strong> Servers insert: </strong> insert: <br />
manufacturer-name: insert: <strong> HP insert: </strong> insert: <br />
model-number: insert: <strong> various insert: </strong> insert: <br />
other-data: insert: <strong> 40 units insert: </strong> insert: <br />
insert: <br />
equipment-name: insert: <strong> Firewalls insert: </strong> insert: <br />
manufacturer-name: insert: <strong> Cisco insert: </strong> insert: <br />
model-number: insert: <strong> PIX 515 E insert: </strong> insert: <br />
other-data: insert: <strong> 2 units, 8 IP addresses insert: </strong> insert: <br />
insert: <br />
equipment-name: insert: <strong> Workstations insert: </strong> insert: <br />
manufacturer-name: insert: <strong> Dell insert: </strong> insert: <br />
model-number: insert: <strong> GX150 insert: </strong> insert: <br />
other-data: insert: <strong> 22 units, 1 IP address each insert: </strong> insert: <br />
insert: <br />
equipment-name: insert: <strong> Routers insert: </strong> insert: <br />
manufacturer-name: insert: <strong> Cisco insert: </strong> insert: <br />
model-number: insert: <strong> 3825 insert: </strong> insert: <br />
other-data: insert: <strong> 2 units insert: </strong> insert: <br />
insert: <br />
equipment-name: insert: <strong> Routers insert: </strong> insert: <br />
manufacturer-name: insert: <strong> Cisco insert: </strong> insert: <br />
model-number: insert: <strong> AS5300 insert: </strong> insert: <br />
other-data: insert: <strong> 1 unit, 32 ports insert: </strong> insert: </pre>
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 "equipment-name" field. insert: <br />
insert: <br />
In the "equipment-name" field, enter the type of equipment requiring address space from this assignment. insert: <br />
insert: <br />
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. for the piece of equipment in the "manufacturer-name" and "model-number" fields.

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

insert: <p>

insert: <a name="network"> insert: </a> insert: </p>

insert: <h2>

Network Description insert: </h2>

insert: <pre>
 #[NETWORK DESCRIPTION]#  insert: <br /> 
% insert: <br />
% Please add more information if you think it will help us understand insert: <br />
% this request. insert: <br />
insert: <br />
insert: <strong> We have 11 branches across Santa City linked by corporate fibre insert: <br />
channels. We will assign a /28 subnet for each branch. Each branch insert: <br />
will have SMTP, WWW, file server, e-banking and dial-up pool. insert: <br />
insert: <br />
Public Internet Services: SMTP (2 IP addresses), WWW (6 IP addresses, insert: <br />
2 servers), FTP (1 IP address), DNS (2 IP addresses) Financial insert: <br />
Services: 6 servers, 3 IP addresses each. Operations network: insert: <br />
Security, Monitoring, VPN, Proxy, DNS insert: </strong>
insert: </pre>
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 evaluate your request more quickly. insert: </p>

insert: <p>

insert: <a name="documentation"> insert: </a> insert: </p>

insert: <h2>

Supporting Documentation insert: </h2>

insert: <pre>
 #[SUPPORTING DOCUMENTATION]#  insert: <br /> 
% insert: <br />
% If this request is being sent by a sponsoring LIR on behalf of insert: <br />
% an End User, please do not hesitate to contact the delete: <br /> NCC. Please note attach a copy of the signed "End User Assignment insert: <br />
% Agreement" and the company registration papers of the End User. insert: <br />
% You can also attach a network diagram or other supporting insert: <br />
% documentation. insert: <br />
% insert: <br />
% Have you attached any files/documents to this request? (Yes/No) insert: <br />
insert: <br />
file-attached: insert: <strong> Yes insert: </strong> insert: </pre>
insert: <p>

For each PI assignment that all queries should, if possible, be made is requested through delete: <br /> e-mail and sent to <hostmaster@ripe.net>. 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. insert: <br />
insert: <br />
If this request is for an LIR or a "Direct Assignment User", you do not have access to delete: <br /> electronic mail, then to attach a copy of 'End User Assignment Agreement' and company registration papers. insert: <br />
insert: <br />
A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. insert: </p>

insert: <p>

insert: <a name="database"> insert: </a> insert: </p>

insert: <h2>

Database Template(s) insert: </h2>

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

Leave the "inetnum" field empty as we prefer to communicate by fax rather than by delete: <br /> ordinary mail. will choose the address range. insert: <br />
insert: <br />
The "netname" should be a short and descriptive name for the network and should reflect the organisation name of the End User. insert: <br />
insert: <br />
Enter the End User's organisation name in the "descr" field. insert: <br />
insert: <br />
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 insert: <strong> inetnum insert: </strong> object. insert: <br />
insert: <br />
Enter the org-ID of the End User's organisation object in the "org" field. insert: <br />
insert: <br />
The nic-handle of the insert: <strong> role insert: </strong> or insert: <strong> person insert: </strong> object in the "admin-c" field should reflect someone who is administratively responsible for the network. insert: <br />
insert: <br />
The nic-handle of the insert: <strong> role insert: </strong> or insert: <strong> person insert: </strong> object in the "tech-c" field should reflect someone who has technical knowledge of the network. insert: <br />
insert: <br />
The "status" field must be ASSIGNED PI. insert: <br />
insert: <br />
The "mnt-by" and "mnt-lower" fields must contain RIPE-NCC-END-MNT. 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 put the LIR's or End User's maintainers in separate "mnt-by", "mnt-routes" and "mnt-domains" fields. insert: <br />

The Netherlands delete: <br /> delete: <br /> If we do not hear from you in the near future we will assume "mnt-by" field shows which maintainer authenticates object updates. The "mnt-routes" and "mnt-domains" fields show which maintainers authenticate the creation of insert: <strong> route insert: </strong> and insert: <strong> domain insert: </strong> objects. insert: <br />
insert: <br />
The RIPE Database must contain all of the objects that you delete: <br /> have contacted use. insert: <br />
insert: <br />
The "changed" field must be hostmaster@ripe.net. insert: <br />
insert: <br />
The "source" field must be RIPE. insert: </p>

insert: <p>

insert: <a name="end"> insert: </a> insert: </p>

insert: <h2>

End of Request insert: </h2>

insert: <pre>
 Best Regards,  insert: <br /> 
insert: <br />
Jan Janssen, Bluelight Admin insert: </pre>
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 "#[END of REQUEST]#" header. insert: </p>

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