Are they publicly viewable or only to the resource holder? Owen
> On Nov 6, 2014, at 10:43 AM, Andy Newton <[email protected]> wrote: > > Just to offer a little more information: > > 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. > > However, both RPKI certification and (L)RSA coverage are viewable in ARIN > Online. > > Andy Newton, > Chief Engineer, ARIN > > On Nov 6, 2014, at 11:34 AM, Tony Tauber <[email protected] > <mailto:[email protected]>> wrote: > >> Hi John, >> >> Is there a way to know which blocks that were legacy assignments are now >> covered by (L)RSA? >> I'm assuming that if they have an (L)RSA, they may be candidates for >> associated ROAs. >> >> Thanks, >> Tony >> >> On Thu, Nov 6, 2014 at 6:22 AM, John Curran <[email protected] >> <mailto:[email protected]>> wrote: >> On Nov 6, 2014, at 11:06 AM, Aaron Hughes <[email protected] >> <mailto:[email protected]>> wrote: >> > >> > ARIN Tech Team, >> > >> > 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? >> >> Aaron - >> >> An address block is legacy in origin if issued prior to ARIN's inception >> on December 22, 1997. Legacy address blocks may subsequently be covered >> by an RSA or LRSA agreement, so scripting specifically on being issued >> prior to ARIN's inception may to be fruitful. >> >> FYI, >> /John >> >> John Curran >> President and CEO >> ARIN >> >> >> _______________________________________________ >> arin-tech-discuss mailing list >> [email protected] <mailto:[email protected]> >> http://lists.arin.net/mailman/listinfo/arin-tech-discuss >> <http://lists.arin.net/mailman/listinfo/arin-tech-discuss> >> >> _______________________________________________ >> arin-tech-discuss mailing list >> [email protected] <mailto:[email protected]> >> http://lists.arin.net/mailman/listinfo/arin-tech-discuss > > _______________________________________________ > arin-tech-discuss mailing list > [email protected] > http://lists.arin.net/mailman/listinfo/arin-tech-discuss
_______________________________________________ arin-tech-discuss mailing list [email protected] http://lists.arin.net/mailman/listinfo/arin-tech-discuss
