- mat-wg - mailman.ripe.net

New on RIPE Labs: RIPE Atlas: Latest Results API and Parsing Library
by Mirjam Kuehne 29 Apr '14

29 Apr '14

Dear colleagues, You can now get the latest results from any of your user-defined measurements with a new API created specifically for this purpose. In addition, we've developed a parsing library that can be used in combination with the new API to make it an even more useful tool. Please find more details on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-resul… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Draft agenda for MAT @ RIPE68
by Christian Kaufmann 23 Apr '14

23 Apr '14

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE68: A. Introduction: Welcome, Scribe, Jabber, Agenda (5m) B. Results: Interconnection density in IPv4 / IPv6 - Christian Kaufmann (15m) C. RIPE Atlas update - Vesna Manojlovic (RIPE NCC) (15m) D. Measuring Access Network Performance using Atlas - Vaibhav Bajpai (Jacobs U.) (20m) E. Fast Internet-wide Scanning and its Security and Measurement Applications - Zakir Durumeric (U. Michigan) (20m) F. RIPEstat update - Vesna Manojlovic (RIPE NCC) (15m) Z. AOB Timings are approximate. The session will take place at 16:00 local time on Thursday 15th May. See you in Warsaw! Richard & Christian

1 0

Call for Presentations at RIPE 68
by Richard Barnes 05 Apr '14

05 Apr '14

Dear MAT WG, We co-chairs are beginning to put together the agenda for the MAT working group meeting at RIPE 68. If you have something you would like to present, please let us know no later than Monday, 14 Apr 2014. Thanks a lot, Richard Barnes and Christian Kaufmann MAT Co-Chairs

1 0

New on RIPE Labs: BGP Leaks in Indonesia
by Mirjam Kuehne 04 Apr '14

04 Apr '14

Dear colleagues, We looked in some more detail at the BGP leak in Indonesia. Please find our analysis on RIPE Labs: https://labs.ripe.net/Members/wilhelm/bgp-leaks-in-indonesia Kind regards, Mirjam Kuehne RIPE NCC

1 0

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

New on RIPE Labs: Improved RIPE Atlas Probe Pages
by Mirjam Kuehne 28 Feb '14

28 Feb '14

Dear colleagues, We've made it easier to get an overview of the history and measurements for all the public probes in the RIPE Atlas network. Read about that and other new functionality on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-improved-pro… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Question about RIPE services
by ceo＠foodee.ru 22 Feb '14

22 Feb '14

Hello! Our company conducts researh and development in Software-Defined Networking. And we are looking for a testbeds and production networks to implement our techniques. We have already tested our prototype successfully in mininet.org, onl.wustl.edu . Has RIPE resourses which could be used to test SDN techniques: slices, ect.? Thank you.

1 0

New on RIPE Labs: Using RIPE Atlas to Investigate Slow Servers
by Mirjam Kuehne 18 Feb '14

18 Feb '14

Dear colleagues, Please find a new article on RIPE Labs contributed by Nathan Howard who used RIPE Atlas to investigate slow running servers at their company: https://labs.ripe.net/Members/suzanne_taylor_muzzin/using-ripe-atlas-to-inv… Kind regards, Mirjam Kuehne RIPE NCC

1 0

... and six more RIPE Atlas anchors activated
by Vesna Manojlovic 13 Feb '14

13 Feb '14

Dear colleagues, We are proud to announce that six new RIPE Atlas anchors have been activated since my previous announcement last month: - se-sto-as59521, hosted by Aivivid in Stockholm, Sweden. - hu-bud-as12303, by BIX in Budapest, Hungary on behalf of RIPE NCC - fr-vbn-as199422, hosted by Rezopole/LyonIX in Lyon, France. - is-rey-as25509, hosted by Hringiðan in Reykjavik, Iceland. - nl-arn-as1140, hosted by SIDN in Arnhem, Netherlands - at-vie-as1120, by VIX in Vienna, Austria, on behalf of RIPE NCC This brings the total number of active anchors to 39. 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

