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] Notice: Fradulent RIPE ASNs
- Previous message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
- Next message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Mon Jan 21 12:53:02 CET 2013
In message <40A6A1EE-5F5B-46A3-ACFE-17F69F24EDB1 at steffann.nl>, Sander Steffann <sander at steffann.nl> wrote: >> Perhaps something more like a couple of checkboxes on the complaint = >form >> which say: >> >> [ ] I wish this complaint to be public. >> [ ] I wish my name to be included in the public report. >> >> This way we could have an opt-in public archive of all abuse reports >> that the RIPE NCC has received. > >Even better! Then we also have an input/output view on the RIPE NCC >fraud/complaint handling procedure. Ummmm... no. Apparently there is some confusion here. Let me try to clear that up. As I understand it, RIPE has contractual confidentiality commitments that are of such a nature that RIPE will _never_ say _anything_ about _any_ aspect of its handling of _any_ abuse report. Period full stop. For that reason, you will *not* ``get an input/output view'' on the process. No person outside of RIPE staff will _ever_ see _any_ ``output''. That's the problem. Putting an extra check box on a report form isn't going to change that. I hope that we are clear on this now. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
- Next message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]