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] Status of 2011-06
- Previous message (by thread): [anti-abuse-wg] Status of 2011-06
- Next message (by thread): [anti-abuse-wg] Status of 2011-06
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
chrish at consol.net
chrish at consol.net
Thu Jan 12 14:40:51 CET 2012
Hi! On 01/12/2012 01:54 PM, Frank Gadegast wrote: > You will have no access restrictions for the abuse contact anymore > and the new abuse-c will be filled in a very short period because > it will be mandatory. The addresses entered into our ripe objects are not private data. They are public addresses for the purpose of ripe-stuff. Following your idea abuse-cs would always be copies of the admin-c. A reasonable approach towards what seems to be your communicated aim would be: Drop all *-c in favour of a single contact, which is meant as contact for ripe-stuff. This is of course public as it's meant that way. In case you actually wish for the possibility of multiple, specific contacts, the straightforward and all-compatible solution would be to add optional further specific contact data - that may be used by people who wish to direct mail to different specific addresses. Translated into the current state that would be: use an optional abuse-mailbox attribute (if this were mandatory, our objects would always just hold a copy of the e-mail attribute). > But maybe they will not find them attractiv at all, because they > know, that they will only reach professionals there, that can easily > seperated spam from good mail and that are trained not to click > every link in an email ;o) Yeah, that will certainly teach them. > But anyway: it will be possible to protect personal contacts much > better in the future, if the proposal gets through, because access Sorry, but it's just a stupid idea to put private data into public databases. Regards, Chris
- Previous message (by thread): [anti-abuse-wg] Status of 2011-06
- Next message (by thread): [anti-abuse-wg] Status of 2011-06
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]