Supporting Notes for the Autonomous System Number Request Form
This document contains instructions for LIRs on how to complete the "Autonomous System Number Request Form"
The instructions are based on the "Autonomous System (AS) Number Assignment Policies and Procedures"
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 more information on language specifications,
please see "Routing Policy Specification Language (RPSL)" (RFC 2622).
- General Information
- AS Number User
- Address Space to be Announced
- Peering Contacts
- Supplemental Comments
- Supporting documentation
- Database Template(s)
- End of Request
#[GENERAL INFORMATION]# % % Please add your RegID. request-type: as-number form-version: 1.2 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 <email@example.com>.
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 % Is this request being sent by a sponsoring LIR on behalf of an % End User? (Yes/No) end-user-of-sponsoring-lir: Yes % If yes, please confirm that the "End User Assignment Agreement" % contains all of the elements listed in paragraph 2.0 of % "Contractual Requirements for Provider Independent Resource Holders % in the RIPE NCC Service Region". (Yes/No) confirmation:
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.
If you are an LIR sending this request on behalf of an End User, you should answer "Yes" in the "end-user-of-sponsoring-lir" field.
If you answered "Yes" you should also confirm that all of the elements of paragraph 2.0 of "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" are listed in the 'End User Assignment Agreement' that is signed by the End User and the sponsoring LIR. PI assignments can only be made to End Users if there is a signed 'End User Assignment Agreement' between the sponsoring LIR and the End User.
You can find an example agreement at http://www.ripe.net/ripe/docs/lir-end-user-agreement.html.
You can send us an agreement in your local language or use the English version.
If this request is sent by a Direct Assignment User, you answer "No" to the above two questions. Direct Assignment Users have already signed an 'End User Assignment Agreement' with the RIPE NCC. If the request is for an LIR, you should also answer with "No".
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]# % % What are the e-mail addresses of the peering % partners for the requested AS Number. peering: firstname.lastname@example.org peering: email@example.com
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.
#[SUPPLEMENTAL COMMENTS]# % % Please add more information if you think it will help us understand % this request. Our peering agreements are provisional and will be confirmed when the new AS Number is assigned. % If you require a 16-bit AS Number instead of a 32-bit AS Number, % please indicate this below and tell us why. For more information, % see http://www.ripe.net/news/asn-32-guide.html AS Number Type: 16-bit Why 16-bit: Our routers are not 32-bit enabled.
As of 1 January 2009, all AS Numbers assigned by the RIPE NCC will be 32-bit by default. If you require a 16-bit AS Number change the default entry "32-bit" to "16-bit" and explain why you require a 16-bit AS Number. If you require further clarification, please see:
#[SUPPORTING DOCUMENTATION]# % % If this request is being sent by a sponsoring LIR on behalf of % an End User, please attach a copy of the signed % "End User Assignment Agreement" and the company registration papers % of the End User. % You can also attach a network diagram or other supporting documentation. % % Have you attached any files/documents to this request? (Yes/No) file-attached:
#[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: firstname.lastname@example.org 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 a short description of the Autonomous System 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 are as follows:
import: from <peer1> accept <filter> export: to <peer1> announce <filter> import: from <peer2> accept <filter> export: to <peer2> announce <filter>
For further details of language specifications, please refer to RFC 2622.
The nic-handle of the role or person object in the "admin-c:" field should reflect someone who is administratively responsible for the network.
The nic-handle of the role or person object in the "tech-c:" field should reflect someone who has technical knowledge of the network.
The "mnt-by" field shows which maintainer authenticates object updates. The "mnt-routes:" field shows which maintainer authenticates the creation of route objects.
The "mnt-by" fields must contain RIPE-NCC-END-MNT.
You can put the LIR's or AS Number User's maintainers in the "mnt-by:" and "mnt-routes:" fields.
The RIPE Database must contain all of the objects that you use.
The "changed:" field must be email@example.com .
The "source:" field must be RIPE.
#[END of REQUEST]# Best Regards, Jan Janssen, Bluelight Admin
Please write your full name below the "#[END of REQUEST]#" header.