October 2014 - mat-wg - mailman.ripe.net

Nine new RIPE Atlas anchors joined the community
by Vesna Manojlovic 07 Nov '14

07 Nov '14

Dear colleagues, We are proud to announce that nine new RIPE Atlas anchors have been activated since my previous announcement: * de-cal-as39702, S-IT Informationstechnologie Betreiber, Calw, Germany. * nz-hlz-as681, hosted by the University of Waikato, Hamilton. This is the first RIPE Atlas anchor in New Zealand! * Three anchors by DigitalOcean: uk-slo-as202109 located in Slough, United Kingdom, us-sfo-as14061 located in San Francisco, United States, & sg-sin-as133165 in Singapore City, Singapore. * de-ett-as202040, hosted by SCT Schiele GmbH in Ettlingen, Germany. * nl-ams-as3265, hosted by XS4ALL in Amsterdam, Nederland. * us-den-as7922, second anchor hosted by Comcast, this time in Denver, United States. * de-nue-as33988, hosted by teamix GmbH in Nuremberg, Germany. This brings the total number of anchors to 78. Due the summer holidays, the growth in RIPE Atlas anchors have slowed down, but we do expect a new "surge" in the last quarter of this year. You can follow the activation rate on the graph here: https://atlas.ripe.net/results/maps/network-coverage/ The map of all anchor locations: https://atlas.ripe.net/anchors/map/ You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ And here are the logos and links to hosting companies: https://atlas.ripe.net/get-involved/community/#!tab-anchor-sponsors We are still accepting new applications from individuals and organisations interested in hosting a RIPE Atlas anchor. We are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa, in order to add more geographical diversity to the measurement data. To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

2 3

Atlas Sagan library and UDP tarceroute results: bug or feature?
by Jen Linkova 31 Oct '14

31 Oct '14

Hello, I've just found that using Sagan library for analyzing UDP traceroute measurement results may produce incorrect results: 'target_responded' variable is not be set to 'True' if the source address of the traceroute reply is not the target address of the traceroute, but any other address that belongs to the node. (From the traceroute.py code: def target_responded(self): if self._target_responded is not None: return self._target_responded self._target_responded = False if self.hops and self.hops[-1].packets: destination_address = IP(self.destination_address) for packet in self.hops[-1].packets: if packet.origin and destination_address == IP(packet.origin): self._target_responded = True return self.target_responded ) I don't think that's a valid assumption that a target node is *always* choosing the probe packet's destination address as a reply source. In particular, in case of UDP packets addressed to anycast, it might fail because the node can reply from another address. In particular, rfc4443 (ICMP for IPv6) says: 2.2. Message Source Address Determination A node that originates an ICMPv6 message has to determine both the Source and Destination IPv6 Addresses in the IPv6 header before calculating the checksum. If the node has more than one unicast address, it MUST choose the Source Address of the message as follows: (a) If the message is a response to a message sent to one of the node's unicast addresses, the Source Address of the reply MUST be that same address. (b) If the message is a response to a message sent to any other address, such as - a multicast group address, - an anycast address implemented by the node, or - a unicast address that does not belong to the node the Source Address of the ICMPv6 packet MUST be a unicast address belonging to the node. == and in the same RFC source address selection for ICMP echo reply messages is defined: The source address of an Echo Reply sent in response to a unicast Echo Request message MUST be the same as the destination address of that Echo Request message. An Echo Reply SHOULD be sent in response to an Echo Request message sent to an IPv6 multicast or anycast address. In this case, the source address of the reply MUST be a unicast address belonging to the interface on which the Echo Request message was received. ==== So, I'm sending this email, first, to warn those of you who is using Sagan to analyze UDP traceroute results, and, secondly, to discuss, if Sagan behavior is a bug (I believe it is) or a feature ;) -- SY, Jen Linkova aka Furry

1 0

New on RIPE Labs: Data Streaming in RIPE Atlas
by Mirjam Kuehne 31 Oct '14

31 Oct '14

Dear colleagues, RIPE Atlas data is now available as a live data stream, opening the door to a host of new applications and use cases. You can read more about this new functionality on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/data-streaming-in-ripe-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Updated Draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 29 Oct '14

29 Oct '14

