The same thing occurs if there's a less specific route(6) object. I would suspect that this is probably unintended behaviour?
-Cynthia On Mon, 15 Apr 2024, 13:12 Aleksi Suhonen via db-wg, <db-wg@ripe.net> wrote: > Hi, > > When migrating a route from one ASN to another, the best practice is to > create a second route(6) object for it with the new origin. The creation > of the new object is dependent on the "mnt-routes:" field of the > enclosing inetnum(6) object. > > Am I correct thus far? > > Because I'm running into an issue. When trying to create a new route > object using the LIR portal, I'm getting an error that the route is not > authenticated by the maintainer of _the other_ route object. > > Am I missing something obvious, or have I found a bug/regression? > > BR, > > -- > Aleksi Suhonen > > () ascii ribbon campaign > /\ support plain text e-mail > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/db-wg >
-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
