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 Discussion Phase (Validation of "abuse-mailbox")
- Previous message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Wed Apr 29 18:22:04 CEST 2020
Serge Droz via anti-abuse-wg wrote on 29/04/2020 16:55: > So, it's the security guys, saying > > This may help a bit, but won't solve all problems. > > versus the infrastructure operators saying > > Beware! This it creating huge costs and will not help at all, and > answering two mails a year will be our ruin. The root problem is that the policy proposes to use the RIPE NCC to enforce abuse management processes. The specifics in this iteration of the document are to threaten and then act to deregister an organisation's number resources - and thereby remove their ability to conduct business - if the organisation declines to handle abuse complaints over email. To be clear, it's a fundamental right in large chunks of the RIPE service region to conduct business. If the RIPE NCC acts to threaten to remove this ability to conduct business, there would need to be sound legal justification for doing so. Nick
- Previous message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]