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] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database) - addtional needs
- Previous message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database) - addtional needs
- Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Adrian
ripe-wg-antiabuse at kyubu.de
Thu Nov 24 14:17:06 CET 2011
On Thu, Nov 24, 2011 at 10:46:38AM +0100, Frank Gadegast wrote: hi, > At least an abuse-c is much nicer to parse for the normal people than > an IRT object, because it will appear in the normal whois output for > any IP asked for. This is also true for the IRT object. Parsing is as easy as parsing any other object. > - how or who will test, if an abuce-c is correct ? > - will the whois state, who to contact (or wich URL to visit), > if an abuse-c isnt reachable or correct ? > - what is happening, if the abuce-c isnt correct ? Thanks for bringing up these questions. Trusted Introducer solved all of these some time ago. Cheers, Adrian
- Previous message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database) - addtional needs
- Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]