You are here: Home > Publications > RIPE Document Store > Supporting Notes For The IPv4 First Allocation Request Form

Changes to Supporting Notes For The IPv4 First Allocation Request Form

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-362: This document contains instructions ripe-609: Supporting Notes for LIRs on how to complete the "IPv4 IPv4 First Allocation Request Form". Form
insert: <p>

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

insert: <p>

To request resources from the RIPE NCC, members should now use the request forms in the insert: <a class="external-link" href="https://lirportal.ripe.net/" target="_self" title=""> LIR Portal insert: </a> . insert: </p>

insert: <p>

The insert: <a class="external-link" href="https://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self" title=""> Resource Request API insert: </a> and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms. insert: </p>

insert: <p>

insert: </p>

This document contains instructions for LIRs on how to complete the " delete: <a href="http://www.ripe.net/publications/docs/first-allocation.html" data-linktype="external" data-val="http://www.ripe.net/publications/docs/first-allocation.html"> insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/first-allocation" target="_self" title=""> IPv4 First Allocation Request Form ". delete: </p> delete: <p> The instructions are based on the " delete: <a href="http://www.ripe.net/publications/docs/ipv4-policies.html" data-linktype="external" data-val="http://www.ripe.net/publications/docs/ipv4-policies.html"> insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies" target="_self" title=""> IPv4 Address Allocation and Assignment Policy for the RIPE region " . delete: </p> delete: <p> LIRs should also send one or more " delete: <a href="http://www.ripe.net/publications/docs/iprequestform.html" data-linktype="external" data-val="http://www.ripe.net/publications/docs/iprequestform.html"> Provider Aggregatable (PA) Assignment Request Forms delete: </a> " for all pending infrastructure and/or customer assignments. ".

insert: <p>

insert: </p>


delete: <h2> delete: <a name="general"> insert: <h3>

insert: <a name="general-information"> General Information delete: </h2> delete: <blockquote> insert: </h3>

 #[GENERAL INFORMATION]# 
%
% Please add your RegID.
 request-type: ipv4-first-alloc 
form-version: 1.1 1.2
x-ncc-regid: delete: <strong> delete: <span class="arial-small"> nl.bluelight delete: </span> delete: </strong> delete: </pre> delete: </blockquote> insert: </pre>

Please do not change the value of the " delete: <span class="pre"> request-type: delete: </span> " "request-type:" and " delete: <span class="pre"> form-version: delete: </span> " insert: <br />
"form-version:" fields.

Enter your Registry Identifier (RegID) in the " delete: <span class="pre"> x-ncc-regid: delete: </span> " "x-ncc-regid:" insert: <br />
field. RegIDs have the following format: <country code>.<name>. If you insert: <br />
do not know your RegID, please contact <ncc@ripe.net>.

delete: <h2> delete: <a name="requester"> insert: <h3>

insert: <a name="requester-template"> Requester Template delete: </h2> delete: <blockquote> insert: </h3>

 #[REQUESTER TEMPLATE]# 
%
% Please add your contact details.
 name: delete: <strong> delete: <span class="arial-small"> John Smith delete: </span> delete: </strong> 
phone: delete: <strong> delete: <span class="arial-small"> +123 45 678910 delete: </span> delete: </strong> delete: <br /> fax-no: delete: <strong> delete: <span class="arial-small"> +123 45 678911 delete: </span> delete: </strong>
email: delete: <strong> delete: <span class="arial-small"> john@bluelight.ripe.net delete: </span> delete: </strong> delete: <br /> nic-hdl: delete: <strong> delete: <span class="arial-small"> HOHO1-RIPE delete: </span> delete: </strong> delete: </pre> delete: </blockquote> insert: </pre>

Enter your contact details in the requester template. You must be a registered contact for the LIR. The delete: <a href="https://lirportal.ripe.net"> insert: <a class="external-link" href="https://lirportal.ripe.net" target="_self" title=""> LIR Portal contains the list of registered contacts for your LIR.

Please use the international dialling codes (for example, +31 for the Netherlands,) in the " delete: <span class="pre"> phone: delete: </span> " and " delete: <span class="pre"> fax-no: delete: </span> " fields. delete: </p> delete: <p> Enter your NIC handle in the " delete: <span class="pre"> nic-hdl: delete: </span> " field, if you have one. delete: </p> delete: <h2> delete: <a name="current"> delete: </a> Current "phone:" field. insert: </p>

