- mat-wg - mailman.ripe.net

New on RIPE Labs: Using RIPE Atlas Measurement Results in Prometheus
by Mirjam Kuehne 09 Jun '17

09 Jun '17

Dear colleagues, In this new article on RIPE Labs Daniel Czerwonk describes how he is exporting metrics based on RIPE Atlas results to Prometheus in order to monitor and visualise trends in latency, packet loss and hop counts. https://labs.ripe.net/Members/daniel_czerwonk/using-ripe-atlas-measurement-… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: Analysis of RIPEstat Outage
by Mirjam Kuehne 08 Jun '17

08 Jun '17

Dear colleagues, Last Thursday, 1 June, RIPEstat suffered from the longest service outage in years. Although the root cause was, in hindsight, trivial, it took more than three hours to fully recover. As unfortunate as this outage was, the situation yielded vital take-aways that will hopefully help prevent future outages. Please find an analysis on RIPE Labs: https://labs.ripe.net/Members/cteusche/sand-in-the-gears Kind regards, Mirjam Kuhne RIPE NCC

1 0

color blindness and color meaning association
by Job Snijders 28 May '17

28 May '17

Hi all, TL;DR - red/green color palettes should be avoided in data visualiations, please pick something else! Yesterday I saw Christian Teuschel present on the "Jedi" tool at SINOG, and two things stood out: A) the data visualisations do not attempt to accomodate for people who are color blind, in fact, the worst colors possible were picked B) by using using common traffic light colors (green, orange, red) an implicit judgement is made on the meaning of the data (traffic crossing an internet exchange was seemingly favored over private peering) To point (A) - red–green color blindness which affect a substantial portion of the human population. In the US, about 7 percent of the male population (or about 10.5 million men) and 0.4 percent of the female population either cannot distinguish red from green, or see red and green differently from how others do (Howard Hughes Medical Institute, 2006). There are quite some pointers as to how to design color palettes which accomodate everyone. http://www.somersault1824.com/tips-for-designing-scientific-figures-for-col… http://blog.usabilla.com/how-to-design-for-color-blindness/ B) As I understand the "Jedi" tool, it shows matrixes of what traffic between atlas probes leaves the country, and what traffic remains within the country - offering insight into a reflection on a country's internal routing arrangements. I'm a big fan of keeping local traffic local, so the tool certainly has value. However, the tool displays traffic which passes over an IXP within the country as green, and traffic that says within the country but didn't cross an IXP as "orange". Since the majority of internet traffic flows over direct, private interconnections between ASNs, signifying that traffic as "orange", has the potential to be taken as a "wrong", rather then as an arbitrary datapoint. I suggest that the Jedi tool either uses the same color for ixp and non-ixp "within country" traffic (and perhaps a small icon is used to signify the additional data attribute that an IXP was observed in the traceroute), or that the jedi tool uses entirely arbitrary colors that have no inherent meaning like the traffic light colors do. Kind regards, Job

3 3

New on RIPE Labs: Introduction to the Quantum Internet
by Mirjam Kuehne 26 May '17

26 May '17

Dear colleagues, At RIPE 74, Stephanie Wehner, Associate Professor at the University of Technology in Delft, The Netherlands, presented about the status of the Quantum Internet and encouraged a lot of hallway chat about that topic. She now published a summary on RIPE Labs: https://labs.ripe.net/Members/becha/introduction-to-the-quantum-internet Please also note the invitation to the Open Day at QuTech in Delft at the end of the article. Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: Anycast Latency: How Many Sites are Enough?
by Mirjam Kuehne 24 May '17

24 May '17

Dear colleagues, Please find this new article on RIPE Labs by Jan Harm Kuipers, researcher at the University of Twente: Anycast Latency: How Many Sites are Enough? Jan Harm has been studying the relationship between latency and anycast using the RIPE Atlas network: https://labs.ripe.net/Members/jh_kuipers/anycast-latency-how-many-sites-are… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: RIPE NCC Technical Services 2017
by Mirjam Kuehne 05 May '17

05 May '17

