That makes perfect sense.

Thank you for taking the time to explain.



On 10/4/2017 12:02 PM, Jon Worley wrote:
Hello Andrew,

The advantage of the default key pair is that it persists over the monthly 
backwashes. You don’t need to re-create the certificate every time; the default 
key pair will always work.

You *can* use your own key pair to generate a cert, but it’ll be overwritten 
with the default key pair during the monthly backwash, so we’d have to delete 
it and then you’d have to re-create it every month to keep using it.

Basically, if you’re testing for more than a month, the default key pair makes 
life easier. You can use your own, but that means monthly deletion and 
re-creation.

Hope that clarifies.

-Jon
Jon Worley
Technical Services Manager
ARIN Registration Services
https://www.arin.net/
[email protected]
703.227.0660
On 10/4/17, 9:13 AM, "Andrew Gallo" <[email protected]> wrote:

     Hello, Jon:
Just created a ROA and the ticket resolved in less than a minute.
     Thanks for taking care of this.
I do have one more RPKI/OTE question if I can tag on to this email..... I've had access to the OT&E for several months now. When I create ROAs,
     I use the key pair posted on the webpage at:
     https://www.arin.net/resources/ote.html#rpki
I did not provide a key-pair when requesting OT&E RPKI access (it wasn't
     required).
A peer of mine just requested RPKI access in the OT&E (since the last
     refresh)- he provided a key-pair in the request ticket inside the OT&E
     environment.  When he requests ROAs, he uses his key-pair.
Is it fair to say, for people using the new access method, they'll use
     their own key-pair, and not the one on the site listed above?
Thank you. On 10/3/2017 2:29 PM, Jon Worley wrote:
     > Hello Andrew,
     >
     > The problem should be resolved. Let us know if you continue to see 
problems.
     >
     > Best regards,
     >
     > Jon Worley
     > Technical Services Manager
     > ARIN Registration Services
     > https://www.arin.net/
     > [email protected]
     > 703.227.0660
     >
     > From: arin-tech-discuss <[email protected]> on behalf of 
Andrew Gallo <[email protected]>
     > Date: Tuesday, October 3, 2017 at 8:44 AM
     > To: "[email protected]" <[email protected]>
     > Subject: Re: [arin-tech-discuss] October OT&E Refresh - Complete
     >
     >
     > I'm wondering is something is up with ROA creation.  I have RPKI access in the 
production environment, so I can create ROAs them in the OT&E.  I've submitted three 
requests to create ROAs in the OT&E and the tickets are still pending (one for several 
hours).  In the past, the ROAs were created almost instantly (<1min).
     >
     >
     >
     > I can provide some pending ticket numbers in the OT&E if that helps.
     >
     >
     >
     > Thank you.
     >
     >
     >
     > On 10/2/2017 10:17 PM, Michael Crossin wrote:
     >
     > List,
     >
     >
     >
     > Apologies for the delayed notification.  The refresh of the Operational 
Testing and Evaluation environment was completed within the outlined maintenance 
window.
     >
     >
     >
     > All systems within this environment should be accessible to you now if 
you have requested access to it. If you have requested access previously, there is 
no need to re-request.
     >
     >
     >
     > If you experience any issues in using the OT&E environment or notice 
anything erroneous, please reach out to us.
     >
     >
     >
     > Thanks,
     >
     >
     >
     > Mike Crossin
     >
     > Database Systems Administrator
     >
     > American Registry for Internet Numbers
     >
     >
     >
     >
     >
     >
     >
     >
     > _______________________________________________
     >
     > 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

Reply via email to