Hi Denis,
+1 as per my previous reasoning.
Thanks,
Liam Glover
> On 15 Apr 2019, at 11:32, ripedenis--- via db-wg wrote:
>
> Colleagues
>
> Problem Definition
>
> There is a need within the routing community to have changes to all/nominated
> routing data objects in the RIPE Database pus
Hi Denis,
> Problem Definition
>
> There is a need within the routing community to have changes to all/nominated
> routing data objects in the RIPE Database pushed out to them, regardless of
> membership status.
>
> Last week Aris was the only person to confirm that he wants this feature. If
Hi,
On Mon, Apr 15, 2019 at 03:33:01PM +0100, Sascha Luck [ml] via db-wg wrote:
> As long as that stream is restricted to routing-relevant objects
> (route/6, as-set, aut-num come to mind) I can see the need for
> this for automated filter-building and have at least no
> objections.
+1
Gert Doer
On Mon, Apr 15, 2019 at 10:32:51AM +, ripedenis--- via db-wg wrote:
Colleagues
Problem Definition
There is a need within the routing community to have changes to all/nominated
routing data objects in the RIPE Database pushed out to them, regardless of
membership status.
Last week Aris was t
On 15/04/2019 13:31, ripedenis--- via db-wg wrote:
I have recently encountered issues in this area as well. I would like
to see the standard "non-billing" users to not only be allowed for the
main resources but also for all sub-groups that appear under the LIR.
Currently, a user added as a r
+1
- Cynthia
On 2019-04-15 12:32, ripedenis--- via db-wg wrote:
Colleagues
Problem Definition
There is a need within the routing community to have changes to
all/nominated routing data objects in the RIPE Database pushed out to
them, regardless of membership status.
Last week Aris was the
Colleagues
Problem Definition
There is a need within the routing community to have changes to all/nominated
routing data objects in the RIPE Database pushed out to them, regardless of
membership status.
Last week Aris was the only person to confirm that he wants this feature. If we
are to move f
Colleagues
I think we have now agreed on these problem and solution definitions:
Problem Definition
LIRs would like a mechanism to easily add/remove users to centralised SSO
authentication groups for maintaining objects in the RIPE Database.
Solution Definition
Stage 1
-Non billing Users listed i
