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
- Previous message (by thread): [anti-abuse-wg] abuse-c cleanup
- Next message (by thread): [anti-abuse-wg] abuse-c cleanup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gilles Massen
gilles.massen at restena.lu
Thu May 7 19:06:36 CEST 2015
Hi, On 5/5/2015 15:59 , denis walker wrote: > 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. I'd like to have the "cleanup" defined and discussed before doing it. The 'remarks' are obviously not really useful, and the abuse-c seems to replace functionally the abuse-mailbox (except that I still miss a 'more specific' abuse-c). The IRT objects are different though, and have features that the abuse-c lacks. So unless the abuse-c is able to replace the IRT, I'd object to deleting those. (to be specific: I'd hate to lose the signature and encryption fields - I think it was a mistake not to add those to the abuse-c from the start) best, Gilles
- Previous message (by thread): [anti-abuse-wg] abuse-c cleanup
- Next message (by thread): [anti-abuse-wg] abuse-c cleanup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]