<html><head></head><body><div class="ydp2884f83yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false"><div><div>Colleagues</div><div><br></div><div dir="ltr" data-setdir="false">I was about to post this to the DB-WG but it may be more appropriate to include it as part of this discussion...</div><div><br></div><div>Yet another 4 year old NWI that needs to be progressed or closed. The details are here:</div><div>https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005242.html</div><div><br></div><div>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.</div><div><br></div><div>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:</div><div>status: [mandatory] [multiple] [ ]</div><div><br></div><div>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.</div><div><br></div><div>The "descr:" attribute is already multiple so it can describe both the allocation and the assignment.</div><div><br></div><div>Is this still considered to be an issue?</div><div><br></div><div>cheers</div><div>denis</div><div><br></div><div>co-chair DB-WG</div></div><br></div><div><br></div>
</div><div id="ydp88fc6355yahoo_quoted_2039788714" class="ydp88fc6355yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, 5 October 2020, 16:13:53 CEST, Erik Bais <ebais@a2b-internet.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Dear WG, <br clear="none"><br clear="none">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. <br clear="none"><br clear="none">Please have a look at this discussion again and provide input if you can. <br clear="none"><br clear="none">Regards,<br clear="none">Erik Bais<br clear="none">Co-chair AP-WG. ( on behalf of the AP-WG Chair collective ) <br clear="none"><div class="ydp88fc6355yqt4880871724" id="ydp88fc6355yqtfd32914"><br clear="none">On 02/07/2020, 13:36, "address-policy-wg on behalf of Petrit Hasani" <<a shape="rect" href="mailto:address-policy-wg-bounces@ripe.net" rel="nofollow" target="_blank">address-policy-wg-bounces@ripe.net</a> on behalf of <a shape="rect" href="mailto:phasani@ripe.net" rel="nofollow" target="_blank">phasani@ripe.net</a>> wrote:<br clear="none"><br clear="none"> Dear colleagues,<br clear="none"> <br clear="none"> Thank you to everyone who responded to our earlier questions on the intent of the policy regarding IPv4 status hierarchies.<br clear="none"> <br clear="none"> While this was helpful, it would be great if we could have input from a wider group of people:<br clear="none"> <br clear="none"> - Should inetnums with these statuses be allowed to be created inside one another?<br clear="none"> - Should there be a limit on the minimum size of a sub-allocation?<br clear="none"> - Do we need a policy update?<br clear="none"> <br clear="none"> <a shape="rect" href="https://www.ripe.net/ripe/mail/archives/address-policy-wg/2020-June/013195.html" rel="nofollow" target="_blank">https://www.ripe.net/ripe/mail/archives/address-policy-wg/2020-June/013195.html</a><br clear="none"> <br clear="none"> We look forward to hearing from you.<br clear="none"> <br clear="none"> Cheers,<br clear="none"> --<br clear="none"> Petrit Hasani<br clear="none"> Policy Officer<br clear="none"> RIPE NCC<br clear="none"> <br clear="none"> <br clear="none"> <br clear="none"> <br clear="none"> <br clear="none"> > On 16 Jun 2020, at 15:36, Petrit Hasani <<a shape="rect" href="mailto:phasani@ripe.net" rel="nofollow" target="_blank">phasani@ripe.net</a>> wrote:<br clear="none"> > <br clear="none"> > Dear colleagues,<br clear="none"> > <br clear="none"> > We are reviewing IPv4 status hierarchies in the RIPE Database (looking at objects with the same status as their less-specifics).<br clear="none"> > <br clear="none"> > 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.<br clear="none"> > <br clear="none"> > 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.<br clear="none"> > <br clear="none"> > 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.<br clear="none"> > <br clear="none"> > 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.<br clear="none"> > <br clear="none"> > Section 5.3 "Sub-allocations" of the IPv4 Address Allocation and Assignment Policies (ripe-733) states:<br clear="none"> > <br clear="none"> > "Sub-allocations are intended to aid the goal of routing aggregation and can only be made from allocations with a status of "ALLOCATED PA".<br clear="none"> > <br clear="none"> > [...]<br clear="none"> > <br clear="none"> > LIRs may make sub-allocations to multiple downstream network operators."<br clear="none"> > <br clear="none"> > <a shape="rect" href="https://www.ripe.net/publications/docs/ripe-733#54" rel="nofollow" target="_blank">https://www.ripe.net/publications/docs/ripe-733#54</a><br clear="none"> > <br clear="none"> > 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:<br clear="none"> > <br clear="none"> > - Should inetnums with these statuses be allowed to be created inside one another?<br clear="none"> > - Should there be a limit on the minimum size of a sub-allocation?<br clear="none"> > - Do we need a policy update?<br clear="none"> > <br clear="none"> > We look forward to your guidance.<br clear="none"> > <br clear="none"> > Kind regards,<br clear="none"> > --<br clear="none"> > Petrit Hasani<br clear="none"> > Policy Officer<br clear="none"> > RIPE NCC<br clear="none"> > <br clear="none"> > <br clear="none"> > <br clear="none"> > <br clear="none"> > <br clear="none"> <br clear="none"> <br clear="none"><br clear="none"></div></div></div>
</div>
</div></body></html>