Colleagues

We would like some feedback on the following NWIs and their current status.

I would also like to remind colleagues that we have posted a couple of questions on the Address Policy WG mailing list about policy requirements for contact details. We would appreciate some feedback on those questions on that mailing list.

cheers

denis

co-chair DB-WG

NWI-7 abuse-c implementation

If the RIPE NCC can confirm that the cleanup of PERSON, ORGANISATION, MNTNER and IRT objects has been done to remove any "abuse-mailbox:" attributes and the 'person' keyword has been updated to take account of the "abuse-c:", we would like to mark NWI-7 as 'Finished'.

NWI-8 LIR´s SSO Authentication Groups

We agreed on this problem definition:

Problem Definition

LIRs would like a mechanism to easily add/remove users to centralised SSO authentication groups for maintaining objects in the RIPE Database.

Do we agree on this (staged) solution definition?

(Draft) Solution Definition

Stage 1

-Non billing Users listed in an LIR´s portal account, who have an SSO authentication account, will be contained in a default authentication group

-Non billing users added or removed through the portal UI, who have an SSO authentication account, will be automatically adjusted in this group

-This authentication group can be referenced in MNTNER objects by a new authentication method

-These authentication groups for LIRs will be stored in a way that updates to the RIPE Database is not dependent on the availability of the portal service

-(Non billing users who did not have an SSO authentication account who then create one, will be automatically adjusted in this group - NCC, is this feasable?)

-(Non billing users who are listed in the LIR's authentication group who then delete their SSO authentication account, will be automatically adjusted in this group - NCC, is this feasable?)

Stage 2

-Non billing Users listed in an LIR´s portal account, who have an SSO authentication account, can be added to and removed from user defined SSO authentication groups

-Each User can be a member of any number of named groups

-The authentication groups can be configured using the portal UI

-These groups can be referenced in MNTNER objects by the new authentication method

NWI-9  In-band notification mechanism? ???

Is there a wish to create this issue as an NWI with the following problem definition?

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.