Dear colleagues,

> On 18 Sep 2025, at 14:41, denis walker <[email protected]> wrote:
> 
> Colleagues
> 
> I guess no one has an opinion on any of this. You are happy to continue with 
> an NWI to create an unenforceable mandatory email address. You don't see any 
> problems adding a new mandatory attribute across, potentially, millions of 
> objects. And you are all OK to continue adding and maintaining an existing 
> mandatory email in millions of objects, even though none of you have any idea 
> what that attribute means. I don't think anyone has time to consider RIPE 
> Database issues any more. As long as it still, just about, works then leave 
> it alone. Well good luck with this project. You will need it if you go ahead 
> with it.
> 
> cheers
> denis
> 

The DB team are working on a Solution Definition for NWI-20 and I'd like some 
feedback on the points that Denis has rasied before we proceed further.

Firstly, do we need to use the Policy Development Process to make e-mail 
mandatory on person objects? E-mail is already mandatory on organisation and 
role but not on person. I couldn't find a reason for this inconsistency in 
existing policies, or any requirement to make it so.

Secondly, do we need to cleanup existing person objects if e-mail is changed to 
be mandatory? Half of the existing 2 million person objects do not have an 
e-mail attribute. It seems unlikely that maintainers will add e-mail 
retrospectively. We could add validation to require e-mail only when person 
objects are updated, however most person objects are created and never updated 
again. We could add validation to require e-mail when a person is added as a 
contact on another object, however most exising persons are referenced from a 
single assignment and then never referenced again.

Thirdly, should mandatory e-mail remain part of NWI-20, in addition to creating 
new contact types? Multiple people in this thread have asked for it, but 
perhaps the changes can be made in phases, and the wider issues that Denis has 
raised can be tackled separately.

Regards
Ed Shryane
RIPE NCC



-----
To unsubscribe from this mailing list or change your subscription options, 
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the 
email matching your subscription before you can change your settings. 
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/

Reply via email to