[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 ]
Lars-Johan Liman
liman at netnod.se
Wed Dec 18 14:15:17 CET 2013
gilles.massen at restena.lu: > 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. Agreed. ... and I would add that I don't want DDoS culprits to be able to use Atlas as a real-time assessment tool of the effectiveness of their attacks. (Maybe they can already, but let's not help them more.) Publishing delayed data is better. Cheers, /Liman #---------------------------------------------------------------------- # Lars-Johan Liman, M.Sc. ! E-mail: liman at netnod.se # Senior Systems Specialist ! Tel: +46 8 - 562 860 12 # Netnod Internet Exchange, Stockholm ! http://www.netnod.se/ #----------------------------------------------------------------------
- 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 ]