Supporting Notes For The IPv6 First Allocation Request Formripe-422: This document contains instructions for LIRs on how to complete the “IPv6 First Allocation Request Form”.https://www.ripe.net/publications/docs/ripe-422https://www.ripe.net/logo.png

Supporting Notes For The IPv6 First Allocation Request Form

Publication date: 14 Nov 2007

This document is obsoleted

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 here.

To request resources from the RIPE NCC, members should now use the request forms in the LIR Portal.

The Resource Request API and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms.

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

Overview of Organisation Template

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

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

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.

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’.

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.

If an End Site needs more than a /48, a separate request form must be submitted.

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.

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.

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

Enter the legal name of the LIR’s organisation in the “ descr:” field.

Enter the ISO country code of the LIR’s organisation in the “ country:” field.

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 (https://lirportal.ripe.net).

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.

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.

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.

The “ status:” field must be ALLOCATED-BY-RIR.

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' (https://lirportal.ripe.net).

The “ mnt-by:” field must be RIPE-NCC-HM-MNT.

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

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

All of the objects that you enter in the template must already exist in the RIPE Database.

We will send an e-mail to the e-mail address in the “ notify:” field every time the inet6num allocation object is updated.

The “ changed:” field must be hostmaster _at_ ripe _dot_ net.

The “ source:” field must be RIPE.

Insert Supplemental Comments

#[INSERT SUPPLEMENTAL COMMENTS]# % % Please add more information if you have specific % addressing needs. We will make the IPv6 connectivity available first to our large corporate customers and then our small business users (SOHOs). The next phase will be to offer the connectivity to our private users. Our large corporate customers will receive a /48. The small business users and private users will receive a /56.

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

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacy policy. You can accept our cookies either by clicking here or by continuing to use the site.