insert: <h3>

insert: <a name="address-space-usage"> insert: </a> Address Space delete: </h2> delete: <blockquote> delete: <pre> #[CURRENT ADDRESS SPACE]# delete: <br /> % delete: <br /> % Are Usage insert: </h3>

insert: <pre>
 #[ADDRESS SPACE USAGE]#  insert: <br /> 
% insert: <br />
% Will you currently using any address space? make assignment(s) from the requested allocation? (Yes/No)
 current-address:  delete: <strong> delete: <span class="arial-small"> usage-confirmation:  Yes delete: </span> delete: </strong> delete: </pre> delete: </blockquote> delete: <p> Enter ‘Yes' in the "  delete: <span class="pre"> current-address:  delete: </span> " field if there is any address space registered  insert: </pre> 
insert: <p>

To receive the allocation please confirm that you will make assignment(s) from the allocation. If you plan to make assignments to your organisation in the RIPE Whois database. delete: </p> delete: <h2> delete: <a name="prefix"> delete: </a> Current Address Space Prefix Template delete: </h2> delete: <blockquote> delete: <pre> #[CURRENT ADDRESS SPACE PREFIX TEMPLATE]# delete: <br /> % delete: <br /> % If yes, which address prefix are you using? delete: </pre> delete: <pre> actual-prefix: delete: <strong> delete: <span class="arial-small"> 192.0.2.0/24 delete: </span> delete: </strong> delete: <br /> actual-prefix: delete: <strong> delete: <span class="arial-small"> 2001:DB8:5::/48 delete: </span> delete: </strong> delete: </pre> delete: </blockquote> delete: <p> If you have entered ‘Yes' in the "Current Address Space" section, please list all of your address space in the " delete: <span class="pre"> actual-prefix: delete: </span> " field. Please specify address prefixes using slash notation (for example, delete: <span class="pre"> x.x.x.x/xx delete: </span> own infrastructure or delete: <span class="pre"> y:y:y::/yy delete: </span> ). You can repeat the " delete: <span class="pre"> actual-prefix: delete: </span> " field as many times as needed. delete: </p> delete: <h2> delete: <a name="database"> customers, enter "Yes". insert: </p>

insert: <h3>

insert: <a name="database-templates"> Database Template(s) delete: </h2> delete: <blockquote> insert: </h3>

 #[DATABASE TEMPLATE(S)]# 
%
% Please complete all of the fields below.
 inetnum: 
netname:
descr: delete: <strong> delete: <span class="arial-small"> Bluelight B.V. delete: </span> delete: </strong>
country: delete: <strong> delete: <span class="arial-small"> NL delete: </span> delete: </strong>
org: delete: <strong> delete: <span class="arial-small"> ORG-Bb2-RIPE delete: </span> delete: </strong>
admin-c: delete: <strong> delete: <span class="arial-small"> HOHO1-RIPE delete: </span> delete: </strong>
tech-c: delete: <strong> delete: <span class="arial-small"> HOHO1-RIPE delete: </span> delete: </strong>
status: ALLOCATED PA
mnt-by: RIPE-NCC-HM-MNT
mnt-lower: delete: <strong> delete: <span class="arial-small"> BLUELIGHT-MNT delete: </span> delete: </strong>
mnt-routes: delete: <strong> delete: <span class="arial-small"> BLUELIGHT-MNT delete: </span> delete: </strong>
notify: delete: <strong> delete: <span class="arial-small"> john@bluelight.ripe.net delete: </span> delete: </strong>
changed: hostmaster@ripe.net
source: RIPE
delete: </blockquote>

Leave the " delete: <span class="pre"> inetnum: delete: </span> " "inetnum:", "netname:", "org:" and " delete: <span class="pre"> netname: delete: </span> " "descr:" fields empty as we (the RIPE NCC) will complete them.

Enter the legal name of the LIR's organisation in the " delete: <span class="pre"> descr: delete: </span> " field. delete: </p> delete: <p> Enter the ISO country code of the LIR's organisation country where the resource will be announced in the " delete: <span class="pre"> country: delete: </span> " "country:" field. delete: </p> delete: <p> Enter the org-ID of the LIR's organisation object in the " delete: <span class="pre"> org: delete: </span> " field. If you don't know your LIR's org-ID, you can find it in the Organisation Object Editor ( delete: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net delete: </a> ).

Person and role objects contain information about people. Each object has a unique NIC handle (nic-hdl). insert: </p>

