April 2013 - mat-wg - mailman.ripe.net

Full BGP full view
by Pavel V. Veselovskiy 30 Apr '13

30 Apr '13

Hello, I'm validating a new technique for finding the route between autonomous systems with the least number of transitions. This method is came from the wireless sensor networks. To compare the efficiency of this method, and BGP algorithms, we need a full BGP routing table that reflects the configuration of all the neighbors for all AS on the Internet. At first I took the BGP Full View from O-IX site http://www.routeviews.org/ And that's specifically from herehttp://archive.routeviews.org/oix-route-views/ Already in the first few tests, it was found out that these tables are incomplete, since a number of traceroutes, we have given from the servers is not suitable neighbors and a method results mismatched with the actual path, or the path is longer than the traceroute outputs. Besides knowing the total number of announced AS and counting the number of unique AS numbers for these log files (http://archive.routeviews.org/oix-route-views/), we found that these logs contains references to only about 60% of the number All advertised by AS. Recommend, please, where we can find a really complete picture of all the neighboring AS? -- Kind Regards, Pavel Veselovskiy, Samara State Aerospace University

2 1

New on RIPE Labs: New Dashboard View and More New Feature on RIPE Atlas
by Mirjam Kuehne 26 Apr '13

26 Apr '13

Dear colleagues, Our latest RIPE Atlas release includes a lot of new features, including completely new opening pages on the website for logged in users and the general public. We also have one-off measurements, APIs, new maps, probe sharing and more! Please find all the details described here: https://labs.ripe.net/Members/kistel/new-ripe-atlas-features-april-2013 Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: The BGP Visibility Scanner
by Mirjam Kuehne 24 Apr '13

24 Apr '13

[apologies for duplicates] Dear colleagues, Please find some interesting research by Andra Lutu, Marcelo Bagnulo and Olaf Maennel on RIPE Labs: "The BGP Visibility Scanner" https://labs.ripe.net/Members/andra_lutu/the-bgp-visibility-scanner The authors developed a tool that checks if prefixes have limited visibility. The article describes some of the results found after analysing many months of global routing table data. Please also note the call for feedback at the end of the article. Kind regards, Mirjam Kuehne RIPE NCC

1 0

Preliminary agenda for MAT @ RIPE66
by Richard Barnes 23 Apr '13

23 Apr '13

Hello All, This is the draft agenda for the Measurement, Analysis and Tools Working Group session at RIPE66: A. Introduction Welcome, Scribe, Jabber, Agenda B. Interconnection density in IPv4 / IPv6 - Christian Kaufmann (unconfirmed) B. IETF LMAP - Philip Eardley (BT) (unconfirmed) C. RPKI measurements - Arturo Servin (LACNIC) (unconfirmed) D. RIPE Atlas update - Vesna Manojlovic (RIPE NCC) E. RIPEstat update - Vesna Manojlovic (RIPE NCC) Z. AOB Timings are approximate. There is still some time left in our agenda and we would welcome any late submissions. Please email them to mat-wg-chairs(a)ripe.net. The session will take place at 16:00 local time on Thursday 16th May. See you in Dublin! Richard & Christian

1 0

Measuring IP address hijacking with RIPE Atlas?
by Anatole Shaw 19 Apr '13

19 Apr '13

Currently I work with Greenhost, which is a RIPE LIR that was recently the recipient of a malicious route advertisement, as described here: https://greenhost.nl/2013/03/21/spam-not-spam-tracking-hijacked-spamhaus-ip/ IP address hijacking is a real problem. How often does it happen? Which networks are being spoofed, and which networks are the victims? My sense is that we don't have solid up-to-date answers to these questions. I have some thoughts about how to detect successful IP hijacking, using empirical measurements taken from multiple network vantagepoints. I'll hold off on details for now, but I'm aware that the answer is *not* simple analysis of AS paths or traceroute output, both of which are increasingly spoofed. It seems like the RIPE Atlas probe network would be an ideal platform for this type of study. Does such a study already exist? How does one begin to propose a RIPE Atlas project? Regards, Anatole Shaw

4 6

Verifying the deployability of Multipath TCP
by Olivier Bonaventure 17 Apr '13

17 Apr '13

Dear colleagues, During RIPE66, I will present a tutorial on Multipath TCP, a major TCP extension that has recently been approved by the IETF (RFC6824). The design of Multipath TCP has been heavily influenced by various types of middleboxes that process/modify/... various fields of the IP/TCP packets. Multipath TCP is in theory capable of handling these middleboxes and either go through or at worst fallback to regular TCP. In order to check this fallback mechanism, we ask your help to perform test behing as many real middleboxes as possible. To ease the testing, we have placed a modified Linux kernel that includes Multipath TCP inside a virtualbox image, added several measurement scripts to automate the test and collect packet traces. The tests run on Linux and MacOS. They do not currently work on Windows. You can download the virtualbox image from : http://multipath-tcp.org/pmwiki.php?n=Users.AboutMeasures The script needs about 15 minutes to complete and you will have access to a trace of all the packets sent and received by your virtualbox and our server if you'd like to check the interference caused by your middleboxes. We'd appreciate tests in networks that are more likely to include middlboxes such as entreprise networks, WiFi hotspots or cellular networks. From a technical viewpoint, the tests use various applications including traceroute, ftp (to trigger NAT ALG), http, https, scp. We use multipath subflows (1 and 4) and a modified Multipath TCP kernel that provides more debugging and also three different schedulers. The first scheduler is the standard MPTCP scheduler that sends packets over the best subflows, a second scheduler that sends packets in strict round robin and a scheduler that copies each packet over all subflows to detect the impact of retransmissions. Since Multipath TCP has never been deployed/tested on a large scale, these tests might trigger some alarms from firewalls/IPS/DPI boxes that could detect unknown behaviour. If this happens, please send a report to Fabien Duchene indicating the type of alarm. All the data collected will be analysed and I plan to report on these results during the tutorial at RIPE66 Thanks for your help, Olivier Bonaventure

1 0

Recent RIPE Atlas features and developments
by Vesna Manojlovic 08 Apr '13

08 Apr '13

Dear colleagues, Please find a description of the recent RIPE Atlas features n RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-april-2013-u… Highlights: - one-off measurements & REST API for UDMs released to testers - new web-site navigation - we started shipping 3rd generation of probes We also have new ways to take part in the community, by: - adding your code to GitHub Community repository - submitting your photos of probes - meeting RIPE Atlas Ambassadors at some of the upcoming conferences We are looking forward to your feedback and questions. Regards, Vesna

1 0

RIPE66 - Call for presentations in the MAT-WG
by Christian Kaufmann 02 Apr '13

02 Apr '13

Dear Working Group Colleagues, RIPE 66 will take place from 13rd - 17th May 2013 in Dublin. (http://ripe66.ripe.net/) The MAT-WG session is scheduled to run between 16:00 - 17:30 on Thursday 16th May. My co-chair 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 & Richard Co-chair's MAT Working Group

1 0