- mat-wg - mailman.ripe.net

New on RIPE Labs: Measuring your Web Server Reachability with TCP Ping
by Mirjam Kuehne 27 Sep '17

27 Sep '17

Dear colleagues, HTTP measurements from RIPE Atlas probes are only possible towards RIPE Atlas anchors. However, when it comes to measuring the connectivity and latency of web servers on the network level, an alternative exists, which we call TCP Ping: a traceroute with special options that mimic the TCP handshake that takes place when an HTTP connection is established. In this RIPE Labs article we compare the results of large scale HTTP and TCP Ping measurements: https://labs.ripe.net/Members/wilhelm/measuring-your-web-server-reachabilit… Kind regards, Mirjam Kuhne RIPE NCC

1 0

Draft agenda for MAT-WG @ RIPE 75
by Nina Bargisen 13 Sep '17

13 Sep '17

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE75: A. Introduction: Welcome, Scribe, Jabber, Agenda - 5 min B. Introduction of Brian Trammel - 5 min C. Comparing a set of latency measurements - Agustin Formoso - 20 min D. A new almost reliable UDP protocol - Nuno M. Garcia - 25 min E. Country Reports and OpenIPMap - RipeNCC - 30 min F. Reflections and Saying bye - Christian Kaufmann - 5 min Z. AOB Timings are approximate:-) The session will take place at 09:00 local time on Tuesday 24th September. See you in Dubai! Nina and CK MAT WG Chairs

2 1

Call for MAT CoChair candidates
by ckaufman 12 Sep '17

12 Sep '17

Dear MAT WG, the time has come to make my “Chair” vacant and bring some fresh blood into the MAT WG:-) As you might remember I am one of original three MAT WG CoChairs since the MAT was rechartered out of the original Test Traffic WG at RIPE60 in Prague. Originally I was chairing together with Ian Meikle and Richard Barnes which left over the years and where eventually succeeded by Nina Bargisen. (Job description for interested Candidates:-)) I have done the job now for 7,5 years prepared the session, chaired the session, answered emails, welcomed new attendees at RIPE Meetings, represented the WG at ENOG and sometimes other conferences, had countless conversation with Daniel, Robert, Kaveh and of course Vesna about RIPE Atlas and the Anchors and about further and future collaboration. Attended RIPE Hackathons. Participated in the PDP review and in the WG collective as your representative, etc. These are all tasks a MAT WG CoChair does do to one or the other degree, and which you should be interested in if you apply for it. In the last years we came up with an election process which was approved by you and used when we elected Nina and which I want to use now for replacing me. We will go through the process as described below and ideally present the new WG CoChair at the next WG Session in Dubai. After the Dubai Meeting I will then officially step down. The process: 1. A call for interested parties is made on the WG mailing list at three yearly intervals, or as needed 2. Interested parties have 2 weeks to make their interest known via the mailing list 3. The MAT-WG chairs issue a call for discussion as per normal. WG members express their approval or otherwise of the presented candidates. 4. After two weeks the chairs declare consensus as they would do for a policy proposal As a remainder our Charter and Website can be found at: https://www.ripe.net/ripe/groups/wg/mat <https://www.ripe.net/ripe/groups/wg/mat> and the official Job description at: https://www.ripe.net/ripe/docs/ripe-542 <https://www.ripe.net/ripe/docs/ripe-542> Please feel free to nominate yourself if you are interested or shanghai others ( with their approval:-)) till the 11th September. Thx a lot and it was a pleasure to serve you. Christian Kaufmann MAT WG Co-Chair PS: I want to thank the RIPE NCC for their support over all the years, without them there would be no MAT WG, especially Mark Dranse who inspired me to start this journey, Daniel for starting RIPE Atlas and his vision, Rob B. for his wisdom as RIPE Chair, Robert and Kaveh for their never ending support and input, Vesna for her spirit and energy and for bringing so many people together, Amanda for the minutes and Hans Petter for doing an excellent job as a WG Chair Dompteur. And last but not least Nina for continuing the WG and her support in the last years.

8 9

New on RIPE Labs: Evaluation of Hurricane Harvey's Effects on the Internet's Edge
by Mirjam Kuehne 08 Sep '17

08 Sep '17

Dear colleagues, In this new article on RIPE Labs, John Heidemann, researcher at USC/ISI, evaluates the effects of Hurricane Harvey and examines what outages in edge networks can say about damage on the ground. https://labs.ripe.net/Members/john_heidemann/evaluation-of-hurricane-harvey… Kind regards, Mirjam Kuhne RIPE NCC

1 0

[Training] Launching RIPE NCC:: Educa - Online Learning Event
by Sandra Bras 04 Sep '17

04 Sep '17

