- mat-wg - mailman.ripe.net

Announcing RIPE Atlas Anchors, Pilot Phase
by Vesna Manojlovic 31 Aug '12

31 Aug '12

Dear colleagues, [apologies for duplicate messages] Please find a new article on RIPE Labs describing the details of RIPE Atlas Anchors: https://labs.ripe.net/Members/dfk/ripe-atlas-anchors Right now, we are looking for a small number of pilot hosts from the RIPE NCC membership for deployment to begin in October 2012. If you are interested, please contact me or Daniel Karrenberg before the RIPE65. We will be discussing further details at the RIPE meeting. Regards, Vesna Manojlovic -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder +31205354444 for Measurements Tools RIPE NCC http://ripe.net

1 0

DNS & SSL certificate measurements available as RIPE Atlas UDMs
by Vesna Manojlovic 28 Aug '12

28 Aug '12

Dear MAT-WG, I am happy to announce DNS & SSL certificate measurements, a new addition to the RIPE Atlas UDMs, making it in total 4 types of customized measurements available to RIPE Atlas hosts & RIPE NCC members. Please find out the details in the RIPE Labs article: https://labs.ripe.net/Members/becha/dns-user-defined-measurements-in-ripe-a… Please let us know what you think, and enjoy the measurements :) If you have a success-story to share, consider giving a presentation at the RIPE65, or writing RIPE Labs article. I am willing to work on this together with you, so do let me know if you need any help. Regards, Vesna

1 0

RIPE Atlas Roadmap: monthly update: August
by Vesna Manojlovic 08 Aug '12

08 Aug '12

Dear colleagues, While developing RIPE Atlas, we wish to keep community involved and informed. We are maintaining a roadmap of the features we are working on, and with this update we are asking for feedback, so that we can use it as guidance for making further plans. You can find much more details are in the RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-roadmap-august-2012-update Here I only want to copy the plans for next 4-6 weeks, and three months after that, and to repeat the questions from the article: Plans for the next month: * Users can get more flavors of customized measurements: DNS & SSL - new wizard for two new types of measurements, currently beta-tested * Making it possible to download measurements results without having to be logged in - by deploying & enabling API Keys * Making it easier to follow the rate of deployment of probes over time - by updating the graphs that show the distribution and status of probes * Atlas hosts and sponsors can meet developers during RIPE65, Amsterdam - exchange experiences, give feedback and requirements - so developers can adjust priorities Plans for Q4 2012: * Installing Atlas Anchors as new targets for pre-defined measurements - this will offer greater topological diversity for measurements - Atlas Anchors will also become powerful probes, capable of performing more measurements then small probes * In order to remind you if the probe is not plugged in or if it is down - we will add more automatic email notifications of events * We will create Internet Traffic Maps based on Atlas data - maps will illustrate the health (e.g. reachability) of measured networks Questions: - About the current functionality: what do you want us to improve? - About additions to the next release: what are the most-wanted features for each one of them? - And finally, from the less-specific planned functionalities that we will work on three-six months from now: - what do you find most important? - to which one of them shall we give most priority? Thank you for your feedback, and see you soon in Amsterdam, Vesna

1 0

RIR prefix size distribution in RIPEstat
by Vesna Manojlovic 08 Aug '12

08 Aug '12

Dear colleagues, last week new RIPE Labs article was published: https://labs.ripe.net/Members/becha/rir-prefix-size-distribution-in-ripestat RIPEstat developers have created another visual interpretation of RIR "delegations" data: an interactive widget in which you can query for any address space prefix (0/0, 2000::/3 or 5/8, for example) and receive a prefix size distribution as an output: https://stat.ripe.net/widget/rir-prefix-size-distribution A data call API is also available for the scripting and creating your own favorite filters. We are interested in your feedback: - do you find this useful? - how can we improve it, so that it suits your needs even better? Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder +31205354444 for Measurements Tools RIPE NCC http://ripe.net

1 1

New on RIPE Labs: RIPE NCC Active Measurements of World IPv6 Launch Dataset
by Mirjam Kuehne 27 Jul '12

27 Jul '12

Dear colleagues, Please find a new article on RIPE Labs: "RIPE NCC Active Measurements of World IPv6 Launch Dataset" https://labs.ripe.net/datarepository/data-sets/ripe-ncc-active-measurements… Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Fwd: New on RIPE Labs: Test your IPv6 Reachability by Using RIPE Atlas (now visualised)
by Mirjam Kuehne 17 Jul '12

17 Jul '12

