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] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
- Previous message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
- Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
U.Mutlu
security at mutluit.com
Wed Jan 18 12:27:16 CET 2012
Dan Luedtke wrote, On 2012-01-18 08:39: > On Mon, Nov 28, 2011 at 10:08 PM, Tobias Knecht<tk at abusix.com> wrote: >> The abuse-c will reference a person, role or >> organization object. > I followed the discussion and looked at some RIPE Database entries to > get an idea what the problem was. With the reference to roles and/or > organizations, for most space holders it will be easy to comply with > the proposed policy. > > I support this proposal, even if the wording might not be the best at > the moment (I guess it will change during the process, I saw that on > other policies already). I too support the proposal, but under these conditions: the new handle "abuse-c" and the abuse contact info under this handle must be _mandatory_, not optional, and it must be a functioning email address, not a web link etc. A non-functional abuse email contact shall mean an abuse itself. To automate the task of abuse reporting (and of abuse processing at the receiver side) I even would like to have several (2 or 3) abuse contact email addresses as there are several kinds of abuses (spam with ads, spam with criminal intent, hacking attempts, flood attacks/(D)DoS, portscans, service attacks, copyright infringement, impersonation, sockpuppetry, insult/discrimination, ...), but I think this should be made some time later in a new proposal when enough experience has been collected with "abuse-c". Another method would be to use just one abuse address but use a specific keyword in the subject line for automatic filtering/routing the report to the right department at the receiver side. These keywords (key) should be the same for all organizations, ie. it shall be standardized and published by the RIR. But as said, these extended methods can be done some time later in a new proposal. For newcomers: here's the ongoing proposal and some related pages: http://www.ripe.net/ripe/policies/proposals/2011-06 https://labs.ripe.net/ripe-database/abuse-handling-in-the-ripe-database http://www.ripe.net/ripe/groups/tf/abuse-contact Minutes and archives: http://www.ripe.net/ripe/groups/wg/anti-abuse Rgds, U.Mutlu www.mutluit.com
- Previous message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
- Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]