Supporting Notes for the Autonomous System (AS) Number Request Form

Filiz Yilmaz Bican,
Emma Bretherick
Laura Cobley 

Document ID: ripe-305
Date: 26 April 2004
Obsoletes: ripe-228, ripe-279

See also: ripe-304

     _________________________________________________________________

Contents

Introduction
Supporting Notes
Example
References


Introduction

This document contains instructions for completing the 'Autonomous System (AS) Number 
Request Form'. It is a tool for gathering the information necessary to evaluate the request 
and to ensure that the same guidelines are applied to each request. Where necessary, the 
RIPE NCC will ask for additional information.

The 'Autonomous System (AS) Number Request Form' can be found at:

http://www.ripe.net/ripe/docs/asnrequestform.html

Please read all the information below carefully before submitting your application for an 
AS Number. For more detailed explanations on routing policy objects, please refer to 
"Routing Policy Specification Language (RPSL)" (RFC 2622). For an explanation on when 
an AS Number is needed, please see: "Guidelines for Creation, Selection and Registration 
of an Autonomous System" (RFC 1930). For Autonomous System Number policies, 
please refer to the RIPE document "European Internet Registry Policies and Procedures" 
found at:

 http://www.ripe.net/ripe/docs/ir-policies-procedures.html

When sending the completed AS Number request form to the RIPE NCC, all information 
requested in the form must be supplied, including the technical routing policy. 


Supporting Notes for the Request Form Templates

#[GENERAL INFORMATION]#

request-type: as-number
form-version: 1.1

Please do not alter the value of the 'request-type' and 'form-version' fields.

x-ncc-regid:

The Registry Identifier (RegID) must be included in every message sent to 
<hostmaster@ripe.net>. It is used to identify the Local Internet Registry (LIR). It has the 
following format: 

<country code>.<organisation name>

Warning: Requests sent to the RIPE NCC that lack a proper RegID (x-ncc-regid) will 
bounce back to the sender.


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

In the 'legal-organisation-name' field please enter the registered/legal name of the 
organisation for whom the AS Number is being requested.

In the 'website-if-available' field please enter the URL of the organisations 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:

Please specify the address space using the CIDR (slash) notation (i.e. x.x.x.x/xx).

% 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:

To process this request you must complete either the 'prefix' field or the 'pending-ticket-ID' 
field.

#[PEERING CONTACTS]#
%
% Please list the e-mail contact addresses of peering 
% partners for the requested AS Number.
peering:
peering:

Please list all your peering partners here. The minimum number of peers that may be 
given is two to ensure that the organisation will be multihomed. If you have more than two 
peers, please add these to the list using the same format (i.e. '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 
%