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]/
[atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]
- Previous message (by thread): [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]
- Next message (by thread): [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Fri Dec 16 20:25:32 CET 2022
Hi, On Fri, Dec 16, 2022 at 08:07:14PM +0100, ripe.net at toppas.net wrote: > Sorry Gert, but i strongly disagree. > > > I might be troubleshooting something in our network where I have no interest in making the results public. > RIPE Atlas is primarily designed for INTERnet measurements, not Intranet. To see, how things look like from other networks. If you want to troubleshoot something inside your own network and need privacy, you can do it the classic way, by using your internal test-equipment or monitoring. I am an ISP. So I *must* see how things look like from the outside - but in case I've done stupid things to my own networks before, I might not want the world to see that. > > There's no "right to see all measurements" here > I highly appreciate RIPE NCCs efforts for maximum transparency and open-data, and i hope this will never change. This is what Atlas was intended to be (as far as i can tell). All my probes do public and open measurements "for everyone", and they are happy to do measurements for you. And I'm happy to bear the costs for that (an Atlas Anchor costs real money). > > if someone wants to see something, they are free to run their own measurements with their own credits. > In this point, i disagree as well. It shouldn't be necessary to run the same measurement multiple times. For what reason? It would be a waste of credits, time and ressources. Also, keep in mind that this redundant data has to be stored somewhere. You wouldn't run the same measurements that I want to do, if I have to do some troubleshooting. > If one has a problem with open-data philosophy, he shouldn't participate in this project. > _There's only one exception_ i could agree with: measurements can be private, if you only deploy your own probes/anchors for that measurement. But if you decide to use other peoples probes, the results should be public. This is a valid opinion for a network researcher, I guess. For those that actually run the show here, we might see things in a different light... (as I'm not the only one explaining the desire for private measurements). Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: </ripe/mail/archives/ripe-atlas/attachments/20221216/9b08a8d6/attachment.sig>
- Previous message (by thread): [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]
- Next message (by thread): [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]