<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><span><div>Colleagues</div><div><br></div><div>We would like some feedback on the following NWIs and their current status.</div><div><br></div><div>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.</div><div><br></div><div>cheers</div><div>denis</div><div>co-chair DB-WG</div><div><br></div><div><br></div><div>NWI-7 abuse-c implementation</div><div><br></div><div>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'.</div><div><br></div><div><br></div><div>NWI-8 LIR´s SSO Authentication Groups</div><div><br></div><div>We agreed on this problem definition:</div><div><br></div><div>Problem Definition</div><div>LIRs would like a mechanism to easily add/remove users to centralised SSO authentication groups for maintaining objects in the RIPE Database.</div><div><br></div><div>Do we agree on this (staged) solution definition?</div><div>(Draft) Solution Definition</div><div><br></div><div>Stage 1</div><div><br></div><div>-Non billing Users listed in an LIR´s portal account, who have an SSO authentication account, will be contained in a default authentication group</div><div><br></div><div>-Non billing users added or removed through the portal UI, who have an SSO authentication account, will be automatically adjusted in this group</div><div><br></div><div>-This authentication group can be referenced in MNTNER objects by a new authentication method</div><div><br></div><div>-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</div><div><br></div><div>-(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?)</div><div><br></div><div>-(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?)</div><div><br></div><div>Stage 2</div><div><br></div><div>-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</div><div><br></div><div>-Each User can be a member of any number of named groups</div><div><br></div><div>-The authentication groups can be configured using the portal UI</div><div><br></div><div>-These groups can be referenced in MNTNER objects by the new authentication method</div><div><br></div><div><br></div><div>NWI-9 In-band notification mechanism? ???</div><div>Is there a wish to create this issue as an NWI with the following problem definition?</div><div><br></div><div>Problem Definition</div><div>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.</div></span><br></div></div></body></html>