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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] WHOIS (AS204224)
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeffrey Race
jrace at attglobal.net
Fri Nov 6 15:35:02 CET 2015
On Fri, 6 Nov 2015 11:56:51 +0100, denis wrote: >Add to that all the possible language issues and I am not sure how you >will expect the RIPE NCC to validate all this personal contact data with >people who they have no relationship with and who may have never heard >of the RIPE NCC or RIPE. Anyone who receives an email from an >organisation they have never heard of, possibly in a language they don't >understand, asking to validate personal information...well you know how >that will be treated these days. An essential element in cleaning up the mess is to educate everyone that periodic revalidations will occur (e.g. using tokens as mentioned earlier) and the process; it becomes part of the mechanism by which users retain their access to the entrusted public resources. Same idea as inputting a pin when I turn on my mobile phone, or dealing with the periodic messages I receive in a standard format from NetSol regarding maintenance of my website >Also bear in mind a single data validation is quite pointless. Periodic automated revalidations :) Jeffrey Race
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]