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] the mandatory abuse field
- Previous message (by thread): [anti-abuse-wg] the mandatory abuse field
- Next message (by thread): [anti-abuse-wg] the mandatory abuse field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ian Eiloart
iane at sussex.ac.uk
Tue Jul 31 18:12:13 CEST 2012
On 31 Jul 2012, at 14:50, Denis Walker <denis at ripe.net> wrote: > Dear Michele > > This is a very reasonable question. One of the technical advantages of the "abuse-c:" proposal is that it references an object in which is stored contact information. Currently the discussion is focussing on an "abuse-mailbox:" attribute in that object as the primary contact method. > > As Tobias said, technically, we could easily add an additional "abuse-url:" attribute if required. Or anything else like "abuse-im:" or "abuse-mobile:". If we have the framework referencing a contact object then whatever the community wants inside that object is possible. You just decide what methods you want and what should be mandatory, required, optional, this or that, etc and the RIPE NCC can build it. Why not leave it at abuse-url: and let people use mailto: urls? So, they can put anything in there that has a url schema. -- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148
- Previous message (by thread): [anti-abuse-wg] the mandatory abuse field
- Next message (by thread): [anti-abuse-wg] the mandatory abuse field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]