RIPEstat has a new layout as part of a series of user interface improvements we'll be making over the coming months. Users will now benefit from query results that are organised and presented more efficiently. Here we describe the new features and give an overview of the next round of upcoming improvements.
Similar to an experiment done for IPv4 address space, Merit is now performing a darknet experiment with the IPv6 ranges that have been allocated to the RIRs. This also includes prefixes allocated to the RIPE NCC.
While developing RIPE Atlas, we are maintaining and publishing a roadmap to keep the RIPE community involved and informed of the features we are working on. Please find below our achievements in October, and plans for November 2012 and beyond.
The sixth RIPEstat demo of 2012 gives an overview of the new user interface, an update on the new features, as well as plans for the future. It was recorded during the RIPE 65 Meeting in Amsterdam, where users had the chance to meet the developers and ask questions face to face.
After causing lots of damage in the Caribbean, superstorm Sandy is having a devastating effect on the US East Coast. We looked at the RIPE Atlas network to find out what effects this superstorm has on the Internet. Below are some preliminary results of what we saw.
At the recent ARIN XXX meeting in October 2012 I listened to a debate on a policy proposal concerning the reservation of a pool of IPv4 addresses to address critical infrastructure. The term "critical infrastructure" is intended to cover a variety of applications, including use by public Internet Exchanges and authoritative name servers for various top level domains. As far as I can tell, the assumptions behind this policy proposal includes the assumption that a top level authoritative name server will need to use IPv4 for the foreseeable future, so that an explicit reserved pool of these IPv4 addresses needs to be maintained for use by the authoritative name servers for these domain names.
This is a followup article to "Counting DNSSEC" that reflects some further examination of the collected data. This time I'd like to describe some additional thoughts about the experiment, and some revised results in our efforts to count just how much DNSSEC is being used out there.
Together with Euro-IX we take a look at Internet Exchange Point (IXP) traffic levels during Felix Baumgartner's 39-kilometre jump to Earth, and we take a closer look at what exactly we can see at IXPs.
We did some measurements on the round-trip (RT) values of DNS queries for SOA (Start of Authority) records from our RIPE Atlas probes, over both UDP and TCP. We plotted the TCP/UDP ratios on graphs, and found that, as expected, for the majority of the measurements, it is around 2. However, we also observed other values for some servers (including K-root). Upon investigation, we found that the K-root servers were configured to allow at most 10 concurrent TCP connections. This caused several much bigger RT values than on other root servers. When we changed the configuration to allow for 100 concurrent TCP connections, K-root showed ratios similar to the other root servers.
During the recent RIPE 65 meeting, some attendees experienced problems with the wireless network. Together with these attendees we investigated the problem. Find a detailed report below.