insert: <p>

Maintainers protect objects in the RIPE Whois database. They contain the information needed to authorise creation, deletion or modification of these objects. insert: </p>

insert: <p>

To create the first person and maintainer objects of an organisation, you can use insert: <a class="external-link" href="https://apps.db.ripe.net/startup/" target="_self" title=""> https://apps.db.ripe.net/startup/ insert: </a> insert: </p>

insert: <p>

You can create person additional person, role and role maintainer objects using insert: <a data-linktype="internal" target="_self" title="" href="./resolveuid/9b44ba81d0c52950aa7b5160d2a49412" data-val="9b44ba81d0c52950aa7b5160d2a49412" class="external-link"> webupdates ( delete: <a class="external-link" title="" href="https://apps.db.ripe.net/webupdates" target="_self"> delete: <span class="external-link"> https://www.ripe.net/webupdates delete: </span> delete: </a> ). insert: </a> .

The nic-hdl of the role or person object in the " delete: <span class="pre"> admin-c: delete: </span> " "admin-c:" field should reflect someone who is administratively responsible for the network.

The nic-hdl of the role or person object in the " delete: <span class="pre"> tech-c: delete: </span> " "tech-c:" field should reflect someone who has technical knowledge of the network.

Maintainers protect objects in the RIPE Whois database. They contain the information needed to authorise creation, deletion or modification of these objects. You can create maintainers using the Maintainer Editor ( delete: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net delete: </a> ). delete: </p> delete: <p> The " delete: <span class="pre"> mnt-by: delete: </span> " The "status:" field must be delete: <span class="pre"> RIPE-NCC-HM-MNT delete: </span> . ALLOCATED PA. insert: </p>

insert: <p>

The "mnt-by:" field must be RIPE-NCC-HM-MNT. You will be able to update your allocation object using the Allocation Editor ( delete: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net delete: </a> ). delete: </p> delete: <p> The " delete: <span class="pre"> mnt-lower: delete: </span> " insert: <a class="external-link" href="https://lirportal.ripe.net" target="_self" title=""> Object Editors insert: </a> . insert: </p>

insert: <p>

The "mnt-lower:" field shows which maintainer authorises the creation of inetnum objects (i.e. assignments) within the allocation block.

The " delete: <span class="pre"> mnt-routes: delete: </span> " "mnt-routes:" field shows which maintainer authorises the creation of route objects for the allocation block.

The RIPE Whois database must contain all of the objects that you enter. mention.

We will send an email to the email address in the " delete: <span class="pre"> notify: delete: </span> " "notify:" field every time the allocation object is updated.

The " delete: <span class="pre"> changed: delete: </span> " "changed:" field must be hostmaster@ripe.net.

The " delete: <span class="pre"> source: delete: </span> " "source:" field must be RIPE.

delete: <h2> delete: <a name="comments"> insert: <h3>

insert: <a name="insert-supplemental-comments"> Insert Supplemental Comments delete: </h2> delete: <blockquote> insert: </h3>

 #[INSERT SUPPLEMENTAL COMMENTS]# 
%
% Please You can add more information if you have specific delete: <br /> delete: <br /> % addressing needs. delete: </pre> delete: <pre> delete: <strong> delete: <span class="arial-small"> We will send one infrastructure request (/24) delete: <br /> and three customer requests (/27 each) later today. delete: <br /> This is for all of our immediate addressing needs. delete: </span> delete: </strong> delete: </pre> delete: </blockquote> necessary insert: </pre>

You can use this space for additional information that you think will be helpful for us when we evaluate your request.

delete: <h2> delete: <a name="end"> insert: <h3>

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

 #[END of REQUEST]# 
delete: </blockquote> delete: <p> delete: <br /> When you have sent this request form to us, please send separate " delete: <a href="http://www.ripe.net/publications/docs/iprequestform.html"> Provider Aggregatable (PA) Assignment Request Forms delete: </a> " for all pending infrastructure and customer assignments. Complete one PA Assignment Request form for your infrastructure and additional PA Assignment forms for each organisation you will assign PA address space to. Send each form in a separate email to <hostmaster@ripe.net>. delete: </p> delete: <p> You will receive a unique ticket number (NCC#xxxxxxxxxx) for each form. We will then evaluate the requests for your first allocation and your first PA assignment(s) at the same time. delete: </p>
Supporting Notes For The for the IPv4 First Allocation Request Form
RIPE Documents Search