[arin-ppml] Draft Policy 2008-7: Identify Invalid WHOIS POC's

[Kevin Kargel]

> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
> Behalf Of Owen DeLong
> Sent: Thursday, April 02, 2009 2:51 PM
> To: William Herrin
> Cc: arin-ppml at arin.net
> Subject: Re: [arin-ppml] Draft Policy 2008-7: Identify Invalid WHOIS POC's
> 
> 
> On Apr 2, 2009, at 10:54 AM, William Herrin wrote:
> 
> > On Thu, Apr 2, 2009 at 12:28 PM, Owen DeLong <owen at delong.com> wrote:
> >> In any case, given the data now at hand, do you support or oppose
> >> the policy?
> >
> > Hi Owen,
> >
> > Support the general idea. Oppose as written.
> >
> > The systemic costs have not been adequately quantified or considered.
> > Relatively trivial edits could and should be used to reduce the cost
> > with little or no damage to the proposal's effectiveness.
> >
> > Edits I would make if it were my proposal include:
> >
> > 1. Don't ping POCs for which at least one attached resource has been
> > updated in the past 3 to 5 years. If some other behavior demonstrates
> > a high probability that the POC is valid, there's no need to burn more
> > of the POC's time.
> 
> I think that the number of POCs that update their records annually is
> low enough that this would not be a significant savings.
> 

While the POCs that update may be few, the POCs that make changes or
amendments or ask questions or pay fees are not few.  My read says that any
activity by a POC counts as a refresh.  

I have no idea how ARIN will track this, perhaps a database of "last email
received" or some such, but it seems very doable.

Kevin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3224 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20090402/5b57334b/attachment.bin>