On Sun, Nov 01, 2015 at 06:50:41PM -0800, Ronald F. Guilmette wrote: [irrelevant ranting redacted]
Is anyone here either willing or able to defend _either_ the accuracy and correctness of that specific RIPE WHOIS record _or_ the vetting process that RIPE NCC applied to the data contained therein? If so, please proceed. I'm all ears.
While I can't speak for the accuracy of the AS204224 record, I can say that the procedures used by the RIPE NCC to verify the identity of its members are sufficient and, in my personal opinion sometimes overreaching. So are the sanctions available for incorrect or false registry entries. If you were a member or had you bothered to read the relevant documentation of the process as detailed at https://www.ripe.net you would know that. If I remember correctly, I have also pointed you at this documentation before. The RIPEDB allows the registration of out-of-region objects which is mostly due to the fact that there are RIRs who either have no, or no useful, WHOIS registry. the NCC is doing that for the good of the Internet and has, obviously, no legal authority to verify the identity of those objects.
If so, please proceed. I'm all ears.
From where I am sitting however it appears me that the both the data contained in the RIPE WHOIS record for AS204224 and also whatever process RIPE NCC followed to validate that data are... not to put too fine a point on it... nothing short of bovine excrement.
Evidence please, until then I will regard this as baseless slander.
Forget ICANN. Is _RIPE_ also a slacker when it comes to maintaining its own WHOIS data base? Are officially sanctioned RIPE policies and procedures making to harder than it ought to be to stop, or even to just merely identify criminals, con men, and spammers on the Internet? If so, when was that decision ratified, and by whom?
The Policy Development Process is detailed in documentation on the abovementioned website. rgds, Sascha Luck