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] abuse-c cleanup
- Next message (by thread): [anti-abuse-wg] abuse-c cleanup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at yahoo.co.uk
Tue May 5 15:59:01 CEST 2015
Hi All
When the original implementation plan was put forward for "abuse-c:", the time line (if I remember correctly) was:-allowing 6 months to deploy to all members allocations-then 12 months to deploy to all independent resources-then do a cleanup
The first two steps are done, but the last one seems to have been overlooked. The idea of "abuse-c:" was to create one single place/way of documenting abuse contact details. So far all that has been achieved is to add a fourth way to document it. All the old ways ("abuse-mailbox:" in 5 object types, IRT and remarks) are still littered throughout the database.
I think it is time to schedule that cleanup.
Can the RIPE NCC confirm that all resources now have an "abuse-c:"?
cheersDenis WalkerIndependent Netizen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/anti-abuse-wg/attachments/20150505/b0c742ab/attachment.html>
- Next message (by thread): [anti-abuse-wg] abuse-c cleanup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]