- mat-wg - mailman.ripe.net

New on RIPE Labs: Changes to RIPE Atlas Raw Data Structure
by Mirjam Kuehne 18 Jun '12

18 Jun '12

Dear colleagues, With the introduction of a new firmware version for RIPE Atlas probes, the structure of the measurement results will be changing. Anyone making use of the raw results is advised to read about these upcoming changes on RIPE Labs: https://labs.ripe.net/Members/emileaben/ripe-atlas-data-structure-changes We also suggest to subscribe to our RSS feed to be notified of future firmware releases. Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Uptake of RIPEstat IPv6 Launch DNS Widget
by Mirjam Kuehne 18 Jun '12

18 Jun '12

Dear colleagues, For World IPv6 Launch, the RIPE NCC offered a RIPEstat DNS widget. This article looks at the response to this offering: https://labs.ripe.net/Members/becha/world-ipv6-launch-ripestat-case-studies Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: De-bogonising 128.0.0.0/16
by Mirjam Kuehne 15 Jun '12

15 Jun '12

[apologies for duplicates] Dear colleagues, Please find an update on RIPE Labs about our effort to help network operators clean-up redundant settings with respect to 128.0.0.0/16 https://labs.ripe.net/Members/mirjam/de-bogonising-128.0.0.0-16 Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Adding Interactivity to Embedded RIPEstat Widgets
by Mirjam Kuehne 01 Jun '12

01 Jun '12

Dear colleagues, It's been possible to embed RIPEstat widgets for some time. You can now also include a resource bar so that your site's visitors can query resources via RIPEstat on your website. Please find more information on RIPE Labs: https://labs.ripe.net/Members/becha/adding-interactivity-to-embeded-ripesta… Kind regards, Mirjam Kuehne RIPE NCC

1 0

new on RIPE Labs: RIPEstat DNS Widget for World IPv6 Launch
by Mirjam Kuehne 25 May '12

25 May '12

Dear colleagues, RIPEstat has a new DNS widget for World IPv6 Launch. The widget can be included in any website where you'd like viewers to be able to perform IPv6 (and IPv4) DNS lookups or view your site's DNS details. Please find more details on RIPE Labs: https://labs.ripe.net/Members/becha/ripestat-dns-widget-for-world-ipv6-laun… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New CIDR navigation in RIPEstat Address Space Hierarchy widget
by Mirjam Kuehne 23 May '12

23 May '12

Hello, Please find the new RIPEstat CIDR navigation feature in the Address Space Hierarchy widget. It is now documented on RIPE Labs: https://labs.ripe.net/Members/becha/ripestat-address-space-hierarchy-widget… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Ripe Probes and Android
by Stefan Wahl 16 May '12

16 May '12

Hi, as promised in Ripe64, I want to introduce Ingo Albrecht. He is the person, who is in charge and the owner of the project "Android and Atlas Probes". He sent me a paper called "inital-concept", which I would like to copy to the mailing-list. I hope that we will get a lot of feedback and make progress in defining and funding the project. greetings from Berlin Stefan Wahl Ingo Albrecht: GENERAL CONCEPT The client should implement a proper subset of the features present in the web interface, limiting itself to the most common and most operationally useful features. As such, emphasis should be given to "general" information that has use in network operations, as opposed to "specific" detailed information. Display should concentrate on displaying "current" information as opposed to browsing history, for which a laptop is much better suited. As an example, consider display of per-probe data. The client should display basic probe information and current/recent measurement results, not a whole set of graphs. Also, emphasis should be given to search as opposed to full-list browsing, facilitating ad-hoc use. DEVELOPMENT PROCESS Development would progress in monthly stages, accompanied by public release from the second stage on. The feature set specified in this document should be achievable within 3 to 5 such stages. This concept would be revised during each stage, allowing for integration of feedback. As the developer, I propose that the source code for the project, including history, be published via github or similar. FEATURES Base features: * Display of announcements * Display of "My Probes" list * Display as list * Display map of own probes * Search for probes by AS, IP4/IP6 prefix, country * Result display as list * Result display as map * Notification when a users own probes go down or stay down * Configurable "acceptable downtime" * Configurable "silent times" based on phone timezone * Probe view (reachable from probe lists and maps) * Display standing data * Display most recent measurements Basic browsing features: * View standard measurements (equivalent of "Maps" view) * Fixed destination measurements (reachability and RTT) * Limitable by probe AS and prefix * Limitable by destination * DNS measurements (instance choice and RTT) * Limitable by probe AS and prefix * Limitable by root instance continent * Limitable by specific root instance UDM features: * Display of configured UDMs * Adding/removing UDMs * Display of most recent UDM results * Possibly with history * Maybe with graphs Features not considered: Display of coverage information (not terribly useful ad-hoc).

