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/[email protected]/
[db-wg] [anti-abuse-wg] Proposal 2022-01
- Previous message (by thread): [db-wg] [anti-abuse-wg] Proposal 2022-01
- Next message (by thread): [db-wg] Thoughts on 2022-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Fri Jun 24 02:09:19 CEST 2022
In message <CAKvLzuHjvzMjV8uT0nvv_ocL2h-uF49uNwTdAJDRvDpJabfqdA at mail.gmail.com> denis walker <ripedenis at gmail.com> wrote: >Yes Carlos you are absolutely right. There is no suggestion whatsoever that >any membership will be revoked or any resources de-registered if any >verification fails. What then is the enforcement mechanism that underpins sections 4.0, 5.0, and 6.0 of your proposal then? Foul language? If recalcitrant members continue to put bogus garbage into their WHOIS records, then what happens? Will NCC step in, take control of the relevant WHOIS record(s) and insert correct information taken from the member's original bona fide documents that the member submitted when the member joined RIPE? You can't have it both ways. You can't make it a matter of formal policy that names, street addresses, phone numbers, and email addresses will henceforth have to be "verified" without explaining who is going to do this, when it is going to be done, what exactly qualifies as "verified", and what you believe will happen or should happen if it -isn't- done. Regards, rfg
- Previous message (by thread): [db-wg] [anti-abuse-wg] Proposal 2022-01
- Next message (by thread): [db-wg] Thoughts on 2022-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]