RIPE NCC 

Doc-ID: RIPE-304
Date: 26 April 2004 

% AS Number Request Form

#[GENERAL INFORMATION]#
request-type: as-number
form-version: 1.1
x-ncc-regid: 

#[AS NUMBER USER]#
%
% Who will use the AS Number being requested?
legal-organisation-name:      
website-if-available: 

#[ADDRESS SPACE TO BE ANNOUNCED]#
%
% Please list the address prefixes that will originate from 
% the new AS Number. Please specify each prefix in a 
% separate "prefix" field below. 
prefix:
 
%
% If the organisation wishing to be multi-homed does not 
% have address space yet but has a pending request sent to 
% <hostmaster@ripe.net>, please include the ticket number 
% of the request below.
pending-ticket-ID:
 
#[PEERING CONTACTS]#
%
% Please list the e-mail contact addresses of peering 
% partners for the requested AS number.
peering:
peering:

#[DATABASE TEMPLATE(S)]# 
%
% Please include database template(s) here so that the 
% Hostmaster can register the assignment in the RIPE 
% Database. If it is necessary to create a maintainer object 
% please include that template too. 
%
% Please also note that although "import:" and "export:" 
% attributes for an "aut-num" object are optional in terms 
% of database software, they are mandatory in terms of RIPE 
% policies. This ensures that the AS Number requested is to 
% be multi-homed. 

aut-num:       ASNEW 
as-name:       [mandatory]  [single]     [ ]
descr:         [mandatory]  [multiple]   [ ]
import:        [optional]   [multiple]   [ ]
export:        [optional]   [multiple]   [ ]
org: 		[optional]   [single]     [inverse key]
admin-c:       [mandatory]  [multiple]   [inverse key]
tech-c:        [mandatory]  [multiple]   [inverse key]
mnt-routes:    [optional]   [multiple]   [inverse key]
mnt-by:        [mandatory]  [multiple]   [inverse key]
changed:       hostmaster@ripe.net
source:        RIPE


#[INSERT SUPPLEMENTAL COMMENTS]#
%
% Please add any supplementary information that you think 
% may facilitate the evaluation of this request below.

#[END of REQUEST]#