Skip to main content
  • Legend
  • Added
  • Deleted

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

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

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

This document contains instructions for LIRs on how to complete the "IPv4 First Allocation Request Form Link: Link: ". The instructions are based on the "IPv4 Address Allocation and Assignment Policy for the RIPE region

  • Insert Supplemental Comments Link: #insert-supplemental-comments Link: #comments
  • End of Request Link: #end-of-request Link: #end

  • General Information

    % Please add your RegID.
    request-type: ipv4-first-alloc
    form-version: 1.2 1.1
    x-ncc-regid: nl.bluelight

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

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

    Requester Template

    % Please add your contact details.
    name: John Smith
    phone: +123 45 678910
    email: [email protected]

    fax-no: +123 45 678911
    email: [email protected]
    nic-hdl: HOHO1-RIPE

    Enter your contact details in the requester template. You must be a registered contact for the LIR. The 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.

    Address Space Usage

    % Will you make assignment(s) from the requested allocation? (Yes/No)
    usage-confirmation: Yes

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

    "phone:" and "fax-no:" fields.

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

    Current Address Space

    % Are you currently using any address space? (Yes/No)
    current-address: Yes

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

    Current Address Space Prefix Template

    % If yes, which address prefix are you using?
    actual-prefix: 2001:DB8:5::/48

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

    Database Template(s)

    % Please complete all of the fields below.
    descr:          Bluelight B.V.
    country:       NL
    org:             ORG-Bb2-RIPE
    admin-c:       HOHO1-RIPE
    tech-c:        HOHO1-RIPE
    status:        ALLOCATED PA
    mnt-by:        RIPE-NCC-HM-MNT
    mnt-lower:     BLUELIGHT-MNT
    mnt-routes:    BLUELIGHT-MNT
    notify:        [email protected]
    changed:       [email protected]
    source:        RIPE

    Leave the "inetnum:", "netname:", "org:" and "descr:" "inetnum:" 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 country where the resource will be announced in the "country:" field. 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 ( Link: ).

    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 ( Link: ).

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

    The nic-hdl of the role or person object in the "tech-c:" 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.

    To create the first person and maintainer objects of an organisation, you can use Link:

    You can create

    additional person, role and maintainer objects using webupdates Link: /manage-ips-and-asns/db/webupdates/ .

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

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

    The "status:" maintainers using the Maintainer Editor ( Link: ).The "mnt-by:"

    field must be

    ALLOCATED PA.The "mnt-by:" field must be RIPE-NCC-HM-MNT.

    RIPE-NCC-HM-MNT. You will be able to update your allocation object using the

    Object Editors Link: .The "mnt-lower:" Allocation Editor ( Link: ).The "mnt-lower:"

    field shows which maintainer authorises the creation of inetnum objects (i.e. assignments) within the allocation block.

    The "mnt-routes:" "mnt-routes:" 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:" "notify:" field every time the allocation object is updated.

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

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

    Insert Supplemental Comments

    % You can Please add more information if necessary
    you have specific

    % addressing needs.
    We will send one infrastructure request (/24) 
    and three customer requests (/27 each) later today.
    This is for all of our immediate addressing needs.

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

    End of Request

    #[END of REQUEST]#

    When you have sent this request form to us, please send separate "Provider Aggregatable (PA) Assignment Request Forms Link: " 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]>.

    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.