Dear colleagues, The RIPE NCC has a new way to dive deep into a topic without having to travel or leave your desk. RIPE NCC::Educa are free, online learning events that bring industry experts together to share insight, expertise and best practice with those that want more in-depth knowledge on a particular subject. Our first event focuses on RIPE Atlas on Thursday, 5 October from 8:00 - 13:00 UTC. Reserve your place here: https://www.ripe.net/support/training/ripe-ncc-educa <https://www.ripe.net/support/training/ripe-ncc-educa> You can join us for one session, multiple sessions or the full programme. We’re updating the agenda constantly, so be sure to check here for the latest additions: https://www.ripe.net/support/training/ripe-ncc-educa/agenda <https://www.ripe.net/support/training/ripe-ncc-educa/agenda> For more information on RIPE NCC::Educa, check out our RIPE Labs article: https://labs.ripe.net/Members/sandra_bras/introducing-ripe-ncc-educa <https://labs.ripe.net/Members/sandra_bras/introducing-ripe-ncc-educa> If you have any questions, please get in touch with us: <e-learning(a)ripe.net <mailto:e-learning@ripe.net>> Warm regards, Sandra Brás E-Learning Program Manager RIPE NCC

1 0

Plan to Implement RIPE Atlas WiFi Measurements
by Robert Kisteleki 30 Aug '17

30 Aug '17

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

2 2

Are you using passive on-path RTT measurements in day-to-day operations?
by Brian Trammell 29 Aug '17

29 Aug '17

Greetings, all, I've proposed a lightning talk on this subject for Dubai, but it occurred to me that this working group might be a better place to answer this question: how prevalent is the use of passive latency measurement (e.g., by looking at DNS request/response times, or TCP seq-ack / timestamp delays) in everyday network operations, and for what is it commonly used? I ask this question in the context of a very specific design proposal before the IETF's QUIC working group. QUIC encrypts almost all of its header information beyond that needed for its crypto handshake, which makes equivalent techniques to those used in TCP impossible: you see no ACK numbers, and no timestamps, so it's impossible to match an upstream QUIC packet with its downstream counterpart. However, a recently proposed addition to the spec (https://github.com/quicwg/base-drafts/pull/609) would add a single bit to the header which would be explicitly intended for passive round trip time measurement. Since this adds a small amount of complexity to the wire image, one useful piece of input to the decision whether or not to add this measurability is how useful it is, in terms of operational impact of having passive measurability go away as TCP flows are replaced by QUIC flows. Thanks, cheers, Brian

1 0

Call for Presentations at RIPE 75 in Dubai
by ckaufman 28 Aug '17

28 Aug '17

Dear MAT WG, We are working on putting together the agenda for the MAT working group meeting on Tuesday 24th October at RIPE 75 in Dubai and there are still slots left.:-) So if you have something you would like to present, please let us know till the 11th September. Thanks a lot, Nina and CK MAT WG Chairs PS: Important information! RIPE 75 will commence on Sunday 22 October and end on Thursday 26 October, as this is the standard working week in Dubai.

1 0

Last call for presentations and Draft programme for RIPE 75
by Benno Overeinder 25 Aug '17

25 Aug '17

Colleagues, A list of currently accepted RIPE 75 presentations is now published at: https://ripe75.ripe.net/programme/meeting-plan/draft-programme/ There are still plenary, BoF, tutorial and workshop slots remaining for the final RIPE 75 programme and RIPE Programme Committee will accept new proposals until *6 September 2017*. This is our last call for you to submit your proposals. You can find the CFP for RIPE 75 below or at https://ripe75.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. Update to UAE DTCM requirements: It is now confirmed that a photocopy of speakers' passports is *not* required. Non-UAE/international speakers need only to provide: * Passport number * Date of birth * A short biography (at least 60 words) Residents of the UAE are required to upload a copy of their Emirates ID (in jpeg format). More details are available here: https://ripe75.ripe.net/attend/dctm-requirements Kind regards, Benno Overeinder RIPE PC Chair https://ripe75.ripe.net/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 75 will take place from 22-26 October in Dubai, UAE. 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 75. See the full descriptions of the different presentation formats, https://ripe75.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *6 September 2017*. 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) Speakers Due to UAE law, confirmed Non-UAE/international speakers need to provide: * Passport number * Date of birth * A short biography (at least 60 words) Residents of the UAE are required to upload a copy of their Emirates ID (in jpeg format). More details are available here: https://ripe75.ripe.net/attend/dctm-requirements Please also note that speakers do not receive any discount or funding towards the meeting fee at RIPE Meetings. 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://ripe75.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe75.ripe.net/submit-topic/) 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. 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: Processing RIPE Atlas Results with jq
by Mirjam Kuehne 21 Aug '17

21 Aug '17

Dear colleagues, Please find this new article by Stephane Bortzmeyer on RIPE Labs: Processing RIPE Atlas Results with jq https://labs.ripe.net/Members/stephane_bortzmeyer/processing-ripe-atlas-res… Kind regards, Mirjam Kuhne RIPE NCC

1 0