About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
DBConstat
     
RIPE NCC Projects:
RIPE NCC Navigation Ends
Test Traffic
DISI
RIS
RRCC
ERX
DBConstat
K.root Servers.net
RIPE NCC Navigation Ends
Next Section

Assignments from Assignments

Hierarchical organisation of inetnum objects in the RIPE Whois Database is shown below:

Hierarchy of inetnum objects in RIPE Whois Database

Note that the leaf nodes in the tree are the assigned blocks of customers.
In this scheme, additional hierarchies are undesired since leaf nodes should not have leaf nodes.

Example:

    inetnum: 10.0.0.0 - 10.255.255.255
    status: ALLOCATED UNSPECIFIED
    
    inetnum: 10.1.0.0 - 10.1.255.255
    status: ASSIGNED PI
    
    inetnum: 10.1.0.1 - 10.1.0.255
    status: ASSIGNED PI

Here, the inetnum 10.1.0.1 - 10.1.0.255 is an assignment from an assignment, thus inconsistent.

If you want more information about sub-allocations, please read our sub-allocation FAQ.


Yearly

 

Next Section
     About RIPE NCC | Service Announcements | Site Map | LIR Portal | About RIPE | Contact | © RIPE NCC. All rights reserved.
RIPE NCC Homepage Go to the RIPE NCC LIRPortal Go to the RIPE Community pages