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

Changes to Supporting Notes For The Initial IPv6 Allocation Request Form

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-413: Supporting Notes For The Initial IPv6 ripe-422: This document contains instructions for LIRs on how to complete the “IPv6 First Allocation Request Form 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 href="https://www.ripe.net/../ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" class="external-link" 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" title="" href="https://lirportal.ripe.net/" target="_self"> LIR Portal insert: </a> . insert: </p>

insert: <p>

The insert: <a href="https://www.ripe.net/../data-tools/developer-documentation/resource-request-api" target="_self" class="external-link" 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 href="http://www.ripe.net/publications/docs/ipv6-initial.html"> IPv6 First Allocation Request Form insert: </a> ”. insert: </p>

insert: <p>

The instructions are based on the “ insert: <a href="http://www.ripe.net/publications/docs/ipv6-policy.html"> IPv6 Address Allocation and Assignment Policy insert: </a> ”. insert: </p>

insert: <hr />
insert: <ul> insert: <hr />
insert: <h2>

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

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

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

insert: <p>

Enter your Registry Identifier (RegID) in the “ x-ncc-regid:” field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact <ncc@ripe.net>. insert: </p>

insert: <h2>

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

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

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: </p>

insert: <p>

Please use international dialling codes (for example, +31 for the Netherlands,) in the “ phone:” and “ fax-no:” fields. insert: </p>

insert: <p>

Enter your NIC handle, if you have one, in the “ nic-hdl:” field. insert: </p>

insert: <h2>

insert: <br />
insert: <a name="required"> insert: </a> Required Information insert: </h2>

insert: <pre>
 #[REQUIRED INFORMATION]#  insert: <br /> 
% insert: <br />
% Do you accept the IPv6 Address Allocation and Assignment insert: <br />
% Policy? (Yes/No) insert: <br />
confirmation: insert: <strong> yes insert: </strong> insert: <br />
% If you have any online information about your future insert: <br />
% IPv6 services, please add the URL below. insert: <br />
website: insert: <strong> http://www.bluelight.ripe.net/ipv6-connectivity.html insert: </strong> insert: </pre>
insert: <p>

You must read the insert: <a href="http://www.ripe.net/publications/docs/ipv6-policy.html"> IPv6 Address Allocation and Assignment Policy insert: </a> . Enter ‘yes' in the “ confirmation:” field if you agree to follow this policy. insert: </p>

insert: <p>

If you have any online information about your planned IPv6 services, enter the URL in the “ website:” field. insert: </p>

insert: <h2>

insert: <br />
insert: <a name="overview"> insert: </a> Overview of Organisation Template insert: </h2>

insert: <pre>
 #[OVERVIEW OF ORGANISATION TEMPLATE]#  insert: <br /> 
% insert: <br />
% Please add a short description of your organisation. insert: <br />
org-description: insert: <strong> Bluelight B.V. is an ISP. We will insert: <br />
make IPv6 connectivity available to all 10,000 of our ADSL customers. insert: </strong>
insert: <br />
% If your organisation has IPv6 allocations from any of the Regional insert: <br />
% Internet Registries (RIRs), please list the ranges below. insert: <br />
other-allocation: insert: <strong> none insert: </strong> insert: <br />
% Will the whole organisation use the requested allocation? insert: <br />
% If another part of the organisation will request separate IPv6 insert: <br />
% address space from any RIR, please inform us below. (Whole/Part) insert: <br />
for-whole-or-part-of-the-organisation: insert: <strong> whole insert: </strong> insert: </pre>
insert: <p>

In the “ org-description:” field, write a short description of your organisation. Include information about your IPv6 services and customers. insert: </p>

insert: <p>

Use the “ other-allocation:” field to list all the IPv6 allocations that you already have. These can be from any RIR. You can repeat this field as many times as needed. insert: </p>

insert: <p>