Dear colleagues, On September 15 we announced the draft of new Terms and Conditions for the RIPE Atlas service, and the implementation procedure: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service In the meantime, we received feedback from the community and we’d like to thank you for your input. It was summarized here: https://www.ripe.net/ripe/mail/archives/mat-wg/2014-October/000498.html Based on that, we published second revision of the proposed document, available here: https://atlas.ripe.net/legal/terms-conditions-draft/ Summary of changes: - article 3.2: word "critical" replaced with "important" - new article 3.4: Users are required to register and maintain a valid email address and contact details in the RIPE Atlas Portal. - article 4.4: grammar about "email addresses of hosts" fixed - article 6.1: link to MoU added - articles 7.1 & 7.2: security checks specified as "reasonable" - article 10.1: clarified that this refers to other documents, by inserting "Without prejudice to Article 2.3 ..." Please review the document and post your comments to the list, or during MAT working group at the RIPE69 Meeting. After the meeting we will coordinate with Working Group chairs to have a final draft of the document circulated and publish our implementation plan as soon as we get the go ahead from working group chairs. Kind regards, Vesna Manojlovic Community Builder for Measurements Tools

1 0

New on RIPE Labs: New RIPE Atlas Measurements User Interface
by Mirjam Kuehne 28 Oct '14

28 Oct '14

Dear colleagues, We're very excited to announce an all-new user interface for RIPE Atlas measurements. Users can now schedule, monitor and manage their own customised measurements more efficiently than ever before, and can now make use of the tagging feature when selecting probes for use in those measurements. Learn more about the new features on RIPE Labs and let us know what you think: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-new-measurem… Kind regards, Mirjam Kuehne RIPE NCC

1 0

RIPE Atlas Value Proposition Published
by Kaveh Ranjbar 24 Oct '14

24 Oct '14

Dear colleagues, During its meeting in September, the RIPE NCC presented the RIPE NCC Executive Board with a value proposition document detailing the value that RIPE Atlas can bring to network operators, researchers and the Internet community as a whole. The board asked the RIPE NCC to publish this document, which is available on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-value-propos… We also plan to incorporate much of the document's content into the RIPE Atlas website so that RIPE Atlas users can clearly understand the different ways this global Internet measurement network can be used and the many unique benefits it provides. We hope you will find this document useful and that you may even be inspired to make use of RIPE Atlas in new ways. Kind regards, Kaveh Ranjbar Chief Information Officer RIPE NCC

1 0

Draft agenda for MAT @ RIPE69
by Christian Kaufmann 20 Oct '14

20 Oct '14

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE69: A. Introduction: Welcome, Scribe, Jabber, Agenda (5m) B. On the suitability of two large-scale Internet measurement platforms (20m) Randy Bush D. The value of WLAN measurements for the R&E Community (20m) Brook Schofield E. OpenIPMap (crowdsourcing Internet infrastructure geolocation) (10m) Emile Aben F. "RIPE Atlas #dataviz” (10m) Vesna Manojlovic G. Python and RIPE ATLAS (20m) APIVaibhav Bajpai Z. AOB Timings are approximate. The session will take place at 14:00 local time on Wednesday 5th November. We are looking forward to see you all in London, Richard & Christian

2 1

Community Feedback on Draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 07 Oct '14

07 Oct '14

