You are here: Home > Publications > RIPE Document Store > Policy For Reverse Address Delegation of IPv4 And IPv6 Address Space in the RIPE NCC Service Region

Changes to Policy For Reverse Address Delegation of IPv4 And IPv6 Address Space in the RIPE NCC Service Region

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-302: This document describes the policy for reverse delegation of IPv4 and IPv6 address space in the ripe-072: RIPE NCC service region. Internet Numbers Registration Procedures

delete: <h2> insert: 

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

delete:  Reverse delegations for IPv4 and IPv6 addresses allocated by the RIPE NCC are made to Local Internet Registries (LIRs) and further delegated by the LIRs to Internet Service Providers or End Users. delete:  delete: <h2> delete: <a name="delegation"> delete: </a> 2.0 Obtaining Delegation of an in-addr.arpa or ip6.arpa sub-domain delete: </h2> delete:  The RIPE NCC provides reverse delegation for address space that has been allocated or assigned by the RIPE NCC. It also provides systems to control reverse delegations relating to early registrations that have been transferred to the RIPE Database. Registrants of address space allocations or assignments may delegate authority for requesting reverse delegation from the RIPE NCC. delete:  delete:  The RIPE NCC accepts requests for reverse delegation for address space that has been allocated by the RIPE NCC to an LIR or, in the case of PI address space, an assignment that has been made to an End User. delete:  delete: <h2> delete: <a name="procedures"> delete: </a> 3.0 Procedures delete: </h2> delete:  The procedures for requesting and modifying reverse delegation and information about the requirements the RIPE NCC enforces to maintain the quality of the reverse delegations are published at: delete:  delete: <blockquote> delete:  delete: <a data-val="275a3e401b56a46b5cf7b0a5a93c1492" href="resolveuid/275a3e401b56a46b5cf7b0a5a93c1492" data-linktype="internal" class="internal-link"> http://www.ripe.net/reverse/ delete: </a> delete:  delete: </blockquote> delete: <h2> delete: <a name="references"> delete: </a> 4.0 References delete: </h2> delete:  [1] "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")" delete:   [ delete: <a href="ftp://ftp.ripe.net/rfc/rfc3172.txt"> RFC 3172 delete: </a> ] delete:  delete:  [2] "DNS Extensions to Support IPv6 Address Aggregation and Renumbering" [ delete: <a href="ftp://ftp.ripe.net/rfc/rfc2874.txt"> RFC 2874 delete: </a> ] delete: 

Policy For Reverse Address Delegation of IPv4 And IPv6 Address Space in the RIPE NCC Service Region Internet Numbers Registration Procedures