ripe-72
          RIPE NCC Internet Numbers Registration Procedures	

                         16 October 1992

			   version 0.7
			
			   M.Terpstra
   
   ** This documents obsoletes ripe-65, version 0.6 of this document **
   
   Abstract
   ========
   
   This document describes the procedures for the reassignment of IP
   network numbers from blocks obtained from the RIPE Network Coordination
   Centre.  It deals with items as providing information for the RIPE 
   database, as well as reassignment of IP addresses in light of
   the "Supernetting" proposal, as documented in RFC 1338, by Vince Fuller
   et al.
   
   
   Introduction
   ============
   
   Since May 1st 1992, the RIPE Network Coordination Centre (NCC) is
   acting as a delegated registry for IP networks numbers to NICs and NOCs
   in Europe.  It is RIPE NCC policy not to give out network numbers to
   individual organisations, who should refer in turn, to their IP network
   service provider. 
   
   The mission of the RIPE NCC is to give network numbers to the various
   service providers and NICs.  The NICs and NOCs can then reassign the
   actual IP network numbers to organisations requesting IP network
   numbers. 
   
   
   Class B Network Number Allocation Procedure
   ===========================================
   
   Service providers can request Class B network numbers on a one-by-one
   basis from the RIPE NCC.  Because class B address space is a critical
   resource, a request for a class B network number must be accompanied by
   a justification in terms of the requesting organisation's size, current
   network and expected network growth.  The requestor should also make
   clear why they cannot use a block of class C network numbers to achieve
   their goals.  The RIPE NCC will review requests using the same standards 
   as any other Internet Registry, particularly the US NIC. 
   
   
   Class C Allocation Procedures
   =============================
   
   NICs and NOCs accepting a block of class C numbers agree to adhere to
   the following procedures:
   
   A) The RIPE NCC will assign complete class C blocks to individual NICs
   and NOCs.  They can be requested from <hostmaster@ripe.net>. 
   
   B) In order to prevent implementation problems, network numbers ending
   with 0 or 255 should NOT be reassigned. 
   
   C) Full information about reassigned network numbers must be reported
   back to the RIPE NCC in full RIPE database format (ref ripe-13).
   The complete entries should be sent immediately after reassignment to
   <assign@ripe.net>.
   The RIPE NCC is ready to accept block entries for the RIPE database.
   For block syntax, please contact the RIPE NCC.
   
   D) Reassignment of class C network numbers should be done in a manner
   that facilitates Supernetting (see next section). 
   
   E) Requests for network numbers should be reasonable.  All NICs and NOCs 
   should prevent stockpiling of network numbers. 
   
   F) On first request from the RIPE NCC, the class C network numbers not
   yet reassigned, must be returned to the RIPE NCC.
   
   
   Supernetting
   ============
   
   NICs and NOCs reassigning IP network numbers are urgently requested to
   read the Supernetting proposal by Vince Fuller et al.  This document can
   be obtained from the rfc section of the RIPE document store or other RFC
   servers. It is called rfc1338.txt.
   The Supernetting proposal was made to reduce the increase of routing
   table size in the current Internet.  It proposes to create a hierarchy
   of IP network numbers, which can then be aggregated resulting in less
   routing table entries in routing equipment.  While this proposal has not
   been formally adopted we expect that something at least along the same
   principle will be implemented in the near future. 
   
   Here is how it works:
   
   If an