Invalid Assignments

LIRs can find an overview of all invalid assignments that have been created in the RIPE Database by using the IP Analyser application in the LIR Portal. LIRs should check for invalid assignments regularly to fix possible issues. This helps to ensure the accuracy of RIPE Database entries and RIPE Registry records. All invalid assignments must be cleared before an LIR can receive an additional allocation.

Invalid assignments fall into five categories:

Overlapping assignments

In this case, two or more inetnum objects have been registered sharing the same IP address range.
The inetnum objects can be assignments but also sub-allocations. For example:
  • inetnum: 192.0.2.0 - 192.0.2.255
  • inetnum: 192.0.2.0 - 192.0.2.128
This can be fixed by removing the overlapping objects that were incorrectly registered.

Sub-allocation warnings

An LIR can sub-allocate up to a /20 every 12 months to a single organisation. The minimum sub-allocation size is a /24. A sub-allocation is identified by the netname. You should use a unique netname for each organisation that an LIR sub-allocates to. If you use the same netname for different customers, a sub-allocation warning could be unintentionally triggered.

Objects with an incompatible "status" attribute

In this case, one or more objects have been created in the RIPE Database with a status that is incompatible with the parent object.
Allowed status inside Provider Aggregatable allocations:
  • LIR-PARTITIONED PA
  • SUB-ALLOCATED PA
  • ASSIGNED PA
Allowed status inside Provider Independent allocations:
  • LIR-PARTITIONED PI
  • ASSIGNED PI
Allowed status inside "UNSPECIFIED" allocations:
  • LIR-PARTITIONED PA
  • ASSIGNED PA
  • LIR-PARTITIONED PI
  • ASSIGNED PI

Incomplete RIPE Database objects

In this case, one or more inetnum objects do not contain an attribute that is mandatory.
Please ensure that the following attributes are included in the inetnum object:
  • "netname:"
  • "status:"
  • "changed:"

If the syntax of the date in the "changed:" attribute cannot be parsed, then the object will also be flagged as an invalid assignment. The correct syntax is: YYYYMMDD