- 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 04 Apr '14

04 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

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

New on RIPE Labs: Map a RIPE Atlas Anchor
by Mirjam Kuehne 27 Nov '13

27 Nov '13

Dear colleagues, Please find a new article, contributed by Daniel Karrenberg, on RIPE Labs: RIPE Atlas Fun - Map a RIPE Atlas Anchor. https://labs.ripe.net/Members/dfk/map-a-ripe-atlas-anchor It shows some interesting graphs based on RIPE Atlas traceroute measurements. Kind regards, Mirjam Kuehne RIPE NCC

1 0

Updates on Measurements of Typhoon Haiyan Impact
by Mirjam Kuehne 22 Nov '13

22 Nov '13

Dear colleagues, Over the last few days we published a number of updates to the original article "Typhoon Haiyan - What do We see in RIPEstat and RIPE Atlas". Please see the links on top of this page: https://labs.ripe.net/Members/emileaben/typhoon-haiyan-what-we-see-in-ripes… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Network Anomaly Detection Survey
by Mirjam Kuehne 20 Nov '13

20 Nov '13

Dear colleagues, Jan Rejchrt from the Institute of Computer Science at the Masaryk University in Brno, Czech Republic, is conducting a survey that will help develop network anomaly detection tools. Please find some more information and the link to the survey on RIPE Labs: https://labs.ripe.net/Members/jan_rejchrt/network-anomaly-detection-survey Kind regards, Mirjam Kuehne RIPE NCC

1 0

IPv6 extension headers support on RIPE Atlas
by Jen Linkova 19 Nov '13

19 Nov '13

[ This is a outcome of some online&offline discussions we have had on IETF8 ] There are some ongoing efforts to measure IPv6 extension headers filtering in the Internet (in particular, see Fernando Gont's talk: http://www.iepg.org/2013-11-ietf88/fgont-iepg-ietf88-ipv6-frag-and-eh.pdf ) While individuals are running some experiments from their networks, I think it would be extremely useful to run distributed measurements using Atlas to understand the current situation and possible impact better. Therefore it would be great if Atlas supports: - inserting Ipv6 extension headers into probe packets. Ideally user should be allowed to define a chain of extension headers as specified in RFC2460. In particular, it would be nice to insert the following headers: -- Hop-by-Hop Options -- Fragment -- Destination Options - HTTP measurements (Tim, please add particular requirements if you have any). If anyone else would like to see such features supported by Atlas - please speak up! -- SY, Jen Linkova aka Furry

15 20

New on RIPE Labs: Measuring Google's Public DNS
by Mirjam Kuehne 11 Nov '13

11 Nov '13

Dear colleagues, Geoff Huston gave an interesting presentation at the recent IEPG meeting in Vancouver about Google's Public DNS service and who is using it. You can now read the results on RIPE Labs: https://labs.ripe.net/Members/gih/measuring-googles-public-dns Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Typhoon Haiyan - What do We see in RIPEstat and RIPE Atlas
by Mirjam Kuehne 08 Nov '13

08 Nov '13

Dear colleagues, Please find a new article on RIPE Labs: Typhoon Haiyan - What do We see in RIPEstat and RIPE Atlas https://labs.ripe.net/Members/emileaben/typhoon-haiyan-what-we-see-in-ripes… For now we only see a modest effect of typhoon on the Philippine Core Internet Infrastructure. Kind regards, Mirjam Kuehne RIPE NCC

1 0

Asking methods to monitor used IPs
by Jahangir Asadi 07 Nov '13

07 Nov '13

Dear Sir or Madam I have some customers who I have allocated high band width with wide ranges of IPv4 addresses to. Because of lack of IPv4, I would like to see that how many IPs they are using. It would be grateful if you tell me how can I do this and what soft ware I have to use to monitor the used IPs. I would like to thank you in advance and I am looking forward to hearing from you soon. Regards. Jahangir Asadi Network Manager of Padidar Information Technology (Your LIR Member and the owner of AS198357)

4 3

Announcing the RIPE Atlas Anchors Service
by Vesna Manojlovic 07 Nov '13

07 Nov '13

Dear colleagues, We're pleased to announce that RIPE Atlas anchors went into production at the RIPE 67 Meeting in Athens in October 2013. Anchors are both enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. The RIPE Atlas anchors pilot ran for a year, and now there are 15 anchors deployed. The RIPE NCC's goal is to have 50 anchors in operation around the world by the end of 2014. We are now actively seeking applications from those interested in and capable of hosting a RIPE Atlas anchor in their own networks. Find out what RIPE Atlas anchors are all about, the benefits of hosting an anchor, and how you can get involved: https://labs.ripe.net/Members/suzanne_taylor_muzzin/announcing-the-ripe-atl… Regards, Vesna

1 0

Re: [mat-wg] IPv6 extension headers support on RIPE Atlas
by Mikael Abrahamsson 06 Nov '13

06 Nov '13

On Wed, 6 Nov 2013, Ole Troan wrote: > wouldn't it be sufficient to support the fragment header initially? I am mostly interested in extension- and fragment header, and combinations of these. The others you're right about, they probably won't work well anyhow. But extension nnd fragment headers have real legitimate use and we should try to assure that these work properly on the wider Internet. If someone at the edge decides they don't want these then that's fine, but if there are routers out there that by default treat these badly, I think it's good if everybody knows this. -- Mikael Abrahamsson email: swmike(a)swm.pp.se

1 0

New on RIPE Labs: How “National” is the Dutch Critical IP Infrastructure?
by Mirjam Kuehne 23 Oct '13

23 Oct '13

Dear colleagues, For those of you who missed Razvan C. Oprea's presentation during the MAT-WG in Athens, we put a summary report on RIPE Labs: How “National” is the Dutch Critical IP Infrastructure? https://labs.ripe.net/Members/benno_overeinder/dutch-critical-ip-infrastruc… This is a contribution by Benno Overeinder, Fahimeh Alizadeh and Razvan C. Oprea. Kind regards, Mirjam Kuehne RIPE NCC

1 0

Traceroute visualisation
by Mike Hughes 18 Oct '13

18 Oct '13

Good talk by Emile on visualisation of traceroutes and the various sources of geo-loc that can be munged and derived to try and give more accurate info. While there was talk of commercial geo-loc such as Maxmind, what about mining the DNS for LOC records? Has there been any investigation of that? Or am I just an ossified dinosaur, talking about LOC records? :) Cheers, Mike

