You are here: Home > Publications > RIPE Document Store > Supporting Notes For The RIPE NCC Autonomous System Number Request Form

Changes to Supporting Notes For The RIPE NCC Autonomous System Number Request Form

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-228: Supporting Notes For The RIPE NCC Autonomous ripe-570: This document contains instructions for LIRs on how to complete the "Autonomous System Number Request Form Form"

This insert:  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:  insert: 

insert: 

To request resources from the RIPE Document 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: 

insert: 

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 in ASCII for members with workflows that prevent them from using the LIR Portal request forms. insert: 

insert: 

insert: 

insert: 

insert: 

insert: 

This document contains instructions for LIRs on how to complete the " insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/as-request.html"> Autonomous System Number Request Form insert: </a> " insert: 

insert: 

The instructions are based on the " insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/asn-assignment"> Autonomous System (AS) Number Assignment Policies and PDF delete:  Procedures insert: </a> " insert: 

insert: 

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

insert: 

For more information on language specifications, insert:  
please see insert: <a href="ftp://ftp.ripe.net/rfc/rfc2622.txt"> "Routing Policy Specification Language (RPSL)" (RFC 2622) insert: </a> . insert: 

insert: <ul>

insert: <li>

insert: <a href="#info"> General Information insert: </a> insert: </li>

insert: <li>

insert: <a href="#user"> AS Number User insert: </a> insert: </li>

insert: <li>

insert: <a href="#announce"> Address Space to be Announced insert: </a> insert: </li>

insert: <li>

insert: <a href="#peering"> Peering Contacts insert: </a> insert: </li>

insert: <li>

insert: <a href="#comments"> Supplemental Comments insert: </a> insert: </li>

insert: <li>

insert: <a href="#documentation"> Supporting documentation insert: </a> insert: </li>

insert: <li>

insert: <a href="#database"> Database Template(s) insert: </a> insert: </li>

insert: <li>

insert: <a href="#end"> End of Request insert: </a> insert: </li>

insert: </ul>

insert: <hr />

insert: 

insert: <a name="info"> insert: </a> insert: 

insert: <h2>

General Information insert: `</h2>`

insert: <pre>

 #[GENERAL INFORMATION]#  insert: <br /> 
 %  insert: <br /> 
 % Please add your RegID.  insert: <br /> 
 insert: <br /> 
 request-type: as-number  insert: <br /> 
 form-version: 1.2  insert: <br /> 
 x-ncc-regid:  insert: </pre>

insert: 

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

insert: 

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

insert: 

insert: <a id="user" name="user"> insert: </a> insert: 

insert: <h2>

AS Number User insert: `</h2>`

insert: <pre>

 #[AS NUMBER USER]#  insert: <br /> 
 %  insert: <br /> 
 % Who will use the requested AS Number?  insert: <br /> 
 insert: <br /> 
 legal-organisation-name:  insert: <b>  North SantaBank  insert: </b>  insert: <br /> 
 website-if-available:  insert: <b>  http://www.nsb.nn  insert: </b>  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: <b>  Yes  insert: </b>  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: </pre>

insert: 

Enter the legal name of the organisation that will use this AS Number in the " insert:  legal-organisation-name: insert:  " field. If this organisation has a website, enter the URL in the " insert:  website-if-available: insert:  " field. Otherwise, enter " insert:  none insert:  " in this field. insert:  
insert:  
If you are an LIR sending this request on behalf of an End User, you should answer " insert:  Yes insert:  " in the " insert:  end-user-of-sponsoring-lir insert:  " field. insert:  
insert:  
If you answered " insert:  Yes insert:  " you should also confirm that all of the elements of paragraph 2.0 of " insert: <a data-val="b4db2a127586d02986acbcc4f1cf8651" href="resolveuid/b4db2a127586d02986acbcc4f1cf8651" data-linktype="internal" class="internal-link"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> " 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. insert:  
insert:  
You can find an example agreement at insert: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/ripe/docs/lir-end-user-agreement.html insert: </a> . insert: 

