- mat-wg - mailman.ripe.net

Portolan/Desktop
by Luciano Lenzini 23 Jan '15

23 Jan '15

Dear Colleague, The University of Pisa and IIT, an Institute of the Italian National Research Council, have designed and developed a crowdsourcing-based system, named PORTOLAN, which initially employed smartphones as mobile monitors probing the Internet. The aim of PORTOLAN is to enhance the current topology of the Internet at the Autonomous System level of abstraction - all with the contribution of volunteers. Find out more on our website (http://portolan.iet.unipi.it) Portolan was initially deployed in 2012 and since then it has been available on smartphone clients running Android. In order to increase the number of users, Portolan IS NOW available for desktop operating systems Linux, Windows and OS X. In this way we hope to obtain a more precise Internet structure with respect to the one now available. PORTOLAN works in the background, it is designed not to interfere in any way with users' activities and does not affect the smartphone/desktop's overall performance. In order to motivate users to contribute to the PORTOLAN project, we have added several services, which include diagnostic network tools (such as Ping, Paris Traceroute with Multipath Detection Algorithm, Maximum Throughput achievable along a path, etc.) and coverage measurement tools (available on smartphones only). All the tools are totally under the user's control. Data collected by these tools are stored in our server located in Pisa, in a completely anonymous way. The PORTOLAN component that runs on Android smartphones can be downloaded by users from Google play (https://play.google.com/store/apps/details?id=it.unipi.iet.portolan.tracero ute). The PORTOLAN component for desktop, available for Windows 7/8, Linux and OS X, can be downloaded at our website http://portolan.iet.unipi.it/download. The success of Portolan depends upon the number of users who join the experiment. Feel free to share this message with your colleagues students and friends!. Many thanks in advance for your cooperation. All the best, Luciano On behalf of the Portolan Development Team ------------------------------------------------ Prof. Luciano Lenzini Associate Researcher IIT/CNR lenzini44(a)gmail.com Former Full Professor Department of Information Engineering School of Engineering University of Pisa, Italy http://www.iet.unipi.it/~lenzini and Research Director CNUCE/CNR

1 0

Proposal for public HTTP measurements
by Robert Kisteleki 21 Jan '15

21 Jan '15

Dear RIPE Atlas users, The topic of publicly available HTTP measurements in RIPE Atlas comes up from time to time. There were a number of discussions about pros and cons for this feature over the years (including exposing probe hosts to unnecessary risks of other users "measuring" just about any kind of HTTP content out there), with no firm outcome. While we understand that this feature would come handy for some of our users, it does not benefit everyone. Therefore our proposal is the following: 1. We'll enable HTTP measurements to be performed by all atlas users, from any probes. 2. The targets of such measurements can only be RIPE Atlas anchors (these already run HTTP servers, see https://atlas.ripe.net/docs/anchors/) 3. Parameters like costs, minimum frequency, maximum number of probes involved, etc. will be set by the development team, just as with the other measurements. 4. The RIPE NCC will still be able to support other, vetted HTTP measurements as long as it benefits the community, as well as other HTTP measurements that we deem operationally useful. These will be evaluated on a case by case basis. Please speak up at the MAT working group list (mat-wg(a)ripe.net) if you support / don't support this proposal, of if you have any other opinion about it. Regards, Robert Kisteleki RIPE NCC R&D manager, for the RIPE Atlas team

8 14

Six new RIPE Atlas anchors, and that makes one hundred total!
by Vesna Manojlovic 16 Jan '15

16 Jan '15

Dear colleagues, We are proud to announce that six new RIPE Atlas anchors have been activated since our previous announcement: * uk-lon-as8676 hosted by PRT Systems Ltd in London, United Kingdom * br-sao-as22548 hosted by Núcleo de Informação e Coordenação do Ponto BR - NIC.br in Sao Paulo, Brazil * us-qas-as10745 hosted by ARIN on behalf of RIPE NCC in Ashburn, United States * us-phx-as53824 hosted by Liquid Web in Phoenix, United States * se-sln-as49515 hosted by Nordiska Servercentralen in Solna, Sweden * dk-blp-as39839 hosted by DK Hostmaster A/S in Ballerup, Denmark This brings the total number of anchors to 100! We wrote an article on RIPE Labs to cover all the details, which includes some changes to the anchoring measurements: https://labs.ripe.net/Members/suzanne_taylor_muzzin/one-hundred-ripe-atlas-… To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ For any other questions, please contact us at atlas(a)ripe.net Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

Call For Presentations RIPE 70, submission deadline 1 March 2015
by Benno Overeinder 13 Jan '15

13 Jan '15

Dear colleagues, Please find the CFP for RIPE 70 below. The deadline for submissions is 1 March 2015. 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 for the RIPE Programme Committee http://www.ripe.net/ripe/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 70 will take place from 11-15 May 2015 in Amsterdam, The Netherlands. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 70. 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. The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at https://ripe70.ripe.net/submit-topic/presentation-formats/ Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for "lightning talks", which are selected immediately before or during the conference. The following general requirements apply: - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 1 March 2015, using the meeting submission system at https://ripe70.ripe.net/submit-topic/submission-form/. Proposals submitted after this date will be considered on a space-available basis. Important Dates regarding RIPE 70 can be found at: https://ripe70.ripe.net/programme/important-dates/ - Lightning talks should also be submitted using the meeting submission system (https://ripe70.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. - Presenters should indicate how much time they will require. See more information on time slot allocations per presentation format at https://ripe70.ripe.net/submit-topic/presentation-formats/. - Proposals for talks 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, it is expected that most, if not all, presenters/panellists will 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

Deprecating the old measurement UI
by Robert Kisteleki 09 Jan '15

09 Jan '15

Dear all, In October last year, we introduced a new UI for browsing and scheduling measurements. For details, see: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-new-measurem… Your feedback about this was predominantly positive, and we’d like to thank everyone who helped this development with suggestions and bug reports. As stated at the time, we plan to deprecate and eventually remove the old interface (both the UI and the "API" it used). Our timeline is the following: 1. We'll make the new UI the default, and remove links to the old UI from the RIPE Atlas main menu, around 21 January. The old pages will still be accessible if one reaches them from somewhere else, such as a browser bookmark or hard-coded scripts. 2. Around the beginning of March, we'll remove the old pages from the system (/atlas/udm.html and related pages). This step will include the "deep links" that some of our users directly access to schedule and manage measurements from scripts (notably /atlas/*udm*.json). We'd like to encourage all of our users to switch to the new UI and API in the following weeks, if you haven't already done so. As always, we're happy to answer any questions or hear any feedback you might have. Regards, Robert Kisteleki, for the RIPE Atlas team

1 0

Apply for the RIPE Atlas data visualisation hackathon
by Vesna Manojlovic 08 Jan '15

08 Jan '15

Dear colleagues, we are happy to invite you to the first RIPE Atlas open data hackathon! In short: various groups will come together during the long weekend in Amsterdam, to make new visualisations (or modify existing ones) based on RIPE Atlas data, and to give that SW back to the community. We are inviting: programers, designers, operators, data-lovers, hackers, students... help us spread the word! Comcast is generously offering prizes and some coverage for travel expenses for several people -- to be awarded/selected by a jury. Dates: 27-28-29 March 2015 (Friday to Sunday) How to apply: https://www.ripe.net/s/XUJy More information in the RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-hackathon-20… Hope to see you there! Regards, Vesna

1 1

MAT-WG proposal for WLAN measurements on RIPE Atlas
by Brook Schofield 26 Dec '14

26 Dec '14

MAT-WG, thankyou for giving me the opportunity to present on "The Value of WLAN Measurements for the R&E Community" at the Measurement and Tools Working Group at RIPE69. You can find my presentation and stenography logs at: https://ripe69.ripe.net/presentations/91-eduroam-and-Atlas-RIPE69.pdf https://ripe69.ripe.net/archives/steno/40 To progress this work within the RIPE NCC Atlas development team I'd like your input into the following five (5) points: #1: For "opt-in" WLAN measurements to be enabled on RIPE Atlas As a point of clarification (and reiterated by Daniel Karrenberg) the intention is that ALL v3 probes will be capable of WLAN measurements - but measurements will ONLY be turned on by a probe host. #2: WLAN measurements will support associating to an "open" or 802.1X protected network for the purposes of performing a measurement As an active monitoring network the Atlas probes WILL NOT scan and report on all/available SSIDs. It will ONLY associate with EXPLICITLY defined SSIDs listed in the measurement. For eduroam quality purposes the success/failure of an 802.1X associations is initially the most interesting part of the measurement in determining whether sites are correctly deploying this service. There will be results related to the authentication process. #3: Any measurements performed over the wireless interface are aligned with a request to associate/authenticate to a particular network. The wireless interface will be connected only for particular tests bundled with the association to an SSID. All other tests will be performed via the wired interface as is currently the case. #4: The schedule for implementation will be determined by the RIPE NCC R&D team ...but hopefully your support for this work will allow them to prioritise this work while not jeopardising the other commitments the team has made to the community. #5: This proposal is inline with your understanding of "WiFi measurements" on the Atlas roadmap I'd be particularly interested in your feedback on whether you thought that the WiFi Measurements listed in the http://roadmap.ripe.net/ripe-atlas/ would accomplish the above or something completely different. My feeling from the room was that the above was largely accepted. I'd appreciate those that voiced their support to also do this on the mailing list again. If there's any confusion I'm willing to clarify further. Thanks, -Brook -- =================================================== Brook Schofield, Project Development Officer GÉANT Association, Singel 468 D, 1017 AW Amsterdam, The Netherlands Tel +31 20 530 4488 Fax +31 20 530 4499 Mob +31 65 155 3991 www.géant.org <http://www.xn--gant-bpa.org>

8 11

New on RIPE Labs: Visualising RIPE Atlas Probe Distribution
by Mirjam Kuehne 16 Dec '14

16 Dec '14

Dear colleagues, Please find a new article on RIPE Labs showing a visualisation of the distribution of RIPE Atlas probes compared to population: https://labs.ripe.net/Members/emileaben/distribution-of-ripe-atlas-probes Kind regards, Mirjam Kuehne RIPE NCC

1 0

Sixteen new RIPE Atlas anchors joined the community
by Michela Galante 08 Dec '14

08 Dec '14

Dear colleagues, We are proud to announce that sixteen new RIPE Atlas anchors have been activated since our previous announcement: * nl-ams-as12041 hosted by Afilias in Amsterdam, Netherlands. * kz-ala-as21299 hosted by 2Day Telecom LLP in Almaty, Kazakhstan. * Two anchors hosted by Booking.com: nl-ams-as43996 located in Amsterdam, Netherlands and uk-slo-as43996 located in Slough, United Kingdom * sk-bts-as201702 hosted by skHosting.eu in Bratislava, Slovakia. * kz-plx-as21282 hosted by KazNIC Organization in Semey, Kazakhstan. * lk-cmb-as38229 hosted by Lanka Education & Research in Colombo, Sri Lanka and sg-sin-as45494 hosted by openmirror.asia in Singapore, Singapore. These are the first two of ten anchors that APNIC will sponsor. * qa-doh-as8781 hosted by Ooredoo in Doha, Qatar on behalf of RIPE NCC since they are one of our K-root hosts. First anchor in Middle East! * uk-lon-as5459 hosted by LINX in London, United Kingdom on behalf of RIPE NCC since they are one of our K-root hosts and RIS Remote Route Collector locations. * si-lzp-as198644 hosted by the Go6 Institute in Skofja Loka, Slovenia, and sponsored by SIDN, Netherlands. * it-mil-as16004 hosted by Milan Internet eXchange (MIX) in Milan, Italy on behalf of RIPE NCC since they are one of our k-root hosts and RIS Remote Route Collector locations. * Three anchors hosted by Wikimedia Foundation in United States: us-qas-as14907 located in Ashburn, us-cax-as14907 located in Carrollton and us-sfo-as14907 located in San Francisco. * us-lan-as32244 hosted by Liquid Web Inc in Lansing Charter Township, United States. This brings the total number of anchors to 94. 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. There are more organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at mcb(a)ripe.net To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Kind regards, Michela Galante Measurements Community Building Team RIPE NCC

1 0

Updated Draft RIPE Atlas Service Terms and Conditions, v3.2
by Vesna Manojlovic 01 Dec '14

01 Dec '14

Dear colleagues, Here is an update on RIPE Atlas Service Terms and Conditions: On 15 September, we announced a draft version of new RIPE Atlas Service Terms and Conditions, along with a proposed implementation procedure: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service We published version 3.1 on 29 October, after incorporating feedback received from the community. During RIPE 69 in London last month, more feedback was received, and we’ve now published a third version (3.2), available here: https://atlas.ripe.net/legal/terms-conditions-draft/ Summary of changes: - Extended clarification of point 8.5.a - Minor modifications to grammar and references The revised implementation plan, with adjusted dates, is as follows: - December: last call for comments. If consensus is reached: - In January 2015, existing probe hosts will be notified by email about the upcoming transition to the new terms and conditions. - In addition to email notification, existing users and probe hosts will be presented with a pop-up window when they log in to the RIPE Atlas website, to inform them of the upcoming transition. - From 1 February 2015, RIPE Atlas will become a production service; new probe hosts will be asked to agree to the new terms and conditions when applying for a probe and all existing probe hosts will be subject to the new terms and conditions. We are coordinating with the MAT Working Group Chair to have a final call for comments for both the draft document and the implementation plan. Kind regards, Vesna Manojlovic Senior Community Builder Measurements Community Building

2 1

RIPE 69 presentation atlas vs nlring : data publicly available
by Thomas Holterbach 10 Nov '14

10 Nov '14

Hi, The results of the experiments that have been presented during the MAT session of the RIPE 69 meeting by Randy Bush (*On the Suitability of Two Large-Scale Internet Measurement Platforms)* are now publicly available in http://psg.com/~thomas/. Best regards, Thomas

1 0

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 vs nlring data available
by Randy Bush 06 Nov '14

06 Nov '14

From: Thomas Holterbach <thomasholterbach(a)gmail.com> > did you hear daniel karrenberg on making the data public? Yes, the data of the first experiment is already public and available on http://psg.com/~thomas/ Tomorrow I'll add the data of the second experiment.

1 0

Atlas Light Map
by Daniel Karrenberg 05 Nov '14

05 Nov '14

In the meeting George Michaelson referred to the light maps from space that were part of the the inspiration for RIPE Atlas as shown in http://www.slideshare.net/ripencc/ripe-atlas-a-real-big-measurement-network… Attached is a map of the RIPE Atlas probes in a similar colour scheme which I did a couple of months ago. It is large, you can zoom in. I leave it to your judgement how similar these are. Personally I am amazed how how well one can see things around Europe. Daniel

1 0

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

Re: [mat-wg] [dns-wg] Final Call For Presentations RIPE 69, deadline 1 October 2014
by Daniel Karrenberg 25 Sep '14

25 Sep '14

The correct link for the draft program is: https://ripe69.ripe.net/programme/meeting-plan/draft-programme/

1 0

Call For Presentations RIPE 69, deadline 31 August 2014
by Benno Overeinder 24 Sep '14

24 Sep '14

Dear colleagues, Please find the CFP for RIPE 69 in London below. The deadline for submissions is 31 August 2014. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, RIPE PC http://www.ripe.net/ripe/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 69 will take place from 3-7 November 2014 in London, UK. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 69. 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. The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at https://ripe69.ripe.net/submit-topic/presentation-formats/ Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for "lightning talks", which are selected immediately before or during the conference. The following general requirements apply: - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 31 August 2014, using the meeting submission system at https://ripe69.ripe.net/submit-topic/guidelines/. Proposals submitted after this date will be considered on a space-available basis. - Lightning talks should also be submitted using the meeting submission system (https://ripe69.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. - Presenters should indicate how much time they will require. See more information on time slot allocations per presentation format at https://ripe69.ripe.net/submit-topic/presentation-formats/. - Proposals for talks 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, it is expected that most, if not all, presenters/panellists will 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 1

Feedback on draft RIPE Atlas Service Terms and Conditions
by Adam Piggott 16 Sep '14

16 Sep '14

Hello, Having read the draft I find the T&Cs quite sensible but have some points to bring up. 7.1. [...] The RIPE NCC may perform security checks and audits to determine unauthorised use of the RIPE Atlas Service. 7.2. Users must assist the RIPE NCC with security checks and audits. These are a very open-ended statements and I'm sure that RIPE NCC has no intention of visiting our homes or places of work to perform "security checks and audits". The terms are written in a "legalese" form of language and hence must be taken at face value by those who accept them. I would not be comfortable agreeing to these two points without some sort of clarification as to what "security audits and checks" could be, and what "assistance" I would be obliged to provide. 10.1. All the RIPE Documents referred to in this agreement are available on http://www.ripe.net/. The Probe Host will regularly take notice of updated RIPE Documents on the website. I cannot accept this term. I can only accept to be bound to new terms if they are sent to me directly, for example by email. Article 2.3 seems to infer that RIPE NCC will indeed contact users directly at least 30 days in advance, which is acceptable. Thanks to RIPE NCC for including the community in such an important process. -- Adam Piggott, Proprietor Proactive Services (Computing)

2 1

Seeking community feedback on draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 15 Sep '14

15 Sep '14

Dear colleagues, As RIPE Atlas transitions from a pilot project to a production service, we want to publish RIPE Atlas Service Terms and Conditions that describe the use of the service and spell out both the user's and the RIPE NCC's obligations. We have published these proposed terms and conditions, along with an implementation plan, on RIPE Labs. Please take a look and let us know what you think. Your feedback is valuable, and and want to ensure we keep the community involved in every step of the process. https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service The main discussion about this should happen on the MAT Working Group Mailing List. We are asking to receive all feedback by the end of the RIPE 69 meeting in London, which takes places 3-7 November. Once the MAT Working Group Chairs have determined that consensus has been reached, a final version of the terms and conditions will be published. We're aiming to do so before the end of the year, so that RIPE Atlas can become a full production service by January 2015. Kind regards, Vesna Manojlovic Senior Community Builder Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: RIPE Atlas Measurements with Tagged Probes coming soon
by Mirjam Kuehne 12 Sep '14

12 Sep '14

Dear colleagues, Please find a new article on RIPE Labs: RIPE Atlas: Measurements with Tagged Probes Coming Soon https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-measurements… If you have any comments or questions, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

1 0

The Beta Version of the New DNSMON is Now Available
by Vesna Manojlovic 08 Sep '14

08 Sep '14

Dear colleagues, The DNS Monitoring Service (DNSMON) has been providing a comprehensive, objective and up-to-date overview of the quality of various global and regional DNS operators' services since 2003. We are in the process of integrating DNSMON within RIPE Atlas and the beta version of the new DNSMON is now publicly available: https://atlas.ripe.net/dnsmon We have also published a RIPE Labs article detailing what’s changed in the new DNSMON: https://labs.ripe.net/Members/fatemah_mafi/an-updated-dns-monitoring-service We invite you all to try the new service and provide your feedback. We’re confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features. Please send your comments and questions to the DNS Working Group Mailing List at dns-wg(a)ripe.net. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

7 11

New on RIPE Labs: Time Warner Cable Outage Measurements
by Mirjam Kuehne 28 Aug '14

28 Aug '14

Dear colleagues, The Time Warner Cable network suffered an outage yesterday. We looked at some interesting details of this outage using the RIPE Routing Information Service and RIPE Atlas. Please find the results on RIPE Labs: https://labs.ripe.net/Members/emileaben/time-warner-cable-outage Kind regards, Mirjam Kuehne RIPE NCC

1 0

Upcoming "Measurements Tools" Workshop for LIRs: 19 September 2014, in Amsterdam
by Vesna Manojlovic 27 Aug '14

27 Aug '14

Dear colleagues, Training Services, RIPEstat/RIPE Atlas developers and me will be giving a hands-on "Measurements Tools" Workshop on 19 September, in Amsterdam. Registration is possible for members of RIPE NCC via LIR Portal: https://lirportal.ripe.net/training/courses More information: https://www.ripe.net/lir-services/training/courses/tailor-made-workshops#to… Regards, Vesna

1 0

Fwd: [ARIN-consult] Consultation on New Experimental Allocation
by Emile Aben 05 Aug '14

05 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, 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. We plan to publish the results on RIPE Labs. Kind regards, Emile Aben RIPE NCC > From: ARIN <info(a)arin.net> Subject: [ARIN-consult] Consultation on > New Experimental Allocation Date: 4 Aug 2014 19:18:13 GMT+2 To: > arin-consult(a)arin.net > > ARIN is soliciting community input on a proposed experiment that > will require the temporary use of space from 23.128.0.0/10, the > IPv4 addresses reserved to facilitate IPv6 deployment. (see NRPM > policy 4.10 https://www.arin.net/policy/nrpm.html#four10 ) > > There has been much discussion on the NANOG mailing list about the > usability / routability of prefixes longer than a /24. In order to > try to provide some additional data on this topic, the RIPE NCC > has requested a small block of address space from the reserved /10 > in order to run the following experiment: > > RIPE Routing Information System (RIS) plans to announce a few > blocks of sizes /24 to /28 (no more then ten at a time) out of the > 23.128/10. They will monitor how this address space propagates in > BGP and its reachability. > > * This experiment will provide the global community with insight > on whether prefixes longer than a /24 from 23.128/10 are useable > and reachable on the global Internet. > > * A description of this experiment, as well as the results of > this research, will be published on https://labs.ripe.net/ . > Additionally, ARIN will provide a link to the RIPE Labs page, as > well as the end date of this experiment in the public Whois record > of this registration. > > Do you support the use of this reserved space for this experiment > or not, and why? Please provide comments to arin-consult(a)arin.net. > > This consultation will remain open through 5:00 PM EDT on Monday, > 1 September 2014. > > Regards, > > Leslie Nobile Director of Registration Services American Registry > for Internet Numbers (ARIN) > > > > _______________________________________________ ARIN-Consult You > are receiving this message because you are subscribed to the ARIN > Consult Mailing List (ARIN-consult(a)arin.net) Unsubscribe or manage > your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/arin-consult Please contact > the ARIN Member Services Help Desk at info(a)arin.net if you > experience any issues. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlPgtBkACgkQj05ACITZaqqG+gD/YRg/U4t+5AcfJooBICUSkrQc CZgsPUjBNKPTyAZuo0wA/2OnoB2Ls7V4J0M9PGmr0yPUERhWO5KCpwvfoyMvVBux =7/LU -----END PGP SIGNATURE-----

2 2

Nine new RIPE Atlas anchors so far this summer
by Vesna Manojlovic 25 Jul '14

25 Jul '14

Dear colleagues, We are proud to announce that nine new RIPE Atlas anchors have been activated since my previous announcement last month: - two hosted by NTT Communications in United States: us-sea-as2914, in Seattle & us-atl-as2914, in Atlanta - us-dal-as7366, hosted by Lemuria Communications in Dallas, USA - mu-plu-as327681, hosted by AFRINIC in Port Louis, Mauritius, on behalf of the RIPE NCC - cz-prg-as2852, hosted by CESNET, in Prague, Czech Republic. - dk-blp-as59469, hosted by Solido Networks ApS in Ballerup, Denmark - be-anr-as2611, hosted by MOSAIC/University of Antwerp/iMinds, Belgium - uk-lon-as60157, hosted by Antheus Telecom LTD, London, UK - us-wct-as7922 is hosted by Comcast, West Chester, PA, USA This brings the total number of anchors to 69. All RIPE Atlas anchors can be seen on this list: where logged-in users can access each anchor's measurements: https://atlas.ripe.net/anchors/list/ And on the map: https://atlas.ripe.net/anchors/map/ 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. Learn more about RIPE Atlas anchors and the benefits of hosting an anchor at: https://atlas.ripe.net/about/anchors/ For detailed announcements and updates about RIPE Atlas, please join the RIPE Atlas mailing list: https://www.ripe.net/mailman/listinfo/ripe-atlas Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

Read on RIPE Labs: Midsummer Update for RIPE Atlas
by Vesna Manojlovic 24 Jul '14

24 Jul '14

Dear colleagues, in these hot and slow summer days, we give you an overview of the current status of RIPE Atlas, new features since the last update during RIPE68, and an insight into past and future community activities: https://labs.ripe.net/Members/fatemah_mafi/ripe-atlas-midsummer-update-2014 Regards, Vesna -- Measurements Community Building team <MCB(a)ripe.net>

1 0

Last Part or our World Cup Analysis now available on RIPE Labs
by Mirjam Kuehne 14 Jul '14

14 Jul '14

Dear colleagues, The final part of our analysis of the World Cup 2014 is now available on RIPE Labs, with a look at what happened during the final four matches of the tournament: https://labs.ripe.net/Members/emileaben/internet-traffic-during-the-world-c… (section 4) If you have any comments or extra information, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: How RIPE Atlas Helped Wikipedia Users
by Mirjam Kuehne 09 Jul '14

09 Jul '14

Dear colleagues, Engineers from the Wikimedia foundation and the RIPE NCC recently collaborated on a project to measure the latency of Wikimedia sites for users worldwide. Together, we identified ways to decrease latency and improve performance for users around the world. Please find more information on RIPE Labs: https://labs.ripe.net/Members/emileaben/how-ripe-atlas-helped-wikipedia-use… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Part 2 of Internet Traffic during World Cup 2014
by Mirjam Kuehne 08 Jul '14

08 Jul '14

Dear colleagues, Please find on RIPE Labs part 2 of our World Cup 2014 analysis of IXP data, featuring extra time, penalty shootouts and much more: https://labs.ripe.net/Members/emileaben/internet-traffic-during-the-world-c… If you have any comments or extra information, please post it under the article. Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Internet Traffic During the World Cup 2014
by Mirjam Kuehne 27 Jun '14

27 Jun '14

Dear colleagues, It's Friday! To get you in the mood for the weekend, RIPE Labs has some festive football figures. In our most recent RIPE Labs article, we take a look at what happened with IXP traffic during the group stages of the 2014 FIFA World Cup: https://labs.ripe.net/Members/emileaben/internet-traffic-during-the-world-c… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Using RIPE Atlas to Debug Network Issues
by Vesna Manojlovic 12 Jun '14

12 Jun '14

Dear colleagues, Please find the use-case for RIPE Atlas in debugging network issues, in this RIPE Labs article written by Tim Kleefass from BelWü, who is hosting a RIPE Atlas anchor. (and who holds the record for the shortest time from purchasing the anchor to it going live!) https://labs.ripe.net/Members/tim_kleefass/how-fast-the-ripe-atlas-anchor-h… Regards, Vesna

1 0

Five more RIPE Atlas anchors since RIPE68
by Vesna Manojlovic 05 Jun '14

05 Jun '14

Dear colleagues, We are proud to announce that five new RIPE Atlas anchors have been activated since my previous announcement last month: - de-fra-as8763, hosted by DENIC eG in Frankfurt, Germany - us-dal-as2914 & us-mia-as2914, hosted by NTT Communications in Dallas & in Miami, United States. - se-got-as50168, hosted by Bogal AB in Gothenburg, Sweden - ru-mow-as15835, hosted by RIPN in Moscow, Russia (RIS RRC host) This brings the total number of anchors to 60. All RIPE Atlas anchors can be seen on this list, where logged-in users can access each anchor's measurements: https://atlas.ripe.net/anchors/list/ 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. Learn more about RIPE Atlas anchors and the benefits of hosting an anchor at: https://atlas.ripe.net/about/anchors/ For detailed announcements and updates about RIPE Atlas, please join the RIPE Atlas mailing list: https://www.ripe.net/mailman/listinfo/ripe-atlas Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

Planned Test Traffic Measurements Service Closure
by Romeo Zwart 05 Jun '14

05 Jun '14

Dear colleagues, The RIPE NCC’s Test Traffic Measurements (TTM) Service will be decommissioned at the end of June 2014. Most of the functionality offered by TTM is available as part of RIPE Atlas and we encourage you to take advantage of this service: https://atlas.ripe.net Handover of Responsibility of TTM Machines We will contact the individual TTM hosts during June to arrange the handover of responsibility for the remaining TTM systems. Many hosts asked us about the possibilities to keep the old hardware around as a stand-alone NTP server. We have a RIPE Labs article detailing the options to transition your TTM system to a dedicated NTP server. The article is available here: https://labs.ripe.net/Members/colin_petrie/how-to-convert-your-ttm-box-to-a… Availability of TTM Data - No new data will be collected via TTM once decommissioned - Current interface for TTM data visualisations will be available until at least the end of 2014 - Raw data from TTM measurements will be downloadable indefinitely Background For more information about the end of TTM, please read this RIPE Labs article by Kaveh Ranjbar posted last year: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services We delayed the decommissioning date mentioned in the article by six months to provide a smooth transition for the DNSMON service from TTM to RIPE Atlas. We also wanted to allow TTM users adequate time to start using RIPE Atlas or other tools. We invite your feedback regarding the above planning. Please send your comments directly to me (<romeo.zwart(a)ripe.net>) or to the MAT Working Group mailing list (<mat-wg(a)ripe.net>). Regards, Romeo Zwart RIPE NCC

1 0

Changes to the Distribution Model for RIPE Atlas Probes
by Vesna Manojlovic 03 Jun '14

03 Jun '14

Dear colleagues, we have made some adjustments in the distribution model of RIPE Atlas probes to ensure wider topological and geographical probe coverage. Please read more in this RIPE Labs article: https://labs.ripe.net/Members/fatemah_mafi/changes-to-the-distribution-mode… Regards, Vesna

1 0

New Article on RIPE Labs: ReFlow: Reports on Internet Flows
by Mirjam Kuehne 03 Jun '14

03 Jun '14

Dear colleagues, This new article on RIPE Labs is describing ReFlow - a public website containing statistics about general Internet traffic. The main goal of ReFlow is to maintain historical traffic data, allowing for comparisons and analysis of trends on Internet traffic This article has been contributed by Martijn Hoogesteger from the University of Twente: https://labs.ripe.net/Members/martijn_hoogesteger/reflow-reports-on-interne… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New article on RIPE Labs: Basic Evaluation of new IXP Peering Partners with RIPE Atlas and Zabbix
by Mirjam Kuehne 26 May '14

26 May '14

Dear colleagues, In this new article on RIPE Labs, Daniel Gomez explains how he used RIPE Atlas to evaluate new peering partners within an Internet Exchange Point and how this helped to improve customer services: https://labs.ripe.net/Members/daniel_gomez/basic-evaluation-of-new-ixp-peer… Kind regards, Mirjam Kuehne RIPE NCC

1 0

BEREC - Network Neutrality
by Gordon Lennox 20 May '14

20 May '14

BEREC have just issued a press release commenting on the Parliament's modified proposal and recalling some of their concerns with the Commission's initial proposal. About network neutrality they write: <<BEREC supports the promotion of and the clear commitment of the European Parliament to the principle of net neutrality. This is in line with BEREC’s public position, and indeed BEREC has been deeply involved with the subject since 2010, since when it has developed a set of principles and guidelines that can be implemented and adapted by national regulatory authorities, under the existing framework. The internet has proven to be highly innovative, thanks to certain fundamental principles such as the separation of network and application layer, the best effort principle and universal connectivity. This innovation should be safeguarded, both on the edges and within the network. BEREC recognizes that guaranteeing an open internet is a challenging objective, not least given its complex and dynamic ecosystem. Yet, the Commission’s original proposal would turn a flexible and progressive regulatory regime (under the 2009 Framework) into a rigid regulatory system and the European Parliament has generally retained this approach. BEREC would instead prefer an approach based on principles rather than detailed rules and which provides NRAs with the necessary powers to ensure that those principles (such as the ones developed by BEREC on what constitutes reasonable traffic management and on the relationship between specialized services and internet access services) are respected. Under such an approach, national regulators would be pursuing the same objective and enforcing the same principles, but the specific triggers and thresholds for regulatory intervention in a given market could be adapted to address national circumstances. If a rules-based approach is nonetheless to be pursued, then further work would be required to ensure that the definitions and rules were legally precise, future-proof and enforceable in practice. While some of the language in the text adopted by European Parliament draws upon BEREC previous publications on the subject, improving the original Commission’s proposals, it does not yet meet these standards. A balanced approach to promoting net neutrality on the Internet in parallel to the provision of specialised services is a difficult challenge. BEREC considers that specialised services should be clearly separated (physically or virtually) from internet access services at the network layer, to ensure that sufficient safeguards prevent degradation of the internet access services. Therefore BEREC welcomes the European Parliament’s acknowledgement of this principle. However, some inconsistencies in the proposed rules and definitions still raise legal and policy concerns.>> http://berec.europa.eu/eng/news_consultations/whats_new/2203-berec-publishe… So if you want network neutrality then you need regulation? The only question left is what kind. One indication of where they see the limits can perhaps be found in the sentence "This innovation should be safeguarded, both on the edges and within the network." I feel this is a significant shift. I cannot remember regulators looking in detail at what happens within traditional networks. They limited themselves to the "edges". Gordon

1 0

BEREC
by Gordon Lennox 16 May '14

16 May '14

BEREC - the Body of European Regulators for Electronic Communications, http://berec.europa.eu - are interested in metrics and monitoring. They are looking in particular at how regulators can monitor QoS for Internet access services in the context of network neutrality. Indeed they just had a public consultation on: "Monitoring quality of services in the context of network neutrality" based on a draft report, a draft which I think is still worth reading. See: http://berec.europa.eu/eng/news_consultations/ongoing_public_consultations/… From there - still also accessible from their home page - you can access the draft report and the annex where Atlas is mentioned. They have published a number of other reports on this going back over the past few years. Lots of reading! I brought this up on the Cooperation List and was requested to made a short presentation at the Connect session. There was an initial discussion on where this could sit between Cooperation and Connect. But looking forward maybe a more natural home would be between Connect and MAT. I will leave that for others to decide. But I do think it would be good to get somebody from BEREC to present in London. I will share the contact details I have with the co-chairs. Regards, Gordon

1 0

RIPE Atlas use cases and more
by Vesna Manojlovic 13 May '14

13 May '14

Dear colleagues, There have been a lot of great examples recently of how RIPE Atlas can be used to investigate network events, troubleshoot problems, explore how the Internet behaves, and more. Some of the topics include: - Investigating customer complaints about slow servers - Comparing TCP and UDP Response Times of DNS Root Servers - Discovering Path MTU black holes on the Internet We’ve collected all of these user experiences, analyses, papers and presentations in one place on RIPE Labs, in order to make it easy to discover how others are making use of the RIPE Atlas network - and maybe spark some ideas about how you can, too. https://labs.ripe.net/atlas/user-experiences If you have your own story about how you’ve used RIPE Atlas, we want to hear from you! Please get in touch with us at atlas(a)ripe.net. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

Re: [mat-wg] Trimble GPS from old TTM
by George Michaelson 13 May '14

13 May '14

We just upgraded BSD to 10 and it seems to be fne, but I haven't completed the cutover. Certainly, the driver ID for the 127.x.x.x instance is still in the BSD port codebase. -G On Tue, May 13, 2014 at 9:39 AM, Romeo Zwart <romeo.zwart(a)ripe.net> wrote: > Hi Antonio, > > On 14/05/13 00:44 , Antonio M. Moreiras wrote: > > Hello, we are trying to reuse the trimble GPS from our old TTM server in > > a Linux NTP machine, and it is not working. > > We have been doing some testing in the RIPE NCC with some linux > flavours. A RIPE Labs article with details is in preparation and will be > shared with this list soon. > > We will contact you off line to share our experience. > > Regards, > Romeo > > > We can read some trash with a "cat /dev/ttyS0" (what means that the GPS > > is sending information), and we can use PPS driver (127.127.22.0) to > > read correctly the PPS signal. But the driver from RIPE (127.127.43.0) > > doesn't work. > > > > We compiled the ntpd (version 4.2.6p5) with the following options: > > > > ./configure --with-openssl-libdir=/usr/lib/x86_64-linux-gnu > > --with-openssl-incdir=/usr/include --enable-RIPENCC > > > > Our Linux is: > > > > # uname -a > > Linux monitor 3.11.0-20-generic #35~precise1-Ubuntu SMP Fri May 2 > > 21:32:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > > > > # lsb_release -a > > No LSB modules are available. > > Distributor ID: Ubuntu > > Description: Ubuntu 12.04.4 LTS > > Release: 12.04 > > Codename: precise > > > > Only after follow the recommendations at > > http://linuxpps.org/wiki/index.php/LinuxPPS_NTPD_support, the driver > > 127.127.43.0 is loaded by NTP, and appears in the list of peers, but no > > sync, just zeros. > > > > Does anyone in this list have any tips? > > > > Regards, > > Moreiras. > > > > > > > >

2 2

Prevention of NTP reflection attacks using TTM systems
by Romeo Zwart 13 May '14

13 May '14

Dear colleagues, During the evening of Wednesday 8 January, the RIPE NCC received initial reports about the abuse of some of our Test Traffic Measurement (TTM) systems, specifically about the use of NTP in reflection attacks. Within 24 hours of receiving the first report, we adapted the NTP configuration on all our TTM hosts so that this specific type of attack is no longer possible using the TTM infrastructure. We would like to thank Gert Doering (SpaceNet) and Michael Hausding (SWITCH-CERT) for reporting the abuse to us. We’d also like to share this resource about securing NTP servers that you may find useful: http://www.team-cymru.org/ReadingRoom/Templates/secure-ntp-template.html We are taking this opportunity to remind you that we are nearing end of service for TTM. As we announced previously, TTM shutdown is scheduled for the end of Q1, 2014. RIPE Atlas, and specifically RIPE Atlas anchors, will provide much of the functionality of TTM. More details, including information about hosting a RIPE Atlas anchor, are available at: https://atlas.ripe.net/about/anchors/ Kind regards, Romeo Zwart RIPE NCC

4 4

Five more RIPE Atlas anchors in the previous month
by Vesna Manojlovic 07 May '14

07 May '14

Dear colleagues, We are proud to announce that five new RIPE Atlas anchors have been activated since my previous announcement last month: - uy-mvd-as28000, hosted by LACNIC in Montevideo, Uruguay. (This is the first anchor in Latin America and the first one hosted by an RIR on behalf of the RIPE NCC. ) - au-bne-as4608, hosted by APNIC in Brisbane, Australia - cz-prg-as39392, hosted by SuperNetwork in Prague, Czech Republic - fr-tin-as196670, hosted by ADP in Pantin, France - be-lln-as2611 by the Université catholique de Louvain in Belgium This brings the total number of anchors to 55. All RIPE Atlas anchors can be seen on this list, where logged-in users can access each anchor's measurements: https://atlas.ripe.net/anchors/list/ 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. Learn more about RIPE Atlas anchors and the benefits of hosting an anchor at: https://atlas.ripe.net/about/anchors/ For detailed announcements and updates about RIPE Atlas, please join the RIPE Atlas mailing list: https://www.ripe.net/mailman/listinfo/ripe-atlas Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0