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

RIPE NCC 

Document ID: ripe-445
Date: January 2009
Obsoletes: ripe-395, ripe-406, ripe-443

------------------------------------------------------------------

This document contains instructions for LIRs on how to complete the
"Autonomous System Number Request Form"
http://www.ripe.net/ripe/docs/asnrequestform.html

The instructions are based on the "Autonomous System (AS) Number
Assignment Policies and Procedures"
http://www.ripe.net/ripe/docs/asn-assignment.html

For an explanation on when an AS Number is needed,
please see: "Guidelines for Creation, Selection and Registration of an
Autonomous System" (RFC 1930)"
ftp://ftp.ripe.net/rfc/rfc1930.txt

For more information on language specifications,
please see "Routing Policy Specification Language (RPSL)" (RFC 2622)"
and "RPSL extensions for 32 bit AS Numbers"
ftp://ftp.ripe.net/rfc/rfc2622.txt and
http://tools.ietf.org/html/draft-uijterwaal-rpsl-4byteas-ext-03

General Information

AS Number User

Address Space to be Announced

Peering Contacts

Database Template(s)

Insert Supplemental Comments

End of Request



General Information


#[GENERAL INFORMATION]#
%
% Please add your RegID.

request-type: as-number
form-version: 1.1
x-ncc-regid:


Please do not change the value of the "request-type:" and
"form-version:" fields.

Enter your Registry Identifier (RegID) in the "x-ncc-regid:" field.
RegIDs have the following format: <country code>.<name>.
If you do not know your RegID, please contact <ncc@ripe.net>.


AS Number User


#[AS NUMBER USER]#
%
% Who will use the requested AS Number?

legal-organisation-name: North SantaBank
website-if-available: http://www.nsb.nn


Enter the legal name of the organisation that will use this AS Number in
the "legal-organisation-name:" field. If this organisation has a
website, enter the URL in the "website-if-available:" field. Otherwise,
enter "none" in this field.


Address Space to be Announced


#[ADDRESS SPACE TO BE ANNOUNCED]#
%
% Which address prefix will originate from the new AS Number?

prefix: 192.0.2.0/24

% If the address assignment is waiting for approval, please
% include the ticket number of the request below.

pending-ticket-ID:


You must include either an address prefix or a pending RIPE NCC ticket
number (for example, NCC#xxxxxxxx).

Please specify address prefixes using slash notation (for example,
x.x.x.x/xx ). The address space must be a valid assignment to the
organisation that will use the AS number.


Peering Contacts


#[PEERING CONTACTS]#
%
% What are the e-mail addresses of the peering
% partners for the requested AS Number.

peering: noddy@grottoinvestments.nn
peering: mary@northernbanking.nn


You must list the email addresses of at least two peering partners in
the "peering:" fields. You can repeat the "peering:" field as many times
as needed.


Database Template(s)


#[DATABASE TEMPLATE(S)]#
%
% Please complete all of the fields below.

aut-num:    ASNEW
as-name:    NSB-AS
descr:      North SantaBank's AS Number
org:        ORG-NS31-RIPE
import:     from AS64532 accept ANY
export:     to AS64532 announce ASNEW
import:     from AS64518 accept ANY
export:     to AS64518 announce ASNEW
admin-c:    ACM2-RIPE
tech-c:     HOHO1-RIPE
mnt-by:     SANTA-MNT
mnt-routes: SANTA-MNT
changed:    hostmaster@ripe.net
source:     RIPE


The "aut-num:" field must be ASNEW as we (RIPE NCC) will choose the AS
number.

The "as-name:" should be a short name associated with the Autonomous
System. We recommend that the name reflects the name of the organisation
that will use the AS Number.

Enter the legal organisation name of the AS Number user in the "descr:"
field.

Enter the org-ID of the AS Number user's organisation object in the
"org:" field.

The "import:" and "export:" fields should contain the complete routing
policy. Both fields may be repeated as many times as needed.

Basic syntax entries ar