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-273: Supporting Notes ripe-362: This document contains instructions for LIRs on how to complete the IPv4 "IPv4 First Allocation Request Form Form".

This document contains instructions for LIRs on how to complete the " 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: </a> ". insert: 

insert: 

The instructions are based on the " 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 Document region insert: </a> " . insert: 

insert: 

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. insert: 

insert: <ul>

insert: <li>

insert: <a href="#general"> General Information insert: </a> insert: </li>

insert: <li>

insert: <a href="#requester"> Requester Template insert: </a> insert: </li>

insert: <li>

insert: <a href="#current"> Current Address Space insert: </a> insert: </li>

insert: <li>

insert: <a href="#prefix"> Current Address Space Prefix Template insert: </a> insert: </li>

insert: <li>

insert: <a href="#database"> Database Template(s) insert: </a> insert: </li>

insert: <li>

insert: <a href="#comments"> Insert Supplemental Comments insert: </a> insert: </li>

insert: <li>

insert: <a href="#end"> End of Request insert: </a> insert: </li>

insert: </ul>

insert: <hr />

insert: <h2>

insert: `<a name="general">` insert: `</a>` General Information insert: `</h2>`

insert: <blockquote>

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.1  insert: <br /> 
 x-ncc-regid:  insert: <strong>  insert: <span class="arial-small">  nl.bluelight  insert: </span>  insert: </strong>  insert: </pre>

insert: </blockquote>

insert: 

Please do not change the value of the " insert:  request-type: insert:  " and " insert:  form-version: insert:  " fields. insert: 

insert: 

Enter your Registry Identifier (RegID) in the " insert:  x-ncc-regid: insert:  " field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact <[email protected]>. insert: 

insert: <h2>

insert: `<a name="requester">` insert: `</a>` Requester Template insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[REQUESTER TEMPLATE]#  insert: <br /> 
 %  insert: <br /> 
 % Please add your contact details.  insert: </pre>

insert: <pre>

 name:  insert: <strong>  insert: <span class="arial-small">  John Smith  insert: </span>  insert: </strong>  insert: <br /> 
 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>  insert: <br /> 
 email:  insert: <strong>  insert: <span class="arial-small">  [email protected]  insert: </span>  insert: </strong>  insert: <br /> 
 nic-hdl:  insert: <strong>  insert: <span class="arial-small">  HOHO1-RIPE  insert: </span>  insert: </strong>  insert: </pre>

insert: </blockquote>

insert: 

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

insert: 

Please use the international dialling codes (for example, +31 for the Netherlands,) in the " insert:  phone: insert:  " and " insert:  fax-no: insert:  " fields. insert: 

insert: 

Enter your NIC handle in the " insert:  nic-hdl: insert:  " field, if you have one. insert: 

insert: <h2>

insert: `<a name="current">` insert: `</a>` Current Address Space insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[CURRENT ADDRESS SPACE]#  insert: <br /> 
 %  insert: <br /> 
 % Are you currently using any address space? (Yes/No)  insert: </pre>

insert: <pre>

 current-address:  insert: <strong>  insert: <span class="arial-small">  Yes  insert: </span>  insert: </strong>  insert: </pre>

insert: </blockquote>

insert: 

Enter ‘Yes' in the " insert:  current-address: insert:  " field if there is available in ASCII any address space registered to your organisation in the RIPE Whois database. insert: 

insert: <h2>

insert: `<a name="prefix">` insert: `</a>` Current Address Space Prefix Template insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[CURRENT ADDRESS SPACE PREFIX TEMPLATE]#  insert: <br /> 
 %  insert: <br /> 
 % If yes, which address prefix are you using?  insert: </pre>

insert: <pre>

 actual-prefix:  insert: <strong>  insert: <span class="arial-small">  192.0.2.0/24  insert: </span>  insert: </strong>  insert: <br /> 
 actual-prefix:  insert: <strong>  insert: <span class="arial-small">  2001:DB8:5::/48  insert: </span>  insert: </strong>  insert: </pre>

insert: </blockquote>

insert: 

If you have entered ‘Yes' in the "Current Address Space" section, please list all of your address space in the " insert:  actual-prefix: insert:  " field. Please specify address prefixes using slash notation (for example, insert:  x.x.x.x/xx insert:  or insert:  y:y:y::/yy insert:  ). You can repeat the " insert:  actual-prefix: insert:  " field as many times as needed. insert: 

insert: <h2>

insert: `<a name="database">` insert: `</a>` Database Template(s) insert: `</h2>`

