[ppml] Getting aggressive about vetting

[Ted Mittelstaedt]

>-----Original Message-----
>From: John Curran [mailto:jcurran at istaff.org]
>Sent: Thursday, March 15, 2007 5:19 PM
>To: Ted Mittelstaedt
>Cc: ppml at arin.net
>Subject: Re: [ppml] Getting aggressive about vetting
>
>
>At 4:00 PM -0700 3/15/07, Ted Mittelstaedt wrote:
>>If ARIN and the other registries do NOT "do the right thing" and get
>>agressive about "vetting" the IP allocations, but merely continue to
>>act as "stewards" then we will have a failure, ...
>
>Ted -
> 
>   I suspect that ARIN will get as aggressive about "vetting"
>   IP allocations (new, existing, or both) as ARIN's approved
>   Internet resource policies allow.   The cool thing is that
>   you (collective) get to actual set the policies.  The downside
>   is that there has to be an actual policy proposal before
>   there can be any new policy...
>
>   What do you propose?  ARIN ask for a third-party audits
>   of IP address usage?  Perhaps company officers should
>   actually sign & attest to the accuracy of the applications?
>   Should ARIN partner with equipment manufacturers to
>   insert secret hidden remote monitoring options??  There
>   is a very wide range of possible ways that RIR's can get
>   more aggressive in vetting new (and existing) resource
>   allocations, but you've got to be a little more specific
>   so that a proposal can be: 1) Written, 2) Approved, and
>   3) Implemented by ARIN.
>

I think that this should go in stages, you see.  There is going to
have to be a lot of work in bringing space under registry control
first, obviously.  But, eventually your going to have to confront
the idea of how to audit.

In the United States the IRS does tax audits based on a secret
algorithm they use when looking at tax returns.  It seems to me
that such a computer program could be designed for ARIN that would
read through all assignments and cough up a list of likely audit
candidates.  For example, if an organization has not changed a
SWIP in over 5 years, that might increase it's chances of getting an
IP audit.

An IP audit could consist of nothing more than ARIN sending a letter
to the administrative contact requesting a signed statement from the
contact that the allocation is still being used.

My guess is that doing some very simple things like this would 
likely uncover a large amount of unused space.

Ted