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] Whois Inverse Query by "sponsoring-org:" Attribute
- Next message (by thread): [db-wg] creating a second route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aleksi Suhonen
ripe-ml-2024 at ssd.axu.tm
Mon Apr 15 13:12:12 CEST 2024
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
- Previous message (by thread): [db-wg] Whois Inverse Query by "sponsoring-org:" Attribute
- Next message (by thread): [db-wg] creating a second route object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]