RIPE NCC Autonomous System Number Request Form

 Nurani Nimpuno
 Sabrina Waschke

 Document ID: ripe-227
 Date: 2 October 2001
 Obsoletes: ripe-147

 See also: ripe-228

 Abstract

This document contains the set of templates to be used by Local
Internet Registries when requesting an Autonomous System (AS) Number
from the RIPE NCC.

 Instructions

This request form is to be submitted to the RIPE NCC via e-mail to
hostmaster@ripe.net. It should be used to request an AS Number to
facilitate routing in multi-homed environments.  An Autonomous System
is a connected group of one or more IP prefixes run by one or more
network operators which has a SINGLE and CLEARLY DEFINED routing
policy (RFC 1930).

An AS Number should only be requested for networks with the intention
of peering with at least two other Autonomous Systems. Please refer to
RFC 1930 to determine whether an AS Number is required in your
case. For Autonomous System Number policies, please refer to the RIPE
document: "European Internet Registry Policies and Procedures" at:

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


For detailed instructions on how to fill out this request form, please
refer to the RIPE document: "Supporting Notes for the RIPE NCC
Autonomous System Number Request Form" at:

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

The form must include the LIR's Registry Identifier (RegID) in the
header or at the top of the form. (It is recommended to add
X-NCC-RegID in the e-mail header.) Please note that requests sent to
the RIPE NCC that lack a proper Registry Identifier will be rejected
and returned to the sender. Any modifications to the templates or
missing templates may result in a delay in handling.


 X-NCC-RegID: 

 #[ANNOUNCED ADDRESS RANGES]#

Please list the address prefixes that will be originated from the new
AS here:

  

 Prefixes: 

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




 #[PEERING CONTACTS]#

Please list the e-mail contact addresses of peering partners for the
requested AS Number here:

  


 #[AUT-NUM TEMPLATE]#

aut-num:      NEW [mandatory]
as-name:      [mandatory]
descr:        [mandatory] 
member-of: 
import: 
export: 
default: 
remarks: 
admin-c:      [mandatory] 
tech-c:       [mandatory] 
cross-mnt: 
cross-nfy: 
notify: 
mnt-by:	      [mandatory] 
mnt-lower: 
mnt-routes:
changed:      [mandatory] 
source:       RIPE [mandatory]


 #[MAINTAINER TEMPLATE]#

mntner:       [mandatory]
descr:        [mandatory]
admin-c:      [mandatory]
tech-c:
upd-to:       [mandatory]
mnt-nfy:
auth:         [mandatory]
remarks:
notify:
mnt-by:       [mandatory]
auth-override:
referral-by:  [mandatory]
changed:      [mandatory]
source: RIPE  [mandatory]


 #[PERSON TEMPLATE]#

person:       [mandatory]
address:      [mandatory]
phone:	      [mandatory]
fax-no: 
e-mail:
nic-hdl:      [mandatory]
remarks:
notify:
mnt-by:
changed:      [mandatory]
source:       RIPE [mandatory]


 #[ADDITIONAL INFORMATION]#

Please add any supplementary information that may facilitate the
evaluation of this request here:






 #[TEMPLATE END]#