Changes to RIPE Internet Network Numbers Template

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 href="https://www.ripe.net/../ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" class="external-link" title=""> insert: <span class="external-link"> here insert: </span> insert: </a> . insert: </strong> insert: </p>

To request resources from the RIPE Internet Network Numbers Template delete: <br /> delete: <br /> D.Karrenberg delete: <br /> delete: <br /> Aug 1992 delete: <br /> delete: <br /> delete: <br /> delete: <br /> To whom it may concern, delete: <br /> delete: <br /> NCC, members should now use the request forms in the insert: <a class="external-link" title="" href="https://lirportal.ripe.net/" target="_self"> LIR Portal insert: </a> . insert: </p>

The RIPE Network Coordination Centre now handles all requests for IP delete: <br /> network numbers insert: <a class="external-link" title="" href="http://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self"> Resource Request API insert: </a> and accompanying documentation is available for members with workflows that prevent them from European organisations. Our aim is to provide a delete: <br /> rapid and efficient service to all European organisations. As this is delete: <br /> a recent initiative, procedures for handling network number requests are delete: <br /> in the process of being established. Therefore we apologise in advance delete: <br /> for any duplication of effort 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 using the LIR Portal request forms. insert: </p>

  insert: </p>

This document contains instructions for LIRs on how to complete and for us to process. delete: <br /> Before the “ insert: <a class="external-link" title="" href="http://www.ripe.net/ripe/docs/iprequestform" target="_self"> Provider Aggregatable (PA) Assignment Request Form insert: </a> ”. insert: </p>

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

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

insert: <li>
• insert: <a class="anchor-link" title="" href="#general-information" target="_self"> General Information insert: </a> insert: </li>
insert: <li>
• insert: <a class="anchor-link" title="" href="#address-space-user" target="_self"> Address Space User insert: </a> insert: </li>
insert: <li>
• insert: <a class="anchor-link" title="" href="#addressing-plan" target="_self"> Addressing Plan insert: </a> insert: </li>
insert: <li>
• insert: <a class="anchor-link" title="" href="#equipment-description" target="_self"> Equipment Description insert: </a> insert: </li>
insert: <li>
• insert: <a class="anchor-link" title="" href="#network-description" target="_self"> Network Description insert: </a> insert: </li>
insert: <li>
• insert: <a class="anchor-link" title="" href="#network-diagram" target="_self"> Network Diagram insert: </a> insert: </li>
insert: <li>
• insert: <a class="anchor-link" title="" href="#end-of-request" target="_self"> End insert: </a> insert: <a class="anchor-link" title="" href="#end-of-request" target="_self"> insert: <span class="anchor-link"> of Request insert: </span> insert: </a> insert: </li>
insert: </ul>

insert: <strong> insert: <a name="general-information"> insert: </a> General Information insert: </strong> insert: </h3>

 #[GENERAL INFORMATION]#  insert: <br /> 
 %  insert: <br /> 
 % Please add  your application  RegID.  insert: <br /> 
 %  insert: <br /> 
 % request-type: pa-ipv4  insert: <br /> 
 form-version: 1.3  insert: <br /> 
 x-ncc-regid:  insert: <strong>  nl.bluelight  insert: </strong>  insert: </pre> 

Please do not change the value of the “request-type:” and “form-version:” fields. insert: </p>

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 protected]>. insert: </p>

insert: <strong> insert: <a name="address-space-user"> insert: </a> Address Space User insert: </strong> insert: </h3>

 #[ADDRESS SPACE USER]#  insert: <br /> 
 %  insert: <br /> 
 % Who will use the requested address space?  insert: <br /> 
 %  insert: <br /> 
 % legal-organisation-name:  insert: <strong>  North SantaBank  insert: </strong>  insert: <br /> 
 organisation-location:  insert: <strong>  Santa City, NN  insert: </strong>  insert: <br /> 
 website-if-available:  insert: <strong>  http://www.nsb.nn  insert: </strong>  insert: <br /> 
 %  insert: <br /> 
 % Does this End User already have address space that  can be processed  insert: <br /> 
 % used for this assignment? (Yes/No)  insert: <br /> 
 %  insert: <br /> 
 % space-available:  insert: <strong>  No  insert: </strong>  insert: </pre> 

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

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