7 6

New on RIPE Labs: Test your IPv6 Reachability by Using RIPE Atlas
by Mirjam Kuehne 09 May '12

09 May '12

[apologies for duplicate mails] Dear colleagues, You can now use RIPE Atlas to test your IPv6 reachability. This also works if you do not host a RIPE Atlas probe yourself. However, please note that this is only available to RIPE NCC members. Please find the details on RIPE Labs: https://labs.ripe.net/Members/becha/test-your-ipv6-reachability-using-ripe-… If you have any comments or questions, please let us know. Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Introducing the Android Atlas Client and myself
by Ingo Albrecht 02 May '12

02 May '12

Hello! Just as Stefan Wahl wrote, I am the guy who initially came forward with the idea of implementing an Android client for the RIPE Atlas. My professional background is as a programmer of various media systems with a lot of experience in mobile applications, high-profile showroom and media installations as well as related topics. Beyond that, being a jack of many trades, I also have experience in network operations and service hosting, both professionally and in various voluntary contexts such as open source projects. Having heard of RIPE Atlas and knowing a lot of people from the network community, I decided to step forward and offer to implement an Android application that allows proper mobile use of the Atlas. Stefan Wahl of ECIX was so kind as to announce my project at RIPE64. I am now hoping to collect further feedback. For further discussion, I have pasted my initial draft concept below. Feel free to comment, propose features and discuss. If you wish, you can also contact me directly about this project. Greetings Ingo ========================================================================= RIPE Atlas Android Client - Concept Proposal (C) 2012 Ingo Albrecht <prom(a)berlin.ccc.de> Revision 2012-04-16 21:00 CEST GENERAL CONCEPT The client should implement a proper subset of the features present in the web interface, limiting itself to the most common and most operationally useful features. As such, emphasis should be given to "general" information that has use in network operations, as opposed to "specific" detailed information. Display should concentrate on displaying "current" information as opposed to browsing history, for which a laptop is much better suited. As an example, consider display of per-probe data. The client should display basic probe information and current/recent measurement results, not a whole set of graphs. Also, emphasis should be given to search as opposed to full-list browsing, facilitating ad-hoc use. DEVELOPMENT PROCESS Development would progress in monthly stages, accompanied by public release from the second stage on. The feature set specified in this document should be achievable within 3 to 5 such stages. This concept would be revised during each stage, allowing for integration of feedback. As the developer, I propose that the source code for the project, including history, be published via github or similar. FEATURES Base features: * Display of announcements * Display of "My Probes" list * Display as list * Display map of own probes * Search for probes by AS, IP4/IP6 prefix, country * Result display as list * Result display as map * Notification when a users own probes go down or stay down * Configurable "acceptable downtime" * Configurable "silent times" based on phone timezone * Probe view (reachable from probe lists and maps) * Display standing data * Display most recent measurements Basic browsing features: * View standard measurements (equivalent of "Maps" view) * Fixed destination measurements (reachability and RTT) * Limitable by probe AS and prefix * Limitable by destination * DNS measurements (instance choice and RTT) * Limitable by probe AS and prefix * Limitable by root instance continent * Limitable by specific root instance UDM features: * Display of configured UDMs * Adding/removing UDMs * Display of most recent UDM results * Possibly with history * Maybe with graphs Features not considered: Display of coverage information (not terribly useful ad-hoc).

1 0

RIPE Atlas JSON traceroutes
by Paul Hoogsteder 19 Apr '12

19 Apr '12

Hi, has anyone written or found a tool to convert JSON output to a more human readable format, like traditional traceroute? INPUT: { "from": "80.123.123.123", "fw": 1, "msm_id": 1234567, "prb_id": 12345, "result": "traceroute to 91.228.151.2 (91.228.151.2), 30 hops max, 38 byte packets NEWLINE 1 192.168.123.123 2.087 ms 1.732 ms 1.928 ms NEWLINE 2 194.109.123.123 16.650 ms 16.570 ms 17.072 ms NEWLINE", "timestamp": 1234567890 }, OUTPUT: traceroute to 91.228.151.2 (91.228.151.2), 30 hops max, 38 byte packets 1 192.168.123.123 2.087 ms 1.732 ms 1.928 ms 2 194.109.123.123 16.650 ms 16.570 ms 17.072 ms etc. I'm hopeless as a programmer, otherwise I would have written something myself... Best regards, Paul Hoogsteder

