Changes to Supporting Notes For Provider Aggregatable (PA) Assignment Request Form
Legend | (+) Added | (-) Deleted |
---|---|---|
Changed | Tag Added | Tag Deleted |
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 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 contains instructions for LIRs on how to 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 the “ delete: <a data-val="ad8cc394acf725d0acbdeb5d20356d9c" href="resolveuid/ad8cc394acf725d0acbdeb5d20356d9c" data-linktype="internal" class="internal-link"> 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 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 region”. delete: </p> delete: <p> LIRs should send separate “Provider Aggregatable (PA) Assignment Request” forms for each End User. delete: </p> delete: <hr /> delete: <ul> delete: <li> delete: <a href="#general"> General Information delete: </a> delete: </li> delete: <li> delete: <a href="#user"> Address Space User delete: </a> delete: </li> delete: <li> delete: <a href="#plan"> Addressing Plan delete: </a> delete: </li> delete: <li> delete: <a href="#equipment"> Equipment Description delete: </a> delete: </li> delete: <li> delete: <a href="#description"> Network Description delete: </a> delete: </li> delete: <li> delete: <a href="#diagram"> Network Diagram delete: </a> delete: </li> delete: <li> delete: <a href="#end"> End of Request delete: </a> delete: </li> delete: </ul> delete: <hr /> delete: <h2> delete: <a name="general"> delete: </a> General Information delete: </h2> delete: <blockquote> 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.2 delete: <br /> x-ncc-regid: delete: <span class="arial-small"> delete: <b> nl.bluelight delete: </b> delete: </span> delete: </pre> delete: </blockquote> delete: <p> Please NCC. insert: <br />
insert: <br />
If you have any further queries please do not change the value of the “ delete: <span class="pre"> request-type: delete: </span> ” and “ delete: <span class="pre"> form-version: delete: </span> ” fields. delete: </p> delete: <p> Enter your Registry Identifier (RegID) in the “ delete: <span class="pre"> x-ncc-regid: delete: </span> ” field. RegIDs have the following format: <country code>.<name>. hesitate to contact the insert: <br />
NCC. Please note that all queries should, if possible, be made through insert: <br />
e-mail and sent to <[email protected]>. If you do not know your RegID, please contact <[email protected]>. delete: </p> delete: <h2> delete: <a name="user"> delete: </a> Address Space User delete: </h2> delete: <blockquote> delete: <pre> #[ADDRESS SPACE USER]# delete: <br /> % delete: <br /> % Who will use the requested address space? delete: <br /> % delete: <br /> % legal-organisation-name: delete: <span class="arial-small"> delete: <b> North SantaBank delete: </b> delete: </span> delete: <br /> organisation-location: delete: <span class="arial-small"> delete: <b> Santa City, NN delete: </b> delete: </span> delete: <br /> website-if-available: delete: <span class="arial-small"> delete: <b> http://www.nsb.nn delete: </b> delete: </span> 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: <span class="arial-small"> delete: <b> No delete: </b> delete: </span> delete: </pre> delete: </blockquote> delete: <p> Enter the legal name and primary location of the organisation that will use this address space in the “ delete: <span class="pre"> legal-organisation-name: delete: </span> ” and “ delete: <span class="pre"> organisation-location: delete: </span> ” fields. If this End User has a website, enter the URL in the “ delete: <span class="pre"> website-if-available: delete: </span> ” 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 “ delete: <span class="pre"> space-available: delete: </span> ” field. If you answer “yes”, you can explain why the End User needs another assignment of address space in the “ delete: <span class="pre"> Network Description delete: </span> ” section at the end of this form. delete: </p> delete: <h2> delete: <a name="plan"> delete: </a> Addressing Plan delete: </h2> delete: <blockquote> delete: <pre> #[ADDRESSING PLAN]# delete: </pre> delete: <pre> % As of 1 January 2010 assignments are for a period of up to 12 months. delete: <br /> % As of 1 July 2010 assignments are for a period of up to 9 months. delete: <br /> % As of 1 January 2011 assignments are for a period of up to 6 months. delete: <br /> % As of 1 July 2011 assignments are for a period of up to 3 months. delete: </pre> delete: <pre> % 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: </pre> delete: <pre> subnet: delete: <b> /26 32 64 64 Employee VPN delete: </b> delete: <b> Access delete: </b> delete: <br /> subnet: delete: <b> /26 18 34 64 Financial Services delete: </b> delete: <br /> subnet: delete: <b> /26 22 30 60 Workstations delete: </b> delete: <br /> subnet: delete: <b> /27 11 15 28 Public Services delete: </b> delete: <br /> subnet: delete: <b> /27 7 18 30 Operations delete: </b> delete: <br /> subnet: delete: <b> /24 176 192 240 Branch Offices delete: </b> delete: <br /> totals: delete: <b> /23 266 353 486 delete: </b> delete: <br /> delete: </pre> delete: <pre> number-of-subnets: delete: <b> 6 delete: </b> delete: </pre> delete: <pre> % Will the End User return any address space? delete: </pre> delete: <pre> address-space-returned: delete: <b> 85.118.187/24 to nl.bluelight in 3 months delete: </b> delete: </pre> delete: <p> The addressing plan shows how the End User will use the requested address space. access to insert: <br />
electronic mail, then we prefer to communicate by fax rather than by insert: <br />
ordinary mail. 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 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 Netherlands insert: <br />
insert: <br />
If we do not hear from you in the near future we will assume that subnet over the next time period. 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