Dear colleagues,
We wanted to update the community and let you know that we plan to start
work on the proposed experiment with WiFi measurements in mid-2016. As we
communicated in a recent RIPE Labs article, we will work with GÉANT as a
test partner to learn more about the operational effects of introducing WiFi
measurements to the RIPE Atlas system, in addition to the benefits we
believe this could provide for the entire RIPE Atlas community. Please see
the article for more details if you are interested:
https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure…
We will continue to update you once we’ve begun work on this plan, and we
welcome your comments in the meantime.
Regards,
Robert Kisteleki
RIPE NCC
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
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
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
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
