- mat-wg - mailman.ripe.net

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