<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>Just to offer a little more information:</div>
<div><br>
</div>
<div>When organizations sign up for RPKI, they have the option to leave some of their resources out of the certification even if those resources are covered by an (L)RSA. For ROA scripting purposes, there is no easy way to determine if a resource is covered
via our RESTful services. The only programmatic way to make that determination is to consult the RPKI itself by looking at the RFC 3779 extensions of the certificates in the repository.</div>
<div><br>
</div>
<div>However, both RPKI certification and (L)RSA coverage are viewable in ARIN Online.</div>
<div><br>
</div>
<div>Andy Newton,</div>
<div>Chief Engineer, ARIN</div>
<br>
<div>
<div>On Nov 6, 2014, at 11:34 AM, Tony Tauber <<a href="mailto:ttauber@1-4-5.net">ttauber@1-4-5.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Hi John,<br>
<br>
</div>
Is there a way to know which blocks that were legacy assignments are now covered by (L)RSA?<br>
</div>
I'm assuming that if they have an (L)RSA, they may be candidates for associated ROAs.<br>
<br>
</div>
Thanks,<br>
Tony<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Nov 6, 2014 at 6:22 AM, 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">
<span class="">On Nov 6, 2014, at 11:06 AM, Aaron Hughes <<a href="mailto:aaronh@tcp0.com">aaronh@tcp0.com</a>> wrote:<br>
><br>
> ARIN Tech Team,<br>
><br>
> In scripting some ROA related stuff the question came up, how does one check to see if block is legacy. Is there a flag in restwhois to identify this?<br>
<br>
</span>Aaron -<br>
<br>
An address block is legacy in origin if issued prior to ARIN's inception<br>
on December 22, 1997. Legacy address blocks may subsequently be covered<br>
by an RSA or LRSA agreement, so scripting specifically on being issued<br>
prior to ARIN's inception may to be fruitful.<br>
<br>
FYI,<br>
/John<br>
<br>
John Curran<br>
President and CEO<br>
ARIN<br>
<br>
<br>
_______________________________________________<br>
arin-tech-discuss mailing list<br>
<a href="mailto:arin-tech-discuss@arin.net">arin-tech-discuss@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-tech-discuss" target="_blank">http://lists.arin.net/mailman/listinfo/arin-tech-discuss</a><br>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
arin-tech-discuss mailing list<br>
<a href="mailto:arin-tech-discuss@arin.net">arin-tech-discuss@arin.net</a><br>
http://lists.arin.net/mailman/listinfo/arin-tech-discuss<br>
</blockquote>
</div>
<br>
</body>
</html>