You are here: Home > Publications > RIPE Document Store > RIPE Internet Network Numbers Template

Changes to RIPE Internet Network Numbers Template

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

ripe-048: RIPE Internet Network Numbers Template ripe-489: This document contains instructions for LIRs on how to complete the “Provider Aggregatable (PA) Assignment Request Form”.

delete:  insert: 

This document contains instructions for LIRs on how to complete the “ insert: <a data-val="ad8cc394acf725d0acbdeb5d20356d9c" href="resolveuid/ad8cc394acf725d0acbdeb5d20356d9c" data-linktype="internal" class="internal-link"> Provider Aggregatable (PA) Assignment Request Form insert: </a> ”. insert: 

insert: 

The instructions are based on the “IPv4 Address Allocation and Assignment Policy for the RIPE Internet region”. insert: 

insert: 

LIRs should send separate “Provider Aggregatable (PA) Assignment Request” forms for each End User. insert: 

insert: <hr />

insert: <ul>

insert: <li>

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

insert: <li>

insert: <a href="#user"> Address Space User insert: </a> insert: </li>

insert: <li>

insert: <a href="#plan"> Addressing Plan insert: </a> insert: </li>

insert: <li>

insert: <a href="#equipment"> Equipment Description insert: </a> insert: </li>

insert: <li>

insert: <a href="#description"> Network Numbers Template delete:   delete:   D.Karrenberg delete:   delete:   Aug 1992 delete:   delete:   delete:   delete:   To whom it may concern, delete:   delete:   The RIPE Description insert: </a> insert: </li>

insert: <li>

insert: <a href="#diagram"> Network Coordination Centre now handles all requests for IP delete:   network numbers from European organisations. Our aim is to provide a delete:   rapid Diagram insert: </a> insert: </li>

insert: <li>

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

insert: </ul>

insert: <hr />

insert: <h2>

insert: `<a name="general">` insert: `</a>` General Information insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[GENERAL INFORMATION]#  insert: <br /> 
 %  insert: <br /> 
 % Please add your RegID.  insert: <br /> 
 %  insert: <br /> 
 % request-type: pa-ipv4  insert: <br /> 
 form-version: 1.2  insert: <br /> 
 x-ncc-regid:  insert: <span class="arial-small">  insert: <b>  nl.bluelight  insert: </b>  insert: </span>  insert: </pre>

insert: </blockquote>

insert: 

Please do not change the value of the “ insert:  request-type: insert:  ” and efficient service to all European organisations. As this is delete:   a recent initiative, procedures for handling network number requests are delete:   “ insert:  form-version: insert:  ” fields. insert: 

insert: 

Enter your Registry Identifier (RegID) in the process of being established. Therefore we apologise in advance delete:   for any duplication of effort “ insert:  x-ncc-regid: insert:  ” field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact <[email protected]>. insert: 

insert: <h2>

insert: `<a name="user">` insert: `</a>` Address Space User insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[ADDRESS SPACE USER]#  insert: <br /> 
 %  insert: <br /> 
 % Who will use the requested address space?  insert: <br /> 
 %  insert: <br /> 
 % legal-organisation-name:  insert: <span class="arial-small">  insert: <b>  North SantaBank  insert: </b>  insert: </span>  insert: <br /> 
 organisation-location:  insert: <span class="arial-small">  insert: <b>  Santa City, NN  insert: </b>  insert: </span>  insert: <br /> 
 website-if-available:  insert: <span class="arial-small">  insert: <b>  http://www.nsb.nn  insert: </b>  insert: </span>  insert: <br /> 
 %  insert: <br /> 
 % Does this End User already have address space  that may be required by you due to new  delete: <br /> forms and templates. As the European NIC, we require different  delete: <br /> information to that required by the US and for it to be presented in a  delete: <br /> format which is both easy for you to complete and for us to process.  delete: <br /> Before your application  can be processed  insert: <br /> 
 % used for this assignment? (Yes/No)  insert: <br /> 
 %  insert: <br /> 
 % space-available:  insert: <span class="arial-small">  insert: <b>  No  insert: </b>  insert: </span>  insert: </pre>

