[arin-ppml] Policy idea: POC Validation

[Ted Mittelstaedt]

I like this solution a lot!   It will, of course, result in the 
offending ISPs POCs being spammed to death by their own automated 
systems which auto-fill the SWIPs with information they seem to pull
out of thin air.

But sacrifices have to be made!

Ted

On 4/14/2015 11:08 AM, William Herrin wrote:
> On Mon, Apr 13, 2015 at 5:31 PM, Martin Hannigan<hannigan at gmail.com>  wrote:
>> Did ARIN/you consider a consultation instead and simply adding a NACK button
>> to the confirmation and reassigning the block back to the ISP in question or
>> re designate to the  online account owner?
>
> Hi Marty,
>
> That's a fantastic idea. But instead of deregistering the block (which
> would add chaos to the process for the right-org-wrong-POC case) do
> two things:
>
> 1. Feed the fact of the NACK back to the ISP with a message that the
> POC reports a registration mistake (requests contact for correction)
> and a gentle reminder that they are asked to publish accurate records
> as a condition of retaining allocations. Mistakes will be made. How
> will the folks who made the mistake find out if they don't get any
> feedback?
>
> 2. Use the data to build a stochastic model that separates routine
> bookkeeping error from orgs who are more on the negligence/fraud end
> of SWIP management.
>
> Regards,
> Bill Herrin
>