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 ]
Leo Vegoda
leo.vegoda at icann.org
Tue Jul 31 19:57:23 CEST 2012
Hi Denis, Denis Walker <denis at ripe.net>: [...] > As I follow these discussion my mind keeps focussing on the Abuse Finder > tool and the technical nightmare we have right now in trying to make > that work. One of the many problems with it is we cannot parse remarks > that (may) include abuse contacts. I think you have highlighted a fundamental issue with the design of RIPE database objects. They include data that is specifically for human consumption in objects that are structured so they can be parsed by software. I do not know what the best way to combine software parsable database objects and human readability is but recognise that this is not the Database WG list and that I am not a database expert. Regards, Leo Vegoda -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5488 bytes Desc: not available URL: </ripe/mail/archives/anti-abuse-wg/attachments/20120731/2180c812/attachment.p7s>
- 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 ]