Hi Everyone, I would go ahead and say that this can be declared NWI-20. I think enough time has passed to give all working group participants the opportunity to voice their opinion on this. Leo's original Email defines a problem and already touches on a solution definition, which would be phase two of the NWI process. As the working group participants have already started talking about potential implementation details, I will declare consensus on the problem definition Leo has posted. With this we can move to phase two of the NWI process, where I would like to ask the RIPE NCC for further input on potential solutions, as, for example, certain contact types being a legal requirement within the RIPE service region has not been evaluated yet. Thank you for all your input on this proposal. Have a nice week, everybody. On 6/3/25 4:15 AM, Leo Vegoda wrote:
Hi Denis,
On Mon, 2 Jun 2025 at 18:16, denis walker <ripedenis@gmail.com> wrote:
Hi Guys
I agree that this would be more suited as a policy clause rather than just an agreed NWI documented in the mailing list archives. Are you suggesting that database capabilities should be documented in policy?
I can understand why we'd want to document registration requirements. Documenting the database requirements in policy would mean that any new features could only be added after a policy development process. Why add friction?
Regards,
Leo ----- 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/