5 4

Ambient measurements
by Richard Barnes 18 Oct '13

18 Oct '13

Hey all, As a follow-up to Mikael's point in AOB at the MAT meeting today (that there are lots of statistics already being kept by hosts, e.g., in TCP stacks): I did a presentation at the IEPG back at the Beijing IETF about the idea of standardizing a "Network Measurement Reporting" language, so that things like ping and traceroute could share their results with the rest of the Internet. <http://iepg.org/2010-11-ietf79/NMR-IEPG.pdf> It's long enough ago that I don't remember precisely what the feedback was. But no further work got done, so it probably wasn't that positive :) Nonetheless, I continue to think that collecting ambient measurement data is a really interesting idea, so it would be cool to hear what others here think. Cheers, --Richard

2 1

Completed Migration of RIS Visualisation to RIPEstat
by Vesna Manojlovic 08 Oct '13

08 Oct '13

Completed Migration of Routing Information to RIPEstat Dear colleagues, We have now successfully completed the planned* migration of RIS data visualisation to RIPEstat: http://stat.ripe.net Our Routing Information Service (RIS) has been collecting global BGP routing information for over 12 years. During this period, many different interfaces to analyse and visualise accumulated data have been developed. Therefore, we have centralised access to the RIS interfaces and tools, and decommissioned some of the outdated interfaces and the old backend. This is in line with our long-term goal to provide more consolidated services, as communicated previously by our Chief Information Officer, Kaveh Ranjbar, in his article, "The Future of RIPE NCC Technical Services": https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services More information about the migration of RIS data visualisation to RIPEstat is available on RIPELabs: https://labs.ripe.net/Members/fatemah_mafi/improved-routing-information-ava… Please submit any requests for additional features via email to stat(a)ripe.net so that we can add these to the RIPEstat Roadmap and include them in our planning: http://roadmap.ripe.net/ripe-stat/ We look forward to your feedback. Regards, Vesna * The original announcement and the reminder can be found at: http://www.ripe.net/ripe/mail/archives/mat-wg/2013-August/000323.html http://www.ripe.net/ripe/mail/archives/mat-wg/2013-September/000350.html

