- mat-wg - mailman.ripe.net

RIPE Atlas "Commercial use" policy
by Robert Kisteleki 17 Aug '16

17 Aug '16

Dear colleagues, A few different organisations have approached us about using RIPE Atlas data for commercial products, services, reports, etc. We’ve now published conditions for the commercial use of RIPE Atlas data: https://atlas.ripe.net/get-involved/commercial-use/ Please read these conditions carefully if you plan on using RIPE Atlas data for any commercial purpose, and don’t hesitate to contact us if you have any questions. Regards, Robert Kisteleki RIPE NCC

1 0

New on RIPE Labs: Detecting IXPs in Traceroute Paths Using traIXroute
by Suzanne Taylor Muzzin 03 Aug '16

03 Aug '16

Dear colleagues, Is observing an IP address from an IXP prefix sufficient evidence to conclude that a traceroute path crossed an IXP? In this latest RIPE Labs article, George Nomikos and Xenofontas Dimitropoulos explain why they don't think so - and then show how using the traIXroute tool can help: https://labs.ripe.net/Members/george_nomikos/detecting-ixps-in-traceroute-p… Kind regards, Suzanne Taylor Muzzin RIPE NCC

1 0

New on RIPE Labs: Internet Access Disruption In Turkey - July 2016
by Mirjam Kuehne 19 Jul '16

19 Jul '16

Dear colleagues, With the attempted coup in Turkey, reports went out about social media being throttled and/or blocked. We analysed data about this that we collected with RIPE Atlas and the Open Observatory of Network Interference (OONI). Please find the results on RIPE Labs: https://labs.ripe.net/Members/emileaben/internet-access-disruption-in-turke… Kind regards, Mirjam Kuehne RIPE NCC

1 0

More than 200 RIPE Atlas anchors now online
by Michela Galante 29 Jun '16

29 Jun '16

Dear colleagues, Thanks to thirteen new RIPE Atlas anchors being activated over the last two months, we have now reached an important milestone: more than 200 anchors online! Learn more about what anchor measurements can do for you: https://atlas.ripe.net/anchors/about/ We have also started decommissioning anchors with older hardware and working with hosts to replace them with updated hardware. We'd like to thank Nick Hilliard for helping us test our decommissioning procedure and becoming the first anchor host to update to the new hardware for as2128, hosted by INEX in Dublin, Ireland. Since our last announcement, the following anchors have become active: - cz-brq-as24971, hosted by Master Internet s.ro.o in Brno, Czech Republic - nl-ams-as1200, hosted by AMS-IX B.V. in Amsterdam, Netherlands - ca-wtl-as4508, hosted by NeuStyle Corporation in Waterloo, Canada - ie-ork-as2128, second anchor for INEX, hosted in Cork, Ireland - lv-rix-as52048, hosted by DATACLUB S.A. in Riga, Latvia - dk-taa-as51468, hosted by One.com in Tastrup, Denmark - ie-dub-as2128, hosted by INEX in Dublin, Ireland (replaces older hardware) - us-rno-as3851, hosted by University of Nevada in Reno, United States - nl-dft-as31019, hosted by Meanie in Delft, Netherlands - ru-mot-as13238, hosted by Yandex LLC in Mytishchi, Russia - de-bwe-as680, hosted by TU Braunschweig, Gauss-IT-Zentrum in Braunschweig, Germany - nl-ams-as35733, hosted by EURid VZW in Amsterdam, Netherlands - us-abn-as51468, hosted by One.com in Ashburn, United States - kh-pnh-as7712, hosted by Sabay Digital Coperation (sponsored by APNIC) in Phnom Penh, Cambodia The map of all anchor locations is available at: https://atlas.ripe.net/anchors/map/ You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ And here are all of the anchor hosts: https://atlas.ripe.net/get-involved/community/#!tab-anchor-sponsors We are still accepting new applications from organisations interested in hosting a RIPE Atlas anchor, and are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa in order to add more geographical diversity to the measurement data. To apply for your own RIPE Atlas anchor, please visit: https://atlas.ripe.net/get-involved/become-an-anchor-host/ It’s also possible to sponsor an anchor for organisations that want to host one but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at atlas(a)ripe.net Regards, Michela Galante Measurements Community Building RIPE NCC

