Changes to Supporting Notes for the IPv4 First Allocation Request Form
| Legend | (+) Added | (-) Deleted |
|---|---|---|
| Changed | Tag Added | Tag Deleted |
This document contains instructions for LIRs on how to complete the " delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/first-allocation" target="_self" title=""> insert: <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"> IPv4 First Allocation Request Form ". insert: </p>
insert: <p>The instructions are based on the " delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies" target="_self" title=""> insert: <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"> IPv4 Address Allocation and Assignment Policy for the RIPE region ". " . insert: </p>
insert: <p>LIRs should also send one or more " insert: <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 insert: </a> " for all pending infrastructure and/or customer assignments.
- delete: <a class="anchor-link" href="#general-information" target="_self" title=""> insert: <a href="#general"> General Information
- delete: <a class="anchor-link" href="#requester-template" target="_self" title=""> insert: <a href="#requester"> Requester Template
- delete: <a class="anchor-link" href="#address-space-usage" target="_self" title=""> insert: <a href="#current"> Current Address Space Usage delete: </a> delete: <br /> delete: <a class="anchor-link" href="#database-templates" target="_self" title=""> delete: <span class="anchor-link"> delete: </span>
- delete: <a class="anchor-link" href="#database-templates" target="_self" title=""> delete: <span class="anchor-link"> insert: <a href="#prefix"> Current Address Space Prefix Template insert: </a> insert: </li> insert: <li>
- insert: <a href="#database"> Database Template(s) delete: </span>
- delete: <a class="anchor-link" href="#insert-supplemental-comments" target="_self" title=""> insert: <a href="#comments"> Insert Supplemental Comments
- delete: <a class="anchor-link" href="#end-of-request" target="_self" title=""> insert: <a href="#end"> End of Request
delete: <h3> delete: <a name="general-information"> insert: <h2>
insert: <a name="general"> General Information delete: </h3> insert: </h2>
insert: <blockquote>#[GENERAL INFORMATION]#
%
% Please add your RegID.request-type: ipv4-first-allocinsert: </blockquote>
form-version: 1.2 1.1
x-ncc-regid: insert: <strong> insert: <span class="arial-small"> nl.bluelight delete: </pre> insert: </span> insert: </strong> insert: </pre>
Please do not change the value of the "request-type:" " insert: <span class="pre"> request-type: insert: </span> " and delete: <br /> "form-version:" " insert: <span class="pre"> form-version: insert: </span> " fields.
Enter your Registry Identifier (RegID) in the "x-ncc-regid:" delete: <br /> " insert: <span class="pre"> x-ncc-regid: insert: </span> " field. RegIDs have the following format: <country code>.<name>. If you delete: <br /> do not know your RegID, please contact <[email protected]>.
delete: <h3> delete: <a name="requester-template"> insert: <h2>insert: <a name="requester"> Requester Template delete: </h3> insert: </h2>
insert: <blockquote>#[REQUESTER TEMPLATE]#
%
% Please add your contact details.name: insert: <strong> insert: <span class="arial-small"> John Smith insert: </span> insert: </strong>insert: </blockquote>
phone: insert: <strong> insert: <span class="arial-small"> +123 45 678910 insert: </span> insert: </strong> insert: <br />
fax-no: insert: <strong> insert: <span class="arial-small"> +123 45 678911 insert: </span> insert: </strong>
email: insert: <strong> insert: <span class="arial-small"> [email protected] delete: </pre> insert: </span> insert: </strong> insert: <br />
nic-hdl: insert: <strong> insert: <span class="arial-small"> HOHO1-RIPE insert: </span> insert: </strong> insert: </pre>
Enter your contact details in the requester template. You must be a registered contact for the LIR. The delete: <a class="external-link" href="https://lirportal.ripe.net" target="_self" title=""> insert: <a href="https://lirportal.ripe.net"> 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 "phone:" field. delete: </p> delete: <h3> delete: <a name="address-space-usage"> delete: </a> " insert: <span class="pre"> phone: insert: </span> " and " insert: <span class="pre"> fax-no: insert: </span> " fields. insert: </p>
insert: <p>Enter your NIC handle in the " insert: <span class="pre"> nic-hdl: insert: </span> " field, if you have one. insert: </p>
insert: <h2>insert: <a name="current"> insert: </a> Current Address Space Usage delete: </h3> delete: <pre> #[ADDRESS insert: </h2>
insert: <blockquote>insert: <pre>insert: <p>#[CURRENT ADDRESS SPACE]# insert: <br />insert: <pre>
% insert: <br />
% Are you currently using any address space? (Yes/No) insert: </pre>current-address: insert: <strong> insert: <span class="arial-small"> Yes insert: </span> insert: </strong> insert: </pre>insert: </blockquote>
Enter ‘Yes' in the " insert: <span class="pre"> current-address: insert: </span> " field if there is any address space registered to your organisation in the RIPE Whois database. insert: </p>
insert: <h2>insert: <a name="prefix"> insert: </a> Current Address Space Prefix Template insert: </h2>
insert: <blockquote>insert: <pre>insert: <p>#[CURRENT ADDRESS SPACE USAGE]# delete: <br /> % delete: <br /> % Will PREFIX TEMPLATE]# insert: <br />insert: <pre>
% insert: <br />
% If yes, which address prefix are you make assignment(s) from the requested allocation? (Yes/No) delete: </pre> delete: <pre> usage-confirmation: Yes delete: </pre> delete: <p> To receive the allocation please confirm that you will make assignment(s) from the allocation. using? insert: </pre>actual-prefix: insert: <strong> insert: <span class="arial-small"> 192.0.2.0/24 insert: </span> insert: </strong> insert: <br />insert: </blockquote>
actual-prefix: insert: <strong> insert: <span class="arial-small"> 2001:DB8:5::/48 insert: </span> insert: </strong> insert: </pre>
If you plan to make assignments to your own infrastructure have entered ‘Yes' in the "Current Address Space" section, please list all of your address space in the " insert: <span class="pre"> actual-prefix: insert: </span> " field. Please specify address prefixes using slash notation (for example, insert: <span class="pre"> x.x.x.x/xx insert: </span> or customers, enter "Yes". delete: </p> delete: <h3> delete: <a name="database-templates"> insert: <span class="pre"> y:y:y::/yy insert: </span> ). You can repeat the " insert: <span class="pre"> actual-prefix: insert: </span> " field as many times as needed. insert: </p>
insert: <h2>insert: <a name="database"> Database Template(s) delete: </h3> insert: </h2>
insert: <blockquote>#[DATABASE TEMPLATE(S)]#
%
% Please complete all of the fields below.inetnum:insert: </blockquote>
netname:
descr: insert: <strong> insert: <span class="arial-small"> Bluelight B.V. insert: </span> insert: </strong>
country: insert: <strong> insert: <span class="arial-small"> NL insert: </span> insert: </strong>
org: insert: <strong> insert: <span class="arial-small"> ORG-Bb2-RIPE insert: </span> insert: </strong>
admin-c: insert: <strong> insert: <span class="arial-small"> HOHO1-RIPE insert: </span> insert: </strong>
tech-c: insert: <strong> insert: <span class="arial-small"> HOHO1-RIPE insert: </span> insert: </strong>
status: ALLOCATED PA
mnt-by: RIPE-NCC-HM-MNT
mnt-lower: insert: <strong> insert: <span class="arial-small"> BLUELIGHT-MNT insert: </span> insert: </strong>
mnt-routes: insert: <strong> insert: <span class="arial-small"> BLUELIGHT-MNT insert: </span> insert: </strong>
notify: insert: <strong> insert: <span class="arial-small"> [email protected] insert: </span> insert: </strong>
changed: [email protected]
source: RIPE
Leave the "inetnum:", "netname:", "org:" " insert: <span class="pre"> inetnum: insert: </span> " and "descr:" " insert: <span class="pre"> netname: insert: </span> " fields empty as we (the RIPE NCC) will complete them.
Enter the legal name of the LIR's organisation in the " insert: <span class="pre"> descr: insert: </span> " field. insert: </p>
insert: <p>Enter the ISO country code of the country where the resource will be announced in the "country:" LIR's organisation in the " insert: <span class="pre"> country: insert: </span> " field. insert: </p>
insert: <p>Enter the org-ID of the LIR's organisation object in the " insert: <span class="pre"> org: insert: </span> " field. If you don't know your LIR's org-ID, you can find it in the Organisation Object Editor ( insert: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net insert: </a> ).
Person and role objects contain information about people. Each object has a unique NIC handle (nic-hdl). You can create person and role objects using webupdates ( insert: <a class="external-link" title="" href="https://apps.db.ripe.net/webupdates" target="_self"> insert: <span class="external-link"> https://www.ripe.net/webupdates insert: </span> insert: </a> ). insert: </p>
insert: <p>The nic-hdl of the role or person object in the " insert: <span class="pre"> admin-c: insert: </span> " 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 " insert: <span class="pre"> tech-c: insert: </span> " 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. delete: </p> delete: <p> To create the first person and maintainer objects of an organisation, you can use delete: <a class="external-link" href="https://apps.db.ripe.net/startup/" target="_self" title=""> https://apps.db.ripe.net/startup/ delete: </a> delete: </p> delete: <p> You can create additional person, role and maintainer objects maintainers using delete: <a data-linktype="internal" target="_self" title="" href="./resolveuid/9b44ba81d0c52950aa7b5160d2a49412" data-val="9b44ba81d0c52950aa7b5160d2a49412" class="external-link"> webupdates delete: </a> . the Maintainer Editor ( insert: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net insert: </a> ).
The nic-hdl of the role or person object in the "admin-c:" field should reflect someone who is administratively responsible for the network. delete: </p> delete: <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. delete: </p> delete: <p> The "status:" " insert: <span class="pre"> mnt-by: insert: </span> " field must be ALLOCATED PA. delete: </p> delete: <p> The "mnt-by:" field must be RIPE-NCC-HM-MNT. insert: <span class="pre"> RIPE-NCC-HM-MNT insert: </span> . You will be able to update your allocation object using the delete: <a class="external-link" href="https://lirportal.ripe.net" target="_self" title=""> Object Editors delete: </a> . Allocation Editor ( insert: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net insert: </a> ).
The "mnt-lower:" " insert: <span class="pre"> mnt-lower: insert: </span> " field shows which maintainer authorises the creation of inetnum objects (i.e. assignments) within the allocation block.
The "mnt-routes:" " insert: <span class="pre"> mnt-routes: insert: </span> " 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 mention. enter.
We will send an email to the email address in the "notify:" " insert: <span class="pre"> notify: insert: </span> " field every time the allocation object is updated.
The "changed:" " insert: <span class="pre"> changed: insert: </span> " field must be [email protected]
The "source:" " insert: <span class="pre"> source: insert: </span> " field must be RIPE.
delete: <h3> delete: <a name="insert-supplemental-comments"> insert: <h2>insert: <a name="comments"> Insert Supplemental Comments delete: </h3> insert: </h2>
insert: <blockquote>#[INSERT SUPPLEMENTAL COMMENTS]#insert: <pre>
%
% You can Please add more information if necessary delete: </pre> you have specific insert: <br />
insert: <br />
% addressing needs. insert: </pre>insert: <strong> insert: <span class="arial-small"> We will send one infrastructure request (/24) insert: <br />insert: </blockquote>
and three customer requests (/27 each) later today. insert: <br />
This is for all of our immediate addressing needs. insert: </span> insert: </strong> insert: </pre>
You can use this space for additional information that you think will be helpful for us when we evaluate your request.
delete: <h3> delete: <a name="end-of-request"> insert: <h2>insert: <a name="end"> End of Request delete: </h3> insert: </h2>
insert: <blockquote>insert: <p>#[END of REQUEST]#insert: </blockquote>
insert: <br />
When you have sent this request form to us, please send separate " insert: <a href="http://www.ripe.net/publications/docs/iprequestform.html"> Provider Aggregatable (PA) Assignment Request Forms insert: </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 <[email protected]>. insert: </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. insert: </p>