Dear colleagues, In preparation of Kaveh Ranjbar's presentation at the RIPE NCC Services working group session next week in Budapest, please find on RIPE Labs a high-level report on the status and plans for our technical services and tools on. It has three parts: 1. Focus on RIPE Atlas https://labs.ripe.net/Members/kranjbar/ripe-ncc-technical-services-2017-par… 2. Focus on our DNS services https://labs.ripe.net/Members/kranjbar/ripe-ncc-technical-services-2017-par… 3. Focus on Tools and research activities: https://labs.ripe.net/Members/kranjbar/ripe-ncc-technical-services-2017-par… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: BBR TCP (by Geoff Huston)
by Mirjam Kuehne 05 May '17

05 May '17

Dear colleagues, Please find this new article on BBR TCP by Geoff Huston on RIPE Labs: https://labs.ripe.net/Members/gih/bbr-tcp Kind regards, Mirjam Kuhne RIPE NCC

1 0

Draft Agenda for the MAT WG at RIPE74
by Christian Kaufmann 26 Apr '17

26 Apr '17

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE74: A. Introduction: Welcome, Scribe, Jabber, Agenda - 5m B. Fast.com - Sergey Fodorov - 20 mins C. v6 Health Metric with NOMA - Leslie Dangle - 20 min D. Atlas News - Robert Kisteleki - 15 min E. Traceroute Visualisation - Massimo Candela - 20 min F. Russian Hackathon Examples - Alexander Isavnin - 10 min Z. AOB Timings are approximate:-) The session will take place at 14:00 local time on Wednesday 10th May. See you in Budapest! Nina and CK MAT WG Chairs

1 0

RIPE 74 call for late submissions, LTs, and one tutorial and BoF
by Benno Overeinder 14 Apr '17

14 Apr '17

Dear colleagues, Brief version: The RIPE PC invites submissions for plenary, tutorial, BoF and Lightning Talks. Longer version: As distinct from previous RIPE meetings, the RIPE Programme Committee decided to keep two plenary slots open for so-called “late submission”. These plenary slots gives the community the opportunity to submit presentations that report on recent developments, issues, security incidents, etc., that are relevant to the RIPE audience. Independent from the realisation of late submissions, the PC has received a fair amount of high-quality submissions for the first deadline on March 12th. From these submissions, we have selected 14 presentations to complete the RIPE 74 plenary programme and no second CFP with a deadline in April was required. For the tutorials and BoFs we have one slot for each available: - Monday morning, 2 hour tutorial slot - evening, 1 hour BoF slot Also please consider to submit Lightning Talks for the Monday plenary. During the week of the RIPE meeting we will accept LTs for Tuesday and Friday. Please submit your plenary “late submission”, tutorial or BoF submission via the PC submission system, https://ripe74.ripe.net/submit-topic/submission-form/. The deadline for the submissions is *April 26th*. Kind regards, Benno Overeinder RIPE PC Chair https://ripe74.ripe.net/programme/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 74 will take place from 8-12 May 2017 in Budapest, Hungary. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 74. See the full descriptions of the different presentation formats, https://ripe74.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 26 April 2017. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe74.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. Allocation of lightning talks will start a few days before the meeting, and will continue throughout the meeting. During the meeting, they may be announced on the day before the talk or even on the same day as the talk. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

New on RIPE Labs: Using RIPE Atlas to Measure Latency to Reunion Island
by Mirjam Kuehne 11 Apr '17

11 Apr '17

Dear colleagues, Please find this new article on RIPE Labs in which Réhan Noordally and his colleagues explain how they measure latency to and from La Reunion using Rasberry Pi's and RIPE Atlas: https://labs.ripe.net/Members/rehan_noordally/using-ripe-atlas-to-measure-l… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: TraceMON - Network Debugging Made Easy
by Mirjam Kuehne 10 Apr '17

10 Apr '17

Dear colleagues, TraceMON is a client-side tool for visualising network topology generated by traceroutes reaching one or more targets in a network. It provides a one-click access to a set of information useful during day to day operations. Please find more details on RIPE Labs: https://labs.ripe.net/Members/massimo_candela/tracemon-traceroute-visualisa… Kind regards, Mirjam Kuhne RIPE NCC

