December 2013 - mat-wg - mailman.ripe.net

Seven new RIPE Atlas anchors are now active!
by Vesna Manojlovic 17 Jan '14

17 Jan '14

Dear colleagues, We are proud to announce that seven new RIPE Atlas anchors have been activated since RIPE Atlas anchors became a full production service at the RIPE 67 Meeting in Athens last month. This brings the total number of anchors to 22. All RIPE Atlas anchors can be seen on this list, where users can also 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 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 2

Proposing more public RIPE Atlas data and clarifying the current situation
by Vesna Manojlovic 10 Jan '14

10 Jan '14

Dear colleagues, Sharing information about Internet performance is at the heart of collaborative efforts such as RIPE Atlas. Most of the RIPE Atlas probes and RIPE Atlas measurements are already public, and we'd now like to suggest opening up the publication of RIPE Atlas data further. We also want to clarify exactly what is and isn't public in the current system. We describe this in more detail in this RIPE Labs article, where we also ask for community feedback about our suggested plan to move forward: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… Our proposed plan is to make all *new* measurements and technical information about the *new* probes public from an agreed upon date in the future. We propose implementing this change in mid-April. All probes and measurements that were not marked "public" by April 2014 would remain non-"public". For a detailed description of what this means, please see the RIPE Labs article (above). Although we believe that having public measurement data contributes to the goal of RIPE Atlas, the RIPE NCC greatly values our users' privacy. We want to ensure you that we will continue to protect our probe hosts' personal information. We look forward to your feedback and comments on the MAT Working Group Mailing List. Regards, Vesna Manojlovic Senior Community Builder Measurements Community Building RIPE NCC

12 18

Updating the DNS Monitoring Service
by Romeo Zwart 19 Dec '13

19 Dec '13

Dear colleagues, Our DNS Monitoring Service (DNSMON) has been providing an up-to-date service overview of certain DNS root and Top-Level Domain (TLD) name servers for over eight years now, using the Test Traffic Measurement Service (TTM) as the underlying measurement platform. Last week, we sent out an announcement explaining that TTM would be decommissioned and its functions replicated within RIPE Atlas. As DNSMON currently relies on TTM for its data collection, the decommissioning of TTM will impact DNSMON. As announced in the RIPE NCC Activity Plan and Budget 2013, DNSMON in its current state will be shut down and most of its functionality migrated over to RIPE Atlas and RIPEstat, providing an improved and more future-proof DNS Monitoring Service. RIPE Atlas, and specifically the RIPE Atlas anchors, will perform measurements providing the data previously collected by TTM systems. More information is available in the RIPE Labs article, “Future of RIPE NCC Technical Services”, written by Kaveh Ranjbar, Chief Information Officer at the RIPE NCC: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services Some of our current DNSMON users have volunteered to conduct preliminary testing of the new, updated service, in the first quarter of 2014. Partly based on the user feedback from this testing phase, we will develop the new service so that it best meets the needs of current users. We hope to have the migration completed, with the new service fully implemented and available, by the end of the first quarter of 2014. After that, we will start to expand the service and accept applications from new users. You can find the most up-to-date plans on the DNSMON roadmap: http://roadmap.ripe.net/dnsmon/ If you have any questions or feedback, please contact <dnsmon-future(a)ripe.net> or reply to the MAT-WG Mailing List. Regards, Robert Kisteleki Romeo Zwart

1 0

New on RIPE Labs: Infrastructure Geolocation - Plan of Action
by Mirjam Kuehne 19 Dec '13

19 Dec '13

Dear colleagues, At RIPE 67 we presented our ideas on infrastructure geolocation. This new RIPE Labs article by Emile Aben shows the current thinking on how to develop router geolocation further. Any feedback will be appreciated. https://labs.ripe.net/Members/emileaben/infrastructure-geolocation-plan-of-… Kind regards, Mirjam Kuehne RIPE Labs

1 0

Scheduled shutdown of Test Traffic Measurement Service (TTM)
by Romeo Zwart 13 Dec '13

13 Dec '13

Dear colleagues,  We are currently in the process of shutting down our Test Traffic Measurement Service (TTM). These plans were previously announced at RIPE 64 by Daniel Karrenberg in the Measurement Analysis and Tools (MAT) Working Group session, and in section 2.4.5 of the RIPE NCC Activity Plan and Budget 2013: http://www.ripe.net/ripe/docs/ripe-558 This is now scheduled for completion by the end of the first quarter of 2014. The TTM service has been operational for more than ten years. The equipment used to provide this service, as well as the software underlying it, have become outdated and costly to maintain. Several years ago, we introduced our new measurements service, RIPE Atlas. RIPE Atlas and RIPE Atlas anchors can provide almost all of the functionality provided by TTM. This was explained by Kaveh Ranjbar, the RIPE NCC's Chief Information Officer, in the RIPE Labs article, “The Future of RIPE NCC Technical Services”. As noted in this article, one difference is that RIPE Atlas does not support one-way latency measurements; however, these were not used by most TTM users and also required special, expensive equipment. The article is available in full at: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services We will contact individual TTM hosts shortly to make arrangements to decommission their TTM systems. We are also investigating the possibility of creating an archive of TTM measurement results that can be used for research purposes. As previously mentioned, RIPE Atlas, and specifically RIPE Atlas anchors, provide much of the functionality of TTM. More details about the features and benefits of RIPE Atlas anchors, including information about how you can host a RIPE Atlas anchor, are available at: https://atlas.ripe.net/about/anchors/ We look forward to any feedback or questions you may have regarding this development. Regards, Romeo Zwart Global Information Infrastructure Services Manager RIPE NCC

2 2