Changes to RIPE Internet Network Numbers Template

insert: <a data-val="046f7e54-4540-4541-adff-aceeea440a2f" href="resolveuid/046f7e54-4540-4541-adff-aceeea440a2f" data-linktype="internal" class="internal-link"> This 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 /> The document has been obsoleted due to the RIPE Network Coordination Centre now handles all requests for IP delete: <br /> network numbers from European organisations. Our aim is to provide a delete: <br /> rapid NCC reaching the last /8 of IPv4 address space. insert: </a> insert: </p>

insert: <img src="./resolveuid/1f075ef0-1420-4b37-95a9-b77d6721138b" alt="" class="image-inline" title="" data-val="1f075ef0-1420-4b37-95a9-b77d6721138b" data-linktype="image" /> insert: </p>

 % Provider Independent (PI) Assignment Request Form  insert: <br /> 
 insert: <br /> 
 % RIPE NCC members (LIRs)  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  Direct Assignment Users can use this form  insert: <br /> 
 % to request a PI assignment. Please see "Supporting Notes for the  insert: <br /> 
 % Provider Independent (PI) Assignment Request Form" for instructions on  insert: <br /> 
 % how  to complete and for us to process.  delete: <br /> Before your application can be processed any further, you will need to  delete: <br /> complete the enclosed templates and return them to the appropriate  delete: <br /> organisation responsible for issuing IP network numbers. In most cases  delete: <br /> this will be your IP service provider or the RIPE NCC. Before  delete: <br /> completion of the template, please be sure to read the following text  delete: <br /> and examples carefully which will guide you.  delete: <br /> delete: <br /> A new classless IP addressing scheme called CIDR has recently been  delete: <br /> adopted to cope with routing table growth and 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 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 /> this form.  insert: <br /> 
 % http://www.ripe.net/ripe/docs/pi-requestsupport.html  insert: <br /> 
 %  insert: <br /> 
 %  Please note that this  the End User should have a signed "End User  insert: <br /> 
 % Assignment Agreement" with either the sponsoring LIR or the RIPE NCC.  insert: <br /> 
 insert: <br /> 
 #[GENERAL INFORMATION]#  insert: <br /> 
 %  insert: <br /> 
 % Please add your RegID.  insert: <br /> 
 insert: <br /> 
 request-type: pi-ipv4  insert: <br /> 
 form-version: 1.3  insert: <br /> 
 x-ncc-regid:  insert: <br /> 
 insert: <br /> 
 #[ADDRESS SPACE USER]#  insert: <br /> 
 %  insert: <br /> 
 % Who will use the requested address space?  insert: <br /> 
 insert: <br /> 
 legal-organisation-name:  insert: <br /> 
 organisation-location:  insert: <br /> 
 website-if-available:  insert: <br /> 
 insert: <br /> 
 % Is this request being sent by a sponsoring LIR on behalf of  insert: <br /> 
 % an End User? (Yes/No)  insert: <br /> 
 insert: <br /> 
 end-user-of-sponsoring-lir:  insert: <br /> 
 insert: <br /> 
 % If yes, please confirm that the "End User Assignment Agreement"  insert: <br /> 
 % contains all of the elements listed in paragraph 2.0 of "Contractual  insert: <br /> 
 % Requirements for Provider Independent Resource Holders in the  insert: <br /> 
 % RIPE NCC Service Region".(Yes/No)  insert: <br /> 
 insert: <br /> 
 confirmation:  insert: <br /> 
 insert: <br /> 
 % Does this End User already have address space that can be used for  insert: <br /> 
 % this assignment? (Yes/No)  insert: <br /> 
 insert: <br /> 
 space-available:  insert: <br /> 
 insert: <br /> 
 #[INITIAL INFORMATION]#  insert: <br /> 
 %  insert: <br /> 
 % Why  is contrary to earlier recommendations where  PI address space required rather than PA address space?  insert: <br /> 
 insert: <br /> 
 why-pi:  insert: <br /> 
 insert: <br /> 
 % Is the End User requesting extra address space for routing and/or  insert: <br /> 
 % administrative reasons? (Yes/No)  insert: <br /> 
 insert: <br /> 
 routing-reasons:  insert: <br /> 
 insert: <br /> 
 % Is the End User aware of the consequences and disadvantages  insert: <br /> 
 % of PI address space? (Yes/No)  insert: <br /> 
 insert: <br /> 
 confirmation:  insert: <br /> 
 insert: <br /> 
 insert: <br /> 
 #[ADDRESSING PLAN]#  insert: <br /> 
 % As of 1 January 2010 assignments are for a period of up to 12 months.  insert: <br /> 
 % As of 1 July 2010 assignments are for a period of up to 9 months.  insert: <br /> 
 % As of 1 January 2011 assignments are for a period of up to 6 months.  insert: <br /> 
 % As of 1 July 2011 assignments are for a period of up to 3 months.%  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: <br /> 
 subnet:  insert: <br /> 
 totals:  insert: <br /> 
 insert: <br /> 
 number-of-subnets:  insert: <br /> 
 insert: <br /> 
 % Will the End User return any address space?  insert: <br /> 
 insert: <br /> 
 address-space-returned:  insert: <br /> 
 insert: <br /> 
 #[EQUIPMENT DESCRIPTION]#  insert: <br /> 
 %  insert: <br /> 
 % What equipment will be used and how will  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  the requested  insert: <br /> 
 % address space?  insert: <br /> 
 insert: <br /> 
 equipment-name:  insert: <br /> 
 manufacturer-name:  insert: <br /> 
 model-number:  insert: <br /> 
 other-data:  insert: <br /> 
 insert: <br /> 
 equipment-name:  insert: <br /> 
 manufacturer-name:  insert: <br /> 
 model-number:  insert: <br /> 
 other-data:  insert: <br /> 
 insert: <br /> 
 #[NETWORK DESCRIPTION]#  insert: <br /> 
 %  insert: <br /> 
 % Please add more  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  think it will help us understand  insert: <br /> 
 % this request.  insert: <br /> 
 insert: <br /> 
 <add more information>  insert: <br /> 
 insert: <br /> 
 #[SUPPORTING DOCUMENTATION]#  insert: <br /> 
 %  insert: <br /> 
 % If this request is being sent by a sponsoring LIR on behalf of  insert: <br /> 
 % an End User, please attach a copy of the signed "End User Assignment  insert: <br /> 
 % Agreement"  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 /> If you have any further queries please do not hesitate to contact the  delete: <br /> NCC. Please note that all queries should, if possible, be made through  delete: <br /> e-mail 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.  the company registration papers of the End User.  insert: <br /> 
 %  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  also attach a network diagram or other supporting  insert: <br /> 
 % documentation.  insert: <br /> 
 %  insert: <br /> 
 % Have  you in the near future we will assume that you  delete: <br /> have contacted your IP service provider.  delete: <br /> delete: <br /> Yours sincerely,  delete: <br /> delete: <br /> delete: <br /> delete: <br /> The  attached any files/documents to this request? (Yes/No)  insert: <br /> 
 insert: <br /> 
 file-attached:  insert: <br /> 
 insert: <br /> 
 #[DATABASE TEMPLATE(S)]#  insert: <br /> 
 %  insert: <br /> 
 % Please complete all of the fields below.  insert: <br /> 
 insert: <br /> 
 inetnum: <leave empty>  insert: <br /> 
 netname: <add netname>  insert: <br /> 
 descr: <add End User organisation name>  insert: <br /> 
 country: <add country code>  insert: <br /> 
 org: <add org-ID>  insert: <br /> 
 admin-c: <add nic-handle of administrative contact>  insert: <br /> 
 tech-c: <add nic-handle of technical contact>  insert: <br /> 
 status: ASSIGNED PI  insert: <br /> 
 mnt-by: RIPE-NCC-END-MNT  insert: <br /> 
 mnt-lower: RIPE-NCC-END-MNT  insert: <br /> 
 mnt-by: <add mntner name>  insert: <br /> 
 mnt-routes: <add mntner name>  insert: <br /> 
 mnt-domains: <add mntner name>  insert: <br /> 
 changed: [email protected]  insert: <br /> 
 source:  RIPE NCC staff  insert: <br /> 
 insert: <br /> 
 insert: <br /> 
 #[END of REQUEST]#  insert: <br /> 
 insert: <br /> 
 insert: <br /> 
 insert: </pre> 

insert: <img src="./resolveuid/93c82862-6241-4309-8d0f-9d4355eeded7" alt="" class="image-inline" title="" data-val="93c82862-6241-4309-8d0f-9d4355eeded7" data-linktype="image" />