[apologies for duplicate mails] Dear colleagues, As announced in earlier, it is possible for RIPE NCC members to do IPv6-traceroutes from all RIPE Atlas probes to IPv6 destinations. In this new article on RIPE Labs we present a first experimental analysis and a prototype visualisation of the traceroute results: https://labs.ripe.net/Members/emileaben/visualise-your-ipv6-connectivity-us… Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Recent RIPEstat improvements
by Ann Barcomb 11 Jul '12

11 Jul '12

Hello, We have recently released several improvements to RIPEstat which we would like to inform you of. First, we have improved the amount of information available about each widget. If you click on the 'Info' link, you will see information about data sources, data timeliness, and interpretation of the visualisation. Second, the Object Browser for the RIPE DB is now serving up realtime data! Try out the Object Browser: https://stat.ripe.net/widget/object-browser This change has also been documented in the Object Browser article on RIPE Labs: https://labs.ripe.net/Members/becha/ripestat-objects-browser-for-ripe-datab… Third, the Address Space Hierarchy widget can now optionally query the APNIC database. This is the first step toward offering results independent of the data source. Try out the Address Space Hierarchy widget: https://stat.ripe.net/widget/address-space-hierarchy The related RIPE Labs article was also updated: https://labs.ripe.net/Members/becha/ripestat-address-space-hierarchy-widget Kind Regards, Ann -- Ann Barcomb RIPE NCC Community Builder http://www.ripe.net Measurements Community Building +31 20 535 4444

1 0

New Version of RIPEstat Mobile App
by Mirjam Kuehne 11 Jul '12

11 Jul '12

Dear colleagues, A new version of the RIPEstat mobile app is available now. Please find more details on RIPE Labs: https://labs.ripe.net/Members/becha/new-version-ripestat-mobile Kind regards, Mirjam Kuehne RIPE NCC

1 0

Short update on TTM service
by Vesna Manojlovic 05 Jul '12

05 Jul '12

Dear colleagues, We received a lot of feedback from the community after we announced our proposal to discontinue TTM at RIPE 64. After reviewing the RIPE community's feedback and reevaluating our own planning, we are pleased to announce that we will continue supporting TTM until sometime in 2013. As presented during the MAT Working Group and RIPE NCC Services Working Group sessions at RIPE 64, we plan to implement RIPE Atlas Anchors and to migrate DNSMON functionality to RIPE Atlas. We will do this in parallel to the current TTM infrastructure in order to give the RIPE community enough time to build confidence in and test the new infrastructure. We will give you more details about transition in early September and look forward to discussing our proposed plans with you at RIPE 65 in Amsterdam. If you are a TTM host you have received a more detailed version of this email, if this is not the case then please contact with me and I would be more than happy to provide further information for you. I wish you relaxed summer holidays. Kind regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder +31205354444 for Measurement Tools RIPE NCC http://ripe.net

2 1

New on RIPE Labs: A Use Case for IPv6 Reachability Testing with RIPE Atlas
by Mirjam Kuehne 03 Jul '12

03 Jul '12

Dear colleagues, Please see a new article on RIPE Labs describing a use case for the recently released RIPE Atlas IPv6 reachability test. https://labs.ripe.net/Members/becha/world-ipv6-launch-ripe-atlas-use-cases Kind regards, Mirjam Kuehne RIPE NCC

1 0

RIPE Atlas / UDM as a replacement for TTM
by Gert Doering 19 Jun '12

19 Jun '12

Hi, things have been strangely silent on the topic of "the end of the TTM boxes" after the last RIPE meeting - so let me try to stir this somewhat. I've been told that UDMs in Atlas "can do what I need" (use RIPE measurements to prove to our customers that our Internet reachability is good). It might, but I find it surprising painful, as I can only request pings from "10 probes at a time" in the UDM - and for reasonable accuracy, we'd need something of at least the size of TTM (100+ probes), or *better*, as we know that individual Atlas probes are not expected to have the same network stability as a TTM box ("always up. ALWAYS!") - setting up 30 or more individual UDMs to get 150 clients each to ping our two TTM boxes is... not the way to go. Second, I'm a bit confused how to automatedly download the .json-format UDM results - while I'm logged in, clicking on the link gives me a nice .json download, but when using the same link with wget, I get a login page. I'm not overly willing to download 30 UDM result files manually every day - so there must be some way to use "wget" etc. to get these data files... any hints on that? Example link: https://udm01.atlas.ripe.net/atlas/udm_download.json?attach=1&msm_id=100200… Third, we still need reasonable ping targets in our network, that are sort of "not under our control" (to meet the goal of "the RIPE NCC does these measurements, they are neutral, so we're not faking anything here") - and that are not part of the normal network churn that www.space.net or one of our routers might have. So far we use the TTM boxes for that - but they might die of old age some day... Which brings back the topic of the Atlas Anchor boxes... any news on that? Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279

4 6

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