[arin-ppml] How bad is it really?

[Owen DeLong]

On Jul 14, 2010, at 12:11 PM, <michael.dillon at bt.com> wrote:

>> Whether you consider it fraud, abuse, or negligence, SWIPing resources
>> to an
>> ORG that is no longer using them (or leaving them SWIPped as such) is
>> in
>> violation of ARIN policy and the RSA. As such, if you know of a
>> situation where
>> an ORG has done so, the right thing to do is report it through the
>> fraud and
>> abuse reporting process.
> 
> Actually I think this is a stupid approach and will just lead to
> lawsuits.
> 
> Martin Hannigan had the right idea when he suggested that you should
> 
> 1. send an email to the former provider asking for the record to
>   be updated, and
> 2. send an email to ARIN CCing the former provider, asking ARIN 
>   to clean up the provider's mess.
> 
> And none of this needs to be reported to fraud or abuse departments
> since it is a simple operational issue of exception handling. Mistakes
> are common and you need an exception process to collect mistakes and
> shepherd them through to correction.
> 
ARIN doesn't have a fraud or abuse department. The fraud and abuse
complaints to ARIN are handled by Registration Services almost identical
to the way CCing hostmaster as you mention above will get handled.

I don't see how reporting this kind of violation of the RSA through the
ARIN process intended for such reports will result in lawsuits. Could you
please explain that rather bizarre conclusion?

Owen