1 0

Announcing RIPE Atlas Service Terms Documentation for Anchor Hosts
by Vesna Manojlovic 03 Oct '13

03 Oct '13

Dear colleagues, In the process of transitioning RIPE Atlas anchors towards being a production service, we have developed two documents that describe the service terms: - Draft RIPE Atlas Service Terms and Conditions - Memorandum of Understanding - Hosting a RIPE Atlas Anchor Probe Please see the details in this RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-anchors-terms-and-conditions If you are currently hosting an anchor, or if you are interested in hosting a RIPE Atlas anchor in the future, we would like to hear any feedback you have on these draft documents. Our goal is to finalise the documents by 11 October so that we can announce the production service at the upcoming RIPE 67 Meeting in Athens. Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0

New on RIPE Labs: RIPE Atlas - Packet Size Matters
by Mirjam Kuehne 02 Oct '13

02 Oct '13

Dear colleagues, This new RIPE Labs article (contributed by Emile Aben) talks about trying to send large packets over the Internet. Above a certain size, these packets will have to be fragmented, which is known to cause problems. In both IPv4 and IPv6, we see approximately 10% of RIPE Atlas probes that are unsuccessful in pings with fragmented packets, while they don't encounter problems with smaller unfragmented packets. Please find the detailed results on RIPE Labs: https://labs.ripe.net/Members/emileaben/ripe-atlas-packet-size-matters Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Recent Internet Disruptions in Sudan
by Mirjam Kuehne 26 Sep '13

26 Sep '13

Dear colleagues, Please see this new article on RIPE Labs showing the recent Internet disruption in Sudan as viewed in RIPEstat and RIPE Atlas: https://labs.ripe.net/Members/emileaben/sudan-internet-disruptions Kind regards, Mirjam Kuehne RIPE NCC

1 0

RIPE NCC is Migrating the RIS Dashboard to RIPEstat
by Vesna Manojlovic 25 Sep '13

25 Sep '13

Dear colleagues, I would like to remind you of our announcement, made last month. In the coming days, we will be migrating RIS data visualisation to RIPEstat: http://stat.ripe.net We will, therefore, be decommissioning some of the outdated RIS interfaces and tools, and the old backend. We still welcome your feedback, so please let us know your comments so that we can accommodate your needs. More information can be found in the original announcement, below. Regards, Vesna Manojlovic Our Routing Information Service (RIS) has been collecting global BGP routing information for 12 years now. During this period, many different interfaces to analyse and visualise accumulated data have been developed. In line with our long-term goals to provide more consolidated services, we will be integrating the RIS interface's tools and services into RIPEstat. More information about this is detailed in a new RIPE Labs article: https://labs.ripe.net/Members/fatemah_mafi/improved-routing-information-ava… We invite the community to comment on these upcoming changes at MAT-WG. Please submit any requests for additional features via email to stat(a)ripe.net so that we can implement these along with the planned migration of tools and features, or have them added to the RIPEstat Roadmap for later consideration: http://roadmap.ripe.net/ripe-stat/ We look forward to your feedback. Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0

Re: [mat-wg] [atlas] "Spoofing" tests.
by Andrei Robachevsky 18 Sep '13

18 Sep '13

