Hi Ed,

I still support this solution just as I was back in March 2022 and I
would like to see it implemented.

-Cynthia

On Thu, May 11, 2023 at 2:38 PM Edward Shryane via db-wg <[email protected]> wrote:
>
> Dear Colleagues,
>
> Following is an update for NWI-14, to protect references to objects in the 
> RIPE database.
>
> Problem Definition
> ------------------
>
> Ref. https://www.ripe.net/ripe/mail/archives/db-wg/2022-March/007320.html
>
> Solution Definition
> -------------------
>
> To protect references to person, role, mntner, irt objects, I propose adding 
> an optional, multiple, "mnt-ref:" attribute to those object types.
>
> This attribute will work the same for these object types as on the existing 
> organisation type.
>
> Impact Analysis
> ---------------
>
> Low impact on Whois. The "mnt-ref:" attribute already exists on the 
> organisation object as a mandatory attribute. Usage of this attribute will be 
> the same for the new object types.
>
> The main impact to adding this attribute is that Whois updates referencing 
> one of these objects may require authorisation from *multiple* maintainers 
> (i.e. the object maintainer and the reference maintainer, if they are 
> different). This is the same as for the organisation object, however most 
> references to an organisation use the same maintainer. If multiple 
> maintainers are necessary, each can be added as a separate "mnt-ref:" 
> attribute on the referenced object.
>
> This attribute is optional. If any adverse impact is observed, the attribute 
> can be removed again from the referenced object.
>
> Please reply with any feedback. If there are no objections, the DB team will 
> implement this change in the next Whois release.
>
> Regards
> Ed Shryane
> RIPE NCC
>
>
>
> > On 9 May 2022, at 15:00, denis walker <[email protected]> wrote:
> >
> > Colleagues
> >
> > The chairs propose creating NWI-14 for expanding the optional use of
> > the "mnt-ref:" attribute to protect objects from accidental or
> > intentional mis-representation of responsibility.
> >
> > See slide 14 of this presentation for the problem definition:
> > https://ripe78.ripe.net/presentations/129-RIPE78-Operational-Update.pdf
> >
> > We ask the RIPE NCC to add NWI-14 to the list.
> >
> > cheers
> > denis
> > co-chair DB-WG
>
>
> --
>
> To unsubscribe from this mailing list, get a password reminder, or change 
> your subscription options, please visit: 
> https://lists.ripe.net/mailman/listinfo/db-wg

-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/db-wg

Reply via email to