insert: <strong> insert: <a name="addressing-plan"> insert: </a> Addressing Plan insert: </strong> insert: </h3>

 #[ADDRESSING PLAN]#  insert: <br /> 
 % How will the End User use this address space?  insert: <br /> 
 %  insert: <br /> 
 % Subnet Immediate Intermediate Entire Purpose  insert: <br /> 
 % size (/nn) Requirement Requirement Period  insert: <br /> 
 insert: <br /> 
 subnet:  insert: <strong>  /26 32 64 64 Employee VPN  insert: </strong>  insert: <strong>  Access  insert: </strong>  insert: <br /> 
 subnet:  insert: <strong>  /26 18 34 64 Financial Services  insert: </strong>  insert: <br /> 
 subnet:  insert: <strong>  /26 22 30 60 Workstations  insert: </strong>  insert: <br /> 
 subnet:  insert: <strong>  /27 11 15 28 Public Services  insert: </strong>  insert: <br /> 
 subnet:  insert: <strong>  /27 7 18 30 Operations  insert: </strong>  insert: <br /> 
 subnet:  insert: <strong>  /24 176 192 240 Branch Offices  insert: </strong>  insert: <br /> 
 totals:  insert: <strong>  /23 266 353 486  insert: </strong>  insert: <br /> 
 insert: <br /> 
 number-of-subnets:  insert: <strong>  6  insert: </strong>  insert: <br /> 
 insert: <br /> 
 % Will the End User return any address space?  insert: <br /> 
 insert: <br /> 
 address-space-returned:  insert: <strong>  85.118.187/24 to nl.bluelight in 3 months  insert: </strong>  insert: </pre> 

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: </p>

In order to demonstrate the predicted growth of your network, you must provide an estimate of the address space you will need require over three distinct periods: Immediate, Intermediate and the Entire period. Your estimates should include interfaces used for hosts, routers, gateways, terminal concentrators and any other machines requiring one or more network 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: </p>

Assignments' immediate utilisation should be at least 25% of the assigned space. After one year, this should be at least 50% of the space unless special circumstances are defined. insert: </p>

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: </p>

In the “totals” row, add the total of each column. The total of the “Subnet size (/nn)” column should be the total amount of address space you are requesting for this assignment. insert: </p>

In the “number-of-subnets:” field, enter the total number of subnets listed in the addressing plan. insert: </p>

The “netname:” should be a short, descriptive name for the network and should reflect the End User's organisation name. You should use the same “netname:” when you register this assignment in the RIPE Whois Database. insert: </p>

If there is any address space assigned to delete: <br /> complete the enclosed templates and return them the End User that they will return, list each prefix in separate “address-space-returned:” fields. The expected time for renumbering is three months. You can use the following syntax: <x.x.x.x/xx> to the appropriate delete: <br /> organisation responsible for issuing IP network numbers. In most cases delete: <br /> this <which LIR/ISP> in <time period> for this field. insert: </p>

