You are here: Home > Publications > RIPE Document Store > IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region

Changes to IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-324: Obsolete: IPv4 Address Allocation and Assignment Policies for the ripe-065: RIPE NCC Service Region Internet Numbers Registration Procedures
insert: <p>

insert: <b> This document is obsoleted by ripe-72, version 0.7 of this documen insert: </b> t insert: </p>

This document describes the procedures for the reassignment of IP insert: <br />
network numbers from blocks obtained from the RIPE Network Coordination insert: <br />
Centre. It deals with items as providing information for the RIPE and insert: <br />
US NIC databases, as well as reassignment of IP addresses in light of insert: <br />
the "Supernetting" proposal, as documented in RFC 1338, by Vince Fuller insert: <br />
et al. insert: <br />
insert: <br />
insert: <br />
Introduction insert: <br />
insert: <br />
Since May 1st 1992, the RIPE Network Coordination Centre (NCC) is only available for download insert: <br />
acting as a PDF file. delegated registry for IP networks numbers to NICs and NOCs insert: <br />
in Europe. It is RIPE NCC policy not to give out network numbers to insert: <br />
individual organisations, who should refer in turn, to their IP network insert: <br />
service provider. insert: <br />
insert: <br />
The mission of the RIPE NCC is to give network numbers to the various insert: <br />
service providers and NICs. The NICs and NOCs can then reassign the insert: <br />
actual IP network numbers to organisations requesting IP network insert: <br />
numbers. insert: <br />
insert: <br />
insert: <br />
Class B Network Number Allocation Procedure insert: <br />
insert: <br />
Service providers can request Class B network numbers on a one-by-one insert: <br />
basis from the RIPE NCC. Because class B address space is a critical insert: <br />
resource, a request for a class B network number must be accompanied by insert: <br />
a justification in terms of the requesting organisation's size, current insert: <br />
network and expected network growth. The requestor should also make insert: <br />
clear why they cannot use a block of class C network numbers to achieve insert: <br />
their goals. The RIPE NCC will review requests using the same standards insert: <br />
as any other Internet Registry, particularly the US NIC. insert: <br />
insert: <br />
insert: <br />
Class C Allocation Procedures insert: <br />
insert: <br />
insert: <br />
NICs and NOCs accepting a block of class C numbers agree to adhere to insert: <br />
the following procedures: insert: <br />
insert: <br />
A) The RIPE NCC will assign complete class C blocks to individual NICs insert: <br />
and NOCs. They can be requested from <hostmaster@ripe.net>. insert: <br />
insert: <br />
B) In order to prevent implementation problems, network numbers ending insert: <br />
with 0 or 255 should NOT be reassigned. insert: <br />
insert: <br />
C) Full information about reassigned network numbers must be reported insert: <br />
back to the RIPE NCC and the US NIC in full RIPE database format (ref insert: <br />
ripe-13). The complete entries should be sent immediately after insert: <br />
reassignment to <ripe-dbm@ripe.net> and <hostmaster@nic.ddn.mil> insert: <br />
Unfortunately, the RIPE NCC is not yet ready to accept block entries for insert: <br />
the RIPE database, so you must send in each individual entry. insert: <br />
insert: <br />
D) Reassignment of class C network numbers should be done in a manner insert: <br />
that facilitates Supernetting (see next section). insert: <br />
insert: <br />
E) Requests for network numbers should be reasonable. All NICs and NOCs insert: <br />
should prevent stockpiling of network numbers. insert: <br />
insert: <br />
F) On first request from the RIPE NCC, the class C network numbers not insert: <br />
yet reassigned, must be returned to the RIPE NCC. insert: <br />
insert: <br />
insert: <br />
Supernetting insert: <br />
insert: <br />
NICs and NOCs reassigning IP network numbers are urgently requested to insert: <br />
read the Supernetting proposal by Vince Fuller et al. This document can insert: <br />
be obtained from the rfc section of the RIPE document store or other RFC insert: <br />
servers. It is called rfc1338.txt. insert: <br />
The Supernetting proposal was made to reduce the increase of routing insert: <br />
table size in the current Internet. It proposes to create a hierarchy insert: <br />
of IP network numbers, which can then be aggregated resulting in less insert: <br />
routing table entries in routing equipment. While this proposal has not insert: <br />
been formally adopted we expect that something at least along the same insert: <br />
principle will be implemented in the near future. insert: <br />
insert: <br />
Here is how it works: insert: <br />
insert: <br />
If an organisation A needs 8 class C network numbers, the numbers should insert: <br />
be given out in such a way that the routing information for each of insert: <br />
these 8 networks could appear as one entry with the correct mask in insert: <br />
routers. insert: <br />
insert: <br />
More concretely: insert: <br />
insert: <br />
Service provider S hands out networks 192.24.8 through 192.24.15 to insert: <br />
organisation A. These networks can then appear in routing equipment as a insert: <br />
supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C insert: <br />
network numbers appear as one routing table entry. insert: <br />
insert: <br />
The guidelines that can be derived from the Supernetting proposal are: insert: <br />
insert: <br />
A) Service providers should reserve blocks of class C network numbers from insert: <br />
their allocation for each organisations requesting class C network numbers. insert: <br />
insert: <br />
B) The size of these blocks should always be a power of 2. insert: <br />
insert: <br />
C) The numbers in these blocks should be contiguous. insert: <br />
insert: <br />
D) The blocks should start on bit boundaries. insert: <br />
(ie powers of 2, AND multiples of the block size) insert: <br />
insert: <br />
E) The blocks reserved for an organisation should be sufficient for a insert: <br />
reasonable expected growth over the next few years. insert: <br />
insert: <br />
F) Multi-homed organizations may obtain address space from one of their insert: <br />
providers, the RIPE NCC, or the global NIC, as is appropriate to their insert: <br />
network configuration. These organisations are strongly encouraged to insert: <br />
contact the RIPE NCC for guidance. insert: <br />
insert: <br />
If you have any questions concerning this, please do not hesitate to insert: <br />
call or mail us at ncc@ripe.net.

IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Internet Numbers Registration Procedures