- mat-wg - mailman.ripe.net

New on RIPE Labs: Using RIPE Atlas to Debug Network Connectivity Problems
by Mirjam Kuehne 10 May '16

10 May '16

Dear colleagues, Please find this new article by Stéphane Bortzmeyer on RIPE Labs where he explains how he used RIPE Atlas probes, the official RIP Atlas API and custom scripts, to debug network issues: https://labs.ripe.net/Members/stephane_bortzmeyer/using-ripe-atlas-to-debug… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Connectivity in the LAC Region
by Mirjam Kuehne 04 May '16

04 May '16

Dear colleagues, Please find this guest post by Agustín Formoso, Software Developer at LACNIC, on RIPE Labs: Connectivity in the LAC Region https://labs.ripe.net/Members/mirjam/connectivity-in-the-lac-region?pk_camp… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Agenda - RIPE72 MAT WG
by Nina Bargisen 03 May '16

03 May '16

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE72: A. Introduction: Welcome, Scribe, Jabber, Agenda - 5m B. Measuring DNSSEC Configuration of Upstream Resolvers with RIPE Atlas - Moritz Mueller - 15m C. Vantage Point Selection for IPv6 Measurements: Benefits and Limitations of RIPE Atlas Tags - Vaibhav Bajpai - 10m D. Internet Path Transparency Measurements using RIPE ATLAS - Brian Trammell - 20m E. RIPE ATLAS news - Vesna - 20m F. RIPE ATLAS Hackathon winner - 10m Z. AOB - 5m Timings are approximate:-) The session will take place at 14:00 local time on Wednesday 25th May. See you in Copenhagen! Nina and CK MAT WG Chairs

1 0

New on RIPE Labs: How Elasticsearch and Kibana Help us Analyse RIPE Atlas Data Logs
by Mirjam Kuehne 29 Apr '16

29 Apr '16

Dear colleagues, RIPE Atlas backend applications run on more than 40 servers. Each day these machines can produce thousands of application logs of any kind of severity level. In order to be able to track down serious errors, warnings or even unusual behaviour, we decided some time ago to try Elasticsearch as a logging sink. In this article we will look at the design of such a system and describe how we can easily make sense from an ocean of logs: https://labs.ripe.net/Members/andreas_strikos/how-elasticsearch-and-kibana-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Broadband Services and Infrastructure Mapping
by Mirjam Kuehne 28 Apr '16

28 Apr '16

Dear colleagues, Please find on RIPE Labs a short report about a conference on Broadband Services and Infrastructure Mapping, where a number of interesting mapping projects were presented. Emile Aben attended and presented RIPE Atlas: https://labs.ripe.net/Members/emileaben/broadband-services-and-infrastructu… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: How Pingable are the Pingables?
by Mirjam Kuehne 05 Apr '16

05 Apr '16

Dear colleagues, We look at how the "pingable:" and "ping-hdl:" attributes have been adopted in the last five years and how reachable the pingable addresses registered in the RIPE Database are when pinged from RIPE Atlas. Spoiler alert: It could be better. Please find the details on RIPE Labs: https://labs.ripe.net/Members/wilhelm/how-pingable-are-the-pingables?pk_cam… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Last call for presentations and Draft programme for RIPE 72
by Benno Overeinder 02 Apr '16

02 Apr '16

Colleagues, A list of currently accepted RIPE 72 presentations is now published at: https://ripe72.ripe.net/programme/meeting-plan/draft-programme/ There are still few slots remaining for a final RIPE 72 programme and RIPE Programme Committee will accept new proposals until 15 April 2016. This is our last call for you to submit your proposals. You can find the CFP for RIPE 72 below, or at https://ripe72.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/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 72 will take place from 23-27 May 2016 in Copenhagen, Denmark. 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 72. See the full descriptions of the different presentation formats, https://ripe72.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 15 April 2016. 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 in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange 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 The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe72.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe72.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: RIPE Atlas Update: DNSMON Code Available, LatencyMON Comparisons, New Credit Sharing and More
by Mirjam Kuehne 30 Mar '16

30 Mar '16

Dear colleagues, In the past few months, we've added some new features and functionality to RIPE Atlas, including making the DNSMON code available on GitHub for personal use, displaying IPv4 vs IPv6 comparisons in LatencyMON, new credit sharing options, and new limits on probes per measurement and results per day. Learn more about the latest updates on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-altas-update-dnsmo… Kind regards, Mirjam Kuehne RIPE NCC

1 0

MOOC on Internet Measurements
by Renata Cruz Teixeira 25 Mar '16

25 Mar '16

Dear colleagues, I’m pasting the announcement of the MOOC on Internet Measurements that my colleague, Timur Friedman, and I are doing. Classes start 23 May 2016 and run through 19 June 2016. I note that the MOOC is free. Please help us advertise to people who can be potentially interested. Best regards, Renata The MOOC "Internet Measurements: a Hands-on Introduction" will be available soon on the platform France Université Numérique. It will be taught by Timur Friedman from UPMC and Renata Teixeira from Inria. This course is taught in English and will cover internet measurement basics, including network topology and routes; connectivity, losses, latency, and geolocation; bandwidth; and traffic measurements; with hands-on exercises on PlanetLab Europe. This course is of interest to a wide range of people: system or network operators, designers of applications or services running over the internet or just curious end-users who would like to better diagnose problems. The prerequisite for this course is a level of understanding of internet technology that comes from an advanced undergraduate course or a first Masters course in networking, or equivalent professional experience. Program: Week 1 : Introduction Week 2 : Topology and routes Week 3 : Connectivity, losses, latency, and geolocation Week 4 : Bandwidth Week 5 : Traffic measurements It will be available from May, 23, to June, 19, 2016. Registrations are already open: https://www.fun-mooc.fr/courses/inria/41011/session01/about <https://www.fun-mooc.fr/courses/inria/41011/session01/about>

1 0

New on RIPE Labs: Support for Elliptic Curve Cryptography (ECC) in DNS Resolvers as Seen by RIPE Atlas
by Mirjam Kuehne 21 Mar '16

21 Mar '16

Dear colleagues, Please find this new article on RIPE Labs contributed by Maciej Andzinski: The Elliptic Curve Cryptography (ECC) is becoming increasingly popular in DNSSEC. While it is sometimes considered to be a remedy for the low DNSSEC adoption rate, there is also a lot of controversy around it. One of the main concerns is that DNSSEC-validating resolvers don't always make use of ECC. We used RIPE Atlas to measure the support for ECC in DNS resolvers. https://labs.ripe.net/Members/maciej_andzinski_2/support-for-elliptic-curve… Kind regards, Mirjam Kuehne RIPE NCC

1 0