Internet Routing Registry Cleanup for Peering- October 22

[Karl Reuss <>]

    I think there's another level of complexity here for some people.  
    In order to create a ROA, unless your organization has signed the
    latest ARIN RSA/LRSA you will need to click through an agreement
    that contains jurisdiction and indemnification clauses that lawyers
    don't like.  This is mentioned in the RPKI documentation, step 5
    under 'Submitting a Certificate Request':
https://www.arin.net/resources/manage/rpki/hosted/#submitting-a-certificate-request
    
>       
>         Read and agree to the RPKI Terms of
>           Service. (Note: Not required for resources covered
>           by an RSA version 12 or greater.)
>       
>     
    
    If your org doesn't want you to click agree on legal stuff and your
    agreement predates Aug 16, 2016 then you're still stuck.
    
    -Karl

On 10/23/20 5:26 PM, Linda Roos wrote:

      Hi,

See below for a message from Steve Wallace in follow-up to the discussion on the 10/22/20 TechEXtra: IRR Cleanup for Peering.

It’s my understanding that you can determine if a legacy resource is covered by ARIN’s L/RSA via whois. 

The registration date is before Dec 22nd 1997 and the OrgID ends with -Z, then the resource is covered by an L/RSA, and should be able accept a ROA.

—

Linda Roos
Sr Director, State and Regional Networks
Internet2
812-558-0615