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/ripe-atlas@ripe.net/
[atlas] Proposing more public RIPE Atlas data and clarifying the current situation
- Previous message (by thread): [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
- Next message (by thread): [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Tue Dec 17 13:52:54 CET 2013
On Tue, Dec 17, 2013 at 01:28:21PM +0100, Gilles Massen wrote: > I agree very much with this thinking. Personally I could live with > non-public data becoming public a few days after the measurement, but if > everything is public in realtime Atlas would lose a lot of its > attractiveness as debugging tool. there are two aspects: 1) disclosure of the meaasurements and results I agree with Gilles and Gert that there is a difference between the results of measurements and the fact that something is measured right now and here. A publication delay seems the minimum to me, but for one off measurements in particular there might be reasons to not ever disclose them. 2) privacy of the probe host Maybe we need to work on "privacy considerations for probe hosts"; The ability to track the last 25 "connections" allows tracking the probe's IP address (maybe that's possible even easier?) and I'm not sure every host is aware of that. Opt-In is probably the very least we can do. -Peter
- Previous message (by thread): [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
- Next message (by thread): [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]