3 2

RIPE Atlas JSON traceroutes
by Paul Hoogsteder 19 Apr '12

19 Apr '12

Hi, has anyone written or found a tool to convert JSON output to a more human readable format, like traditional traceroute? INPUT: { "from": "80.123.123.123", "fw": 1, "msm_id": 1234567, "prb_id": 12345, "result": "traceroute to 91.228.151.2 (91.228.151.2), 30 hops max, 38 byte packets NEWLINE 1 192.168.123.123 2.087 ms 1.732 ms 1.928 ms NEWLINE 2 194.109.123.123 16.650 ms 16.570 ms 17.072 ms NEWLINE", "timestamp": 1234567890 }, OUTPUT: traceroute to 91.228.151.2 (91.228.151.2), 30 hops max, 38 byte packets 1 192.168.123.123 2.087 ms 1.732 ms 1.928 ms 2 194.109.123.123 16.650 ms 16.570 ms 17.072 ms etc. I'm hopeless as a programmer, otherwise I would have written something myself... Best regards, Paul Hoogsteder.

1 0

on DNSMON
by Gilles Massen 19 Apr '12

19 Apr '12

Hello, Later this afternoon Daniel is presenting on the (non-)future of TTM and specifically DNSMON. Unfortunately I'm unable to attend even remotely, so here are a few comments on our use of DNSMON which might be useful to the discussion. While we have been hosting a TTM box for a long time, DNSMON is basically the only derived servie we have been using. We are operating a TLD, and DNSMON is currently the only way we have to monitor the overall quality and reachability of our DNS service, specifically as many of the nameservers are anycast clouds. DNSMON is used from casual checking if everything is still green, down to specific debugging of local issues, even using the raw data from time to time. So what matters to us is: - easily interpreted graphs and overviews, with the ability to drill down on servers or probes - historical information (whithin the graphs) - detailed (raw) data I have a few ideas what could be added, but these are really the functions that would be dearly missed if DNSMON were to disappear. If the data is collected by ATLAS probes or TTM boxes does obviously not matter very much. The ease of access to the information however is important. Have a nice meeting! Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473

1 0

New article on RIPE Labs: RIPEstat Address Hierarchy Widget
by Mirjam Kuehne 19 Apr '12

19 Apr '12

Dear colleagues, Please find a new article on RIPE Labs describing the Address Space Hierarchy Widget that is now available in RIPEstat: https://labs.ripe.net/Members/becha/ripestat-address-space-hierarchy-widget Kind Regards, Mirjam Kuehne RIPE NCC

1 0

New article on RIPE Labs: RIPEstat Object Browser for RIPE Database
by Mirjam Kuehne 18 Apr '12

18 Apr '12

Dear colleagues, Please find a new article on RIPE Labs describing the object browser for RIPE database objects that is now available in RIPEstat: https://labs.ripe.net/Members/becha/ripestat-objects-browser-for-ripe-datab… Kind Regards, Mirjam Kuehne RIPE NCC

1 0

RIPEstat demo report now on RIPE Labs
by Mirjam Kuehne 17 Apr '12

17 Apr '12

Dear colleagues, Please find the latest RIPEstat demo report on RIPE Labs: https://labs.ripe.net/Members/becha/ripestat-demo-s2e04 We would especially like to encourage you to fill in the RIPEstat survey: https://stat.ripe.net/survey You might win one of the RIPEstat widget t-shirts! Kind regards, Mirjam Kuehne RIPE NCC

1 0

RIPE Atlas User-Defined Measurements BoF
by Vesna Manojlovic 12 Apr '12

12 Apr '12

Dear colleagues, We will be holding a session at the RIPE meeting for people interested in discussing user-defined measurements (UDM) with RIPE Atlas. Both beta testers and people who have not yet used UDM are welcome to attend. It is scheduled for Thursday, 19 April at 17:45 in the Grand Union Hall (main room). We will begin after the end of the Measurements, Analysis and Tools (MAT) working group session (which takes place in the same room). And, if you’re lucky, you might get to taste one of the limited edition Atlas beers we’ve got on offer! More details in the Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-udm-bof Regards, Vesna

1 0

