You are here: Home > Publications > RIPE Document Store > Supporting Notes For Provider Aggregatable (PA) Assignment Request Form

Changes to Supporting Notes For Provider Aggregatable (PA) Assignment Request Form

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-584: This document contains instructions for LIRs on how to complete the “Provider Aggregatable (PA) Assignment Request Form”. ripe-048: RIPE Internet Network Numbers Template
delete: <p> delete: <strong> insert: <p style="text-align: left; ">

RIPE Internet Network Numbers Template insert: <br />
insert: <br />
D.Karrenberg insert: <br />
insert: <br />
Aug 1992 insert: <br />
insert: <br />
insert: <br />
insert: <br />
To whom it may concern, insert: <br />
insert: <br />
The RIPE Network Coordination Centre now handles all requests for IP insert: <br />
network numbers from European organisations. Our aim is to provide a insert: <br />
rapid and efficient service to all European organisations. As this is insert: <br />
a recent initiative, procedures for handling network number requests are insert: <br />
in the process of being established. Therefore we apologise in advance insert: <br />
for any duplication of effort that may be required by you due to new insert: <br />
forms and templates. As the European NIC, we require different insert: <br />
information to that required by the US and for it to be presented in a insert: <br />
format which is both easy for you to complete and for us to process. insert: <br />
Before your application can be processed any further, you will need to insert: <br />
complete the enclosed templates and return them to the appropriate insert: <br />
organisation responsible for issuing IP network numbers. In most cases insert: <br />
this will be your IP service provider or the RIPE NCC. Before insert: <br />
completion of the template, please be sure to read the following text insert: <br />
and examples carefully which will guide you. insert: <br />
insert: <br />
A new classless IP addressing scheme called CIDR has recently been insert: <br />
adopted to cope with routing table growth and address space exhaustion insert: <br />
problems in the Internet. Under this scheme it is beneficial for insert: <br />
everyone to get their network numbers allocated via their respective insert: <br />
IP service providers. Your IP service provider is the organisation insert: <br />
providing external connectivity to your network. If you are planning insert: <br />
to connect your network to other networks outside your organisation in insert: <br />
the foreseeable future we strongly urge you to get numbers allocated insert: <br />
from your current or prospective IP service provider. Alternatively, if insert: <br />
this is not likely, then you will be allocated a number from a different insert: <br />
part of the address space by the RIPE NCC. Please note: pay careful attention insert: <br />
to this matter. insert: <br />
insert: <br />
Class A and B network numbers are a scarce resource and some insert: <br />
justification in terms of expected network size and structure will be insert: <br />
needed before such a number can be allocated. Class A numbers will only insert: <br />
be assigned to networks which technically need more than 65000 hosts to insert: <br />
be on one network number. A detailed technical justification is needed, insert: <br />
review takes place on a global scale and the allocation process can take insert: <br />
several months. Similarly due to class B scarcity, a reasonable number insert: <br />
of class C numbers will be assigned over class B. If you can engineer insert: <br />
your network to use multiple class C numbers, it is strongly advised. insert: <br />
Please note that this is contrary to earlier recommendations where it insert: <br />
was recommended to use Bs over multiple Cs due to routing table size insert: <br />
constraints. A one page document detailing the information needed by insert: <br />
the NCC to evaluate requests for class B numbers is available from the insert: <br />
NCC if it is not enclosed with this letter; this document also includes insert: <br />
a list of recommended reading about CIDR and address allocation in insert: <br />
general. insert: <br />
insert: <br />
Appended to this letter is a blank template for IP number registration, insert: <br />
which we would be extremely grateful if you complete and return to the insert: <br />
appropriate organisation responsible for issuing IP network numbers. In insert: <br />
most cases this will be your IP service provider. It may of course also insert: <br />
be the RIPE NCC. insert: <br />
insert: <br />
If you have any further queries please do not hesitate to contact the insert: <br />
NCC. Please note that all email-based request forms queries should, if possible, be made through insert: <br />
e-mail and sent to <[email protected]>. If you do not have been archived on the website and are available through the LIR Portal. access to insert: <br />
electronic mail, then we prefer to communicate by fax rather than by insert: <br />
ordinary mail. You can find an announcement about this delete: <a href="https://www.ripe.net/../ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" class="external-link" title=""> delete: <span class="external-link"> here delete: </span> delete: </a> . delete: </strong> delete: </p> delete: <p> To request resources from the RIPE NCC, members should now use the request forms in the delete: <a class="external-link" title="" href="https://lirportal.ripe.net/" target="_self"> LIR Portal delete: </a> . delete: </p> delete: <p> reach us at: insert: <br />
insert: <br />
Kruislaan 409 Phone: +31 20 592 5065 insert: <br />
NL-1098 SJ Amsterdam Telefax: +31 20 592 5090 insert: <br />
The delete: <a class="external-link" title="" href="http://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self"> Resource Request API delete: </a> and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms. delete: </p> delete: <p>   delete: </p> delete: <p> This document contains instructions for LIRs on how to complete the “ delete: <a class="external-link" title="" href="http://www.ripe.net/ripe/docs/iprequestform" target="_self"> Provider Aggregatable (PA) Assignment Request Form delete: </a> ”. delete: </p> delete: <p> The instructions are based on the “IPv4 Address Allocation and Assignment Policy for the RIPE region”. delete: </p> delete: <p> LIRs should send separate “Provider Aggregatable (PA) Assignment Request” forms for each End User. delete: </p> delete: <div align="center"> delete: <hr align="center" size="2" width="100%" /> delete: </div> delete: <ul> delete: <li> delete: <a class="anchor-link" title="" href="#general-information" target="_self"> General Information delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" title="" href="#address-space-user" target="_self"> Address Space User delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" title="" href="#addressing-plan" target="_self"> Addressing Plan delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" title="" href="#equipment-description" target="_self"> Equipment Description delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" title="" href="#network-description" target="_self"> Network Description delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" title="" href="#network-diagram" target="_self"> Network Diagram delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" title="" href="#end-of-request" target="_self"> End delete: </a> delete: <a class="anchor-link" title="" href="#end-of-request" target="_self"> delete: <span class="anchor-link"> of Request delete: </span> delete: </a> delete: </li> delete: </ul> delete: <div align="center"> delete: <hr align="center" size="2" width="100%" /> delete: </div> delete: <h3> delete: <strong> delete: <a name="general-information"> delete: </a> General Information delete: </strong> delete: </h3> delete: <pre> #[GENERAL INFORMATION]# delete: <br /> % delete: <br /> % Please add your RegID. delete: <br /> % delete: <br /> % request-type: pa-ipv4 delete: <br /> form-version: 1.3 delete: <br /> x-ncc-regid: delete: <strong> nl.bluelight delete: </strong> delete: </pre> delete: <p> Please Netherlands insert: <br />
insert: <br />
If we do not change the value of the “request-type:” and “form-version:” fields. hear from you in the near future we will assume that you insert: <br />
have contacted your IP service provider. insert: <br />
insert: <br />
Yours sincerely, insert: <br />
insert: <br />
insert: <br />
insert: <br />
The RIPE NCC staff

