<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>As noted in the document, a similar option would be </div>
<div id="AppleMailSignature">to restore the records to original state, and then lock </div>
<div id="AppleMailSignature">those which have not been updated recently (until the </div>
<div id="AppleMailSignature">contacts come in and refresh their information.)<br>
<br>
Your proposal would also do the job. It is also possible </div>
<div id="AppleMailSignature">that the current state is "a feature not a bug" and thus</div>
<div id="AppleMailSignature">should stay as-is. What I do know is that additional</div>
<div id="AppleMailSignature">insight (beyond just the staff) is quite desirable...</div>
<div id="AppleMailSignature">(luckily, the Board agreed that I can use this cool</div>
<div id="AppleMailSignature">Services WG to tap for their wisdom...)</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">The goal is a recommendation to bring to the ARIN </div>
<div id="AppleMailSignature">community; it can be one in the document or something</div>
<div id="AppleMailSignature">created by this group, whatever you prefer.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">:-)</div>
<div id="AppleMailSignature">/John</div>
<div><br>
On Jun 14, 2016, at 5:31 PM, Matt Peterson <<a href="mailto:matt@peterson.org">matt@peterson.org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">Maybe I'm missing something here, why not have whois present a flag if the POC record has been validated recently or not. In the case of this, clearly that field would be null or a very old date.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jun 14, 2016 at 4:37 PM, John Curran <span dir="ltr">
<<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">On Jun 14, 2016, at 3:40 PM, John Curran <<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</a>> wrote:<br>
<div>
<blockquote type="cite">...<br>
<div>
<div style="word-wrap:break-word">
<div>Jim Smith gets an /24 for his networking company “Sprockets” in 1994, </div>
<div>so that he can connect to the Internet. He gets /24) and connects to</div>
<div>the Internet via one the early commercial ISPs. </div>
<div><br>
</div>
<div>The netblock reads as follows:</div>
<div><br>
</div>
<div><span style="white-space:pre-wrap"></span>Sprockets</div>
<div><span style="white-space:pre-wrap"></span>4131 El Camino Real, Palo Alta CA</div>
<div><span style="white-space:pre-wrap"></span>X.Y.Z/24</div>
<div><span style="white-space:pre-wrap"></span>Jim Smith</div>
<div><span style="white-space:pre-wrap"></span><a href="mailto:jim@well.com" target="_blank">jim@well.com</a></div>
<div><br>
</div>
<div>Apparently, Jim left Sprockets sometime in the late 90’s… </div>
<div><br>
</div>
Twenty years later, Jim has called and is very upset with ARIN for having
<div>“munged it" all up - ...</div>
</div>
</div>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<div></div>
<blockquote type="cite">
<div>Jim’s not a happy camper, and wants to know why ARIN disassociated him</div>
<div>with his address block randomly sometime after 2010. Jim says that he’s </div>
<div>been been using the address block for his house since leaving Sprockets </div>
<div>(no public IP, but he just uses NAT and connects via his public cable modem </div>
<div>IP address.) ...Because we no longer allow him</div>
<div>
<div>as a abuse contact to update the DNS servers, he can’t even use “his” IP</div>
<div>block now that he’s getting a nice new Internet connection.</div>
</div>
</blockquote>
<div><br>
</div>
</div>
<div>Now on to the more dangerous variation of this story - it starts the same, sounds </div>
<div>the same to ARIN, and it is only in a few (unknown to us) details that it differs - </div>
<div><br>
</div>
<div> - Spockets was sold to Widgets, Inc sometime in late ‘90s </div>
<div> - Widgets renumbered the servers when they moved them to Widgets </div>
<div> HQ and promptly forgot about the X.Y.Z/24 IP address block...</div>
<div><br>
</div>
<div>It’s highly likely (absent a transaction to the contrary) that the rights to the </div>
<div>X.Y.Z/24 IP address block are held by Widgets Inc.</div>
<div><br>
</div>
<div>This hasn’t prevented technical contacts for long-lost companies from trying </div>
<div>to hijack unused address blocks and monetize them (i.e. if ARIN would just </div>
<div>play along…) </div>
<div><br>
</div>
<div>The change of tech contact to abuse significantly reduces the risk of hijack,</div>
<div>although it could be argued that it excessively impacts legacy address holders</div>
<div>(those who have not been updating their IP address records over time.) </div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>/John</div>
</font></span></div>
<br>
_______________________________________________<br>
Services-wg mailing list<br>
<a href="mailto:Services-wg@arin.net">Services-wg@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/services-wg" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/services-wg</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</body>
</html>