insert: </blockquote>

insert: 

Enter the legal name and primary location of the organisation that will use this address space in the “ insert:  legal-organisation-name: insert:  ” and “ insert:  organisation-location: insert:  ” fields. If this End User has a website, enter the URL in the “ insert:  website-if-available: insert:  ” field. Otherwise, enter “none” in this field. insert: 

insert: 

If there is any further, address space assigned to this End User that is not in use, indicate this in the “ insert:  space-available: insert:  ” field. If you answer “yes”, you can explain why the End User needs another assignment of address space in the “ insert:  Network Description insert:  ” section at the end of this form. insert: 

insert: <h2>

insert: `<a name="plan">` insert: `</a>` Addressing Plan insert: `</h2>`

insert: <blockquote>

insert: <pre>
 #[ADDRESSING PLAN]# insert: </pre> 
insert: <pre>
 % As of 1 January 2010 assignments are for a period of up to 12 months. insert: 
 % As of 1 July 2010 assignments are for a period of up to 9 months. insert: 
 % As of 1 January 2011 assignments are for a period of up to 6 months. insert: 
 % As of 1 July 2011 assignments are for a period of up to 3 months. insert: </pre> 
insert: <pre>
 % insert: 
 % How will the End User use this address space? insert: 
 % insert: 
 % Subnet Immediate Intermediate Entire Purpose insert: 
 % size (/nn) Requirement Requirement Period insert: </pre> 
insert: <pre>
 subnet: insert: /26 32 64 64 Employee VPN insert: insert: Access insert: insert: 
 subnet: insert: /26 18 34 64 Financial Services insert: insert: 
 subnet: insert: /26 22 30 60 Workstations insert: insert: 
 subnet: insert: /27 11 15 28 Public Services insert: insert: 
 subnet: insert: /27 7 18 30 Operations insert: insert: 
 subnet: insert: /24 176 192 240 Branch Offices insert: insert: 
 totals: insert: /23 266 353 486 insert: insert: 
 insert: </pre> 
insert: <pre>
 number-of-subnets: insert: 6 insert: insert: </pre> 
insert: <pre>
 % Will the End User return any address space? insert: </pre> 
insert: <pre>
 address-space-returned: insert: 85.118.187/24 to nl.bluelight in 3 months insert: insert: </pre> 
insert: 
The addressing plan shows how the End User will use the requested address space. You can repeat the "subnet" row as many times as needed. Delete any empty "subnet" fields before you send the request. In the "Subnet size (/nn)" column, enter a slash notation prefix for each subnet. Each entry should be large enough to contain the number of addresses needed for that subnet over the next time period. insert: 
insert: 
In order to demonstrate the predicted growth of your network, you must provide an estimate of the address space you will need to delete:   complete the enclosed templates require over three distinct periods: Immediate, Intermediate and return them to the appropriate delete:   organisation responsible for issuing IP the Entire period. Your estimates should include interfaces used for hosts, routers, gateways, terminal concentrators and any other machines requiring one or more network numbers. In most cases delete:   this interfaces. These columns can either contain numbers (for example, 128) or slash notation prefixes (for example, /25). Multiple slash notation prefixes must be separated by comma(s) with no blank spaces (for example, /25,/27). insert: 
insert: 
Starting on 1 January 2010, a gradual reduction in the assignment period will be applied. As the assignment period changes, so too will the information required: insert: 
insert: 
Up to 30 June 2010, assignments are for a period of up to insert:  twelve insert:  months. Therefore, your IP service provider or the RIPE NCC. Before delete:   completion of the template, please request should reflect your immediate requirements, predicted requirements for the coming six months, and predicted requirements for the coming twelve months. insert: 
insert: 
As of 1 July 2010, assignments are for a period of up to insert:  nine insert:  months. Your request should reflect your immediate requirements, predicted requirements for the coming six months, and predicted requirements for the coming nine months. insert: 
insert: 
As of 1 January 2011, assignments are for period of up to insert:  six insert:  months. Your request should reflect your immediate requirements, predicted requirements for the coming three months, and predicted requirements for the coming six months. insert: 
insert: 
As of 1 July 2011, assignments are for a period of up to insert:  three insert:  months. Your request should reflect your immediate requirements, predicted requirements for the coming two months, and predicted requirements for the coming three months. insert: 
insert: 
In the “Purpose” column, write a short description of each subnet. If needed, you can write a more detailed description in the “Network Description” section at the end of this form. insert: 
insert: 
In the “ insert:  totals insert:  ” row, add the total of each column. The total of the “ insert:  Subnet size (/nn) insert:  ” column should be sure to read the following text delete:   and examples carefully which will guide you. delete:   delete:   A new classless IP addressing scheme called CIDR has recently been delete:   adopted to cope with routing table growth and the total amount of address space exhaustion delete:   problems in the Internet. Under this scheme it is beneficial for delete:   everyone to get their network numbers allocated via their respective delete:   IP service providers. Your IP service provider is the organisation delete:   providing external connectivity to your network. If you are planning delete:   to connect your requesting for this assignment. insert: 
insert: 
In the “ insert:  number-of-subnets: insert:  ” field, enter the total number of subnets listed in the addressing plan. insert: 
insert: 
The “ insert:  netname: insert:  ” should be a short, descriptive name for the network to other networks outside your and should reflect the End User's organisation name. You should use the same “ insert:  netname: insert:  ” when you register this assignment in delete:   the foreseeable future we strongly urge you to get numbers allocated delete:   from your current or prospective IP service provider. Alternatively, if delete:   this the RIPE Whois Database. insert: 
insert: 
If there is not likely, then you any address space assigned to the End User that they will return, list each prefix in separate “ insert:  address-space-returned: insert:  ” fields. The expected time for renumbering is three months. You can use the following syntax: <x.x.x.x/xx> to <which LIR/ISP> in <time period> for this field. insert: 
insert: </blockquote>

