- mat-wg - mailman.ripe.net

RIPE Atlas Software Probes
by Philip Homburg 13 Feb '20

13 Feb '20

Dear colleagues, We are glad to announce that, after several months of development and testing, we are now accepting applications for RIPE Atlas software probes. With several different installation options to choose from, software probes provide future hosts a whole new way to get involved with RIPE Atlas. For more details, see our new article on RIPE Labs: https://labs.ripe.net/Members/alun_davies/ripe-atlas-software-probes Kind regards, Philip

5 4

New on RIPE Labs: Evaluating the Performance of NRENs in Deploying IoT in Africa
by Mirjam Kuehne 05 Feb '20

05 Feb '20

Dear colleagues, In this interesting study the authors (Marco Zennaro, Cristel Pelsser, Pietro Manzoni and Franck Albinet) used RIPE Atlas to measure delay and packet loss from African NRENs to The Things Network. Please find the results and some ideas for future work on RIPE Labs: https://labs.ripe.net/Members/marco_zennaro/evaluating-the-performance-of-n… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: Modelling BBR’s Interactions with Loss-based Congestion Control
by Mirjam Kuehne 03 Feb '20

03 Feb '20

Dear colleagues, BBR has rapidly become a major player in Internet congestion control. BBR’s fairness or friendliness to other connections has recently come under scrutiny as measurements from multiple research groups have shown undesirable outcomes when BBR competes with traditional congestion control algorithms (CCAs). In this research Ranysha Ware, PhD student at Carnegie Mellon University, developed a model capturing BBR’s behaviour in competition with loss-based CCAs: https://labs.ripe.net/Members/ranysha_ware/modelling-bbr2019s-interactions-… Kind regards, Mirjam Kühne RIPE NCC

1 0

Looking for topology validation
by Kévin Vermeulen 23 Jan '20

23 Jan '20

Hi mat-wg, Our teams at Sorbonne Université and Naval Postgraduate School have developed a new Internet topology mapping tool, Diamond-Miner. Diamond-Miner[3] combines Paris Traceroute Multipath Detection Algorithm[1] and high probing rate Yarrp[2] techniques to trace the load balanced paths at Internet Scale. We are seeking now some validation of our inferences from operators, in particular the traceroutes links that we have found. We have developed a small website for operators to provide validation: http://heartbeat.planet-lab.eu:8000 You can either publicly submit the validation on the website or send us an email to kevin.vermeulen(a)sorbonne-universite.fr . You will find all the details on the website, do not hesitate to ask if you have further questions. Thanks in advance, Kevin [1]: https://arxiv.org/pdf/1809.10070 [2]: http://rbeverly.net/research/papers/yarrp-imc16.pdf [3]: https://www.usenix.org/conference/nsdi20/accepted-papers

1 0

New on RIPE Labs: The Debogonisation of 2a10::/12
by Mirjam Kuehne 17 Jan '20

17 Jan '20

Dear colleagues, Following the announcement of our plans to debogonise 2a10::/12, we have now shared the results of the tests we've been carrying out to check the usability of address space in this block. Read all about it on RIPE Labs: https://labs.ripe.net/Members/emileaben/the-debogonisation-of-2a10-12 Kind regards, Mirjam Kühne RIPE NCC

1 0

De-bogonising 2a10::/12
by Emile Aben 16 Jan '20

16 Jan '20

Dear colleagues, We have now started de-bogonising 2a10::/12! As part of this, we are announcing a couple of prefixes out of 2a10::/12 from AS12654 (RIPE's Routing Information Service, RIS). Pingable targets have been configured in these prefixes, and we invite network operators to test for themselves whether this address space is reachable. The simplest way to do this would be to perform a ping6 to 2a10:4::1 . Using RIPE Atlas and RIS, we will also be carrying out our own tests in order to investigate connectivity and filtering for this address space. We plan to share our results with the RIPE community via RIPE Labs within the next few days. For those who want to do other testing, beyond the basic test described above, we have a total of 8 targets available for this, with 2 different prefix lengths and all variations of having ROUTE objects in the RIPE DB and/or ROAs. 2a10:3:4::1 /48 ROUTE object + ROA 2a10:3:5::1 /48 no ROUTE object + ROA 2a10:3:6::1 /48 ROUTE object + no ROA 2a10:3:7::1 /48 no ROUTE object + no ROA 2a10:4::1 /32 ROUTE object + ROA 2a10:5::1 /32 no ROUTE object + ROA 2a10:6::1 /32 ROUTE object + no ROA 2a10:7::1 /32 no ROUTE object + no ROA Kind regards, Emile Aben RIPE NCC

1 0

New on RIPE Labs: Do we Need to Rethink Network Monitoring?
by Mirjam Kuehne 17 Dec '19

17 Dec '19

Dear colleagues, Kemal Sanjta advocates a more holistic approach when it comes to network monitoring. Find out more in his article on RIPE Labs: https://labs.ripe.net/Members/kemal_sanjta/do-we-need-to-rethink-network-mo… Kind regards, Mirjam Kühne RIPE NCC

1 0

New RIPE Labs: Impressions from the Internet Measurement Conference 2019
by Mirjam Kuehne 04 Nov '19

04 Nov '19

Dear colleagues, This year's Internet Measurement Conference (IMC) was held in Amsterdam from 21-23 October. In this article we highlight some of the presented work that we think is interesting and that the RIPE community might find useful: https://labs.ripe.net/Members/emileaben/impressions-from-the-internet-measu… Kind regards, Mirjam Kühne RIPE NCC

1 0

MAT WG as an advisory body for RIPE NCC tools
by Brian Trammell (RIPE) 22 Oct '19

22 Oct '19

Greetings, all, We ran out of time today to discuss the proposal I alluded to at the beginning of the meeting, so I'm taking it to the mailing list: I would propose that we make the role of MAT WG in providing information and advice to the RIPE NCC's tools teams more explicit. In this proposal, mat-wg(a)ripe.net mailing would be considered a primary channel for proposals for features for RIPE Atlas. These proposals would then be discussed on the list and/or during MAT WG meetings, and once the discussion on converges, the outcome passed to the RIPE NCC tools team as advice. This would turn the current process, where the tools team disseminates updates about current work and future plans, into a two way street. While I propose that this should be more explicit, I am not proposing that this be made more formal: this would not use the PDP, and would not be in any way binding on the NCC. What do you, the WG, think? Thanks, cheers, Brian (as MAT-WG co-chair)

6 5

New on RIPE Labs: The New RIPEstat In Other Words
by Mirjam Kuehne 15 Oct '19

15 Oct '19

Dear colleagues, We started a complete redesign of the RIPEstat user interface. With the prototype UI having received a lot of positive feedback, we’re still busy adding new features, one of which will allow users to switch between languages when using RIPEstat. As this is a first for us, here’s more detail on what we have in mind: https://labs.ripe.net/Members/stephen_suess_1/the-new-ripestat-in-other-wor… We will tell you more about this during the RIPE 79 MAT WG session on Thursday and look forward to your feedback. Kind regards, Mirjam Kühne RIPE NCC

1 0