RIPE Internet Network Numbers Template

D.Karrenberg

Aug 1992

To whom it may concern,

The RIPE Network Coordination Centre now handles all requests for IP network numbers from European organisations. Our aim is to provide a rapid and efficient service to all European organisations. As this is a recent initiative, procedures for handling network number requests are in the process of being established. Therefore we apologise in advance for any duplication of effort that may be required by you due to new forms and templates. As the European NIC, we require different information to that required by the US and for it to be presented in a format which is both easy for you to complete and for us to process. Before your application can be processed any further, you will need to complete the enclosed templates and return them to the appropriate organisation responsible for issuing IP network numbers. In most cases this will be your IP service provider or the RIPE NCC. Before completion of the template, please be sure to read the following text and examples carefully which will guide you.

A new classless IP addressing scheme called CIDR has recently been adopted to cope with routing table growth and address space exhaustion problems in the Internet. Under this scheme it is beneficial for everyone to get their network numbers allocated via their respective IP service providers. Your IP service provider is the organisation providing external connectivity to your network. If you are planning to connect your network to other networks outside your organisation in the foreseeable future we strongly urge you to get numbers allocated from your current or prospective IP service provider. Alternatively, if this is not likely, then you will be allocated a number from a different part of the address space by the RIPE NCC. Please pay careful attention to this matter.

Class A and B network numbers are a scarce resource and some justification in terms of expected network size and structure will be needed before such a number can be allocated. Class A numbers will only be assigned to networks which technically need more than 65000 hosts to be on one network number. A detailed technical justification is needed, review takes place on a global scale and the allocation process can take several months. Similarly due to class B scarcity, a reasonable number of class C numbers will be assigned over class B. If you can engineer your network to use multiple class C numbers, it is strongly advised. Please note that this is contrary to earlier recommendations where it
was recommended to use Bs over multiple Cs due to routing table size constraints. A one page document detailing the information needed by the NCC to evaluate requests for class B numbers is available from the NCC if it is not enclosed with this letter; this document also includes a list of recommended reading about CIDR and address allocation in general.

This document contains instructions for LIRs on how to complete the "Provider Independent (PI) Assignment Request Form Link: https://www.ripe.net/publications/docs/pi-requestform.html ".

The instructions are based on the "IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region Link: https://www.ripe.net/publications/docs/ipv4-policies.html ".

• General Information Link: #info
• Address Space User Link: #user
• Initial Information Link: #initial
• Addressing Plan Link: #plan
• Equipment Description Link: #equipment
• Network Description Link: #network
• Supporting Documentation Link: #documentation
• Database Template(s) Link: #database
• End of Request Link: #end

General Information

#[GENERAL INFORMATION]#
%
% Please add your RegID.

request-type: pi-ipv4
form-version: 1.3
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: <country code>.<name>. If you do not know your RegID, please contact [email protected] Link: mailto:[email protected] .

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


% Is this request being sent by a sponsoring LIR on behalf of 
% an End User? (Yes/No)

end-user-of-sponsoring-lir: Yes

% 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)

confirmation: Yes

% Does this End User already have address space that can be used for 
% this assignment? (Yes/No)

space-available:  No

If you have any further queries please do not hesitate to contact the NCC. Please note that all queries should, if possible, be made through e-mail and sent to <[email protected]>. If the request is for an LIR, you should also answer with "No".

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 document "IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region".

Addressing Plan

#[ADDRESSING PLAN]#
% As of 1 January 2010 assignments are for a period of up to 12 months.
% As of 1 July 2010 assignments are for a period of up to 9 months.
% As of 1 January 2011 assignments are for a period of up to 6 months.
% As of 1 July 2011 assignments are for a period of up to 3 months.

%
% How will the End User use this address space?
%

%       Subnet       Immediate    Intermediate  Entire      Purpose
%       size (/nn)   Requirement  Requirement   Period
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 time period.

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).
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:

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.

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
the coming 9 months.

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
the coming 6 months.

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.

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: <x.x.x.x/xx> to <which LIR/ISP> in <time period> for this field.

Equipment Description

#[EQUIPMENT DESCRIPTION]#
%
% What equipment will be used and how will it use the requested
% address space?

equipment-name: Core switches
manufacturer-name: Cisco
model-number: 25xx
other-data: 3 units

equipment-name: Servers
manufacturer-name: HP
model-number: various
other-data: 40 units

equipment-name: Firewalls
manufacturer-name: Cisco
model-number: PIX 515 E
other-data: 2 units, 8 IP addresses

equipment-name: Workstations
manufacturer-name: Dell
model-number: GX150
other-data: 22 units, 1 IP address each

equipment-name: Routers
manufacturer-name: Cisco
model-number: 3825
other-data: 2 units

equipment-name: Routers
manufacturer-name: Cisco
model-number: AS5300
other-data: 1 unit, 32 ports

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.

In the "equipment-name" field, enter the type of equipment requiring address space from this assignment.

Enter the vendor name and model number for the piece of equipment in the "manufacturer-name" and "model-number" fields.

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.

Network Description

#[NETWORK DESCRIPTION]#
%
% Please add more information if you think it will help us understand
% this request.

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.

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

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.

Supporting Documentation

#[SUPPORTING DOCUMENTATION]#
%
% If this request is being sent by a sponsoring LIR on behalf of
% an End User, please attach a copy of the signed "End User Assignment
% Agreement" and the company registration papers of the End User.
% You can also attach a network diagram or other supporting
% documentation.
%
% Have you attached any files/documents to this request? (Yes/No)

file-attached: Yes

Phone: +31 20 592 5065
Telefax: +31 20 592 5090
Kruislaan 409
NL-1098 SJ Amsterdam
The Netherlands

If we do not hear from you in the near future we will assume that you have contacted your IP service provider.

Yours sincerely,

The RIPE NCC staff

Database Template(s)

#[DATABASE TEMPLATE(S)]#
%
% Please complete all of the fields below.

inetnum:
netname: NSB-NET
descr: North SantaBank
country: NN
org: ORG-NS31-RIPE
admin-c: ACM2-RIPE
tech-c: HOHO1-RIPE
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-lower: RIPE-NCC-END-MNT
mnt-by: SANTA-MNT
mnt-routes: SANTA-MNT
mnt-domains: SANTA-MNT
changed: [email protected]
source: RIPE

Leave the "inetnum" field empty as we will choose the address range.

The "netname" should be a short and descriptive name for the network and should reflect the organisation name of the End User.

Enter the End User's organisation name in the "descr" field.

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 inetnum object.

Enter the org-ID of the End User's organisation object in the "org" field.

The nic-handle of the role or person object in the "admin-c" field should reflect someone who is administratively responsible for the network.

The nic-handle of the role or person object in the "tech-c" field should reflect someone who has technical knowledge of the network.

The "status" field must be ASSIGNED PI.

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.

The "mnt-by" field shows which maintainer authenticates object updates. The "mnt-routes" and "mnt-domains" fields show which maintainers authenticate the creation of route and domain objects.

The RIPE Database must contain all of the objects that you use.

The "changed" field must be [email protected].

The "source" field must be RIPE.

End of Request

Best Regards,

Jan Janssen, Bluelight Admin

Please write your full name below the "#[END of REQUEST]#" header.