Wessel Sandkuijl wrote on 20/08/2024 12:51:
I think this is something that can be improved. I suggest
implementing the option to force-delete a route(6) object as ASN
resource holder. This saves both the resource holder and RIPE NCC
valuable time.
there's definitely an issue here, but I wonder if the authorisation
model is opened up a bit, whether that would open up a can of worms
(e.g. if you can auth a delete, why shouldn't you be able auth a create?).
Would someone from the RIPE NCC be able to provide some suggestions
about how this situation could be addressed?
Nick
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
