IPv4 Additional Allocation Request Form

   RIPE NCC
           
   Document ID: ripe-240
   Date: 14 June 2002
     _________________________________________________________________

Introduction

   This document contains the set of templates to be used when
   submitting an IPv4 Additional Allocation Request. You should only
   use this form if you have already received an IPv4 allocation and
   about 80% of it has been used in valid IPv4 assignments registered
   in the RIPE Database.

   Please submit the form, as plain text, via e-mail to
   <hostmaster@ripe.net>. Please include the keyword "NEWBLOCK" (in
   upper case) in the Subject header of the e-mail.

   Warning:

   Requests sent to the RIPE NCC that lack a proper Registry
   Identifier (X-NCC-RegID) will be returned to the sender. Please
   include the Registry Identifier in the header of the message or at
   the top of this form. Further, any modifications to the templates
   may result in a delay in handling.

------------------------8<Cut Here>8----------------------


X-NCC-RegID:


#[REQUESTER TEMPLATE]# 

Please enter the details of the person at your Local Internet
Registry (LIR) who is submitting this request.

name:
organisation:
country:
phone:
fax-no:
e-mail:


#[OVERALL USAGE TEMPLATE]# 

Please provide information about your last allocation.  
For example
(*): 

					    a s s i g n e d 
					    %   Number Free Total
192.168.16/20  192.168.16.0 - 192.168.31.255  79.4%  3266   830  4096

Please also provide the same information for all previous
allocations you have received. You may find it easiest to use a
program like asused_public to prepare this information.

ftp://ftp.ripe.net/tools/asused-latest.tar.gz


#[ALLOCATION USAGE TEMPLATE]# In this section, please list all the
assignments you made from your last allocation. Again, you may want
to generate this list with a program like asused_public.

For example: (*)

All assignments

Inetnum                              Size    Date     Netname

192.168.16.0  - 192.168.16.255       256   20011008   RFC-COMPL-1
192.168.17.0  - 192.168.17.63         64   20020111   DEV-NULL-1
192.168.17.64 - 192.168.17.127        64   20020426   RAMONES-HOST-1   

etc...



#[ADDITIONAL INFORMATION]#


#[TEMPLATES END]#

* Please note that we use private IP addresses in our examples.
Requesters should only list public IP addresses in their usage
templates.