<div dir="ltr">Hi Aleksi<div><br></div><div>Here we discuss the semantics of how the database applies the logic for route object creation. If you want to discuss the logic, I suggest you move over to the routing-wg and talk with other routing experts :)</div><div><br></div><div>cheers</div><div>denis</div><div>co-chair DB-WG</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 15 Apr 2024 at 14:52, Aleksi Suhonen <<a href="mailto:ripe-ml-2024@ssd.axu.tm">ripe-ml-2024@ssd.axu.tm</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi and thanks for getting back so quickly,<br>
<br>
Route objects are supposed to be ships in the night. I guess we need to <br>
start a new PDP so that only the inetnum* mnt-* fields affect the <br>
creation of new route* objects. Changing and deleting existing route* <br>
objects should continue to use their own maintainer fields.<br>
<br>
Kind Regards,<br>
<br>
On 15/04/2024 15:42, denis walker wrote:<br>
> Hi guys<br>
> <br>
> It is not unintended behaviour or a bug. It is by design. See<br>
> <a href="https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space/#authorisation-rules-for-creating-route-objects" rel="noreferrer" target="_blank">https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space/#authorisation-rules-for-creating-route-objects</a> <<a href="https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space/#authorisation-rules-for-creating-route-objects" rel="noreferrer" target="_blank">https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space/#authorisation-rules-for-creating-route-objects</a>><br>
> <br>
> There used to be a flow chart showing this but I can't find it now.<br>
> <br>
> cheers<br>
> denis<br>
> co-chair DB-WG<br>
> <br>
> <br>
> On Mon, 15 Apr 2024 at 13:55, Cynthia Revström via db-wg <<a href="mailto:db-wg@ripe.net" target="_blank">db-wg@ripe.net</a> <br>
> <mailto:<a href="mailto:db-wg@ripe.net" target="_blank">db-wg@ripe.net</a>>> wrote:<br>
> <br>
> The same thing occurs if there's a less specific route(6) object.<br>
> <br>
> I would suspect that this is probably unintended behaviour?<br>
> <br>
> -Cynthia<br>
> <br>
> On Mon, 15 Apr 2024, 13:12 Aleksi Suhonen via db-wg, <<a href="mailto:db-wg@ripe.net" target="_blank">db-wg@ripe.net</a><br>
> <mailto:<a href="mailto:db-wg@ripe.net" target="_blank">db-wg@ripe.net</a>>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> When migrating a route from one ASN to another, the best<br>
> practice is to<br>
> create a second route(6) object for it with the new origin. The<br>
> creation<br>
> of the new object is dependent on the "mnt-routes:" field of the<br>
> enclosing inetnum(6) object.<br>
> <br>
> Am I correct thus far?<br>
> <br>
> Because I'm running into an issue. When trying to create a new<br>
> route<br>
> object using the LIR portal, I'm getting an error that the route<br>
> is not<br>
> authenticated by the maintainer of _the other_ route object.<br>
> <br>
> Am I missing something obvious, or have I found a bug/regression?<br>
> <br>
> BR,<br>
> <br>
> -- <br>
> Aleksi Suhonen<br>
> <br>
> () ascii ribbon campaign<br>
> /\ support plain text e-mail<br>
> <br>
> -- <br>
> <br>
> To unsubscribe from this mailing list, get a password reminder,<br>
> or change your subscription options, please visit:<br>
> <a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a><br>
> <<a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a>><br>
> <br>
> -- <br>
> <br>
> To unsubscribe from this mailing list, get a password reminder, or<br>
> change your subscription options, please visit:<br>
> <a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a><br>
> <<a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a>><br>
> <br>
<br>
-- <br>
Aleksi Suhonen<br>
<br>
() ascii ribbon campaign<br>
/\ support plain text e-mail<br>
<br>
</blockquote></div>