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] [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 ]
Brian Nisbet
brian.nisbet at heanet.ie
Fri Jan 19 17:35:06 CET 2018
Eric, Given the NCC have repeatedly said that the ARC is not a suitable way to validate the abuse contact and have proposed an alternative method, supported by the ARC process, do you have any comment on the actually proposed process? Thanks, Brian Co-Chair, RIPE AA-WG On 19/01/2018 14:19, Erik Bais wrote: > I have to agree with Wolfgang here ... > > If any of our helpdesk engineers would click on a link or attachment in what we receive on the abuse-mailbox ... he/she would have to keep restoring the systems due to the massive number of malware that is received in it.. > > I still think that the best way to validate a current abuse-contact is during the ARC's ... > It wouldn't require any additional process nor additional contact moments from the RIPE NCC's point of view to the resource holders. > > Regards, > Erik Bais >
- 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 ]