insert: <blockquote>

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: <strong>  insert: <span class="arial-small">  Bluelight B.V.  insert: </span>  insert: </strong>  insert: <br /> 
 country:  insert: <strong>  insert: <span class="arial-small">  NL  insert: </span>  insert: </strong>  insert: <br /> 
 org:  insert: <strong>  insert: <span class="arial-small">  ORG-Bb2-RIPE  insert: </span>  insert: </strong>  insert: <br /> 
 admin-c:  insert: <strong>  insert: <span class="arial-small">  HOHO1-RIPE  insert: </span>  insert: </strong>  insert: <br /> 
 tech-c:  insert: <strong>  insert: <span class="arial-small">  HOHO1-RIPE  insert: </span>  insert: </strong>  insert: <br /> 
 status: ALLOCATED PA  insert: <br /> 
 mnt-by: RIPE-NCC-HM-MNT  insert: <br /> 
 mnt-lower:  insert: <strong>  insert: <span class="arial-small">  BLUELIGHT-MNT  insert: </span>  insert: </strong>  insert: <br /> 
 mnt-routes:  insert: <strong>  insert: <span class="arial-small">  BLUELIGHT-MNT  insert: </span>  insert: </strong>  insert: <br /> 
 notify:  insert: <strong>  insert: <span class="arial-small">  [email protected]  insert: </span>  insert: </strong>  insert: <br /> 
 changed: [email protected]  insert: <br /> 
 source: RIPE  insert: </pre>

insert: </blockquote>

insert: 

Leave the " insert:  inetnum: insert:  " and PDF delete:  " insert:  netname: insert:  " fields empty as we (the RIPE NCC) will complete them. insert: 

insert: 

Enter the legal name of the LIR's organisation in the " insert:  descr: insert:  " field. insert: 

insert: 

Enter the ISO country code of the LIR's organisation in the " insert:  country: insert:  " field. insert: 

insert: 

Enter the org-ID of the LIR's organisation object in the " insert:  org: insert:  " 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> ). insert: 

insert: 

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:  https://www.ripe.net/webupdates insert:  insert: </a> ). insert: 

insert: 

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

insert: 

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

insert: 

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 ( insert: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net insert: </a> ). insert: 

insert: 

The " insert:  mnt-by: insert:  " field must be insert:  RIPE-NCC-HM-MNT insert:  . You will be able to update your allocation object using the Allocation Editor ( insert: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net insert: </a> ). insert: 

insert: 

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

insert: 

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

insert: 

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

insert: 

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

insert: 

The " insert:  changed: insert:  " field must be [email protected]. insert: 

insert: 

The " insert:  source: insert:  " field must be RIPE. insert: 

insert: <h2>

insert: `<a name="comments">` insert: `</a>` Insert Supplemental Comments insert: `</h2>`

insert: <blockquote>

insert: <pre>

 #[INSERT SUPPLEMENTAL COMMENTS]#  insert: <br /> 
 %  insert: <br /> 
 % Please add more information if you have specific  insert: <br /> 
 insert: <br /> 
 % addressing needs.  insert: </pre>

insert: <pre>

 insert: <strong>  insert: <span class="arial-small">  We will send one infrastructure request (/24)  insert: <br /> 
 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>

insert: </blockquote>

insert: 

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

insert: <h2>

insert: `<a name="end">` insert: `</a>` End of Request insert: `</h2>`

insert: <blockquote>

insert: <pre>
 #[END of REQUEST]# insert: </pre> 
insert: </blockquote>

insert: 

insert:  
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: 

insert: 

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: 

Supporting Notes for the For The IPv4 First Allocation Request Form

RIPE Documents Search

ripe-273

State:

Obsoleted

Updated by:

ripe-312 , ripe-333 , ripe-362 , ripe-609

Updates:

ripe-236

Authors:

Filiz Yilmaz Bican

Emma Bretherick

Agata Peszkowska

Ingrid Wijte

Date:

August 2003

Download

File:
PDF | 38.0KB

Download

File:
ASCII | 13.0KB

Changes to Supporting Notes for the IPv4 First Allocation Request Form

insert: <a name="general"> insert: </a> General Information insert: </h2>

insert: <a name="requester"> insert: </a> Requester Template insert: </h2>

insert: <a name="current"> insert: </a> Current Address Space insert: </h2>

insert: <a name="prefix"> insert: </a> Current Address Space Prefix Template insert: </h2>

insert: <a name="database"> insert: </a> Database Template(s) insert: </h2>

insert: <a name="comments"> insert: </a> Insert Supplemental Comments insert: </h2>

insert: <a name="end"> insert: </a> End of Request insert: </h2>

RIPE Documents Search

ripe-273

insert: `<a name="general">` insert: `</a>` General Information insert: `</h2>`

insert: `<a name="requester">` insert: `</a>` Requester Template insert: `</h2>`

insert: `<a name="current">` insert: `</a>` Current Address Space insert: `</h2>`

insert: `<a name="prefix">` insert: `</a>` Current Address Space Prefix Template insert: `</h2>`

insert: `<a name="database">` insert: `</a>` Database Template(s) insert: `</h2>`

insert: `<a name="comments">` insert: `</a>` Insert Supplemental Comments insert: `</h2>`

insert: `<a name="end">` insert: `</a>` End of Request insert: `</h2>`