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/[email protected]/
[anti-abuse-wg] Proposal for technical details for abuse contact information in the RIPE Database
- Previous message (by thread): [anti-abuse-wg] Proposal for technical details for abuse contact information in the RIPE Database
- Next message (by thread): [anti-abuse-wg] Proposal for technical details for abuse contact information in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Frank Gadegast
ripe-anti-spam-wg at powerweb.de
Thu Dec 1 15:24:05 CET 2011
Shane Kerr wrote: > Denis, Dear Denis, a restriction or ACL for the abuse address is simple not what a lot of people intended. You forgot about bigger ISPs that likes to report abuse automatically in standarized formats (and what most abuse departments really LIKE to receive). An unrestricted abuse contact really helps here a lot. Sure, personal data should be protected, and thats why we really like the idea of seperating them from personal objects. But to be honest: no restriction helps that your email address ends up in a spammers list, they have more power you can dream of (I even heared that they pay people to enter captcha codes). Kind regards, Frank > > On Wed, 2011-11-30 at 16:25 +0100, Denis Walker wrote: >> The RIPE NCC Database Group has now published an article on RIPE Labs >> with a detailed explanation of how we propose to implement abuse >> handling with an "abuse-c:" attribute referencing a ROLE object. >> >> https://labs.ripe.net/ripe-database/abuse-handling-in-the-ripe-database > > Thanks for putting this together. > > Basically, I think that the basic split between ABUSE and STANDARD ROLE > objects does not make a lot of sense, and will likely lead to user > confusion and frustration. Some of the ideas you've presented do make > sense, but make sense for any contact data rather than restricting them > via arbitrary business rules. > > One thing that I think would be a positive step forward for the RIPE > Database is *not* to restrict references to ABUSE ROLE, but rather to > restrict *all* references to person or role objects. I believe the > database currently still allows me to reference any person/role object > if I want to. This is a bug, not a feature, and I think adding > "mnt-ref:" to person/role objects would be a better way forward than > adding yet another special case. (This was introduced as a special case > to the irt type, but then generalised in the organisation object.) > > I also suggest that normal access controls should apply to roles when > used for abuse. Abuse desks don't like spam either. > > -- > Shane > > > > -- Mit freundlichen Gruessen, -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank at powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ====================================================================== Public PGP Key available for frank at powerweb.de
- Previous message (by thread): [anti-abuse-wg] Proposal for technical details for abuse contact information in the RIPE Database
- Next message (by thread): [anti-abuse-wg] Proposal for technical details for abuse contact information in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]