Hello, Thanks to the authors for your work on this. This is a mostly solid proposal, and will improve the quality and usefulness of the RIPE database, and reduce unnecessary and incorrect information in it. But I do have a concern. If I read this right, e-mail would also be optional, and it would be fine for a network's only contact to be WhatsApp, for instance. This means that to contact another network operator, one operator would have to bind themselves to the Meta terms and conditions, which does not feel right to me as a requirement. Having no fixed required methods also risks fragmentation. Now, I can reach most operators through email. If I regularly reach out to other networks, I'd need a Signal, Telegram, WhatsApp, Discord, Matrix, etc. account as everyone has a different contact method. The RIPE NCC also occasionally reaches out to operators in bulk, e.g. for MD5 changes, and may have to add bots to support all those platforms to reach contacts. Therefore, I feel we should keep e-mail mandatory. It is widely established and used, and not (or at least limited) tied to complex T&C. I know it's not everyone's favorite method, but to me it seems like the one we can all tolerate. On 26 May 2025, at 00:49, Leo Vegoda <leo@vegoda.org> wrote:
This proposal is limited to admin-c and tech-c contact types.
Are you intentionally leaving out zone-c and abuse-c, which, if I'm not mistaken, are also references to role or person objects? I understand the abuse-mailbox attribute being a special additional requirement, but reading your proposal literally, we would still require a postal address when a role is used as abuse-c and tech-c, but not when it's only used for tech-c. I don't know whether part of this is oversight or intent, but I think the NWI should at least explicitly mention zone-c/abuse-c. Sasha