A new IETF draft has been published that specifies a new HTTP status code for legally restricted resources. That is, if the government restricts your access to the web page, return this code (similar to how something not found is a 404). The error code: 451. From the Internet Draft, if the user tries to access a page, but access to the page is restricted by the government, display the following... more
Declan McCullagh recently opined that the "FBI [and the] DEA warn [that] IPv6 could shield criminals from police." His post was picked-up relatively widely in the past few days, with the headlines adding more hyperbole along the way. So just how real is this threat? Let's take a look. more
As we start moving more real-time communications into web browsers with the upcoming WebRTC/RTCWEB offerings, what do we do about congestion control? How do we ensure that all these browser-based communications sessions share the network fairly? With RTC capabilities now already available in builds for browsers such as Google Chrome and Mozilla Firefox, how do we deal with the expected increase in voice, video, chat and data traffic? more
For two things that would seem to be completely unrelated there is an interesting parallel between IPv6 and DNSSEC. In both cases there is a misalignment of interests between content providers and service?providers. Content providers aren't highly motivated to deploy IPv6 because only a small proportion of users have v6 connectivity and even fewer only have v6. Service providers aren't anxious to deploy IPv6? because there isn't a lot of content on v6, and virtually none exclusively on v6 - so they don't expand the universe of interesting stuff on the web by deploying IPv6. Basically the same things could be said about DNSSEC. more
In recent interviews about World IPv6 Launch I've been asked by several different people whether or not I think there needs to be some kind of a "Flag Day" on which the world all together switches from Internet Protocol version 4 (IPv4) to the version 6 (IPv6). I don't think a flag day is needed. World IPv6 Launch is just the right thing. It's worth looking at some previous flag-type days to get a better sense of why. more
World IPv6 Launch kicked off 6 June 2012 at 00:00 UTC. On this day, multitudes of website operators, network operators and home router vendors from all over the world have joined thousands of companies and millions of websites in permanently enabling the next generation Internet. They have done this by turning IPv6 support on by default in (at least some of) their products and services. This is a major milestone in the history of the Internet. more
In my previous blog on the topic, I stated that the business case supporting the IPv4 roll-out in the late 90s was the Internet. Although IP depletion will slowly become a reality, the chances are that due to mitigating technologies such as NAT and DNS64, it may take quite a while before organizations in the developed economies will get serious about IPv6. So where should we look to find a business case for IPv6? more
When discussing IPv6, it is easy to forget that we are ultimately talking about an enhanced version of an existing network protocol. Sure, it brings about a number of technical advantages. But when viewed in isolation - without a business case - there really are not that many drivers that would place IPv6 on the agenda of the top decision makers looking after budgets. For IPv6 to gain serious momentum, this has to be changed. more
While a great deal of attention has recently been paid to the enormous amount of change that is taking place at the edge of the network with smartphones, tablets, apps, Web2.0 etc, massive changes are also underway on the network side. The current network has been designed over a period of thirty years and it is due for a serious overhaul to keep abreast of changes in the industry in general. more
No, that title is not a typo. The WHOIS service and the underlying protocol are a relic of another Internet age and need to be replaced. At the recent ICANN 43 conference in Costa Rica, WHOIS was on just about every meeting agenda because of two reasons. First, the Security and Stability Advisory Committee put out SAC 051 which called for a replacement WHOIS protocol and at ICANN 43, there was a panel discussion on such a replacement. The second reason was the draft report from the WHOIS Policy Review Team. more
A World-Renowned Source for Internet Developments. Serving Since 2002.