[address-policy-wg] NWI-4 - role of status: field in multivalued status context -- Last call

 Colleagues
We have not had enough comment on this to make a decision if any change is needed. So can we have a last round of comment to decide if this is a sufficiently important issue to make a change or if we just close this action item?
In brief: when assigning a whole allocation should we be able to give the INET(6)NUM object 2 status values to reflect it being both an allocation and an assignment, rather than splitting it into two smaller assignment objects?
cheersdenis
co-chair DB-WG
    On Monday, 5 October 2020, 16:48:34 CEST, ripedenis--- via address-policy-wg <address-policy-wg at ripe.net> wrote:  
 
  Colleagues
I was about to post this to the DB-WG but it may be more appropriate to include it as part of this discussion...
Yet another 4 year old NWI that needs to be progressed or closed. The details are here:https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005242.html
In summary it concerns the assignment of a whole allocation. Because the range is the primary key (pkey) in the database you cannot have an allocation object and an assignment object with the same pkey. A common work around is to split the allocation and make two assignments. The suggestion is to allow "status:" to be a multiple attribute.
This could be done quite easily and constrained in it's use by business rules in the database software. So the syntax could be changed in INET(6)NUM objects to:status:         [mandatory]  [multiple]     [ ]
The business rules could make this multiple option only allowed in very limited situations. For example if an INETNUM object has 'status: ALLOCATED PA' it could be possible to add a second value 'status: ASSIGNED PA' or 'status: SUB-ALLLOCATED PA'. If the status in an INET6NUM object is 'status: ALLOCATED-BY-RIR' it could be possible to add a second value 'status: ALLOCATED-BY-LIR' or 'status: ASSIGNED'. The business rules could prevent any other multiple status values.
The "descr:" attribute is already multiple so it can describe both the allocation and the assignment.
Is this still considered to be an issue?
cheersdenis
co-chair DB-WG

    On Monday, 5 October 2020, 16:13:53 CEST, Erik Bais <ebais at a2b-internet.com> wrote:  
 
 Dear WG,  

I want to bring the following email and questions of our PDO - Petrit Hasani to your attention that might have slipped over the vacation period.  

Please have a look at this discussion again and provide input if you can.  

Regards,
Erik Bais
Co-chair AP-WG. ( on behalf of the AP-WG Chair collective ) 

On 02/07/2020, 13:36, "address-policy-wg on behalf of Petrit Hasani" <address-policy-wg-bounces at ripe.net on behalf of phasani at ripe.net> wrote:

    Dear colleagues,
    
    Thank you to everyone who responded to our earlier questions on the intent of the policy regarding IPv4 status hierarchies.
    
    While this was helpful, it would be great if we could have input from a wider group of people:
    
    - Should inetnums with these statuses be allowed to be created inside one another?
    - Should there be a limit on the minimum size of a sub-allocation?
    - Do we need a policy update?
    
    https://www.ripe.net/ripe/mail/archives/address-policy-wg/2020-June/013195.html
    
    We look forward to hearing from you.
    
    Cheers,
    --
    Petrit Hasani
    Policy Officer
    RIPE NCC
    
    
    
    
    
    > On 16 Jun 2020, at 15:36, Petrit Hasani <phasani at ripe.net> wrote:
    > 
    > Dear colleagues,
    > 
    > We are reviewing IPv4 status hierarchies in the RIPE Database (looking at objects with the same status as their less-specifics).
    > 
    > Some cases are clear - "ASSIGNED PA" shouldn't be allowed under "ASSIGNED PA", for example. Other statuses might need a closer look and we would like guidance from this working group.
    > 
    > The RIPE Database does not currently have any limitations on creating inetnums that have the status "SUB-ALLOCATED PA" or "LIR-PARTITIONED PA" under inetnums with the same status. This often results in chains of inetnums that have the same status, sometimes ending with the sub-allocation of a single IP address.
    > 
    > Although this might not seem useful at first glance, there might be practical uses for a few levels of sub-allocation. For example, a global company could give sub-allocations to its national branches, which make smaller sub-allocations to their multiple daughter companies. These daughter companies could then create and maintain assignments for their actual networks.
    > 
    > However, this is not allowed under a strict reading of the policy, as only the LIR itself can make sub-allocations, and these must be used for assignments.
    > 
    > Section 5.3 "Sub-allocations" of the IPv4 Address Allocation and Assignment Policies (ripe-733) states:
    > 
    > "Sub-allocations are intended to aid the goal of routing aggregation and can only be made from allocations with a status of "ALLOCATED PA".
    > 
    > [...]
    > 
    > LIRs may make sub-allocations to multiple downstream network operators."
    > 
    > https://www.ripe.net/publications/docs/ripe-733#54
    > 
    > Before making any changes, we want to be sure that we understand the intent of the policy and what the community wants us to do. Thus, we would like to hear from the Address Policy Working Group:
    > 
    > - Should inetnums with these statuses be allowed to be created inside one another?
    > - Should there be a limit on the minimum size of a sub-allocation?
    > - Do we need a policy update?
    > 
    > We look forward to your guidance.
    > 
    > Kind regards,
    > --
    > Petrit Hasani
    > Policy Officer
    > RIPE NCC
    > 
    > 
    > 
    > 
    > 
    
    

    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20201116/1dc71c62/attachment.html>