1 0

Results from RIPE Atlas Interface Hackathon
by Vesna Manojlovic 17 Jun '16

17 Jun '16

Dear colleagues, The third RIPE Atlas hackathon took place in Copenhagen the weekend before RIPE 72. In this article, we share the details about the hackathon: https://labs.ripe.net/Members/becha/ripe-atlas-interface-hackathon-results?… Direct link to all the code contributed by the community: https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib/blob/m… Regards, Vesna

1 0

Keep All RIPE Atlas Data Accessible in the Standard Way
by Daniel Karrenberg 25 May '16

25 May '16

At today's meeting the RIPE NCC raised the question whether RIPE Atlas Data could be "archived" and longer be accessible by the 'standard API'. I consider this a bad idea because we will loose the ability to access the data with current and future tools, both RIPE NCC tools and those developed by the community using the Atlas API. Long baselines are useful not only for scientific research, but also for developing robust tools and applied research. We have not heard why the RIPE NC has raised the question. So I propose that we ask the RIPE NCC to prepare a detailed proposal including the motivation for proposing this. Until that happens we should keep all RIPE Atlas Data accessible as usual and not spend any time discussing this. Daniel

1 0

Proposal: Discontinue Private Measurements in RIPE Atlas
by Daniel Karrenberg 25 May '16

25 May '16

Keeping measurements and results private in RIPE Atlas comes at a significant cost. Latest case in point is the streaming interface where the developers tell me a significant part of the effort was filtering out results from private measurements. This surprises me because iirc we already decided that results from private measurements were indeed public and only the measurement specifications and meta data would be private. Be that as it may I propose that we ask the RIPE NCC to make a plan to remove private measurements from RIPE Atlas altogether and present it well before the next meeting. We can then have a discussion, build consensus and maybe arrive at consensus about this at the next RIPE meeting. Daniel

1 0

New on RIPE Labs: New RIPE Atlas APIs
by Mirjam Kuehne 23 May '16

23 May '16

Dear colleagues, We've updated the RIPE Atlas APIs - and there's a comprehensive new manual to explain how to use them. As a result, the current (version 1) APIs are still available for now, but will be deprecated by the end of the year. Please find more information on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/new-ripe-atlas-apis?pk_… Kind regards, Mirjam Kuehne RIPE NCC

1 0

v4 versus v6 -- who connects faster?
by Bajpai, Vaibhav 23 May '16

23 May '16

Hello, -- sorry for cross-posting Here [a] is a toy v6 service I came up with during the RIPE Atlas hackathon over this weekend. Thought I share this along: [a] http://goo.gl/hbzbwD You enter a dual-stacked website (ALEXA top 10K) and it shows you the difference in TCP connect times over v4 and v6 as seen by all dual-stacked RIPE Atlas probes (~1.3K probes). You can also filter the visualisation from a specific origin-AS. This additional filter can be useful to view performance towards a website from a specific origin-AS (say DTAG). Disclaimer: This is an outcome of a 1.5d long hackathon project. As such, the codebase is possibly inundated with bugs. Please don’t see it as a production service :-) Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================

1 0

New on RIPE Labs: There Is Gold in This Stream - Sifting Through Used RIPE Atlas Traceroute Results
by Mirjam Kuehne 20 May '16

20 May '16

Dear colleagues, Please find a new article on RIPE Labs demonstrating the value of the results collected by RIPE Atlas independent of the original purpose for collecting them. Using all traceroute results from a particular day as an example, we first show that near real-time analysis of the result stream is feasible. Then we show that this has great potential for studying the packet layer of the Internet in general and for providing tools to network operators in particular. All this suggests a large and diverse potential for further work. https://labs.ripe.net/Members/dfk/there-is-gold-in-this-stream?pk_campaign=… Kind regards, Mirjam Kuehne RIPE NCC

1 0