You are here: Home > Participate > RIPE NCC Membership > LIR Basics for Members > Basic Steps for RIPE NCC Members

Basic Steps for RIPE NCC Members

As a RIPE NCC member and Local Internet Registry (LIR), there are a wide range of services and activities available to you. To get the most out of our services, there are some basic steps you should take to ensure you get full value from being a RIPE NCC member:
  1. Log in to the LIR Portal with your RIPE NCC Access account
  2. Manage LIR contacts in the LIR Portal
  3. Manage your ORGANISATION object in the LIR Portal
  4. The RIPE Database
  5. Request your IPv6 allocation
  6. Request your IPv4 allocation
  7. Request an AS number if you need one
  8. Set up reverse delegation for your allocation
  9. Create a route object for your allocation
  10. Certify your address space

1. Log in to the LIR Portal with your RIPE NCC Access account

The LIR Portal is a secure web area for RIPE NCC members to manage everything related to their membership and the Internet number resources they hold. Members also create and manage their resource certificates via the LIR Portal.

The LIR Portal is the LIR’s main communication interface with the RIPE NCC

You can log in to the LIR Portal with your RIPE NCC Access account that was created for you when submitting the New LIR application form.

2. Manage LIR contacts in the LIR Portal

LIR contacts with Administrator privileges can manage access to the LIR Portal for other LIR contacts and decide which level of access they are given (e.g.,Administrator, Operator and Billing User).

You can add and manage other LIR contacts in the menu “My LIR”. It is very important to keep the contact persons listed here up to date because they are the only persons we will accept requests from.

The RIPE NCC also uses the contact addresses in the LIR Portal to make important announcements to all members. You should avoid adding auto-responder ticketing systems as contact email addresses because this can result in ticketed emails being bounced to the RIPE NCC and to the rest of the RIPE NCC membership.

3. Manage your ORGANISATION object in the LIR Portal

All LIRs have an organisation object. The organisation object is an easy way of mapping resources to a particular organisation. This provides a way to find contact people responsible for the operations or usage of the resources represented in the RIPE Database for a certain company.

You can view your organisation object in the menu “Resources” - “Object Editor” – “Organisation Objects Editor”.

Here you will also be able to add and edit certain attributes of the organisation object.

In order to update the address, phone number and fax number in the organisation object, please go to “General Information” in the menu “My LIR”.

More information on the organisation object

4. The RIPE Database

When your Internet number resources request has been approved by the RIPE NCC, your IP allocation and/or AS number will be stored in the RIPE Database.

During the application process, the RIPE NCC created your organisation object, a role object, and your first person and maintainer objects. These objects will be referenced to your Internet number resource objects.

The RIPE NCC has created all necessary objects in order to be able to request Internet number resources. However, we would advise you to read the following information:

What is an “object”?

A record in the RIPE Database is known as an “object”. There are several types of object, and some of these need to be created before you can request and manage your resources.

What is a PERSON object?

A person object contains information about technical or administrative contact persons that are responsible for the object where it is referenced. Each object has a unique NIC handle ("nic-hdl:").

What is a NIC handle?

A NIC handle is the unique identifier of a person. 
It is basically the person's unique ID and it helps to keep different people with the same name apart from each other. 

Whenever a person object is referenced in another object, they are referenced by their NIC handle ("nic-hdl:") and not by their name.
See an example person object

What is a MNTNER (pronounced "maintainer"):

Objects in the RIPE Database can be protected using mntner objects. A mntner object specifies authentication information required to authorise the creation, deletion or modification of the objects protected by the mntner

More information about maintainers and hierarchical authorisation

We have an online tutorial to help you with creating person and mntner objects. It also shows you  how to protect objects with your mntner.

More information about creating and updating RIPE Database objects.

5. Request your IPv6 allocation

The minimum IPv6 allocation size is a /32. For allocations up to a /29, no additional documentation is necessary.

You can qualify for an initial allocation greater than a /29 by submitting documentation that reasonably justifies the request. If so, the allocation size will be based on the number of existing users and the extent of the organisation's infrastructure.

Once you have completed the basic steps to get set up as a RIPE NCC member, you just need to complete the “IPv6 Allocation Request form” in the LIR Portal.

This page outlines the information you will need to provide when completing a request form.

You can also request resources using the Resource Request API.

6. Request your IPv4 allocation

LIRs may receive a single /22 IPv4 allocation from the last /8. To request an IPv4 allocation, you just need to complete the "IPv4 Allocation Request form" in the LIR Portal.

This page outlines the information you will need to provide when completing a request form.

You can also request resources using the Resource Request API.

 

7. Request an AS Number if you need one

An Autonomous System (AS) is a group of IP networks run by one or more network operators with a single clearly defined routing policy. In general you only need an AS Number if you use multiple upstream providers.

Before you can request an AS Number, you should have completed all the basic steps after becoming a member, and then have the following:

  • The prefix (or pending ticket number) for which you request the AS Number. You have to request the AS Number for a specific IP range. You can also provide us with the ticket number of your pending request for IP addresses and we will provide the AS Number as soon as we provide the IP range
  • The AS Numbers and the contact details (an email address) from your peering partners. You need to have at least two peering partners.
  • The unique routing policy in RPSL format.

If you are requesting the AS Number on behalf of a third party, such as customers, we also need to receive an Independent Assignment Request and Maintenance Agreement and a copy of your customer’s company registration papers. You also have to provide an organisation object for your customer.

Once all this is in place, you just need to complete the AS Number Request Form in the LIR Portal.

This page outlines the information you will need to provide when completing a request form.

You can also request resources using the Resource Request API.

8. Set up reverse delegation for your allocation

With reverse DNS, the Domain Name System is used to translate IP addresses to hostnames.  Once you have received your allocation from us, you will want to set up reverse delegation.

Our reverse DNS pages will guide you through this process.

9. Create a ROUTE object for your allocation

Every route on the Internet that is originated by an AS is specified using a route object. If you have an AS Number, you can create a route object that will allow operators to configure their routers and perform network planning.

If you prefer, you can have an allocation/assignment and use the AS Number from your upstream provider.

For information on how to create this object, see the information available on our RIPE Database pages.

10. Certify your address space

Resource Certification (RPKI) is a free opt-in member service that allows you to obtain a resource certificate listing the Internet number resources you hold. The certificate is cryptographically verifiable proof that the Internet number resources have been registered to you by the RIPE NCC.

The practical application offered today is the ability to use resource certificates to help secure Internet routing by providing BGP origin validation.

Using the certificate, an LIR can state which Autonomous Systems are authorised to originate the IP prefixes that the LIR holds. Other network operators can base routing decisions on this information.

If you would like to certify your resources, see the information provided on our Resource Certification pages.