This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Danny McPherson
danny at tcb.net
Wed May 12 19:53:39 CEST 2021
Indeed. We're also very concerned about the security && scalability of the RIRs IT and security operations and broader programs given the clear operational implications of the RPKI _that we're all inherently captive to, and which are now part of all of our operational robustness / attack surfaces. I'm anxious to see the RIRs step up here, and I suspect it's not going to be easy, or cheap. -danny On 2021-05-12 13:39, Randy Bush wrote: > hi filipe, > > i suspect that gert and others understand the business relationships > and > day to day control issues when contracting out to cloud providers. > this > contributes strongly to why ops folk in the community are concerned. > > randy > > --- > randy at psg.com > `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` > signatures are back, thanks to dmarc header butchery
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]