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

delete: <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 delete: <a class="external-link" href="https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" title=""> here delete: </a> . delete: </strong> delete: </p> delete: <p> To request resources from the RIPE NCC, members should now use the request forms in the delete: <a class="external-link" href="https://lirportal.ripe.net/" target="_self" title=""> LIR Portal delete: </a> . delete: </p> delete: <p> The delete: <a class="external-link" href="https://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self" title=""> Resource Request API delete: </a> and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms. delete: </p> delete: <p> delete: </p> delete: <p> 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=""> IPv4 First Allocation Request Form delete: </a> ". The instructions are based on the " delete: <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: </a> ". delete: </p> delete: <ul> delete: <li> delete: <a class="anchor-link" href="#general-information" target="_self" title=""> General Information delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" href="#requester-template" target="_self" title=""> Requester Template delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" href="#address-space-usage" target="_self" title=""> 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> delete: </li> delete: <li> delete: <a class="anchor-link" href="#database-templates" target="_self" title=""> delete: <span class="anchor-link"> Database Template(s) delete: </span> delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" href="#insert-supplemental-comments" target="_self" title=""> Insert Supplemental Comments delete: </a> delete: </li> delete: <li> delete: <a class="anchor-link" href="#end-of-request" target="_self" title=""> End of Request delete: </a> delete: </li> delete: </ul> delete: <p> delete: </p> delete: <hr /> delete: <h3> delete: <a name="general-information"> delete: </a> General Information delete: </h3> delete: <pre> #[GENERAL INFORMATION]# delete: <br /> % delete: <br /> % Please add your RegID. delete: </pre> delete: <pre> request-type: ipv4-first-alloc delete: <br /> form-version: 1.2 delete: <br /> x-ncc-regid: nl.bluelight delete: </pre> delete: <p> Please do not change the value of the "request-type:" and delete: <br /> "form-version:" fields. delete: </p> delete: <p> Enter your Registry Identifier (RegID) in the "x-ncc-regid:" delete: <br /> field. RegIDs have the following format: <country code>.<name>. If you delete: <br /> do not know your RegID, please contact <[email protected]>. delete: </p> delete: <h3> delete: <a name="requester-template"> delete: </a> Requester Template delete: </h3> delete: <pre> #[REQUESTER TEMPLATE]# delete: <br /> % delete: <br /> % Please add your contact details. delete: </pre> delete: <pre> name: John Smith delete: <br /> phone: +123 45 678910 delete: <br /> email: [email protected] delete: </pre> delete: <p> 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=""> LIR Portal delete: </a> contains the list of registered contacts for your LIR. delete: </p> delete: <p> 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> Address Space Usage delete: </h3> delete: <pre> #[ADDRESS SPACE USAGE]# delete: <br /> % delete: <br /> % Will 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. If you plan to make assignments to your own infrastructure or customers, enter "Yes". delete: </p> delete: <h3> delete: <a name="database-templates"> delete: </a> Database Template(s) delete: </h3> delete: <pre> #[DATABASE TEMPLATE(S)]# delete: <br /> % delete: <br /> % Please complete all of the fields below. delete: </pre> delete: <pre> inetnum: delete: <br /> netname: delete: <br /> descr: delete: <br /> country: NL delete: <br /> org: delete: <br /> admin-c: HOHO1-RIPE delete: <br /> tech-c: HOHO1-RIPE delete: <br /> status: ALLOCATED PA delete: <br /> mnt-by: RIPE-NCC-HM-MNT delete: <br /> mnt-lower: BLUELIGHT-MNT delete: <br /> mnt-routes: BLUELIGHT-MNT delete: <br /> notify: [email protected] delete: <br /> changed: [email protected] delete: <br /> source: RIPE delete: </pre> delete: <p> Leave the "inetnum:", "netname:", "org:" and "descr:" fields empty as we (the RIPE NCC) will complete them. delete: </p> delete: <p> Enter the ISO country code of the country where the resource will be announced in the "country:" field. delete: </p> delete: <p> Person and role objects contain information about people. Each object has a unique NIC handle (nic-hdl). delete: </p> delete: <p> 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 using delete: <a data-linktype="internal" target="_self" title="" href="./resolveuid/9b44ba81d0c52950aa7b5160d2a49412" data-val="9b44ba81d0c52950aa7b5160d2a49412" class="external-link"> webupdates delete: </a> . delete: </p> delete: <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. 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:" field must be ALLOCATED PA. delete: </p> delete: <p> The "mnt-by:" field must be RIPE-NCC-HM-MNT. 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> . delete: </p> delete: <p> The "mnt-lower:" field shows which maintainer authorises the creation of inetnum objects (i.e. assignments) within the allocation block. delete: </p> delete: <p> The "mnt-routes:" field shows which maintainer authorises the creation of route objects for the allocation block. delete: </p> delete: <p> The RIPE Whois database must contain all of the objects that you mention. delete: </p> delete: <p> We will send an email to the email address in the "notify:" field every time the allocation object is updated. delete: </p> delete: <p> The "changed:" field must be [email protected] delete: </p> delete: <p> The "source:" field must be RIPE. delete: </p> delete: <h3> delete: <a name="insert-supplemental-comments"> delete: </a> Insert Supplemental Comments delete: </h3> delete: <pre> #[INSERT SUPPLEMENTAL COMMENTS]# delete: <br /> % delete: <br /> % You can add more information if necessary delete: </pre> delete: <p> You can use this space for additional information that you think will be helpful for us when we evaluate your request. delete: </p> delete: <h3> delete: <a name="end-of-request"> delete: </a> End of Request delete: </h3> delete: <pre> #[END of REQUEST]# delete: </pre>

Supporting Notes for the For The IPv4 First Allocation Request Form
RIPE Documents Search