RIPE Atlas User-Defined Measurements Are Here!
by Vesna Manojlovic 11 Apr '12

11 Apr '12

Dear Atlas Hosts and Sponsors, We are pleased to announce the roll-out of user-defined measurements (UDM) for RIPE Atlas. As of today, all hosts and sponsors are invited to run custom measurements. To access UDM, either click on the link at the top right when you are logged in to the RIPE Atlas website, or go directly to: https://atlas.ripe.net/atlas/udm.html Currently, you can schedule two simultaneous measurements to the targets of your choice, from up to 10 probes. You can specify parameters like the area of the probes, IPv4 or IPv6, timing of the measurement, and type (currently ping or traceroute). And you need to have sufficient amount of credits! For the time being, we have created a fairly low rate limit, which we expect to increase over time. More information about limits, credits and other aspects of the UDM system can be found in the documentation: https://atlas.ripe.net/doc/udm Discussion and questions about UDM can be directed to the Atlas mailing list (ripe-atlas(a)ripe.net). You may also be interested in joining us at the UDM "Birds of a Feather" (BoF) session at RIPE 64 in Ljubljana, on Thursday, 19 April after the Measurements, Analysis and Tools (MAT) Working Group session. https://ripe64.ripe.net/programme/meeting-plan/bof/ Happy measuring! - The RIPE Atlas team ps We have also published a RIPE Labs article about UDM launch: https://labs.ripe.net/Members/becha/ripe-atlas-user-defined-measurements-ar…

1 0

Announcement of next RIPEstat demo now on RIPE Labs
by Mirjam Kuehne 10 Apr '12

10 Apr '12

Dear colleagues, The next RIPEstat demo will be presented live at RIPE 64 in Ljubljana on Monday, 16 April at 18:15 in White Hall (side room). After the demonstration there will be time to discuss RIPEstat development with other interested people. Please find more details on RIPE Labs: https://labs.ripe.net/Members/cteusche/ripestat-demo-s2e04 Topics for the demo include ranges, widgetisation, the RIPE Database Object Browser widget, and the Hierarchy Browser widget. If you're not able to attend the demo, there are other opportunities to meet the people behind RIPEstat and to watch a recording of the demo (see details in the article on RIPE Labs). Kind regards, Mirjam Kuehne RIPE NCC

1 0

Draft Agenda MAT-WG RIPE64
by Ian Meikle 05 Apr '12

05 Apr '12

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE64: A. Introduction Welcome, Scribe, Jabber, Agenda B. Mobile broadband measurement (20 min) Amund Kvalbein (Simula) C. RIPE NCC Measurement Strategy 2012/2013 (15 min) Daniel Karrenberg (RIPE NCC) D. Useful and Cool New Things in RIPEstat& RIPE Atlas (10 min) Vesna Manjolovic (RIPE NCC) E. APNIC measurement of IPv6 using paid advertising (20 min) George Michaleson (APNIC) F. MLab update (20 min) Tiziana Refice Z. AOB Timings are approximate, but it looks as if we have a packed and interesting programme of talks. The session will take place at 16:00 local time on Thursday 19th April. See you in Ljubljiana! Ian, Christian and Richard

1 0

New on RIPE Labs: Latest RIPEstat Demo report
by Mirjam Kuehne 20 Mar '12

20 Mar '12

Dear colleagues, Please find the report of the latest RIPEstat demo session on RIPE Labs: https://labs.ripe.net/Members/cteusche/ripestat-demo-s2e03 The third RIPEstat demo for 2012 covered all the new and modified widgets that were added in the last month: ASN Neighbours, Geolocation History, Prefix Count, Prefix Size Distribution, Routing History, and Announced Prefixes. Other new features included enabling the RIPE NCC Access login system, and links to RIPEstat from the RIPE database. It's also time for us to evaluate our demo format, so please take a moment to give us your feedback about what you like about our demos, and what you want changed. Kind Regards, Mirjam Kuehne RIPE NCC

1 0

New Geolocation History Widget in RIPEstat
by Mirjam Kuehne 13 Mar '12

13 Mar '12

Dear colleagues, Please find a new article on RIPE Labs describing the new RIPEstat 'Geolocation History Widget': https://labs.ripe.net/Members/cteusche/geolocation-history It provides information about the physical location of IP address space over time. Kind Regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Preparing RIPE Atlas for RIPE NCC Access
by Mirjam Kuehne 09 Mar '12

09 Mar '12

