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

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

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

Milestone reached: 50 RIPE Atlas anchors! Latest six are...
by Vesna Manojlovic 02 Apr '14

02 Apr '14

Dear colleagues, We are proud to announce that six new RIPE Atlas anchors have been activated since my previous announcement two weeks ago: - es-bcn-as13041, hosted by CSUC in Barcelona, Spain - se-sto-as8674, hosted by Netnod in Stockholm, Sweden (RIS RRC) - ie-dub-as1213, hosted by HEAnet in Dublin, Ireland - de-kel-as13101, hosted by Ennit Server in Kiel, Germany - tn-tun-as5438 , hosted by ATI in Tunis, Tunisia - za-jnb-as10474, hosted by MWEB in Johannesburg, South Africa This brings the total number of anchors to 50. All RIPE Atlas anchors can be seen on this list: https://atlas.ripe.net/anchors/list/ This marks a milestone in RIPE Atlas deployment: our goal is to have 100 anchors by the end of 2014, and today we are halfway there! RIPE NCC team is proud of the achievement, which was possible only through the community support. We are grateful to all the hosts, current and future ones! Congratulations, everyone! Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

2 1

New on RIPE Labs: A RIPE Atlas View of Internet Meddling in Turkey
by Mirjam Kuehne 31 Mar '14

31 Mar '14

Dear colleagues, Please find a new article by Emile Aben on RIPE Labs: A RIPE Atlas View of Internet Meddling in Turkey https://labs.ripe.net/Members/emileaben/a-ripe-atlas-view-of-internet-meddl… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Research papers for IMC or other measurements conferences
by Vesna Manojlovic 15 Mar '14

15 Mar '14

Dear colleagues, a couple of researchers using RIPE Atlas brought this conference to my attention, and I noticed that the CFP deadline is approaching fast. I would be curious to hear if anyone else is planning to submit a paper based on RIPE Atlas data to IMC, or any other conference. Please let me know if you need some extra help from us: more credits, higher limits for usage of probes per measurements, or additional text for your paper. We would be grateful for your mention of the RIPE NCC and RIPE Atlas in your paper, and would like to invite you to share your results, after the conference, with RIPE community, either by presenting at RIPE meetings or publishing on RIPE Labs. Regards, Vesna IMC Details: http://conferences2.sigcomm.org/imc/2014/ The 2014 Internet Measurement Conference (IMC) is a three-day event focusing on Internet measurement and analysis. The conference is sponsored jointly by ACM SIGCOMM and ACM SIGMETRICS. IMC 2014 is the 14th in a series of highly successful Internet Measurement Workshops and Conferences. The ACM IMC 2014 conference will be held in Vancouver, BC, Canada on November 5-7, 2014. Call for papers deadline: 30 April http://conferences2.sigcomm.org/imc/2014/cfp.html

2 1

Additional five RIPE Atlas anchors
by Vesna Manojlovic 13 Mar '14

13 Mar '14

Dear colleagues, We are proud to announce that five new RIPE Atlas anchors have been activated since my previous announcement last month: - fr-prm-as513 by CERN in Prévessin-Moëns, France on behalf of RIPE NCC - au-mel-as38796 hosted by AusRegistry in Melbourne, Australia. - us-pao-as1280 by ISC at PAIX in United States, on behalf of RIPE NCC - ru-mow-as47764 hosted by Mail.ru Group in Moscow, Russia - ie-caw-as39122 by Blacknight Internet Solutions Ltd, Carlow, Ireland This brings the total number of anchors to 44. 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

Encouraging RIPE Atlas users to choose for public probes and measurements
by Vesna Manojlovic 11 Mar '14

11 Mar '14

Dear colleagues, One of the main goals of RIPE Atlas is to share information about Internet performance, which we collect via the active measurements performed by the thousands of probes in the RIPE Atlas network. In order to better achieve that goal, last year we suggested making even more of the collected data public. You can read the full details of this proposal on RIPE Labs: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… We asked for feedback about this proposal from the RIPE Atlas community and, based on that feedback, we have decided not to go ahead with the proposal or make any major changes to the system. We would therefore like to revise our original proposal and suggest the following, revised plan: 1. We will strongly encourage RIPE Atlas users to keep their RIPE Atlas probes public and to perform public measurements as much as possible by: - Making new probes public by default (opt-out available) whenever someone applies for a new probe - Checking the public option by default when using the web interface to create user-defined measurements - Rewarding those who make their probes and measurements public by giving them more credits than those who don’t - Requiring all research enabled by special credits to produce public measurement results - Stressing the public nature of RIPE Atlas as a measurements platform in the RIPE NCC's publications and outreach 2. We will continue to allow users to *not* mark their probes public and to schedule user-defined measurements that are not public. 3. We will improve the documentation in order to clarify exactly what information is available for probes and user-defined measurements that are marked public versus those not marked public. Because this revised plan does not involve making any significant changes to our procedures or interfaces, the implementation would take place during our regular deployment cycle. We are basing this revised plan on the reactions of the 13 RIPE Atlas users who provided feedback after we proposed our original plan (you can find more details about the feedback we received below). We would like to hear from more of you, even if you just confirm that you agree with this revised proposal. Please subscribe to the RIPE Atlas mailing list and let us know what you think: https://www.ripe.net/mailman/listinfo/ripe-atlas Regards, Vesna Manojlovic Senior Community Builder for Measurements Tools RIPE NCC Summary of the feedback (the original comments can also be found on the RIPE Atlas mailing list archives): Eleven people replied on the mailing list and two replied on RIPE Labs, with some people supporting more than one option. - Three people supported making the data more public - Six people supported keeping things the same (i.e. against removing the "not public" option) - One person suggested making the data less public - Three people suggested delaying the publication of the public results (a new suggestion) - One person was completely neutral Specific comments included: - Making the data public by default is okay, but leave the option to not make it public - If a delay in making the data public is introduced, one-off measurements should be excluded - A delay in making the data public will introduce more complexity to the system - A proposal to receive extra/fewer credits for making probes and measurements public/not public, respectively

1 0