Dear colleagues, On September 15 we announced the new draft of the Terms and Conditions for the RIPE Atlas service: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service We received feedback from the community and we’d like to thank you for your input. Below is a summary of the main points raised and our response. ------------------------------- Security audits and user assistance ------------------------------- We were asked to clarify what is meant by “security audits and checks” and what “assistance” users would be obliged to provide. We will clarify this in the next draft. -------------------------------------- Contradiction between Articles 2.3 and 10.1 -------------------------------------- We were asked to clarify the perceived contradiction between Articles 2.3 and 10.1 about informing users about the future changes to the Terms and Conditions (T&C). There was a strong preference stated to actively alert users about upcoming changes. It was suggested to allow for a window of time after notification before changes are applied (e.g. 30 days). We will inform users about the upcoming T&C changes by email, as outlined in the “implementation timeline” (point #3) in the RIPE Labs article. In reference to the articles, Article 2.3 is about amendments to the T&Cs and Article 10.1 is about other RIPE Documents that are created using different procedures and include points of references for the T&Cs. ---------------------- Minor editorial changes ---------------------- We were given several minor editorial suggestions. We will review the suggested edits. --------------------------- Strong legalese in the T&C -------------------------- Some people raised concern about the “strong legalese” included in the updated T&Cs. The inclusion of those provisions is to align the T&Cs with the other legal documents of the RIPE NCC. We felt that the document should reflect the RIPE NCC’s operational practices and should clarify the mutual responsibilities and expectations of probe hosts and the RIPE NCC. The Terms and Conditions is a legal document and the rights and obligations between both parties should be clearly and fully stated. Unfortunately legalese cannot be avoided. We would like to thank you again for your input. If you have any other comments about the text or the implementation procedure, please let us know. Please let us know if you have any other comments on the text or the implementation procedure. Kind regards, Vesna Manojlovic Community Builder for Measurements Tools

1 0

Re: [mat-wg] [routing-wg] Fwd: [ARIN-consult] Consultation on New Experimental Allocation
by Emile Aben 06 Oct '14

06 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/08/14 12:51, Job Snijders wrote: > On Tue, Aug 05, 2014 at 12:38:17PM +0200, Emile Aben wrote: >> I'd like to inform you of an experiment we propose doing together with >> ARIN about the routability of prefixes longer than /24 out of ARINs >> 23.128.0.0/10 block. For more details see ARIN's announcement below. >> >> If people have any feedback on this, please let us know. > > I recommend testing with and without proper route: objects for the small > prefixes. > > As a service provider I would accept smaller than /24... If and only if > there is an exact route object for the prefix, other providers just > discard anything smaller than a /24, regardless of the existance of > proper route objects. Would be good to quantify this. We plan to start announcing a couple of prefixes from AS12654 within the next hour for the purpose of reachability checking of prefixes longer than /24 out of ARINs 23.128.0.0/10 block: With route object: prefix pingable IP 23.128.24.0/24 23.128.24.1 23.128.25.0/25 23.128.25.1 23.128.25.240/28 23.128.25.241 Without route object: prefix pingable IP 23.128.124.0/24 23.128.124.1 23.128.125.0/25 23.128.125.1 23.128.125.240/28 23.128.125.241 best regards, Emile Aben RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJULRhIAAoJEKxthF6wloMOuR4QAJys9r18hwmu8DsF2nr6mCje wjYoKcJP/AAl0vQpQLMhR70D9b9v5XQArcMyvzoXRqcFYTfz5yAy9rsOD1pWOE8r dz/XmTzp45fmTRBMbCgQNVA4FLhv0Iq9Qx2eVSWhgLGSTNRNM9oGUTOVvzaIZ551 hx0+dbexz6AO9LlHeeam+rulHsIrsXXeMHhuLz1yU/MkW+MEyadJPQqLpMjIvCBs 4ENPDe358J4SQVMi7Ur55mXaF8vCJ4lP9CXCzcSvEa+S+iuoN9+xrDC6+QPHPj8k 1ZWiSN903ESQBcTG+uX69GH0qHCD/ADYswL705GEayRhXh0VlCdUwkfBCZdYKRn/ KB5hvJ+xkXIA+2mlBJYuJDWs3WB9xZ4ijID6hEbyqfiX1TqNQy0qPPS5HWrkeZg6 UCVBDFvZnn39z7BOSNLvf3bSc1VWK2AikS+6pzyyd8i4Pdk7GVPxFnsHdfEwkRJz n7h0Vjn7MOrnS6Fy29dJ1E+HC3PlN+W1hE9j4vO3sGrKHEc9tIW9MZ8Wg35qKi5c oUp9wylYhkjl3YKHxtc4bUXwzQqdYa7sxXPKIX5yfYLa+0mIdnQgWqK2Rzd+/rAa JfNPCrgJkxUrd8Gut6OkaV5EhgojYfvrGe3qfZj9OvhG4SQcDjbTW24rdySjtMJS mADNKNND94MRp43ehre3 =bh0Q -----END PGP SIGNATURE-----

1 1

Call for Presentations at RIPE 69 in London
by Christian Kaufmann 06 Oct '14

06 Oct '14

Dear MAT WG, We co-chairs are beginning to put together the agenda for the MAT working group meeting on wednesday 5th November at RIPE 69 in London and there are still 3 slots left. If you have something you would like to present, please let us know no later than Friday, 17th October 2014. Thanks a lot, Richard Barnes and Christian Kaufmann MAT Co-Chairs

2 1