Hi Sascha, Now you are going into implementation details. There are many ways to Rome, as they say. One better than the other.
Every email address in the RIPE database should work. There is a reason to register an email address (and that is not for historical purposes). There should be someone that is able to read those emails (or it should serve its purpose). If it doesn't work, and that was determined correctly (and maybe escalated to the org itself), then it should be removed. Validity of data should be the concern of RIPE. David Hofstee -----Oorspronkelijk bericht----- Van: anti-abuse-wg [mailto:anti-abuse-wg-boun...@ripe.net] Namens Sascha Luck [ml] Verzonden: dinsdag 3 november 2015 14:43 Aan: anti-abuse-wg@ripe.net Onderwerp: Re: [anti-abuse-wg] WHOIS (AS204224) On Tue, Nov 03, 2015 at 02:28:03PM +0100, David Hofstee wrote: >In that line of thought: I would like email validation on a regular >basis. There are so many email addresses that do not work properly >(what then is the sense of registering invalid data?). There are LIRS that register many thousands of objects. Even small LIRs can have many hundreds. Is the idea that they employ someone full-time to solve captchas for the NCC (another idea from this discussion)? Frankly, I'd rather have the spam, at least I can filter that. rgds, Sascha Luck
