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] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
- Previous message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
- Next message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Fri Jan 19 13:08:58 CET 2018
Dear Jordi, Thank you for your question. On 2018-01-18 19:44:51 CET, Jordi Palet Martinez wrote: > HOWEVER, I’ve a question regarding the impact analysis, and specially this sentence: > > “To increase efficiency, this process will use an automated solution that will allow the validation of “abuse-mailbox:” attributes without sending an email. No action will be needed by resource holders that have configured their “abuse-mailbox:” attribute correctly.” > > Reading the policy proposal, how the NCC concludes that it should be “without sending an email”? > During the initial discussion phase and also during the Anti-Abuse WG session at RIPE 75, several people stated that forcing providers to reply to the RIPE NCC doesn't ensure that they will respond to actual abuse reports. At the same time, such a policy requirement would create additional workload to all providers. For these reasons, the proposers decided to remove such a requirement in v2.0 of their proposal. The RIPE NCC will focus on the technical accuracy of abuse contact emails. These checks can be done without the need to send an email. Validating that an abuse mailbox attribute is correctly configured ensures that abuse reports can reach their destination. The way that abuse reports are handled by the receiving party is usually defined by the internal procedures of the providers and not by RIPE Policies. I hope this clarifies. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
- Next message (by thread): [anti-abuse-wg] [policy-announce] 2017-02 Review Phase (Regular abuse-c Validation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]