You are here: Home > Publications > RIPE Document Store > AS Number Request Form

Changes to AS Number Request Form

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-354: ripe-562: AS Number Request Form
insert: <p>

insert: <strong> Please note: all email-based request forms have been archived on the website and are available through the LIR Portal. You can find an announcement about this insert: <a class="external-link" href="https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" title=""> here insert: </a> . insert: </strong> insert: </p>

insert: <p>

To request resources from the RIPE NCC, members should now use the request forms in the insert: <a class="external-link" href="https://lirportal.ripe.net/" target="_self" title=""> LIR Portal insert: </a> . insert: </p>

insert: <p>

The insert: <a class="external-link" href="https://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self" title=""> Resource Request API insert: </a> and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms. insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <img src="./resolveuid/1f075ef0-1420-4b37-95a9-b77d6721138b" alt="" class="image-inline" title="" data-val="1f075ef0-1420-4b37-95a9-b77d6721138b" data-linktype="image" /> insert: </p>

 ------------------------8<Cut Here>8----------------------  delete: </pre> delete: <pre> insert: <br /> 
% AS Number Request Form delete: </pre> delete: <pre> insert: <br />
insert: <br />
% RIPE NCC members (LIRs) can use this form insert: <br />
% to request an Autonomous System (AS) Number. % Please see ripe-355 for For instructions on how to insert: <br />
% complete this form. delete: </pre> delete: <pre> form see: insert: <br />
%"Supporting Notes for the Autonomous System Number Request Form" insert: <br />
% insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/asnsupport.html"> http://www.ripe.net/ripe/docs/asnsupport.html insert: </a> insert: <br />
% insert: <br />
% Please note that the End User should have a signed "End User insert: <br />
% Assignment Agreement" with either the sponsoring LIR or the RIPE NCC. insert: <br />
insert: <br />
#[GENERAL INFORMATION]# % insert: <br />
% insert: <br />
% Please add your RegID. delete: </pre> delete: <pre> RegID insert: <br />
insert: <br />
request-type: as-number insert: <br />
form-version: 1.1 1.2 insert: <br />
x-ncc-regid: delete: </pre> delete: <pre> delete: </pre> delete: <pre> insert: <br />
insert: <br />
#[AS NUMBER USER]# % insert: <br />
% insert: <br />
% Who will use the requested AS Number? delete: </pre> delete: <pre> AS Number being requested? insert: <br />
insert: <br />
legal-organisation-name: insert: <br />
website-if-available: delete: </pre> delete: <pre> delete: </pre> delete: <pre> insert: <br />
insert: <br />
% Is this request being sent by a sponsoring LIR on behalf of an insert: <br />
% End User? (Yes/No) insert: <br />
insert: <br />
end-user-of-sponsoring-lir: insert: <br />
insert: <br />
% If yes, please confirm that the "End User Assignment Agreement" insert: <br />
% contains all of the elements listed in paragraph 2.0 of insert: <br />
% "Contractual Requirements for Provider Independent Resource Holders insert: <br />
% in the RIPE NCC Service Region". (Yes/No) insert: <br />
insert: <br />
confirmation: insert: <br />
insert: <br />
#[ADDRESS SPACE TO BE ANNOUNCED]# % insert: <br />
% insert: <br />
% Which address prefix will originate from the new AS Number? delete: </pre> delete: <pre> number? insert: <br />
insert: <br />
prefix: delete: </pre> delete: <pre> insert: <br />
insert: <br />
% If the address assignment is waiting for approval, please insert: <br />
% include the ticket number of the request below. delete: </pre> delete: <pre> insert: <br />
insert: <br />
pending-ticket-ID: delete: </pre> delete: <pre> delete: </pre> delete: <pre> insert: <br />
insert: <br />
#[PEERING CONTACTS]# % % What are the e-mail insert: <br />
% insert: <br />
% Please list the email contact addresses of the peering insert: <br />
% partners for the requested AS Number? delete: </pre> delete: <pre> Number. insert: <br />
insert: <br />
peering: insert: <br />
peering: delete: </pre> delete: <pre> delete: </pre> delete: <pre> #[DATABASE TEMPLATE(S)]# % % Please complete all of the fields below. delete: </pre> delete: <pre> aut-num: ASNEW as-name: <add name for the AS> descr: <add AS Number User name> org: <add org-ID> import: <specify the outgoing routing policy for the first peer> export: <specify the incoming routing policy for the first peer> import: <specify the outgoing routing policy for the second peer> export: <specify the incoming routing policy for the second peer> admin-c: <add nic-handle of administrative contact> tech-c: <add nic-handle of technical contact> mnt-by: <add mntner name> mnt-routes: <add mntner name> changed: hostmaster@ripe.net source: RIPE delete: </pre> delete: <pre> delete: </pre> delete: <pre> #[INSERT SUPPLEMENTAL insert: <br />
insert: <br />
#[SUPPLEMENTAL COMMENTS]# % insert: <br />
% insert: <br />
% Please add more information if you think it will help % us understand insert: <br />
% this request. insert: <br />
insert: <br />
insert: <br />
insert: <br />
% If you require a 16-bit AS Number instead of a 32-bit AS Number, insert: <br />
% please indicate this below and tell us why. For more information, insert: <br />
% see insert: <a class="external-link" href="http://www.ripe.net/news/asn-32-guide.html"> http://www.ripe.net/news/asn-32-guide.html insert: </a> insert: <br />
insert: <br />
AS Number Type: 32-bit [change as required] insert: <br />
insert: <br />
Why 16-bit: insert: <br />
insert: <br />
#[SUPPORTING DOCUMENTATION]# insert: <br />
% insert: <br />
% If this request is being sent by a sponsoring LIR on behalf of insert: <br />
% an End User, please attach a copy of the signed insert: <br />
% "End User Assignment Agreement" and the company registration papers insert: <br />
% of the End User. insert: <br />
% You can also attach a network diagram or other supporting documentation. insert: <br />
% insert: <br />
% Have you attached any files/documents to this request? (Yes/No) insert: <br />
insert: <br />
file-attached: insert: <br />
insert: <br />
#[DATABASE TEMPLATE(S)]# insert: <br />
% insert: <br />
% Please complete all of the fields below insert: <br />
insert: <br />
aut-num: ASNEW insert: <br />
as-name: <add name for the AS> insert: <br />
descr: <add AS Number User name> insert: <br />
org: <add org-ID> insert: <br />
import: <specify the outgoing routing policy for the first peer> insert: <br />
export: <specify the incoming routing policy for the first peer> insert: <br />
import: <specify the outgoing routing policy for the second peer> insert: <br />
export: <specify the incoming routing policy for the second peer> insert: <br />
admin-c: <add nic-handle of administrative contact> insert: <br />
tech-c: <add nic-handle of technical contact> insert: <br />
mnt-by: RIPE-NCC-END-MNT insert: <br />
mnt-by: <add mntner name> insert: <br />
mnt-routes: <add mntner name> insert: <br />
changed: hostmaster@ripe.net insert: <br />
source: RIPE insert: <br />
insert: <br />
#[END of REQUEST]#
delete: <pre> <add more information> delete: </pre> delete: <pre> delete: </pre> delete: <pre> #[END of REQUEST]# ------------------------8<Cut Here>8---------------------- delete: </pre> insert: <p>

insert: <img src="./resolveuid/93c82862-6241-4309-8d0f-9d4355eeded7" alt="" class="image-inline" title="" data-val="93c82862-6241-4309-8d0f-9d4355eeded7" data-linktype="image" /> insert: </p>

RIPE Documents Search