Enter ‘part' in the “ for-whole-or-part-of-the-organisation:” field if any part of your organisation, anywhere in the world, will request separate IPv6 address space. Otherwise, enter ‘whole'. insert: </p>

insert: <h2>

insert: <br />
insert: <a name="allocation"> insert: </a> IPv6 Allocation Usage Plan insert: </h2>

insert: <pre>
 #[IPv6 ALLOCATION USAGE PLAN]#  insert: <br /> 
% insert: <br />
% When will you use this address space? insert: <br />
% insert: <br />
% Subnet Within Within Within insert: <br />
% size (/nn) 3 months 1 year 2 years Purpose insert: <br />
subnet: insert: <strong> /45 x - - 8 ADSL POPs insert: </strong> insert: <br />
subnet: insert: <strong> /42 - x - Corporate (64 /48s) insert: </strong> insert: <br />
subnet: insert: <strong> /48 - - x SOHOs (256 /56s) insert: </strong> insert: <br />
insert: </pre>
insert: <p>

Enter the size of each subnet in the “ Subnet size (/nn)” column. Please specify the size using IPv6 slash notation (for example, /48 or /56). You can repeat the “ subnet:” field as many times as needed. insert: </p>

insert: <p>

If an End Site needs more than a /48, a separate request form must be submitted. insert: </p>

insert: <p>

In the “ Purpose” column, write a short description of each subnet. If needed, you can write a more detailed description in the “ Insert Supplemental Comments” section at the end of this form. insert: </p>

insert: <p>

Complete the remaining columns with a cross (x) or a dash (-). For example, if you will use a subnet within three months, enter a cross in the “ Within 3 months” column and a dash in both the “ Within 1 year” and “ Within 2 years” columns. insert: </p>

insert: <h2>

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

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

Leave the “ inet6num:” and “ netname:” fields empty as we (the RIPE NCC) will complete them. insert: </p>

insert: <p>

Enter the legal name of the LIR's organisation in the “ descr:” field. insert: </p>

insert: <p>

Enter the ISO country code of the LIR's organisation in the “ country:” field. insert: </p>

insert: <p>

Enter the org-ID of the LIR's organisation object in the “ org:” 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: </p>

insert: <p>

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: </p>

insert: <p>

The nic-hdl of the role or person object entered in the “ admin-c:” field should be for someone who has administrative responsibilities for the network. insert: </p>

insert: <p>

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

insert: <p>

The “ status:” field must be ALLOCATED-BY-RIR. insert: </p>

insert: <p>

Maintainers protect objects in the RIPE 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: </p>

insert: <p>

The “ mnt-by:” field must be RIPE-NCC-HM-MNT. insert: </p>

insert: <p>

The “ mnt-lower:” field shows which maintainer authorises the creation of inet6num objects (assignments) within the allocated block. insert: </p>

insert: <p>

The “ mnt-routes:” field shows which maintainer authorises the creation of route6 objects for the allocated block. insert: </p>

insert: <p>

All of the objects that you enter in the template must already exist in the RIPE Database. insert: </p>

insert: <p>

We will send an e-mail to the e-mail address in the “ notify:” field every time the inet6num 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: <h2>

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

insert: <pre>
 insert: <br /> 
#[INSERT SUPPLEMENTAL COMMENTS]# insert: <br />
% insert: <br />
% Please add more information if you have specific insert: <br />
% addressing needs. insert: <br />
insert: <strong> We will make the IPv6 connectivity available first to our large insert: <br />
corporate customers and then our small business users (SOHOs). insert: <br />
The next phase will be to offer the connectivity to insert: <br />
our private users. insert: </strong>
insert: <br />
Our large corporate customers will receive a /48. The small business insert: <br />
users and private users will receive a /56. 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: <h2>

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

insert: <pre>
 insert: <br /> 
#[END of REQUEST]# insert: </pre>
Supporting Notes For The Initial IPv6 First Allocation Request Form
RIPE Documents Search