insert: 

You can send us an agreement in your local language or use the English version. If the request is for an LIR, you should also answer with " insert:  No insert:  ". insert: 

insert: 

insert: <a id="announce" name="announce"> insert: </a> insert: 

insert: <h2>

Address Space to be Announced insert: `</h2>`

insert: <pre>

 #[ADDRESS SPACE TO BE ANNOUNCED]#  insert: <br /> 
 %  insert: <br /> 
 % Which address prefix will originate from the new AS Number?  insert: <br /> 
 insert: <br /> 
 prefix:  insert: <b>  192.0.2.0/24  insert: </b>  insert: <br /> 
 insert: <br /> 
 % If the address assignment is waiting for approval, please  insert: <br /> 
 % include the ticket number of the request below.  insert: <br /> 
 insert: <br /> 
 pending-ticket-ID:  insert: </pre>

insert: 

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

insert: 

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

insert: 

insert: <a id="peering" name="peering"> insert: </a> insert: 

insert: <h2>

Peering Contacts insert: `</h2>`

insert: <pre>

 #[PEERING CONTACTS]#  insert: <br /> 
 %  insert: <br /> 
 % What are the e-mail addresses of the peering  insert: <br /> 
 % partners for the requested AS Number.  insert: <br /> 
 insert: <br /> 
 peering:  insert: <b>  [email protected]  insert: </b>  insert: <br /> 
 peering:  insert: <b>  [email protected]  insert: </b>  insert: </pre>

insert: 

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

insert: 

insert: <a id="comments" name="comments"> insert: </a> insert: 

insert: <h2>

Supplemental Comments insert: `</h2>`

insert: <pre>

 #[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: <b>  Our peering agreements are provisional and will be confirmed  insert: <br /> 
 when the new AS Number is assigned.  insert: </b>  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 http://www.ripe.net/news/asn-32-guide.html  insert: <br /> 
 insert: <br /> 
 AS Number Type:  insert: <b>  16-bit  insert: </b>  insert: <br /> 
 insert: <br /> 
 Why 16-bit:  insert: <b>  Our routers are not 32-bit enabled.  insert: </b>  insert: </pre>

insert: 

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: insert:  
insert: <a data-val="339580b64ca9bd4b6441dd8463171f70" href="resolveuid/339580b64ca9bd4b6441dd8463171f70" data-linktype="internal" class="internal-link"> http://www.ripe.net/news/asn-32-guide.html insert: </a> insert: 

insert: 

insert: <a id="documentation" name="documentation"> insert: </a> insert: 

insert: <h2>

Supporting documentation insert: `</h2>`

insert: <pre>

 #[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: </pre>

insert: 

insert: <a id="database" name="database"> insert: </a> insert: 

insert: <h2>

Database Template(s) insert: `</h2>`

insert: <pre>

 #[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:  insert: <b>  NSB-AS  insert: </b>  insert: <br /> 
 descr:  insert: <b>  North SantaBank's AS Number  insert: <br /> 
 insert: </b>  org:  insert: <b>  ORG-NS31-RIPE  insert: <br /> 
 insert: </b>  import:  insert: <b>  from AS64532 accept ANY  insert: <br /> 
 insert: </b>  export:  insert: <b>  to AS64532 announce ASNEW  insert: <br /> 
 insert: </b>  import:  insert: <b>  from AS64518 accept ANY  insert: <br /> 
 insert: </b>  export:  insert: <b>  to AS64518 announce ASNEW  insert: </b>  insert: <br /> 
 admin-c:  insert: <b>  ACM2-RIPE  insert: </b>  insert: <br /> 
 tech-c:  insert: <b>  HOHO1-RIPE  insert: </b>  insert: <br /> 
 mnt-by:  insert: <b>  RIPE-NCC-END-MNT  insert: </b>  insert: <br /> 
 mnt-by:  insert: <b>  SANTA-MNT  insert: </b>  insert: <br /> 
 mnt-routes:  insert: <b>  SANTA-MNT  insert: </b>  insert: <br /> 
 changed: [email protected]  insert: <br /> 
 source: RIPE  insert: </pre>