insert: <h2>

insert: `</h2>`

insert: <h2>

insert: `<a name="equipment">` insert: `</a>` Equipment Description insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[EQUIPMENT DESCRIPTION]#  insert: <br /> 
 %  insert: <br /> 
 % What equipment  will be allocated a number from a different  delete: <br /> part of the  used and how will it use the  insert: <br /> 
 % requested address space?  insert: </pre>

insert: <pre>

 equipment-name:  insert: <b>  insert: <span class="arial-small">  Core switches  insert: </span>  insert: </b>  insert: <br /> 
 manufacturer-name:  insert: <b>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </b>  insert: <br /> 
 model-number:  insert: <b>  insert: <span class="arial-small">  25xx  insert: </span>  insert: </b>  insert: <br /> 
 other-data:  insert: <b>  insert: <span class="arial-small">  3 units  insert: </span>  insert: </b>  insert: </pre>

insert: <pre>

 equipment-name:  insert: <b>  insert: <span class="arial-small">  Servers  insert: </span>  insert: </b>  insert: <br /> 
 manufacturer-name:  insert: <b>  insert: <span class="arial-small">  HP  insert: </span>  insert: </b>  insert: <br /> 
 model-number:  insert: <b>  insert: <span class="arial-small">  various  insert: </span>  insert: </b>  insert: <br /> 
 other-data:  insert: <b>  insert: <span class="arial-small">  40 units  insert: </span>  insert: </b>  insert: </pre>

insert: <pre>

 equipment-name:  insert: <b>  insert: <span class="arial-small">  Firewalls  insert: </span>  insert: </b>  insert: <br /> 
 manufacturer-name:  insert: <b>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </b>  insert: <br /> 
 model-number:  insert: <b>  insert: <span class="arial-small">  PIX 515 E  insert: </span>  insert: </b>  insert: <br /> 
 other-data:  insert: <b>  insert: <span class="arial-small">  2 units, 8 IP addresses  insert: </span>  insert: </b>  insert: </pre>

insert: <pre>

 equipment-name:  insert: <b>  insert: <span class="arial-small">  Workstations  insert: </span>  insert: </b>  insert: <br /> 
 manufacturer-name:  insert: <b>  insert: <span class="arial-small">  Dell  insert: </span>  insert: </b>  insert: <br /> 
 model-number:  insert: <span class="arial-small">  insert: <b>  GX150  insert: </b>  insert: </span>  insert: <br /> 
 other-data:  insert: <b>  insert: <span class="arial-small">  22 units, 1 IP address each  insert: </span>  insert: </b>  insert: </pre>

