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] objection to RIPE policy proposal 2016-01
- Previous message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Mon Mar 7 10:23:26 CET 2016
On 07-Mar-2016, at 2:48 PM, Gilles Massen <gilles.massen at restena.lu> wrote: > And as a reporter, I prefer > a clear "I don't care" over wasting my time on an ignored report. > > So advertising the abuse-c actively: yes, sure. Mandatory: no. Thus > changing policy in regard to ERX: no (besides, that's poor form, cf > Peter Koch's comment). As a reporter doing manual reporting of occasional phish - great, an optional format is just fine. As a reporter of quite a lot of phish - I think having something that is standardized and machine parseable helps. Those that really don’t want to handle reports for a range might want to populate something standard there too (and yes, this is a semi ironic policy proposal) - devnull at example.com or whatever. —srs
- Previous message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]