The issue of the relative sizes of the IPv4 and IPv6 Internet in BGP came up during discussion at the APNIC/APRICOT meeting held in Auckland, New Zealand earlier this year.
The third RIPE Atlas hackathon took place in Copenhagen the weekend before RIPE 72. In this article, we share the details about the hackathon and a preview of the fourth hackathon.
As our activity in the Middle East slows from now until the end of July, we take the opportunity to present a recap of the RIPE NCC's second year of operations from the Dubai office.
IP anycast has been widely used to replicate services in multiple locations as a way to deliver better performance and resilience. It has been largely employed by CDNs and DNS operators, such as on the root server system. However, there is little evaluation of anycast under stress.
After 15 years conducting training on IPv6 in over 110 countries, I’ve been asked all sorts of questions. “How do I use my IPv6 addressing space?” “What prefix size should I provide to customers?” Although I have answers to these and many other best practice related questions, the one question, which I have not been able to answer to the best of my ability, is “What is the approach of other ISPs?”. So I decided to find out.
For a while now, the number of active RIPE Atlas probes has hovered around the 9,400 mark. This means that new probes are being connected at a fast enough rate to replace failing probes, but not enough to grow the network. At the same time, the version 3 probes have problems with their USB sticks. This led us to wonder whether these two issues are related.
In May 2015, we looked at IPv4 transfers in the RIPE NCC service region and found signs of an emerging market. Both the number and size of transfers conducted under RIPE Policy showed an upward trend in the years 2013-2014. One year later, we take another look. Did this trend continue? What have been the effects of the inter-RIR transfer policy?
When Rob Blokzijl stepped down, he handed over the role as Chair of RIPE to me in the closing plenary of RIPE 68 in Warsaw, 16 May 2014. Rob had been the RIPE Chair for 25 years since 1989 and there has not been any procedure for selecting the Chair. Rob tasked me to put in place a procedure to elect my successor.
We've updated the RIPE Atlas APIs - and there's a comprehensive new manual to explain how to use them. As a result, the current (version 1) APIs are still available for now, but will be deprecated by the end of the year.
This work demonstrates the value of the results collected by RIPE Atlas independent of the original purpose for collecting them. Using all traceroute results from a particular day as an example, we first show that near real-time analysis of the result stream is feasible. Then we show that this has great potential for studying the packet layer of the Internet in general and for providing tools to network operators in particular. All this suggests a large and diverse potential for further work.