I have to agree with this, so if I have understood everything what we are currently looking at is something like: mntner: TEST1-MNT admin-c: TEST-RIPE auth: SSO-LIR no.foobar mnt-by: TEST1-MNT source: RIPE mntner: TEST2-MNT admin-c: TEST-RIPE auth: SSO-LIR no.foobar group1 mnt-by: TEST2-MNT source: RIPE mntner: TEST3-MNT admin-c: TEST-RIPE auth: SSO-LIR no.foobar group2 mnt-by: TEST3-MNT source: RIPE Person 1 -> Access to TEST1-MNT Person 2 | group1 -> Access to TEST1-MNT, and TEST2-MNT Person 3 | group1, group2 -> Access to TEST1-MNT, TEST2-MNT, and TEST3-MNT Is this what all of you are also thinking of? Kind regards, Cynthia Revström On 2019-01-07 13:35, denis walker wrote:
I suspect the RIPE NCC can't give an answer in 5 minutes as to how long it would take to implement such a feature. So I think it is better to decide what people really want and then ask the NCC to estimate the work required as part of the NWI process.
Given that you are all managing with the system as it is right now, if it takes a little bit longer to implement a slightly more complex feature that benefits all LIRs, that may be better than going for a simple feature that only benefits small LIRs.
But of course that depends if the bigger LIRs think this would be a useful feature for them to use as well.
cheers denis co-chair DB-WG
------------------------------------------------------------------------ *From:* Cynthia Revström <me@cynthia.re> *To:* Tore Anderson <tore@fud.no>; denis walker <ripedenis@yahoo.co.uk>; Nick Hilliard <nick@foobar.org>; Piotr Strzyzewski <piotr.strzyzewski@polsl.pl> *Cc:* "db-wg@ripe.net" <db-wg@ripe.net> *Sent:* Monday, 7 January 2019, 13:26 *Subject:* Re: [db-wg] Idea: magic mntner for all LIR contacts
On one hand I do not want a feature creep thing either but I also want something that will work for larger LIRs too while we are at it.
Could we get someone who knows about the website code to comment on the feasibility of this?
Kind regards, Cynthia Revström
On 2019-01-07 13:21, Tore Anderson wrote:
This would certainly solve my problem too (especially if there's an implicit «all» group available), but I am somewhat worried about feature creep here, as this would require changes / new features in the RIPE NCC Access / LIR Portal applications.
My original proposal would only require reading information already stored in those applications.
I'm not in a position to estimate the amount of additional work needed for this, just keep in mind the saying «perfect is the enemy of good».