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/[email protected]/
[ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Fri Jun 25 13:52:13 CEST 2021
felipe, > Here is what we’re hearing (in no particular order): > > - Requests for more clarity about the "why" > - Risk that relevant technical skills may be lost internally > - Concerns related to security (e.g. cloud providers may present more of a target for state-sponsored actors) > - Some privacy aspects might be overlooked (e.g. while services like the RIPE Database are public, metadata or log files could be a concern) > - Compliance: make sure the RIPE NCC doesn't violate any regulations > - The discussion should focus on requirements rather than implementation... on the other hand, you're going to get solutioneering whether you like it or not - accept it! let me try again, more simply disclose and discuss early in your process. the community is talkative but we are your friends and peers. randy
- Previous message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
- Next message (by thread): [ncc-services-wg] New on RIPE Labs: RIPE NCC and the Cloud - Let’s Start Again
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]