July 2015 - mat-wg - mailman.ripe.net

New on RIPE Labs: Enabling Data Compression in RIPE Atlas
by Vesna Manojlovic 01 Sep '15

01 Sep '15

Dear colleagues, We’d like to enable gzip compression on all of RIPE Atlas' measurement API calls — but thanks to the BREACH vulnerability, doing so could mean that some enterprising individual with an obscene amount of time on their hands might be able read the contents of the responses. This means measurement results as well as metadata for measurements — including the small number of measurements not marked as “public”. We believe the drawbacks are negligible, but we’re looking for community support. Find out more in this RIPE Labs article: https://labs.ripe.net/Members/daniel_quinn_39/enabling-data-compression-in-… Regards, Vesna Manojlovic

2 1

Network Neutrality - Latest on Regulation
by Gordon Lennox 14 Jul '15

14 Jul '15

http://www.consilium.europa.eu/en/press/press-releases/2015/07/08-roaming-c… There is a link to the regulation as PDF. "How will this become a law? The agreed text will undergo technical finalisation. It then needs to be formally approved by the Council and the Parliament. The Council is expected to formally adopt it in the autumn 2015. This does not need to take place in the Telecom Council: any Council configuration has the power to adopt the legal act. The regulation will enter into force 20 days after its publication in the EU Official Journal.”

2 3

New on RIPE Labs: Visualisation of a New Node in LACTLD Anycast Service
by Mirjam Kuehne 10 Jul '15

10 Jul '15

Dear colleagues, Please read on RIPE Labs how RIPE Atlas was used to measure improvements to the LACTLD infrastructure (by Hugo Salgado): https://labs.ripe.net/Members/hugo_salgado/visualisation-of-a-new-node-in-l… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing?
by Mirjam Kuehne 02 Jul '15

02 Jul '15

Dear colleagues, In this article we compare RIPE Atlas deployment against user population estimates provided by APNIC to see what eyeball networks are missing out on RIPE Atlas probes: https://labs.ripe.net/Members/emileaben/improving-ripe-atlas-coverage-what-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Probe and measurement archives vs. the APIs
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear All, We've observed recently that some users are using scripts to "crawl" through all the metadata provided by the probe and measurement APIs. This means that some people out there download basically the entire probe and/or measurement meta data set the system provides. As you can imagine, this is highly inefficient and keeps our servers busy. We believe that there could be better solutions. We have been providing the downloadable archive for probe metadata for some time now, and recently we've added the measurement metadata too. You can now reach these at http://ftp.ripe.net/ripe/atlas/ This way one can even get complete sets of metadata as far back as January 2015 for measurement specifications and March 2014 for probe data. Given the existence of these archives, we will apply a sane limit on how much metadata can be reached via the APIs. In practice this means that the API will not allow fetching results beyond, say, 10.000 (i.e. 500 pages of 20) entries. This is after the application of filters, so for example with no filters at all you could still access metadata of the 10k newest measurements, while if you filter for DNS measurements only, you could get the 10k newest of those, and so on. We believe this keeps the metadata API useful for the majority of the users, while the existence of the archive serves the remaining cases. Our plan is to make this change around the end of July. Regards, Robert Kisteleki

1 0