delete: <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]>. delete: </p> delete: <h3> delete: <strong> delete: <a name="address-space-user"> delete: </a> Address Space User delete: </strong> delete: </h3> delete: <pre> #[ADDRESS SPACE USER]# delete: <br /> % delete: <br /> % Who will use the requested address space? delete: <br /> % delete: <br /> % legal-organisation-name: delete: <strong> North SantaBank delete: </strong> delete: <br /> organisation-location: delete: <strong> Santa City, NN delete: </strong> delete: <br /> website-if-available: delete: <strong> http://www.nsb.nn delete: </strong> delete: <br /> % delete: <br /> % Does this End User already have address space that can be delete: <br /> % used for this assignment? (Yes/No) delete: <br /> % delete: <br /> % space-available: delete: <strong> No delete: </strong> delete: </pre> delete: <p> 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. delete: </p> delete: <p> If there is any 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. delete: </p> delete: <h3> delete: <strong> delete: <a name="addressing-plan"> delete: </a> Addressing Plan delete: </strong> delete: </h3> delete: <pre> #[ADDRESSING PLAN]# delete: <br /> % How will the End User use this address space? delete: <br /> % delete: <br /> % Subnet Immediate Intermediate Entire Purpose delete: <br /> % size (/nn) Requirement Requirement Period delete: <br /> delete: <br /> subnet: delete: <strong> /26 32 64 64 Employee VPN delete: </strong> delete: <strong> Access delete: </strong> delete: <br /> subnet: delete: <strong> /26 18 34 64 Financial Services delete: </strong> delete: <br /> subnet: delete: <strong> /26 22 30 60 Workstations delete: </strong> delete: <br /> subnet: delete: <strong> /27 11 15 28 Public Services delete: </strong> delete: <br /> subnet: delete: <strong> /27 7 18 30 Operations delete: </strong> delete: <br /> subnet: delete: <strong> /24 176 192 240 Branch Offices delete: </strong> delete: <br /> totals: delete: <strong> /23 266 353 486 delete: </strong> delete: <br /> delete: <br /> number-of-subnets: delete: <strong> 6 delete: </strong> delete: <br /> delete: <br /> % Will the End User return any address space? delete: <br /> delete: <br /> address-space-returned: delete: <strong> 85.118.187/24 to nl.bluelight in 3 months delete: </strong> delete: </pre> delete: <p> 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. delete: </p> delete: <p> In order to demonstrate the predicted growth of your network, you must provide an estimate of the address space you will 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). delete: </p> delete: <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. delete: </p> delete: <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. delete: </p> delete: <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. delete: </p> delete: <p> In the “number-of-subnets:” field, enter the total number of subnets listed in the addressing plan. delete: </p> delete: <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. delete: </p> delete: <p> If there is any address space assigned to 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 <which LIR/ISP> in <time period> for this field. delete: </p> delete: <h3> delete: <strong> delete: <a name="equipment-description"> delete: </a> Equipment Description delete: </strong> delete: </h3> delete: <pre> #[EQUIPMENT DESCRIPTION]# delete: <br /> % delete: <br /> % What equipment will be used and how will it use the delete: <br /> % requested address space? delete: <br /> equipment-name: delete: <strong> Core switches delete: </strong> delete: <br /> manufacturer-name: delete: <strong> Cisco delete: </strong> delete: <br /> model-number: delete: <strong> 25xx delete: </strong> delete: <br /> other-data: delete: <strong> 3 units delete: </strong> delete: <br /> equipment-name: delete: <strong> Servers delete: </strong> delete: <br /> manufacturer-name: delete: <strong> HP delete: </strong> delete: <br /> model-number: delete: <strong> various delete: </strong> delete: <br /> other-data: delete: <strong> 40 units delete: </strong> delete: <br /> equipment-name: delete: <strong> Firewalls delete: </strong> delete: <br /> manufacturer-name: delete: <strong> Cisco delete: </strong> delete: <br /> model-number: delete: <strong> PIX 515 E delete: </strong> delete: <br /> other-data: delete: <strong> 2 units, 8 IP addresses delete: </strong> delete: <br /> equipment-name: delete: <strong> Workstations delete: </strong> delete: <br /> manufacturer-name: delete: <strong> Dell delete: </strong> delete: <br /> model-number: delete: <strong> GX150 delete: </strong> delete: <br /> other-data: delete: <strong> 22 units, 1 IP address each delete: </strong> delete: <br /> equipment-name: delete: <strong> Routers delete: </strong> delete: <br /> manufacturer-name: delete: <strong> Cisco delete: </strong> delete: <br /> model-number: delete: <strong> 3825 delete: </strong> delete: <br /> other-data: delete: <strong> 2 units delete: </strong> delete: <br /> equipment-name: delete: <strong> Routers delete: </strong> delete: <br /> manufacturer-name: delete: <strong> Cisco delete: </strong> delete: <br /> model-number: delete: <strong> AS5300 delete: </strong> delete: <br /> other-data: delete: <strong> 1 unit, 32 ports delete: </strong> delete: </pre> delete: <p> 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 “equipment-name:” field. delete: </p> delete: <p> In the “equipment-name:” field, enter the type of equipment requiring address space from this assignment. delete: </p> delete: <p> Enter the vendor name and model number for the piece of equipment in the “manufacturer-name:” and “model-number:” fields. delete: </p> delete: <p> If you have any more information about how this piece of equipment will use the requested address space, add this in the “other-data:” field. delete: </p> delete: <h3> delete: <a name="network-description"> delete: </a> Network Description delete: </h3> delete: <pre> #[NETWORK DESCRIPTION]# delete: <br /> % delete: <br /> % Please add more information if you think it will help us delete: <br /> % understand this request. delete: <strong> delete: <br /> We have 11 branches across Santa City linked by corporate fibre channels. delete: <br /> We will assign a /28 subnet for each branch. delete: <br /> Each branch will have SMTP, WWW, file server, e-banking and dial-up pool. delete: <br /> Public Internet Services: SMTP (2 IP addresses), delete: <br /> WWW (6 IP addresses, 2 servers), FTP (1 IP address), DNS (2 IP addresses) delete: <br /> Financial Services: 6 servers, 3 IP addresses each. delete: <br /> Operations network: Security, Monitoring, VPN, Proxy, DNS delete: </strong> delete: </pre> delete: <p> You can use this space for additional information that you think will be helpful for us when we evaluate your request. A clearer understanding of the network and its addressing needs can help us to evaluate your request more quickly. delete: </p> delete: <h3> delete: <strong> delete: <a name="network-diagram"> delete: </a> Network Diagram delete: </strong> delete: </h3> delete: <pre> #[NETWORK DIAGRAM]# delete: <br /> % delete: <br /> % Have you attached a network diagram to this request? (Yes/No) delete: <br /> delete: <br /> diagram-attached: delete: <strong> Yes delete: </strong> delete: </pre> delete: <p> A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. delete: </p> delete: <h3> delete: <a name="end-of-request"> delete: </a> End of Request delete: </h3> delete: <pre> #[END of REQUEST]# delete: <strong> delete: <br /> delete: <br /> Best Regards, delete: <br /> Jan Janssen, Bluelight Admin delete: </strong> delete: </pre> delete: <p> Please write your full name below the “#[END of REQUEST]#” header. delete: </p>
Supporting Notes For Provider Aggregatable (PA) Assignment Request Form RIPE Internet Network Numbers Template