[atlas] Proposing more public RIPE Atlas data and clarifying the current situation

On 17 Dec 2013, at 12:23, Vesna Manojlovic <BECHA at ripe.net> wrote:

> Dear colleagues,
> 
> Sharing information about Internet performance is at the heart of collaborative efforts such as RIPE Atlas.
> 
> Most of the RIPE Atlas probes and RIPE Atlas measurements are already public, and we'd now like to suggest
> opening up the publication of RIPE Atlas data further. We also want to clarify exactly what is and isn’t
> public in the current system. We describe this in more detail in this RIPE Labs article, where we also ask
> for community feedback about our suggested plan to move forward:
> https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-public [...]
> 
> We look forward to your feedback and comments on the MAT Working Group Mailing List.

Hello,

Thanks for the initiative. I support this.

Additionally, would it be possible to open the built-in measurements of public probes? (via REST API)

Suppose, I am interested in analysing the latency to k.root-servers.net from probes X (public) and Y (public) 
specifically. I have 3 options:

a) Search a UDM that is running this measurement on probe X and Y, and download that JSON data.
b) Run my own UDM using probe X and Y.
c) Fetch the RIPE’s in-built ping4 and ping6 measurements to k.root-servers.net for X and Y.

a) is tedious. b) is what I would do now, however it not only consumes my credit, but also puts measurement 
load on X and Y, even though X and Y are already running this through RIPE’s in-built measurement. In addition,
the timeline of your in-built measurement will be much richer than what I can achieve through a UDM.

It would be great if I could make a REST call to fetch the richer dataset in c)

Best, Vaibhav

-----------------------------------------------------
Vaibhav Bajpai

Research I, Room 86
Computer Networks and Distributed Systems  (CNDS) Lab
School of Engineering and Sciences
Jacobs University Bremen, Germany

www.vaibhavbajpai.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/ripe-atlas/attachments/20131217/1d0f42fc/attachment.sig>