1 0

Live blogging from RightCon in Brussels (e.g. measuring Internet shutdowns)
by Vesna Manojlovic 30 Mar '17

30 Mar '17

Dear all, I am at at a conference where lots of topics are possibly relevant for this community: https://www.rightscon.org/ 29-31. March 2017 , Brussels Please check out these RIPE Labs articles if interested: https://labs.ripe.net/Members/becha/rightscon-2017-day-two https://labs.ripe.net/Members/becha/rightscon-2017-day-one https://labs.ripe.net/Members/becha/live-blogging-from-rightscon Regards, Vesna

1 0

Call for Presentations at RIPE 74 in Budapest
by ckaufman 16 Mar '17

16 Mar '17

Dear MAT WG, We are working on putting together the agenda for the MAT working group meeting on Wednesday 10th May at RIPE 74 in Budapest and there are still slots left.:-) So if you have something you would like to present, please let us know till the 31st March. Thanks a lot, Nina and CK MAT WG Chairs

1 0

RIPE Atlas Infrastructure Maintenance (14 March)
by Paul de Weerd 13 Mar '17

13 Mar '17

Dear all, We'll carry out maintenance work on the core RIPE Atlas and RIPEstat infrastructure tomorrow (14 March 2017), approximately between 09:00 and 11:00 UTC+1. As a result, we will switch over to the reduced data set, limiting the amount of history available from the service. This affects RIPE Atlas, RIPEstat, RIS and DNSMON. We apologise for the inconvenience. Best regards, Paul de Weerd Senior Systems Engineer RIPE NCC

1 0

New on RIPE Labs: New RIPE Atlas Root Zone DNS Measurements
by Mirjam Kuehne 10 Mar '17

10 Mar '17

Dear colleagues, Two new DNS measurements, both designed to assess the impact of issues with one or more root name servers, have been added to every RIPE Atlas probe. Please find more details on RIPE Labs: https://labs.ripe.net/Members/chris_amin/new-ripe-atlas-root-zone-dns-measu… Kind regards, Mirjam Kuhne RIPE NCC

1 0

Atlas: DNS TCP Errors
by John 07 Mar '17

07 Mar '17

Hello Mat-wg, feature request, when preforming DNS queries over TCP would it be possible for the probe to differentiate between a timeout and a TCP Reset. Currently the result just records the following when it gets a reset[1]. `error.timeout: 5000` A similar feature to record ICMP prohibited for udp queries would also be useful but likely much harder. Thanks John [1]https://atlas.ripe.net/api/v2/measurements/7859749/results?start=14888448…

1 0

250 RIPE Atlas Anchors now online!
by Michela Galante 23 Feb '17

23 Feb '17

