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-312: ripe-609: Supporting Notes For The for the IPv4 First Allocation Request Form

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>

insert: <p>

This document contains instructions for LIRs on how to complete the " insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/first-allocation" target="_self" title=""> IPv4 First Allocation Request Form insert: </a> ". The instructions are based on the " 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 insert: </a> ". insert: </p>

insert: <ul> insert: <p>

insert: </p>

insert: <hr />
insert: <h3>

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

insert: <pre>
 #[GENERAL INFORMATION]#  insert: <br /> 
% insert: <br />
% Please add your RegID. insert: </pre>
insert: <pre>
 request-type: ipv4-first-alloc  insert: <br /> 
form-version: 1.2 insert: <br />
x-ncc-regid: nl.bluelight insert: </pre>
insert: <p>

Please do not change the value of the "request-type:" and insert: <br />
"form-version:" fields. insert: </p>

insert: <p>

Enter your Registry Identifier (RegID) in the "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>. insert: </p>

insert: <h3>

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

insert: <pre>
 #[REQUESTER TEMPLATE]#  insert: <br /> 
% insert: <br />
% Please add your contact details. insert: </pre>
insert: <pre>
 name: John Smith  insert: <br /> 
phone: +123 45 678910 insert: <br />
email: john@bluelight.ripe.net insert: </pre>
insert: <p>

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

insert: <p>

Please use the international dialling codes (for example, +31 for the Netherlands,) in the "phone:" field. insert: </p>

insert: <h3>

insert: <a name="address-space-usage"> insert: </a> Address Space Usage insert: </h3>

insert: <pre>
 #[ADDRESS SPACE USAGE]#  insert: <br /> 
% insert: <br />
% Will you make assignment(s) from the requested allocation? (Yes/No) insert: </pre>
insert: <pre>
 usage-confirmation: Yes  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 own infrastructure or customers, enter "Yes". insert: </p>

insert: <h3>

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

insert: <pre>
 #[DATABASE TEMPLATE(S)]#  insert: <br /> 
% insert: <br />
% Please complete all of the fields below. insert: </pre>
insert: <pre>
 inetnum:  insert: <br /> 
netname: insert: <br />
descr: insert: <br />
country: NL insert: <br />
org: insert: <br />
admin-c: HOHO1-RIPE insert: <br />
tech-c: HOHO1-RIPE insert: <br />
status: ALLOCATED PA insert: <br />
mnt-by: RIPE-NCC-HM-MNT insert: <br />
mnt-lower: BLUELIGHT-MNT insert: <br />
mnt-routes: BLUELIGHT-MNT insert: <br />
notify: john@bluelight.ripe.net insert: <br />
changed: hostmaster@ripe.net insert: <br />
source: RIPE insert: </pre>
insert: <p>

Leave the "inetnum:", "netname:", "org:" and "descr:" fields empty as we (the RIPE NCC) will complete them. insert: </p>

insert: <p>

Enter the ISO country code of the country where the resource will be announced in the "country:" field. insert: </p>

insert: <p>

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 additional person, role and maintainer objects using insert: <a data-linktype="internal" target="_self" title="" href="./resolveuid/9b44ba81d0c52950aa7b5160d2a49412" data-val="9b44ba81d0c52950aa7b5160d2a49412" class="external-link"> webupdates insert: </a> . insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

The "status:" field must be 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 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. insert: </p>

insert: <p>

The "mnt-routes:" field shows which maintainer authorises the creation of route objects for the allocation block. insert: </p>

insert: <p>

The RIPE Whois database must contain all of the objects that you mention. insert: </p>

insert: <p>

We will send an email to the email address in the "notify:" field every time the allocation object is updated. insert: </p>

insert: <p>

The "changed:" field must be hostmaster@ripe.net. insert: </p>

insert: <p>

The "source:" field must be RIPE. insert: </p>

insert: <h3>

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

insert: <pre>
 #[INSERT SUPPLEMENTAL COMMENTS]#  insert: <br /> 
% insert: <br />
% You can add more information if necessary insert: </pre>
insert: <p>

You can use this space for additional information that you think will be helpful for us when we evaluate your request. insert: </p>

insert: <h3>

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

insert: <pre>
 #[END of REQUEST]#  insert: </pre> 
Supporting Notes For The for the IPv4 First Allocation Request Form
RIPE Documents Search