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/members-discuss@ripe.net/
[members-discuss] Database Abuse
- Previous message (by thread): [members-discuss] Database Abuse
- Next message (by thread): [members-discuss] Database Abuse
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Lobachov
alxl at telenet.lv
Thu Sep 7 11:23:47 CEST 2017
Good day, I’m all for administrative actions to LIR members (usually guys who are involved in ipv4 transfers) who are found guilty of using the DB with commercial goals. Closing the LIR might be the appropriate (yet quite aggressive one) action for them. Comments? -- Alex Lobachov Telenet, sia Network Systems Engineer LinkedIn: https://lv.linkedin.com/in/allxll E-mail: alxl at telenet.lv Skype: alxl__ Direct office: +371 67886224 Office: +371 67711111 From: Tim Armstrong Sent: Thursday, September 7, 2017 11:17 AM To: Vegard Svanberg Cc: members-discuss at ripe.net Subject: Re: [members-discuss] Database Abuse Or if your details are in the list and / or you are a technical contact attached to an LIR then you can see everything. Only non-technical / non-LIR people can't access it. Perhaps use passing the RIPE DB Training course as a requirement for access. On 7 Sep 2017 10:06 am, "Vegard Svanberg" <vegard at monsternett.no> wrote: * Tim Armstrong <t.armstrong at nerdalize.com> [2017-09-05 10:36]: > I hate to bring this subject up again, but is there really nothing > structural we can do about this? > At a minimum we could occlude e-mail addresses from the public DB, > instead having public complaint submitted via a webform on the NCC > website, requiring the uninitiated to realise this is an abuse / > complaint contact, not a sales opportunity. I understand the problem (and get those pitches myself nearly daily). I have no alternative, simple solutions. I also haven't thought this through in detail. :-) However, and despite all that: I'd oppose the idea of hiding/obfuscating emails and centralising/limiting feedback loops to the NCC website. I'm concerned about the operational consequences of limiting the opportunity to collect emails and build and maintain lists of contact points (potentially) important for operations. And if we remove just emails, we'd probably have to do the same with phone numbers. They're calling from time to time as well. Again, I haven't thought this through, but it's the knee-jerk response anyway. Perhaps naming, shaming and blacklisting the offenders might be a better way to go. Perhaps verified members could get regular database dumps (including contact info) from other sources, or authenticate against the db to get the whole lot. I don't know. I'm not sure the problem is big enough to warrant any major changes. -- -o) Vegard Svanberg, MD - Monsternett (www.monsternett.no) /\\ Violgata 3A, N-1776 HALDEN, NORWAY _\_v Phone: (+47) 69701802 | Fax: (+47) 69701801 ---- If you don't want to receive emails from the RIPE NCC members-discuss mailing list, please log in to your LIR Portal account and go to the general page: https://lirportal.ripe.net/general/ Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses. -------------------------------------------------------------------------------- ---- If you don't want to receive emails from the RIPE NCC members-discuss mailing list, please log in to your LIR Portal account and go to the general page: https://lirportal.ripe.net/general/ Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20170907/0428c2e0/attachment.html>
- Previous message (by thread): [members-discuss] Database Abuse
- Next message (by thread): [members-discuss] Database Abuse
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]