insert: <strong> insert: <a name="equipment-description"> insert: </a> Equipment Description insert: </strong> insert: </h3>

 #[EQUIPMENT DESCRIPTION]#  insert: <br /> 
 %  insert: <br /> 
 % What equipment  will be your  used and how will it use the  insert: <br /> 
 % requested address space?  insert: <br /> 
 equipment-name:  insert: <strong>  Core switches  insert: </strong>  insert: <br /> 
 manufacturer-name:  insert: <strong>  Cisco  insert: </strong>  insert: <br /> 
 model-number:  insert: <strong>  25xx  insert: </strong>  insert: <br /> 
 other-data:  insert: <strong>  3 units  insert: </strong>  insert: <br /> 
 equipment-name:  insert: <strong>  Servers  insert: </strong>  insert: <br /> 
 manufacturer-name:  insert: <strong>  HP  insert: </strong>  insert: <br /> 
 model-number:  insert: <strong>  various  insert: </strong>  insert: <br /> 
 other-data:  insert: <strong>  40 units  insert: </strong>  insert: <br /> 
 equipment-name:  insert: <strong>  Firewalls  insert: </strong>  insert: <br /> 
 manufacturer-name:  insert: <strong>  Cisco  insert: </strong>  insert: <br /> 
 model-number:  insert: <strong>  PIX 515 E  insert: </strong>  insert: <br /> 
 other-data:  insert: <strong>  2 units, 8  IP service provider or the RIPE NCC. Before  delete: <br /> completion of the template, please  addresses  insert: </strong>  insert: <br /> 
 equipment-name:  insert: <strong>  Workstations  insert: </strong>  insert: <br /> 
 manufacturer-name:  insert: <strong>  Dell  insert: </strong>  insert: <br /> 
 model-number:  insert: <strong>  GX150  insert: </strong>  insert: <br /> 
 other-data:  insert: <strong>  22 units, 1 IP address each  insert: </strong>  insert: <br /> 
 equipment-name:  insert: <strong>  Routers  insert: </strong>  insert: <br /> 
 manufacturer-name:  insert: <strong>  Cisco  insert: </strong>  insert: <br /> 
 model-number:  insert: <strong>  3825  insert: </strong>  insert: <br /> 
 other-data:  insert: <strong>  2 units  insert: </strong>  insert: <br /> 
 equipment-name:  insert: <strong>  Routers  insert: </strong>  insert: <br /> 
 manufacturer-name:  insert: <strong>  Cisco  insert: </strong>  insert: <br /> 
 model-number:  insert: <strong>  AS5300  insert: </strong>  insert: <br /> 
 other-data:  insert: <strong>  1 unit, 32 ports  insert: </strong>  insert: </pre> 

The equipment description will help us (RIPE NCC) to understand the requirements listed in the addressing plan and can be sure to read the following text delete: <br /> and examples carefully which will guide you. delete: <br /> delete: <br /> A repeated as many times as needed. Leave an empty line before each new classless IP addressing scheme called CIDR has recently been delete: <br /> adopted to cope with routing table growth and “equipment-name:” field. insert: </p>

In the “equipment-name:” field, enter the type of equipment requiring address space exhaustion delete: <br /> problems in the Internet. Under this scheme it is beneficial for delete: <br /> everyone to get their network numbers allocated via their respective delete: <br /> IP service providers. Your IP service provider is the organisation delete: <br /> providing external connectivity to your network. If you are planning delete: <br /> to connect your network to other networks outside your organisation in delete: <br /> the foreseeable future we strongly urge you to get numbers allocated delete: <br /> from your current or prospective IP service provider. Alternatively, if delete: <br /> this is not likely, then you will be allocated a this assignment. insert: </p>

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

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

insert: <a name="network-description"> insert: </a> Network Description insert: </h3>

 #[NETWORK DESCRIPTION]#  insert: <br /> 
 %  insert: <br /> 
 %  Please note that all queries should,  add more information  if possible, be made through  delete: <br /> e-mail and sent to <[email protected]>. If  you do not  think it will help us  insert: <br /> 
 % understand this request.  insert: <strong>  insert: <br /> 
 We  have access to  delete: <br /> electronic mail, then we prefer to communicate  11 branches across Santa City linked  by fax rather than by  delete: <br /> ordinary mail.  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 dial-up pool.  insert: <br /> 
 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: </strong>  insert: </pre> 

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

insert: <strong> insert: <a name="network-diagram"> insert: </a> Network Diagram insert: </strong> insert: </h3>

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

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

insert: <a name="end-of-request"> insert: </a> End of Request insert: </h3>

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

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