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]/
[mat-wg] [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
- Previous message (by thread): [mat-wg] [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
- Next message (by thread): [mat-wg] [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gilles Massen
gilles.massen at restena.lu
Tue Dec 17 13:28:21 CET 2013
Hi, > I'd support changing the default to "public", but I can't see a compelling > reason why you would want to make *everything* public. > > What if I'm measuring something, where I know some bits of my network are > broken but need to figure out the overall damage, that I don't want the > competition and media to know (if they figure it out themselves, fine, but > not handing it on a silver platter). 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. best, Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473
- Previous message (by thread): [mat-wg] [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
- Next message (by thread): [mat-wg] [atlas] Proposing more public RIPE Atlas data and clarifying the current situation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ mat-wg Archives ]