insert: 

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

insert: 

The " insert:  as-name: insert:  " 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. insert: 

insert: 

Enter a short description of the Autonomous System in the " insert:  descr insert:  :" field. insert: 

insert: 

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

insert: 

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

insert: 

Basic syntax entries are as follows: insert: 

insert: <pre>

 import: from <peer1> accept <filter>  insert: <br /> 
 export: to <peer1> announce <filter>  insert: <br /> 
 import: from <peer2> accept <filter>  insert: <br /> 
 export: to <peer2> announce <filter>  insert: </pre>

insert: 

For further details of language specifications, please refer to insert: <a href="ftp://ftp.ripe.net/rfc/rfc2622.txt"> RFC 2622 insert: </a> . insert: 

insert: 

The nic-handle of the role or person object in the " insert:  admin-c: insert:  " field should reflect someone who is administratively responsible for the network. insert: 

insert: 

The nic-handle of the role or person object in the " insert:  tech-c: insert:  " field should reflect someone who has technical knowledge of the network. insert: 

insert: 

The " insert:  mnt-by insert:  " field shows which maintainer authenticates object updates. The " insert:  mnt-routes: insert:  " field shows which maintainer authenticates the creation of route objects. insert: 

insert: 

The "mnt-by" fields must contain RIPE-NCC-END-MNT. insert: 

insert: 

You can put the LIR's or AS Number User's maintainers in the " insert:  mnt-by: insert:  " and " insert:  mnt-routes: insert:  " fields. insert: 

insert: 

The RIPE Database must contain all of the objects that you use. insert: 

insert: 

The " insert:  changed: insert:  " field must be insert:  [email protected] insert:  . insert: 

insert: 

The " insert:  source: insert:  " field must be RIPE. insert: 

insert: <h2>

insert: `<a id="end" name="end">` insert: `</a>` End of Request insert: `</h2>`

insert: <pre>

 #[END of REQUEST]#  insert: <br /> 
 insert: <br /> 
 insert: <b>  Best Regards,  insert: <br /> 
 Jan Janssen, Bluelight Admin  insert: </b>  insert: </pre>

insert: 

Please write your full name below the " insert:  #[END of REQUEST]# insert:  " header. insert: 

Supporting Notes For The RIPE NCC for the Autonomous System Number Request Form

RIPE Documents Search

ripe-228

State:

Obsoleted

Updated by:

ripe-305 , ripe-335 , ripe-355 , ripe-395 , ripe-406 , ripe-443 , ripe-445 , ripe-457 , ripe-521 , ripe-570

Updates:

ripe-147 , ripe-109 , ripe-097 , ripe-091

Authors:

Nurani Nimpuno

Sabrina Waschke

Date:

October 2001

Download

File:
PDF | 83.0KB

Download

File:
ASCII | 15.0KB

Changes to Supporting Notes For The RIPE NCC Autonomous System Number Request Form

General Information insert: </h2>

AS Number User insert: </h2>

Address Space to be Announced insert: </h2>

Peering Contacts insert: </h2>

Supplemental Comments insert: </h2>

Supporting documentation insert: </h2>

Database Template(s) insert: </h2>

insert: <a id="end" name="end"> insert: </a> End of Request insert: </h2>

RIPE Documents Search

ripe-228

General Information insert: `</h2>`

AS Number User insert: `</h2>`

Address Space to be Announced insert: `</h2>`

Peering Contacts insert: `</h2>`

Supplemental Comments insert: `</h2>`

Supporting documentation insert: `</h2>`

Database Template(s) insert: `</h2>`

insert: `<a id="end" name="end">` insert: `</a>` End of Request insert: `</h2>`