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)
 - Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database) - addtional needs
 
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Frank Gadegast
ripe-anti-spam-wg at powerweb.de
Thu Nov 24 10:46:38 CET 2011
Hi,
Suresh Ramasubramanian wrote:
> it is an interesting question, followed by the 'what is ripe to do in cases where is requirement isnt complied with, or where it is fraudulent' question
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.
And its surely useable automatically.
And a required abuse object is really needed anyway ...
The proposal should also answer the following question:
- are abuse remarks, the abuse-mailbox field or IRT-abuse field
   depricated or could they be used beside the non mandatory
   abuce-c
- will there be any kind of automatic migration of existing abuse
   contact to the abuse-c ?
- will it be possible for an LIR to select something like:
   (x) use the following default abuse-c for all inetnum objects: ______
       if there is non explicitly specified
   ?
- 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 ?
This all leads to the old question if the RIPE NCC is willing
to punish LIRs, that do not answer abuse reports.
Kind regards, Frank
> --srs (iPad)
>
> On 23-Nov-2011, at 20:18, Leo Vegoda<leo.vegoda at icann.org>  wrote:
>
>> Hi,
>>
>> The proposed policy text includes:
>>
>> "The role objects used for abuse contact information will be required to contain a single "abuse-mailbox:" attribute which is intended for receiving automatic and manual reports about abusive behavior originating the resource holders' networks."
>>
>> Do the proposers intend the requirement for the "abuse-mailbox:" attribute to be enforced in any way and if so, how?
>>
>> Thanks,
>>
>> Leo
>>
>
>
>
>
-- 
Mit freundlichen Gruessen,
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================
Public PGP Key available for frank at powerweb.de
- Previous message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
 - Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database) - addtional needs
 
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]