creating a second route object
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
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
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... 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@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@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
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... <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@ripe.net <mailto:db-wg@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@ripe.net <mailto: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 <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 <https://lists.ripe.net/mailman/listinfo/db-wg>
-- Aleksi Suhonen () ascii ribbon campaign /\ support plain text e-mail
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@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... < https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space...
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@ripe.net <mailto:db-wg@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@ripe.net <mailto: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 <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 <https://lists.ripe.net/mailman/listinfo/db-wg>
-- Aleksi Suhonen
() ascii ribbon campaign /\ support plain text e-mail
Hi all! The chart is already in the shared page " https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space... " If you scroll down a little bit, in "Authorisation rules for creating route objects" you can read "Here is a flowchart outlining the entire authorisation process <https://apps.db.ripe.net/docs/Appendices/Appendix-D--Route-Object-Creation-Flowchart/#route-object-creation-flowchart> ." That link points to " https://apps.db.ripe.net/docs/Appendices/Appendix-D--Route-Object-Creation-F... ". Regards! Miguel On Mon, 15 Apr 2024 at 15:24, denis walker via db-wg <db-wg@ripe.net> wrote:
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@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... < https://apps.db.ripe.net/docs/Authorisation/Protection-of-Route-Object-Space...
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@ripe.net
<mailto:db-wg@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@ripe.net <mailto: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 <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 <https://lists.ripe.net/mailman/listinfo/db-wg>
-- 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
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...
There used to be a flow chart showing this but I can't find it now.
This one? https://www.ripe.net/media/documents/Route-Object-Creation-Flowchart.pdf Rob
Hi Denis, Cynthia, The flowchart is linked from that page with the text: "Here is a flowchart outlining the entire authorisation process." to this page: https://apps.db.ripe.net/docs/Appendices/Appendix-D--Route-Object-Creation-F... Regards Ed Shryane RIPE NCC
On 15 Apr 2024, at 14:42, denis walker via db-wg <db-wg@ripe.net> 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...
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@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@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 --
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
participants (6)
-
Aleksi Suhonen -
Cynthia Revström -
denis walker -
Edward Shryane -
Miguel Mosquera -
Rob Evans