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/members-discuss@ripe.net/
[members-discuss] Request for view only access in the LIR Portal
- Previous message (by thread): [members-discuss] Request for view only access in the LIR Portal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Theodoros Polychniatis
tpolychnia at ripe.net
Wed Dec 8 16:54:12 CET 2021
Hi Terrence, Thank you for your input. We've added it to the community input section in the RPKI roadmap: https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/rpki-planning-and-roadmap Nathalie Trenaman and the RPKI team will look at all the suggestions and get back to the community. Best regards, Theo -- Theodoros Polychniatis Asst. Manager Software Engineering RIPE NCC On 04/12/2021 16:01, Terrence de Kat wrote: > Dear Theo, > > Not exactly the same, but close: For sub-allocated blocks it would be handy to be able to give a 3rd party access to change RPKI for that sub-allocation only. In the LIR portal, or even more useful would be the ability to create an RPKI API key with such constraints instead of the current all-or-nothing approach. > > Currently, access to change data in the RIPE database (eg add/modify/delete route object) can be easily delegated by adding the 3rd party's maintainer object, but access to make the corresponding RPKI changes cannot. >
- Previous message (by thread): [members-discuss] Request for view only access in the LIR Portal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]