This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Thoughts on 2022-01
- Previous message (by thread): [db-wg] [anti-abuse-wg] Proposal 2022-01
- Next message (by thread): [db-wg] RIPE Database Quarterly Planning Q3 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo at vegoda.org
Mon Jun 27 16:51:23 CEST 2022
Hi, Thank you for producing this proposal. It's important to regularly review policy and implementation to ensure we are meeting our legal responsibilities. Parts of the text in this proposal are clear and easy to interpret. For example section 3.0 on Notifications is well written. Other parts are highly ambiguous. The text as written would just lead to disputes. For example, "Email addresses added as contact details and all phone and fax numbers entered into the RIPE Database must be verified." Who must verify them, what must they verify, and when should this happen? Is this just a check that the contact information is syntactically correct? Or is this a check that a fax machine is active and used by the organization listed alongside it? It would be helpful to clearly separate the sections defining a principle from those defining an implementation. The text on verification and compliance is so ambiguous that it's not possible to understand what an implementation would look like. Kind regards, Leo Vegoda
- Previous message (by thread): [db-wg] [anti-abuse-wg] Proposal 2022-01
- Next message (by thread): [db-wg] RIPE Database Quarterly Planning Q3 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]