<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Apr 4, 2016, at 8:17 PM, Jon Lewis <<a href="mailto:jlewis@lewis.org" class="">jlewis@lewis.org</a>> wrote:<br class="">
<div>
<div class="">
<div class="">
<blockquote type="cite" class=""><br class="">
</blockquote>
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">If ARIN has a large pool of ASNs which it believes ARIN is responsible for, and are not being paid for, i.e. ASN squatters, then WTH are these ASN's not published in whois as Unused/Reserved/Reclaimed/whatever term/language ARIN comes up with
that clearly identifies the ASN as not belonging to whoever might be trying to use it? That just might help deter transit providers from allowing customers to use them. An automated periodic email to peeringdb/whois contacts for the immediate upstream ASNs
would at least notify/remind networks that they're providing transit to an org squatting on an ASN.</div>
</div>
</blockquote>
<br class="">
</div>
<div>Jon - </div>
<div> </div>
<div> ARIN could undertake automation to monitor the appearance of ASN’s </div>
<div> (or address blocks, for that matter) in the global routing tables and then</div>
<div> send (unrequested) email to the contacts for the appropriate network.</div>
<div><br class="">
</div>
<div> (I will note that much of this information is already being monitored, </div>
<div> and reported on, at <a href="http://www.cidr-report.org" class="">http://www.cidr-report.org</a> , but those ISPs who </div>
<div> really care about such and would act on the results are precisely the </div>
<div> ones who least likely to be the problem…)</div>
<div><br class="">
</div>
<div> If you wish us to proceed as suggested, please writeup a brief suggestion</div>
<div> at <<a href="https://www.arin.net/participate/acsp/acsp.html" class="">https://www.arin.net/participate/acsp/acsp.html</a>> and we will review it</div>
<div> and post for discussion on aria-consult (as it is quite distinct from the current </div>
<div> thread here on PPML regarding whether any policy change for 2-Byte ASN’s </div>
<div> is desirable.)</div>
<div><br class="">
</div>
<div>Thanks!</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br class="">
</div>
</body>
</html>