Resource Consistency

Resource Registration

Role Object

What we can do for you:

We can help you to create a role object and associate it with your Internet Resources 

Internet Resources registered in the RIPE Database are expected to include contact details for the network. These contact details are held in a RIPE Database object known as a "person" object. 

A role object is similar to a person object. However, while a person object represents an individual, a role object represents an organisation (or a department within an organisation). Using a role object significantly reduces the amount of work involved in updating contact details. If an existing contact leaves your organisation or a new contact joins, you will only need to update one (role) object instead of replacing the person object associated with tens, hundreds (or even thousands) of Internet Resources. 

A role object can be used as the administrative (admin-c) or technical (tech-c) contact for resources registered in the RIPE Database. It is also the only object type that can be used for the abuse (abuse-c) contact.   

Assignment Window (AW)

What we can do for you:

We can help you to qualify for an AW  

An Assignment Window (AW) is the maximum amount of IP addresses that you, as an LIR, can assign to End Users or to your own infrastructure from your allocations without prior approval from the RIPE NCC.

The AW for new LIRs is 0 (zero). This means that every assignment made by the LIR requires prior approval by the RIPE NCC.

An AW enables an experienced LIR to evaluate address requests without having to interact with a RIPE NCC IP Resource Analyst (IPRA).

Check out the Assignment Window FAQ.

IPv4 Assignment Registration

What can we do for you:

We can help you to validate any invalid assignments in the RIPE Database 

LIRs can find an overview of all assignments that have been created in the RIPE Database by using the IP Analyser application in the LIR Portal. The LIR Portal also provides notifications if any of the registered assignments are considered to be invalid.

Invalid assignments fall into five categories:

  1. Overlapping assignments
  2. Assignments registered without approval
  3. Sub-allocation warnings
  4. Objects with an incompatible "status" attribute
  5. Incomplete RIPE Database objects

LIRs can check the IP Analyser for invalid assignments and the RIPE NCC can provide support with updating the records. This helps to ensure the accuracy of RIPE Database entries and RIPE Registry records. 

More information about invalid assignments and how to resolve them.

IPv4 Assignment Approvals

What can we do for you:

We can help you to register any assignment approvals that have not yet been (fully) registered in the RIPE Database

When an LIR wants to make an assignment that is larger than their Assignment Window, they need to request approval from the RIPE NCC. A record of this approval is logged using the size of the assignment, the netname and the date of the approval.  

If the LIR no longer needs this assignment approval (for example if the customer cancels the request or if the project has ended) they are expected to delete the assignment from the RIPE Database and inform the RIPE NCC.  

IPv6 End Site Assignments

What we can do for you:

If you have IPv6 End User assignments larger than /48 or smaller than /64, we can help you to validate them 

All IPv6 assignments should be registered in the RIPE Database. 

Read more information about documenting IPv6 assignments.

The size of the assignment is a local decision for the LIR to make, however the minimum size is /64.

An LIR can register assignments up to size /48 without any prior approval from the RIPE NCC. When a single End Site requires an assignment larger than a /48, the LIR must submit a request for approval including documentation or materials that justify the request.

Independent Resources

What we can do for you:

We can help you through the process of updating the documentation for any Independent Resources associated with your registry

Independent Resources are distributed directly from the RIPE NCC to the End User. The resources remain with the End User as long as the original criteria on which the assignment was based are still valid and the assignment is properly registered in the RIPE Database. If the End User no longer needs the resources, they are returned directly to the RIPE NCC. 

Independent Resources fall into 3 categories:

  1. IPv4 Provider Independent (PI) assignments
  2. IPv6 Provider Independent  (PI) assignments
  3. Autonomous System (AS) Numbers

An LIR may hold Independent Resources themselves – they may also perform the role of “sponsoring LIR” for an End User who holds Independent Resources. 

Independent Resources have some specific registration requirements:

  • The legal name of the End User must match in:
    • Company registration papers
    • Organisation object
    • First descr line in the inetnum/autnum object
  • Sub-assignments of Provider Independent (PI) address space are not permitted

If these requirements are not currently being met, the RIPE NCC will help to bring the assignments in line with current policy.