insert: <pre>

 equipment-name:  insert: <b>  insert: <span class="arial-small">  Routers  insert: </span>  insert: </b>  insert: <br /> 
 manufacturer-name:  insert: <b>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </b>  insert: <br /> 
 model-number:  insert: <b>  insert: <span class="arial-small">  3825  insert: </span>  insert: </b>  insert: <br /> 
 other-data:  insert: <b>  insert: <span class="arial-small">  2 units  insert: </span>  insert: </b>  insert: </pre>

insert: <pre>

 equipment-name:  insert: <b>  insert: <span class="arial-small">  Routers  insert: </span>  insert: </b>  insert: <br /> 
 manufacturer-name:  insert: <b>  insert: <span class="arial-small">  Cisco  insert: </span>  insert: </b>  insert: <br /> 
 model-number:  insert: <b>  insert: <span class="arial-small">  AS5300  insert: </span>  insert: </b>  insert: <br /> 
 other-data:  insert: <b>  insert: <span class="arial-small">  1 unit, 32 ports  insert: </span>  insert: </b>  insert: </pre>

insert: </blockquote>

insert: 

The equipment description will help us (RIPE NCC) to understand the requirements listed in the addressing plan and can be repeated as many times as needed. Leave an empty line before each new “ insert:  equipment-name: insert:  ” field. insert: 

insert: 

In the “ insert:  equipment-name: insert:  ” field, enter the type of equipment requiring address space by the RIPE NCC. Please pay careful attention delete:   to this matter. delete:   delete:   Class A from this assignment. insert: 

insert: 

Enter the vendor name and B network numbers are a scarce resource model number for the piece of equipment in the “ insert:  manufacturer-name: insert:  ” and some delete:   justification in terms of expected network size and structure will be delete:   needed before such a number can be allocated. Class A numbers will only delete:   be assigned to networks which technically need more than 65000 hosts to delete:   be on one network number. A detailed technical justification is needed, delete:   review takes place on a global scale and the allocation process can take delete:   several months. Similarly due to class B scarcity, a reasonable number delete:   of class C numbers will be assigned over class B. If you can engineer delete:   your network to use multiple class C numbers, it is strongly advised. delete:   Please note that this is contrary to earlier recommendations where it delete:   was recommended to use Bs over multiple Cs due to routing table size delete:   constraints. A one page document detailing the information needed by delete:   the NCC to evaluate requests for class B numbers is available from the delete:   NCC if it is not enclosed with this letter; this document also includes delete:   a list of recommended reading about CIDR and address allocation in delete:   general. delete:   delete:   Appended to this letter is a blank template for IP number registration, delete:   which we would be extremely grateful if you complete and return to the delete:   appropriate organisation responsible for issuing IP network numbers. In delete:   most cases this will be your IP service provider. It may of course also delete:   be the RIPE NCC. delete:   delete:   “ insert:  model-number: insert:  ” fields. insert: 

insert: 

If you have any further queries please do not hesitate to contact the delete:   NCC. more information about how this piece of equipment will use the requested address space, add this in the “ insert:  other-data: insert:  ” field. insert: 

insert: <h2>

insert: `<a name="description">` insert: `</a>` Network Description insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[NETWORK DESCRIPTION]#  insert: <br /> 
 %  insert: <br /> 
 %  Please note that all queries should,  add more information  if possible, be made through  delete: <br /> e-mail  you think it will help us  insert: <br /> 
 % understand this request.  insert: </pre>

insert: <pre class="arial-small">

 insert: <b>  We have 11 branches across Santa City linked by corporate fibre channels.  insert: <br /> 
 We will assign a /28 subnet for each branch.  insert: <br /> 
 Each branch will have SMTP, WWW, file server, e-banking  and sent to <[email protected]>. If you do not have access to  delete: <br /> electronic mail, then we prefer to communicate by fax rather than by  delete: <br /> ordinary mail.  dial-up pool.  insert: </b>  insert: </pre>

