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] 2017-02 Review Phase (Regular abuse-c Validation)
- Previous message (by thread): [anti-abuse-wg] 2017-02 Review Phase (Regular abuse-c Validation)
- Next message (by thread): [anti-abuse-wg] 2017-02 Review Phase (Regular abuse-c Validation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
aawg at c4inet.net
Fri Jan 19 15:43:16 CET 2018
On Thu, Jan 18, 2018 at 12:22:28PM +0100, Marco Schmidt wrote: >The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: >https://www.ripe.net/participate/policies/proposals/2017-02 It would appear that some participants have issues with comprehensive reading. The Impact Assessment states: "The RIPE NCC has no mandate to interfere with the internal abuse handling procedures of resource holders." I fail to understand how understanding this sentence can lead to demands such as "The recipients must solve captchas and click checkboxes". Apart from that, such demands can, presumably, only be made by those who have never operated a production network. Many operators feed abuse/support emails into a ticket system or otherwise automate the process. There are also those who do not use a web browser to read emails. And, regardless of the above, there are the security issues raised in the thread. Therefore, unless there is a guarantee that such impractical and, frankly, ridiculous proposals cannot be backdoored into this policy via the implementation process, I will have no choice but to oppose this proposal in toto. Kind Regards, Sascha Luck
- Previous message (by thread): [anti-abuse-wg] 2017-02 Review Phase (Regular abuse-c Validation)
- Next message (by thread): [anti-abuse-wg] 2017-02 Review Phase (Regular abuse-c Validation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]