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.
Appended to this letter is a blank template for IP number registration,
which we would be extremely grateful if you complete and return to the
appropriate organisation responsible for issuing IP network numbers. In
most cases this will be your IP service provider. It may of course also
be the RIPE NCC.
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]>.
This document contains instructions for LIRs on how to complete the “Provider Aggregatable (PA) Assignment Request Form Link: /publications/docs/ripe-488/ ”.
The instructions are based on the “IPv4 Address Allocation and Assignment Policy for the RIPE region”.
LIRs should send separate “Provider Aggregatable (PA) Assignment Request” forms for each End User.
#[GENERAL INFORMATION]#
%
% Please add your RegID.
%
% request-type: pa-ipv4
form-version: 1.2
x-ncc-regid: nl.bluelight
Please do not change the value of the “request-type:” and “form-version:” fields.
#[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 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 at the end of this form.
#[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 Periodsubnet: /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 too will the information required:
Up to 30 June 2010, assignments are for a period of up to twelve months. Therefore, your request should reflect your immediate requirements, predicted requirements for the coming six months, and predicted requirements for the coming twelve months.
As of 1 July 2010, assignments are for a period of up to nine months. Your request should reflect your immediate requirements, predicted requirements for the coming six months, and predicted requirements for the coming nine months.
As of 1 January 2011, assignments are for period of up to six months. Your request should reflect your immediate requirements, predicted requirements for the coming three months, and predicted requirements for the coming six months.
As of 1 July 2011, assignments are for a period of up to three months. Your request should reflect your immediate requirements, predicted requirements for the coming two months, and predicted requirements for the coming three 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 total 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.
The “netname:” should be a short, descriptive name for the network and should reflect the End User's organisation name. You should use the same “netname:” when you register this assignment in the RIPE Whois Database.
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]#
%
% 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 unitsequipment-name: Servers
manufacturer-name: HP
model-number: various
other-data: 40 unitsequipment-name: Firewalls
manufacturer-name: Cisco
model-number: PIX 515 E
other-data: 2 units, 8 IP addressesequipment-name: Workstations
manufacturer-name: Dell
model-number: GX150
other-data: 22 units, 1 IP address eachequipment-name: Routers
manufacturer-name: Cisco
model-number: 3825
other-data: 2 unitsequipment-name: Routers
manufacturer-name: Cisco
model-number: AS5300
other-data: 1 unit, 32 ports
The equipment description will help us (RIPE NCC) 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]#
%
% 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 when we evaluate your request. A clearer understanding of the network and its addressing needs can help us to evaluate your request more quickly.
#[NETWORK DIAGRAM]#
%
% Have you attached a network diagram to this request? (Yes/No)diagram-attached: Yes
A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs.
#[END of REQUEST]#Best Regards,
Jan Janssen, Bluelight Admin
Please write your full name below the “#[END of REQUEST]#” header.