insert: <pre class="arial-small">

 insert: <b>  Public Internet Services: SMTP (2 IP addresses),  insert: <br /> 
 WWW (6 IP addresses, 2 servers), FTP (1 IP address), DNS (2 IP addresses)  insert: <br /> 
 Financial Services: 6 servers, 3 IP addresses each.  insert: <br /> 
 Operations network: Security, Monitoring, VPN, Proxy, DNS  insert: </b>  insert: </pre>

insert: </blockquote>

insert: 

You can reach us at: delete:   delete:   Kruislaan 409 Phone: +31 20 592 5065 delete:   NL-1098 SJ Amsterdam Telefax: +31 20 592 5090 delete:   The Netherlands delete:   delete:   If we do not hear from you in the near future we will assume use this space for additional information that you delete:   have contacted think will be helpful for us when we evaluate your IP service provider. delete:   delete:   Yours sincerely, delete:   delete:   delete:   delete:   The RIPE NCC staff delete:  request. A clearer understanding of the network and its addressing needs can help us to evaluate your request more quickly. insert: 

insert: <h2>

insert: `<a name="diagram">` insert: `</a>` Network Diagram insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[NETWORK DIAGRAM]#  insert: <br /> 
 %  insert: <br /> 
 % Have you attached a network diagram to this request? (Yes/No)  insert: </pre>

insert: <pre>

 diagram-attached:  insert: <b>  insert: <span class="arial-small">  Yes  insert: </span>  insert: <br /> 
 insert: </b>  insert: </pre>

insert: </blockquote>

insert: 

A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. insert: 

insert: <h2>

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

insert: <blockquote>

insert: <pre>

 #[END of REQUEST]#  insert: </pre>

insert: <pre class="arial-small">

 insert: <b>  Best Regards,  insert: <br /> 
 Jan Janssen, Bluelight Admin  insert: </b>  insert: </pre>

insert: </blockquote>

insert: 

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

RIPE Internet Network Numbers Template Supporting Notes For Provider Aggregatable (PA) Assignment Request Form

RIPE Documents Search

ripe-048

State:

Obsoleted

Updated by:

ripe-083 , ripe-088 , ripe-095 , ripe-098 , ripe-107 , ripe-115 , ripe-124 , ripe-128 , ripe-129 , ripe-137 , ripe-138 , ripe-141 , ripe-142 , ripe-219 , ripe-220 , ripe-285 , ripe-286 , ripe-315 , ripe-316 , ripe-317 , ripe-318 , ripe-336 , ripe-337 , ripe-356 , ripe-357 , ripe-381 , ripe-382 , ripe-453 , ripe-454 , ripe-455 , ripe-488 , ripe-489 , ripe-490 , ripe-491 , ripe-537 , ripe-583 , ripe-584

Authors:

D.Karrenberg

Date:

January 2011

Download

File:
ASCII | 14.0KB

Changes to RIPE Internet Network Numbers Template

insert: <a name="general"> insert: </a> General Information insert: </h2>

insert: <a name="user"> insert: </a> Address Space User insert: </h2>

insert: <a name="plan"> insert: </a> Addressing Plan insert: </h2>

insert: </h2>

insert: <a name="equipment"> insert: </a> Equipment Description insert: </h2>

insert: <a name="description"> insert: </a> Network Description insert: </h2>

insert: <a name="diagram"> insert: </a> Network Diagram insert: </h2>

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

RIPE Documents Search

ripe-048

insert: `<a name="general">` insert: `</a>` General Information insert: `</h2>`

insert: `<a name="user">` insert: `</a>` Address Space User insert: `</h2>`

insert: `<a name="plan">` insert: `</a>` Addressing Plan insert: `</h2>`

insert: `</h2>`

insert: `<a name="equipment">` insert: `</a>` Equipment Description insert: `</h2>`

insert: `<a name="description">` insert: `</a>` Network Description insert: `</h2>`

insert: `<a name="diagram">` insert: `</a>` Network Diagram insert: `</h2>`

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