Dear colleagues, Please read on RIPE Labs how we prepare to migrate RIPE Atlas to RIPE NCC Access, the RIPE NCC single sign on system: https://labs.ripe.net/Members/kistel/preparing-ripe-atlas-for-ripe-ncc-acce… Kind Regards, Mirjam Kuehne RIPE NCC

1 0

virtual map of Internet on the basis of RIPE ATLAS data
by Andrei Sukhov 09 Mar '12

09 Mar '12

Dear Sirs, I am Andrei Sukhov from Samara. I would like to discuss the construction of virtual map of Internet on the basis of RIPE ATLAS data. Virtual map of the Internet Introduction Recently, numerous measuring systems like RIPE ATLAS are established to monitor the global network, organization of inter-domain routing principles and concepts of connectedness. As a rule, measurement mechanisms are based on modifications of the time-tested tools: ping and traceroute. That is, measure the round-trip time of package and the way as a sequence of routers that handle packets. In order to visualize the resulting pattern geographic maps are used with the coordinates of boxes. This picture doesn’t reflect the structure of the network. More recently, a new approach for the representation of network infrastructure is appeared in sensor networks in [1-3]. Virtual coordinate systems are designed to find the shortest route based solely on intranet information. The network selected a few points, called anchors, the number of network hops is found from these anchors to each box. This number is taken as the location of this point relative to the anchor base. Vectors defining the position of a point relative to this basis are non-negative coordinates, which makes it difficult to build the map. Special virtual conversion allows us to set the direction and pick axes. After that, each point receives a normal position on the map. Depending on the number of selected anchors we can build two-and three-dimensional maps. The building procedure Virtual maps can be constructed to render the most important Internet services, primarily for access to DNS servers and point of traffic exchange (Amsterdam-IX, for example). To do this, we need to select the four key DNS servers as anchors, with the help of a RIPE ATLAS system to measure the number of hops from different boxes to the selected points. Thus, we obtain the original data on the structure of the network. After converting the virtual coordinate system, we calculate the conventional two-dimensional coordinate and construct the corresponding 2D maps. For locations of points can be seen on the availability of new servers, remote seals show the desired location for the mirror. It seems to me important to start a discussion about what the servers selected as anchors and how to make measurements to the traceroute command issued a number of transitions to the anchors. Can you set up a RIPE ATLAS system now that it had the necessary measurements? 1. J.N. Al-Karaki, and A.E. Kamal, “Routing techniques in wireless sensor networks: a survey,” IEEE Wireless Communications, Vol. 11, pp.6-28, Dec. 2004. 2. Bachrach, J., and Taylor, C. Localization in sensor networks. Ch. 9, Handbook of Sensor Networks. Stojmenovic (Editor), John Wiley 2005. 3. D. C. Dhanapala and A. P. Jayasumana, "Topology preserving maps from virtual coordinates for wireless sensor networks," Proc. 35th IEEE Conf. on Local Computer Networks, Oct. 2010 I hope to hear from you shortly. Sincerely yours, Andrei Sukhov

1 0

RIPE64 Call for Presentations
by Christian Kaufmann 01 Mar '12

01 Mar '12

Reminder.... Dear Working Group Colleagues, RIPE 64 will take place from 16 – 20 April 2012 at the Grand Union Hotel in Ljubljana. (http://ripe64.ripe.net/). The MAT-WG session is scheduled to run between 16:00 - 17:30 CET on Thursday 19 April, though this may be subject to change as the meeting plan is still in draft. My co-chairs and I invite you to submit presentations or suggestions for content you would like to see in this session. As a reminder, the working group charter states: "The purpose of the working group is to provide a forum in which the RIPE NCC and the community can collaborate in the areas of data, tools and analysis relating to the Internet and its infrastructure, with a loose focus on monitoring, diagnosis, analysis and forecasting. It is not the purpose of the working group to compare the performance of networks for marketing purposes." If you would like to contribute anything to our session at the next RIPE meeting please email mat-wg-chairs(a)ripe.net Best regards, CK Co-chair MAT Working Group

1 0

New on RIPE Labs: RIPE NCC Access now Works for RIPEstat
by Mirjam Kuehne 29 Feb '12

29 Feb '12

Dear colleagues, The single sign on system, called RIPE NCC Access, also works for RIPEstat now. Please find more information on RIPE Labs: https://labs.ripe.net/Members/kistel/ripe-ncc-access-now-works-for-ripestat Kind regards, Mirjam Kuehne RIPE NCC

1 0