One of the more difficult design exercises in packet-switched network architectures is that of the design of packet fragmentation. In this article, I’d like to examine IP packet fragmentation in detail and look at the design choices made by IP version 4, and then compare that with the design choices made by IP version 6.
Wouldn’t it be nice if turning on IPv6 really was ‘press one button and the rest is magic’ easy?
The holiday season is rapidly approaching and this year is coming to a close, another one done and another one that seen some great and wonderful and also unfortunately some sad moments. One of those key moments was the depletion of the IPv4 pool in the ARIN region, which for some probably means the sad realisation that their business models will hit a growth barrier.
Every so often I hear the claim that some service or other does not support IPv6 not because of some technical issue, or some cost or business issue, but simply because the service operator is of the view that IPv6 offers an inferior level service as compared to IPv4, and by offering the service over IPv6 they would be exposing their clients to an inferior level of performance of the service. But is this really the case? Is IPv6 an inferior cousin of IPv4 in terms of service performance?
One of the measurements that we have been running for a long time is IPv6 RIPEness, where we measure the IPv6 activity of our members. We award our members with stars if they (for example) announce their IPv6 allocation in the global routing table.
We look at the RIPE NCC in terms of growth, geographic distribution and IPv6 deployment. We find that recent RIPE policy changes have had an impact on membership statistics and development trends.
Tony Smith from APNIC is looking at the increase in IPv6 deployment now ARIN depleted their free pool of IPv4 addresses.
If you monitor your external Internet connectivity, you may wonder which machine is the best to ping. Hesitate no more - you can use RIPE Atlas anchors as landmarks.
Some time ago, many people noticed rapid IPv6 deployment growth in Estonia (from 0% to 5% in 4 weeks). Tarko Tikan, from 3249/Elion/Estonian Telecom, explains the reason behind this.
Please find below a guest post by Darrin Veit and Christopher Palmer who originally posted this to the NANOG mailing list. It provides information for Xbox One, but also shares some relevant details on upcoming Windows functionality in terms of Teredo and IPv6 usage.
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 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 try to identify whether 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.