This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] creating a second route object
- Previous message (by thread): [db-wg] creating a second route object
- Next message (by thread): [db-wg] creating a second route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Mon Apr 15 15:23:48 CEST 2024
Hi Aleksi 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 :) cheers denis co-chair DB-WG On Mon, 15 Apr 2024 at 14:52, Aleksi Suhonen <ripe-ml-2024 at ssd.axu.tm> wrote: > Hi and thanks for getting back so quickly, > > Route objects are supposed to be ships in the night. I guess we need to > start a new PDP so that only the inetnum* mnt-* fields affect the > creation of new route* objects. Changing and deleting existing route* > objects should continue to use their own maintainer fields. > > Kind Regards, > > On 15/04/2024 15:42, denis walker wrote: > > Hi guys > > > > It is not unintended behaviour or a bug. It is by design. See > > > https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space/#authorisation-rules-for-creating-route-objects > < > https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space/#authorisation-rules-for-creating-route-objects > > > > > > There used to be a flow chart showing this but I can't find it now. > > > > cheers > > denis > > co-chair DB-WG > > > > > > On Mon, 15 Apr 2024 at 13:55, Cynthia Revström via db-wg <db-wg at ripe.net > > <mailto:db-wg at ripe.net>> wrote: > > > > 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 at ripe.net > > <mailto:db-wg at 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://mailman.ripe.net/ > > <https://mailman.ripe.net/> > > > > -- > > > > To unsubscribe from this mailing list, get a password reminder, or > > change your subscription options, please visit: > > https://mailman.ripe.net/ > > <https://mailman.ripe.net/> > > > > -- > Aleksi Suhonen > > () ascii ribbon campaign > /\ support plain text e-mail > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20240415/613ef39e/attachment.html>
- Previous message (by thread): [db-wg] creating a second route object
- Next message (by thread): [db-wg] creating a second route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]