With the MENOG 15 meeting taking place this week, we look at Internet measurements and statistics for countries in the MENOG region.
We've been working with various Internet Exchange Points (IXPs) over the last few months to see how RIPE Atlas active measurements can provide insight into how they are keeping local traffic local. This could help to improve performance and efficiency for IXPs and their members. To explore this we've created a set of python scripts to analyse Internet traffic paths between RIPE Atlas probes in a given country, and see if we can identify if they traverse IXPs.
On 14 September 2012, the RIPE NCC started allocating IPv4 addresses based on the last /8 policy. With more than two years passed, we look at the effects this had on membership numbers and demographics. We also look at what the last /8 policy meant for IPv6 uptake.
This time we explored Twitter feed visualisation with CartoDB, a map visualisation tool.
RIPE NCC Managing Director Axel Pawlik recently gave an interview about what he sees as the most important developments of 2014 and looks ahead to the big issues in 2015.
Every few months somewhere somebody will tell you that the sky is falling and the end of the Internet is close. The reasons brought up vary through a broad spectrum from superior technology to the lack of capacity. To a large extent people in the industry have become immune to these messages, for they are either unrealistic or in cases where the threat was real, the Internet responded in its usual resilient ways, adopting to the changing environment. It is this remarkable flexibility and the constant search for optimisation that has made Internet seep into every little corner of our lives and businesses.
The IPv6 Analyser is a toolset that offers our members a visual insight into all the allocations, aggregations and assignments they have made. It was announced a few weeks ago and we're seeing LIRs starting to use it. Please find below some more details about this tool.
The change to IPv6 creates new challenges to keep spam out of email. Because of the sheer size of the IPv6 space, it seems more efficient to build a domain-blocking and reputation system rather than an IP-blocking system. But how do we ensure emails over IPv6 have an authenticated domain?
The Dutch Institute for Applied Scientific Research (TNO) and a number of Dutch security companies have recently published a report on IPv6 security test methodologies.
We are in the process of implementing the policy regarding Post Depletion Adjustment of Procedures (2013-03). In this article we will give an overview of the changes we are making to the IP Analyser web interface and API, so you can accommodate your scripts and workflow. We intend to implement these changes on 16 April 2014.
Each RIPE Atlas probe has at least one DNS resolver, indicated by a DHCP reply on the local network of the probe. Irrespective of the IP address of the resolver, this server may have IPv4 and IPv6 connectivity or only IPv4 connectivity. What is the percentage among RIPE Atlas probes?
At the RIPE 67 meeting in Athens, Greece, the RIPE IPv6 Working Group ran a little experiment to test the feasibility of an IPv6-only network and to identify challenges in user experience. While the results were highly encouraging, they indicated that there is still work to be done before IPv4 can be switched off once and for all.
The RIPE NCC recently participated in a meeting of the Saudi Arabian Task Force. A well-attended event, it included presentations and discussions about IPv6 deployment strategies, as well as presentations by operators reporting back on their successful IPv6 pilot projects and plans to roll out IPv6 in the first half of 2014.
This new RIPE Labs article 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.
The Assisted Registry Check is the new name for the RIPE NCC’s audit activities that have been improved using feedback from RIPE NCC members and the RIPE community. This improvement aims to make the process more efficient and less time consuming for Local Internet Registries (LIRs).
This article provides statistics about how much IPv4 address space is being announced by networks (ASNs) that are also announcing IPv6 address space. Currently this is about 70% of IPv4 address space.
Following up from earlier experiments in which MERIT looked at pollution of IPv4 prefixes, Manish Karir and his colleagues now did an experiment with various IPv6 prefixes. The results can be found in this article.
The advent of IPv6 changes not only the network components, but also the security field shifts. We see new types of attacks or at least variations of the attacks we know from IPv4. This article provides an overview of the IPv6 security vulnerabilities that arise with the launch of IPv6.
The IETF has developed solutions that promote a healthy IPv4 and IPv6 co-existence. The happy eyeballs algorithm for instance, provides recommendations to application developers to help prevent bad user experience in situations where IPv6 connectivity is broken. We study the effectiveness of the happy eyeballs algorithm.
To check the connectivity of an IPv6 device with RIPE Atlas, one typically asks N probes to ping the target and deduces the reachability of the target from the percentage of failures. But RIPE Atlas probes, like many IPv6 devices, often believe they are IPv6-connected while they are not.