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] 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 ]
Tobias Knecht
tk at abusix.com
Tue Jul 31 16:34:28 CEST 2012
Hi, >>> No. We had that conversations already and decided not to accept web >>> addresses only. The reason is, that automatic reporting can not be done >>> with web addresses. >> >> Assuming you mean something accessible over HTTP or HTTPS, it does not >> have to be accessed by a person using a browser. If there was a widely >> adopted API, I can see the value in a URL for some kind of RESTful >> service for automatic reports that do not require human involvement. Right. If we are talking about an RESTful API based system that is absolutely fine. At the moment we do not have such an system in place, but as soon as we have I will be the last person to ignore it. At the moment email with it's standards like (m)ARF and x-arf and IODEF and all these are common practice. And we need a solution for this common practice. > An optional abuse-url field is really a good idea, if there would be an > standarized ARAPI (Abuse Report API ?) As soon as we have something in place, I will write the proposal. Promised ;-) Thanks, Tobias
- 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 ]