Using RIPE Atlas for monitoring: introducing "Status Checks"
by Vesna Manojlovic 12 Feb '14

12 Feb '14

Dear colleagues, Status Checks is a new feature that allows you to integrate RIPE Atlas into any monitoring tool you currently use, such as Nagios or Icinga. Please find a new article on RIPE Labs that explains simple steps, gives an example, and points to our future plans: https://labs.ripe.net/Members/suzanne_taylor_muzzin/introducing-ripe-atlas-… Direct link: https://atlas.ripe.net/docs/status-checks/ We are pleased to announce this feature that the operators community has been asking for, and we are looking forward to both your feedback and success stories. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: The Seismograph User Guide
by Suzanne Taylor Muzzin 12 Feb '14

12 Feb '14

Dear colleagues, Please find a new article on RIPE Labs that explains how you can get the most out of the Seismograph, an interactive RIPE Atlas tool that provides an overview of different RTT and packet loss trends measured by multiple RIPE Atlas probes. The Seismograph User Guide https://labs.ripe.net/Members/massimo_candela/seismograph-user-guide Kind regards, Suzanne Taylor Muzzin Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: Increased Reach of RIPE Atlas Anchors
by Michela Galante 29 Jan '14

29 Jan '14

Dear colleagues, Please take a look at the latest news about RIPE Atlas anchors in the RIPE Labs article published today, "Increased Reach of RIPE Atlas Anchors": https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-anchors-janu… Kind regards, Michela Galante Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: The Many Instances of L-root
by Mirjam Kuehne 20 Jan '14

20 Jan '14

Dear colleagues, Please find a new article on RIPE Labs contributed by Stephane Bortzmeyer: The Many Instances of the L-root Name Server https://labs.ripe.net/Members/stephane_bortzmeyer/the-many-instances-of-the… Kind Regards, Mirjam Kuehne RIPE NCC

1 0

RIPEstat 2013: A Year In Review
by Michela Galante 17 Jan '14

17 Jan '14

Dear colleagues, 2013 was a year of big changes for RIPEstat. Take a look at the most exciting advancements from the year, in the new article on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestat-2013-year-in-r… Kind regards, Michela Galante Measurements Community Building RIPE NCC

1 0

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

Newest RIPE Atlas features - seizmograph improvements & more
by Vesna Manojlovic 15 Jan '14

15 Jan '14

Dear colleagues, we are proud to announce the latest features added to RIPE Atlas in the previous few months: - time selection in seizmograph: zoom, and calendar menu; - filtering probe by country & ASN on maps & seizmograph - one-off SSL measurements ... and much more! Please find out the details on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-update-janua… We are looking forward to your feedback! Regards, Vesna -- Measurements Community Building team RIPE NCC

1 0

Call for Presentations: RIPE 68, 12-16 May 2014 in Warsaw, Poland
by Benno Overeinder 14 Jan '14

14 Jan '14

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 68 will take place from 12-16 May 2014 in Warsaw, Poland. 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 68. 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://ripe68.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 2 March 2014, using the meeting submission system at https://ripe68.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://ripe68.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://ripe68.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 panelists, presenters and moderators. - Due to potential technical issues, it is expected that most, if not all, presenters/panelists 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

New on RIPE Labs: How Many RIPE Atlas Probes Can Resolve IPv6-only Domain Names?
by Mirjam Kuehne 13 Jan '14

13 Jan '14

Dear colleagues, Please find a new article on RIPE Labs submitted by Stéphane Bortzmeyer: How Many RIPE Atlas Probes Can Resolve IPv6-only Domain Names? https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-ripe-atlas-probe… Kind regards, Mirjm Kuehne RIPE NCC

1 0

RIPE Atlas 2013: A Year In Review
by Michela Galante 13 Jan '14

13 Jan '14

Dear colleagues, 2013 was an exciting year for RIPE Atlas. Take a look at what you helped us to achieve in 2013, in the new article on RIPE Labs: https://labs.ripe.net/Members/michela_galante/ripe-atlas-2013-year-in-review Kind regards, Michela Galante Measurements Community Building RIPE NCC

1 0

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