Changes to Provider Independent (PI) Assignment Request Form
Legend | (+) Added | (-) Deleted |
---|---|---|
Changed | Tag Added | Tag Deleted |
RIPE document 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 obsoleted 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 the RIPE NCC reaching the last /8 class B scarcity, a reasonable number insert: <br />
of IPv4 address space. delete: </a> delete: </p> delete: <p> delete: <img src="./resolveuid/1f075ef0-1420-4b37-95a9-b77d6721138b" alt="" class="image-inline" title="" data-val="1f075ef0-1420-4b37-95a9-b77d6721138b" data-linktype="image" /> delete: </p> delete: <pre> % Provider Independent (PI) Assignment Request Form delete: <br /> delete: <br /> % RIPE NCC members (LIRs) and Direct Assignment Users class C numbers will be assigned over class B. If you can engineer insert: <br />
your network to use this form delete: <br /> % to request a PI assignment. Please see "Supporting Notes for the delete: <br /> % Provider Independent (PI) Assignment Request Form" for instructions on delete: <br /> % how to complete this form. delete: <br /> % http://www.ripe.net/ripe/docs/pi-requestsupport.html delete: <br /> % delete: <br /> % multiple class C numbers, it is strongly advised. insert: <br />
Please note that the End User should have a signed "End User delete: <br /> % Assignment Agreement" 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 either the sponsoring LIR or 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.
#[GENERAL INFORMATION]# delete: <br /> % delete: <br /> % If you have any further queries please do not hesitate to contact the insert: <br />
NCC. Please add your RegID. delete: <br /> delete: <br /> request-type: pi-ipv4 delete: <br /> form-version: 1.3 delete: <br /> x-ncc-regid: delete: <br /> delete: <br /> #[ADDRESS SPACE USER]# delete: <br /> % delete: <br /> % Who will use the requested address space? delete: <br /> delete: <br /> legal-organisation-name: delete: <br /> organisation-location: delete: <br /> website-if-available: delete: <br /> delete: <br /> % Is this request being note that all queries should, if possible, be made through insert: <br />
e-mail and sent to <[email protected]>. If you do not have access to insert: <br />
electronic mail, then we prefer to communicate by a sponsoring LIR on behalf of delete: <br /> % an End User? (Yes/No) delete: <br /> delete: <br /> end-user-of-sponsoring-lir: delete: <br /> delete: <br /> % fax rather than by insert: <br />
ordinary mail. You can 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 yes, please confirm we do not hear from you in the near future we will assume that the "End User Assignment Agreement" delete: <br /> % contains all of the elements listed in paragraph 2.0 of "Contractual delete: <br /> % Requirements for Provider Independent Resource Holders in the delete: <br /> % 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 Service Region".(Yes/No) delete: <br /> delete: <br /> confirmation: delete: <br /> delete: <br /> % Does this End User already have address space that can be used for delete: <br /> % this assignment? (Yes/No) delete: <br /> delete: <br /> space-available: delete: <br /> delete: <br /> #[INITIAL INFORMATION]# delete: <br /> % delete: <br /> % Why is PI address space required rather than PA address space? delete: <br /> delete: <br /> why-pi: delete: <br /> delete: <br /> % Is the End User requesting extra address space for routing and/or delete: <br /> % administrative reasons? (Yes/No) delete: <br /> delete: <br /> routing-reasons: delete: <br /> delete: <br /> % Is the End User aware of the consequences and disadvantages delete: <br /> % of PI address space? (Yes/No) delete: <br /> delete: <br /> confirmation: delete: <br /> delete: <br /> delete: <br /> #[ADDRESSING PLAN]# delete: <br /> % 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: <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: <br /> subnet: delete: <br /> totals: delete: <br /> delete: <br /> number-of-subnets: delete: <br /> delete: <br /> % Will the End User return any address space? delete: <br /> delete: <br /> address-space-returned: delete: <br /> delete: <br /> #[EQUIPMENT DESCRIPTION]# delete: <br /> % delete: <br /> % What equipment will be used and how will it use the requested delete: <br /> % address space? delete: <br /> delete: <br /> equipment-name: delete: <br /> manufacturer-name: delete: <br /> model-number: delete: <br /> other-data: delete: <br /> delete: <br /> equipment-name: delete: <br /> manufacturer-name: delete: <br /> model-number: delete: <br /> other-data: delete: <br /> delete: <br /> #[NETWORK DESCRIPTION]# delete: <br /> % delete: <br /> % Please add more information if you think it will help us understand delete: <br /> % this request. delete: <br /> delete: <br /> <add more information> delete: <br /> delete: <br /> #[SUPPORTING DOCUMENTATION]# delete: <br /> % delete: <br /> % If this request is being sent by a sponsoring LIR on behalf of delete: <br /> % an End User, please attach a copy of the signed "End User Assignment delete: <br /> % Agreement" and the company registration papers of the End User. delete: <br /> % You can also attach a network diagram or other supporting delete: <br /> % documentation. delete: <br /> % delete: <br /> % Have you attached any files/documents to this request? (Yes/No) delete: <br /> delete: <br /> file-attached: delete: <br /> delete: <br /> #[DATABASE TEMPLATE(S)]# delete: <br /> % delete: <br /> % Please complete all of the fields below. delete: <br /> delete: <br /> inetnum: <leave empty> delete: <br /> netname: <add netname> delete: <br /> descr: <add End User organisation name> delete: <br /> country: <add country code> delete: <br /> org: <add org-ID> delete: <br /> admin-c: <add nic-handle of administrative contact> delete: <br /> tech-c: <add nic-handle of technical contact> delete: <br /> status: ASSIGNED PI delete: <br /> mnt-by: RIPE-NCC-END-MNT delete: <br /> mnt-lower: RIPE-NCC-END-MNT delete: <br /> mnt-by: <add mntner name> delete: <br /> mnt-routes: <add mntner name> delete: <br /> mnt-domains: <add mntner name> delete: <br /> changed: [email protected] delete: <br /> source: RIPE delete: <br /> delete: <br /> delete: <br /> #[END of REQUEST]# delete: <br /> delete: <br /> delete: <br /> delete: </pre> delete: <p> delete: <img src="./resolveuid/93c82862-6241-4309-8d0f-9d4355eeded7" alt="" class="image-inline" title="" data-val="93c82862-6241-4309-8d0f-9d4355eeded7" data-linktype="image" /> staff