Dear colleagues, Thanks to nineteen new RIPE Atlas Anchors being activated over the last three months, we have now reached an important milestone: 250 anchors online! Congratulations to anchor 250 hosted by Mogul Service and Support LLC in Ulaanbaatar, Mongolia and to APNIC for sponsoring it! These are the other anchors that have become active since our last announcement in November: - nl-ede-as12859, hosted by BIT in Ede, Netherlands - de-tua-as21413, hosted by envia TEL GmbH in Taucha, Germany - de-ham-as12731, hosted by IPHH Internet Port Hamburg GmbH in Hamburg, Germany (replaces older hardware) - py-slo-as27733, hosted by IXpy (sponsored by LACNIC) in San Lorenzo, Paraguay - uk-did-as786, hosted by Jisc in Didcot, United Kingdom - Two anchors hosted by Rabobank: nl-bst-as8211 in Best and nl-bxt-as8211 in Boxtel, Netherlands - nz-wlg-as9834, hosted by Trade Me in Wellington, New Zealand - lt-vno-as21412, hosted by CGATES in Vilnius, Lithuania - de-ber-as25291, hosted by SysEleven GmbH in Berlin, Germany (replaces older hardware) - us-bcb-as1312, hosted by Virginia Tech Transportation Institute in Blacksburg, United States - Two anchors hosted by Elisa Obj: fi-hel-as6667 in Helsinki and fi-tmp-as719 in Tampere, Finland - lu-ezt-as2602, hosted by Fondation RESTENA in Esch-sur-Alzette, Luxembourg (replaces older hardware) - de-kae-as8560, hosted by 1&1 Internet SE in Karlsruhe, Germany - fr-par-as5377, hosted by Marlink Enterprise AS in Paris, France - fr-tls-as39405, hosted by FULLSAVE in Toulouse, France - nl-ams-as286, hosted by KPN Eurorings B.V. in Amsterdam, Netherlands - mm-rgn-as132167, hosted by Ooredoo Myanmar (sponsored by APNIC) in Yangon, Myanmar (IPv4-only anchor) - fr-ilm-as57119, hosted by NAITWAYS in Issy, France - us-lxa-as8560, hosted by 1&1 Internet Inc. in Lenexa, United States You can find the full list of anchors, a map of their locations, a list of the hosting organisations and more information about RIPE Atlas Anchors online: https://atlas.ripe.net/anchors/list/ Interested in hosting a RIPE Atlas Anchor? Learn more: https://atlas.ripe.net/get-involved/become-an-anchor-host/ There are several organisations that want to host a RIPE Atlas Anchor but don’t have the necessary funding. Find out more about the RIPE NCC campaign to sponsor 15 RIPE Atlas Anchors https://labs.ripe.net/Members/alun_davies/campaign-to-sponsor-15-ripe-atlas… We would also like to remind you about our ongoing cooperation with APNIC, LACNIC, AFRINIC and ISOC: thanks to their help we are getting more geographical diversity to the measurement data. If your organisation is in their region contact us at <atlas(a)ripe.net> and we will get you in touch with them! And don’t forget to let us know by contacting us at <atlas(a)ripe.net> if you’re doing something interesting with RIPE Atlas data - we always want to hear about your use cases, research and experiences! Regards, Michela Galante RIPE NCC

1 0

Querying popular domains with RIPE Atlas
by Chris Amin 21 Feb '17

21 Feb '17

Dear colleagues, As you are probably aware, DNSMON* and RIPE Atlas built-in** measurements are often used when analysing outages and other issues with important DNS services, particularly the root zone servers. These measurements do not provide a direct indication of the impact on actual end-user experience because they involve directly querying authoritative name servers, thereby ignoring the effects of having multiple authoritative name servers as well as caching local recursive resolvers. To improve upon our DNS monitoring, we will initiate two built-in DNS measurements from all RIPE Atlas probes that use the probes' default resolvers instead of authoritative name servers. The first measurement will query for random top-level domains with the intention of avoiding caches and therefore hitting at least one root name server. The second measurement will query for popular domain names, with the intention of hitting caches where appropriate and getting an idea of the true impact on users. As a starting point for the second measurement, we will use a recent snapshot of the global top 50 visited sites according to the Alexa top sites list***, which combines unique visitors and individual page views in its calculations. Probes will cycle through these domains, querying for a different A record every 10 minutes. Since DNS queries containing these domains will be made from every connected RIPE Atlas probe, we would like to ask for feedback on whether querying the DNS for any of these domains could pose legal or political problems for probe hosts in certain parts of the world. I have also included the next 25 most popular domains below, which will be used to fill any gaps caused by removing items from the main list. Kind regards, Chris Amin RIPE NCC * https://atlas.ripe.net/dnsmon/ ** https://atlas.ripe.net/docs/built-in/ *** https://en.wikipedia.org/w/index.php?title=List_of_most_popular_websites&ol… Provisional 50 domains to query =============================== google.com. youtube.com. facebook.com. baidu.com. wikipedia.org. yahoo.com. google.co.in. amazon.com. qq.com. google.co.jp. live.com. taobao.com. vk.com. twitter.com. instagram.com. hao123.com. sohu.com. sina.com.cn. reddit.com. google.de. linkedin.com. tmall.com. yahoo.co.jp. weibo.com. google.fr. 360.cn. google.co.uk. google.ru. google.com.br. yandex.ru. ebay.com. bing.com. msn.com. google.it. soso.com. t.co. wordpress.com. google.es. microsoft.com. tumblr.com. aliexpress.com. blogspot.com. netflix.com. amazon.co.jp. ok.ru. google.com.hk. stackoverflow.com. google.ca. google.com.mx. imgur.com. Next 25 most popular domains, excluding pornography =================================================== apple.com. Naver.com. mail.ru. imdb.com. popads.net. onclickads.net. office.com. google.co.kr. github.com. pinterest.com. paypal.com. tianya.cn. google.com.tw. google.com.tr. google.com.au. diply.com. amazon.de. google.co.id. microsoftonline.com. onclckds.com. twitch.tv. adobe.com. amazon.co.uk. wikia.com. cnzz.com.