[copying mat-wg, since it is about measureents] Lorenzo Colitti wrote on 9/18/13 6:42 AM: > On Sun, Sep 15, 2013 at 11:57 AM, Randy Bush <randy(a)psg.com > <mailto:randy@psg.com>> wrote: > > then again, if you think most of the botnets are behind broadband home > networks, it makes an interesting sample. compare spoof density of > natted vs un-natted. but then, how you gonna spoof from behind a nat? > > > Just send the packet? > > I expect a nontrivial proportion of NATs will just say "Source address > not in 192.168.1.0/24 <http://192.168.1.0/24>? Cool, don't have to NAT! > Just pass it along." :-) If only we had data ;). It would be interesting, indeed, to see how feasible spoofing is in a natted environment, broadband access networks in particular. It seems that this is the case where spoofing may cause serious problems to the provider itself, as opposed to someone else in the Internet. So, one could assume that even if there are NATs that allow this stupid thing, there maybe DOCSIS SAV and other safeguards in the BB provider provisioning system. Andrei

1 0

New on RIPE Labs: RIPE Atlas Anchors: Summary and Next Steps
by Mirjam Kuehne 16 Sep '13

16 Sep '13

Dear colleagues, This new RIPE Labs article summarises the findings from the pilot phase of the RIPE Atlas anchors project, and gives details about the decision to move to production using a one-service, smaller box for RIPE Atlas anchors: https://labs.ripe.net/Members/becha/ripe-atlas-anchors-pilot-summary-and-ne… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Further Virtualisation Testing for RIPE Atlas Anchor
by Mirjam Kuehne 16 Sep '13

16 Sep '13

Dear colleagues, Please find a new article on RIPE Labs: "Further Virtualisation Testing for the RIPE Atlas Anchor" https://labs.ripe.net/Members/romeo_zwart/further-virtualisation-testing-fo… This report is a follow up to an earlier article, in which we detailed our investigations into the use of virtualisation technology as a suitable means to provide other services via the RIPE Atlas anchor hardware, beyond its primary anchor function. Kind regards, Mirjam Kuehne RIPE NCC

3 4

Draft agenda for MAT @ RIPE67
by Christian Kaufmann 13 Sep '13

13 Sep '13

Hello All, This is the draft agenda for the MAT - Measurement, Analysis and Tools Working Group session at RIPE67: A. Introduction Welcome, Scribe, Jabber, Agenda B. Luciano Lenzini: Mobile network measurement app for Android (20min) C. Vesna Manojlovic: RIPEstat update (10min) D. Robert Kisteleki: Infrastructure geolocation using RIPE NCC data sets (15min) E. Razvan Oprea: Mapping Dutch critical infrastructure (20min) F. Vesna Manojlovic: RIPE Atlas update (RIPE NCC) (20min) Z. AOB Timings are approximate. The session will take place at 16:00 local time on Thursday 17th October. See you in Dublin! Richard & Christian

1 0

Using Atlas for commercial services
by Stephane Bortzmeyer 12 Sep '13

12 Sep '13

[Originally discussed on the RIPE Atlas users mailing list and forwarded here per suggestion of Daniel Karrenberg, to be sure the proper WG has a say.] After reading the Atlas ToS <https://atlas.ripe.net/service-rules/> and checking the FAQ <https://atlas.ripe.net/about/faq/>, I still have a question: Can I use Atlas as a basis for commercial services? The ToS is silent about it. The list in <https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services> gives interesting ideas about new uses of Atlas (specially the part about using Atlas to monitor reachability from Nagios, which could become a service sold to people). Of course, Atlas is "best effort", so one cannot sue the RIPE-NCC if it breaks and stops the commercial service. But it still can be an interesting platform. Today, most Atlas uses seem to be for public research, or for "selfish" measurements (checking my network), including by commercial organisations. But I see nothing forbidding people to sell services (monitoring, quality assessment) to other people, based on Atlas. Is it a good idea to explicitely allow or disallow such services?

7 12

New on RIPE Labs: Visualising Bandwidth Capacity and Network Activity in RIPEstat Using M-Lab Data
by Mirjam Kuehne 09 Sep '13

09 Sep '13

Dear colleagues, As a result of the cooperation between the RIPE NCC and Measurement Lab, you can now visualise the bandwidth profiles and network activity of IP prefixes and individual countries in RIPEstat. For more details, please refer to this new article on RIPE Labs: https://labs.ripe.net/Members/vastur/visualising-bandwidth-capacity-in-ripe… Kind regards, Mirjam Kuehne RIPE NCC

1 0