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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] 2019-04 New Policy Proposal (Validation of "abuse-mailbox")
- Previous message (by thread): [anti-abuse-wg] 2019-04 New Policy Proposal (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] 2019-04 New Policy Proposal (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Thu May 16 23:38:33 CEST 2019
Gert Doering wrote on 16/05/2019 21:47: > No positive effect, but lots of negative side-effects. Abuse mailboxes are already checked. What matters for abuse management is whether reports are acted on. This policy doesn't address that. If the RIPE NCC is instructed to send 6-monthly reminders to all abuse contacts with the implicit threat that if they aren't acted on in the way specified in this policy, that the organisation in question can look forward to having their addressing resources vapourised, this will aggravate the RIPE NCC membership and corrode community trust in the organisation. The one thing it won't do is make abuse management better. Internet abuse management is not something that you're going to fix by beating LIRs with sticks, and if they don't react, that you threaten to beat them harder. Separate to this, it's inappropriate to micromanage the NCC in RIPE policy. It would be good if the RIPE working groups stopped trying to tell the RIPE NCC people how to do their jobs. Nick
- Previous message (by thread): [anti-abuse-wg] 2019-04 New Policy Proposal (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] 2019-04 New Policy Proposal (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]