Colleagues The issue came up again today at the AP-WG session at RIPE-83 about making assignments from a /24 allocation. People are forced to create two 'artificial' /25 assignments. Again this is used as one argument against having to register assignments in the RIPE Database. Regardless of the bigger picture about registering assignments, there is a simple solution to the /24 allocation issue. Make the "status:" attribute multiple. Then this /24 INETNUM object can have: status: ALLOCATED PA status: ASSIGNED PA Business rules can restrict the use of multiple status to very specific use cases. Maybe only allow a second status of 'ASSIGNED PA' in an object with status 'ALLOCATED PA'. The normal rules then apply to an assignment, so there can be no more specifics. Then any allocation of any size can be assigned in its entirety without having to create more specific pseudo assignment objects. Business rules could also allow this option for 'SUB-ALLOCATED PA'. cheers denis co-chair DB-WG