3 3

Join RIPE NCC DNS Measurements hackathon
by Vesna Manojlovic 16 Feb '17

16 Feb '17

Dear colleagues, The fifth RIPE NCC hackathon will take place on Thursday and Friday, 20-21 April 2017, in Amsterdam. Apply online: https://atlas.ripe.net/hackathon/dns-measurements/#!application-form *The application deadline is 26 February 2017* Find out more in this RIPE Labs article: https://labs.ripe.net/Members/alun_davies/dns-measurements-hackathon-2017 Regards, Vesna Manojlovic RIPE NCC Community Builder

1 0

New on RIPE Labs: Update on RIPE Atlas Probe Lifetimes
by Mirjam Kuehne 15 Feb '17

15 Feb '17

Dear colleagues, Please find an update on the status of RIPE Atlas probe connections on RIPE Labs: https://labs.ripe.net/Members/wilhelm/update-on-atlas-probe-lifetimes Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: Campaign to Sponsor 15 RIPE Atlas Anchors
by Mirjam Kuehne 31 Jan '17

31 Jan '17

Dear colleagues, The RIPE NCC is pleased to announce that we will be sponsoring 15 new RIPE Atlas anchors in 2017. This article provides details about the campaign and introduces the criteria that will be used to decide which applicants will receive sponsorship: https://labs.ripe.net/Members/alun_davies/campaign-to-sponsor-15-ripe-atlas… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: Using RIPE Atlas to Validate International Routing Detours
by Mirjam Kuehne 30 Jan '17

30 Jan '17

Dear colleagues, Please read on RIPE Labs an article by Anant Shah in which he describes how he is using RIPE Atlas to validate international routing detours: https://labs.ripe.net/Members/anant_shah/using-ripe-atlas-to-validate-inter… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Reviewing the 2016 Leap Second
by Mirjam Kuehne 17 Jan '17

17 Jan '17

Dear colleagues, Last month we covered the 2015 leap second ahead of the insertion of a leap second at the very end of 2016. As stated previously, leap seconds can trigger poorly-tested code paths; leap second handling always unearths bugs and issues. This one was no exception! Please find more details on RIPE Labs: https://labs.ripe.net/Members/stephen_strowes/reviewing-the-2016-leap-second Kind regards, Mirjam Kuehne RIPE NCC

3 2

RIPE Atlas APIs
by Robert Kisteleki 03 Jan '17

03 Jan '17

Dear colleagues, We've just published a RIPE Labs article about a reminder for the RIPE Atlas API version changes. You can read it here: https://labs.ripe.net/Members/kistel/ripe-atlas-api-changes Regards, Robert Kisteleki RIPE NCC

1 1

New on RIPE Labs: Four Years of RIPE Atlas Anchors
by Mirjam Kuehne 22 Dec '16

22 Dec '16

Dear colleagues, Four years have passed since the RIPE NCC announced its plans to put RIPE Atlas anchors into production. Since the first anchors went online in 2013, we’ve been working hard to both maintain and expand the network. As a result, we currently have 238 anchors deployed across 66 countries! Please find more on RIPE Labs: https://labs.ripe.net/Members/alun_davies/four-years-of-ripe-atlas-anchors Kind regards, Mirjam Kuehne RIPE NCC

1 0