Hi Ben, On 04/11/2024 18:56, Ben Cartwright-Cox wrote:
I may be missing something drastic, but as far as my data exposure to RIPE NCC I have boils to:
A) What I have in the database (something that is almost entirely public)
Yes, the data that is published in the RIPE database is obviously public
B) Know Your Customer documentation that I submitted, though I'm unsure if RIPE even have copies of that anymore
Only the RIPE NCC can answer that :)
C) Mailing list conversations (again, mostly public conversations, other than in my case the working group co-chair duties I do)
Of course, also public
D) I guess I run a RIPE Atlas probe in various places, I suppose there is some argument I should not have something like that running in my home if I don't trust the infrastructure that controls that
Yes, a no brainer, as far as i'm concerned
I'm not really sure what else there is, as far as some of my other suppliers in business, the NCC holds relatively little data on my operations. (I will ignore the situation of what happens if a government agency forces something to be done, because I think that is not what we are arguing here, and also low risk)
I'm glad your life as an LIR is so simple, but many members share a lot more information with the RIPE NCC. Like information about mergers and aquisitions, payment details, resource transfers, information regarding sanctions, etc. There are a lot of potentially sensitive details being shared with the RIPE NCC. Don't get me wrong, i could be easily convinced that storing hundreds of terabytes (or petabytes?) of RIPE Atlas measurements in AWS storage is a good idea as long as the right safeguards are in place. But i do for example, have serious objections against storing potentially sensitive member data (through e-mail) in Google. Not in the least because the savings here are negligible, running your own mail service for ~200 staff isn't all that complicated, and doesn't require a lot of resources (been there, done that). And with todays virtualisation technologies really doesn't demand much rack space either. The reason i have brought up my concerns, is because i believe we, as members, should discuss these fundamental decisions that are being made by the RIPE NCC. And i feel that, so far, these decisions have been made by RIPE NCC executives, without sufficient consultation from the members. Timo Hilbrink Freedom Internet