[db-wg] Options for extending "abuse-c:"
- Previous message (by thread): [db-wg] Options for extending "abuse-c:"
- Next message (by thread): [db-wg] Options for extending "abuse-c:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu May 8 12:07:29 CEST 2014
On Wed, May 07, 2014 at 07:26:59PM +0200, Denis Walker wrote: Dear Denis >> What you want is to hide away the whole RIPE database and provide a point >> and click interface which only dispenses those morsels of information you >> think people should have? > > This is definitely not what I want, nor is it what I said. But it does no > harm to occasionally ask questions of this 15 year old design and see if it > still works "for everyone". In terms of hiding data away, it was agreed to > hide the MD5 hash for security reasons. Let me ask you a question....does > it benefit you, or me or the public that everyone can see your MNTNER > object? What data exists in your MNTNER that I need to know? Do I need to > know who, in your organisation, receives notifications of failed updates > because of authorisation failures? Do I need to know how you have > partitioned the management of your resources within your organisation? At this point of time it helps me that some MNTNERs are visible to the public. Unfortunately admin-c and/or tech-c of MNTNERs are/were used by https://stat.ripe.net/special/abuse as a last resort of finding abuse contact. I have pointed that already both to the RIPE NCC staff members and on one of the RIPE mailing lists. Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [db-wg] Options for extending "abuse-c:"
- Next message (by thread): [db-wg] Options for extending "abuse-c:"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]