Home / Blogs

Bad Journalism, IPv6, and the BBC

Here’s a good way to frighten yourself: Learn about something, and then read what the press writes about it. It’s astonishing how often flatly untrue things get reported as facts.

I first observed this back in 1997 when I was a Democratic lawyer in the U.S. House of Representatives working on the (rather ridiculous) campaign finance investigation. (The investigating committee’s conspiracy-minded chairman was famous for shotgunning pumpkins in his backyard in order to figure out exactly how Hillary snuffed Vince Foster). The investigation was heavily covered by the press; as an investigator, I was privy to a lot of inside information, and got to watch how the underlying stories got reported. What was not surprising was how easy it was for White House officials and Congressional staffers to manipulate reporters by the use of leaks, exclusives, and off-the-record briefing. What was very surprising, though, was how lazy most Capitol Hill reporters seemed to be. Many simply did not undertake to check and verify the facts their insider sources fed them; and once something false was published as fact, most reporters were extremely reluctant to go back and correct the record. Most reporters preferred the pursuit of scoops and leaks to the gumshoe work of investigative reporting. (Some of the reporters I observed did excellent, factually rigorous work, but they were in the minority.)

More recently, I’ve seen the same discouraging phenomenon in reporting on technology and, in particular, the Internet.

For Example: a BBC story on the need for IPv6, by Ian Hardy. Let’s do a basic fact-check, line by line:

BBC ClickOnline’s Ian Hardy investigates what is going to happen when the number of net addresses - Internet Protocol numbers - runs out sometime in 2005.

The claim that IPv4 addresses are going to run out in 2005 is patently absurd. There is not a shred of evidence to support it.

Indeed, had the reporter bothered to contact the RIPE NCC or any of the other three regional address registries (the regional organizations responsible for assigning IP addresses to ISPs), or the IANA (the global organization responsible for allocating IP addresses to the regional registries), he would have been pointed to (gasp! ) publicly available data! For example, he might have looked at the October statistics [PDF] presentation published jointly by the regional address registries. Or he might have Googled up Geoff Huston’s excellent July 2003 paper, “IPv4 - How Long Have We Got?”. I won’t repeat his analysis, but I recommend the paper—like most things geoffhustonian, it’s well-written, straightforward, and true to the data. Geoff’s notable contribution is that he uses BGP routing table data to supplement the address exhaustion pictures painted by the IANA and regional registry tables. With a bunch of careful caveats about how difficult and unreliable it is to predict future growth in demand, Geoff uses statistically reasonable projections to argue convincingly that the IPv4 space will likely last until around 2022. In any event, there is no evidence that IPv4 addresses will be exhausted in the coming decade.

For the BBC to report as a fact—in the boldface header, no less—that IPv4 addresses are going to run out in 2005 (i.e., within 2 years!) mirrors the atrocious quality of technology reporting worldwide.

Bad journalism?  Yes.  But wait! There’s more…

A taskforce of experts hope to solve the problem by creating what is called IPv6 and would provide 64 billion extra IP addresses.

IPv6 is already created; deployment started in 1999. And the sentence massively understates the size of the IPv6 address space. IPv6 replaces the 32-bit address field of IPv4 with a 128-bit address field. Doing the math, IPv4 has around 4.2x10**9, or 4.2 billion, unique addresses. IPv6 has around 3.4x10**38 (that’s 3,400,000,000,000,000,000,000,000,000,000,000,000,000), or 3.4 gazillion. A much, much, much bigger number than 64 billion.

Anyone who logs onto the internet will automatically receive an IP address.

True, sort of, but not every Internet device receives a publicly-routable IP address (which is what matters for address exhaustion analysis). Those who dial-up their ISPs or connect via corporate networks, for example, will receive non-public IP addresses on a temporary basis. It would be nice if every Internet-connected device had its own publicly-routable IP address, but that’s not the world we live in. Many end-users join the Internet from behind Network Address Translation (NAT) boxes. (NAT is a method of connecting multiple computers to the Internet using one publicly-routable IP address.)

So what’s wrong with this sentence? It shows that the reporter hasn’t bothered to learn the basics of IP addressing. The implication is that every new Internet device needs a IP address (and we all know about how many new Internet devices are getting bought up). In fact, the wide deployment of NAT (which is a bad thing, for reasons I’ll blog about later) allows huge numbers of new Internet devices to go online with only small numbers of IP addresses. You can’t speak intelligently about IPv4 address exhaustion without mentioning the impact of NAT. (The reporter later alludes obliquely to the difference between static and dynamic IP address, but without understanding it.)

The global distribution of available IP addresses is extremely unbalanced. Most of the numbers remain in the USA, where the technology was originally invented.

That’s at least a bit misleading. The global distribution of IP addresses mirrors the global distribution of the Internet, which is unbalanced. The policies of the regional addresses registries ensure that IP addresses are allocated and assigned to the networks that need them, worldwide.

More than two-thirds of the world’s IP addresses were bought by American companies.

Wrong. First off, IP addresses not “for sale.” Americans companies receive allocations and assignments as members of regional Internet registries, or as customers of members. IP addresses cannot be bought or sold. And take another look at the actual statistics [PDF]. American companies have been assigned vastly less than two-thirds of the world’s IPv4 addresses. (It is true that the IANA assigned around 90 top-level IPv4 blocks to various companies and government agencies in the late 1980s and early 1990s, but those blocks were not “bought,” comprise less than a third of the total IPv4 space, include some non-US entities, and are vastly underused ? it’s not like Apple Computer actually uses much of its top-level block.)

“Level Three Communications, which is a really large ISP, has more IP addresses than the whole of Asia,” said Matthew Sarrel, Technical Director of PC Magazine Labs.

Wrong again. The public data above shows that APNIC, the IP address registry for the Asia/Pacific region, has been allocated eleven (11) top-level blocks of IPv4 addresses, and three (3) sub-TLA blocks of IPv6 addresses. Level Three has been allocated zero (0) top-level blocks of IPv4 addresses (i.e., something considerably smaller than a top-level block) and zero sub-TLA blocks of IPv6 addresses. This information is not secret. It’s right here on the IANA website, with separate tables for the IPv4 and IPv6 spaces. All Google-able within a click or two.

“As companies and people in Asia get more devices they are going to run out of IP addresses.”

Not true. As note above, the IPv4 space is good for at least another decade, and probably two. The global IP addresses allocation system provides that those need IP addresses can get them, on the basis of need. The article somehow implies that those in Asia are at some kind of relative disadvantage, in terms of getting IP addresses. That’s just not true. The IANA policies for allocation of IPv4 address blocks to the regional Internet registries are applied evenhanded on the basis of need. The regional registries are all non-profit membership organizations dedicated to the service of their members, and to the achievement of IP address availability (as well as conservation and aggregation). My guess is that the reporter did not bother to talk with anyone at one of the regional Internet registries. In any event, he didn’t fact-check the quote above.

One of the biggest pressures on IPv4 is the ‘always on’ internet connection. At the moment, when you dial your ISP they assign you a temporary IP address, which is taken away the moment you log off and given to someone else.

Not so. Always-on Internet devices can be configured either with private addresses or publicly-routable addresses. ISPs decide whether or not to assign their customers publicly-routable addresses or private addresses behind an NAT box, taking account of a variety of network management considerations. Whether customers’ devices are always-on or not may well affect those ISP considerations, but it’s not correct to state that always-on devices automatically require publicly-routable, static IP addresses.

But in the new era of 3G wireless computing, each of us needs a static, or permanent IP address.

That suggests that static IP addresses are (or should be) assigned to individuals, one address to one person. Wrong: IP addresses are assigned to Internet devices, by the relevant service providers. In the future, we will want static IP addresses for each Internet-connected device we have.

This is intended to provide four billion times four billion times four billion as many as currently exist.

Aha! Now we learn why the reporter misreported the total number of IPv6 addresses: He can’t multiply. “Four billion times four billion times four billion” isn’t the same as 4 x 4 x 4 = 64, and then you just tack the “billion” back on, giving you the story’s “64 billion” figure. (You have to multiply out all the zeros, too).

So: Do these factual errors matter?
(i.e., aren’t I being a little hard on the poor reporter? After all, he’s a journalist, not an Internet techie, and he’s got a lot of stories to write.)

  1. It matters because the story paints a false and alarming picture. “Eeek! IPv4 addresses are going to run out ‘sometime in 2005’! Asia is being treated unfairly by the Americans! We’ve got to do something!” Readers reasonably expect the BBC to report reality; this article amounts to scare-mongering.
  2. It matters because there is a real and important IPv6 story that should be reported. Even though there’s no crisis in IP addressing, there is nevertheless an interesting and important story to be told. IPv6 is needed; it’s a powerful upgrade to the Internet’s core protocols; it will enable new capabilities and possibilities by re-enabling a more purely end-to-end architecture for the Internet. There are serious technology and policy implications to the question of whether the Internet is truly end-to-end or not. The false alarmism of the BBC story obscures understanding of the real issues at stake.
  3. It matters because it’s the BBC. The BBC is a news agency of global scope, and a reputation for reliability. It should be able to report on technology with some degree of accuracy. I expect more from the BBC.
  4. It matters because it was easily avoidable. All of the factual errors in the story could have been corrected with some decent reporting. For example, none of the individuals quoted work for one of the regional IP address registries, which are the obvious sources of expert factual information about the resources they are charged with administering.
  5. It matters because of what the error rate implies more generally. IP addressing is something I know fairly well. If the BBC is making such fundamental misstatements of fact about something I know, it is reasonable (and troubling) to wonder whether similar ratios of mistake to fact arise in the rest of the BBC’s reporting.

By Andrew McLaughlin, Senior Fellow at the Berkman Center, Harvard Law School

Filed Under


Christopher Ambler  –  Nov 8, 2003 12:29 AM

Such errors happen on a daily basis. You notice them in articles that pertain to subject matter about which you know something more than the average reader.

Imagine all of the stories that you read with subjects about which you know little more than the average reader. Imagine all of the errors that you take at face value.

Think about the last time a news report was made about someone you know, who later told you, “well, that’s not really how it was…”

Every day. Every damned day.

ed  –  Nov 14, 2003 12:48 PM

I emailed the BBC, and pointed them to this article. It seems they have changed at least a few of their statements.

Troels Arvin  –  Nov 14, 2003 1:47 PM

Thanks for a good article.

About uneven distribution of IP addresses between the US and Asia: I think it’s strange to totally rule out injustices.

I’m sure that IANA is fair, but I think it’s also fair to say that some parts of the World got a head start: There is an important difference between requesting a block of IP addresses in 1993 and doing it in 2003: I’m sure that the assignment policies have become much stricter during the last decade.

So people in countries where the Internet is just starting to have an impact will have a much harder time obtaining IP-addresses than people in countries which started a decade ago.

Karl Auerbach  –  Nov 24, 2003 10:20 AM

Address blocks are sized by “prefix”, the smaller the prefix the bigger the block.  The biggest conventional unit of allocation is a /8 - there simply are not enough of these to hand out one to every country - yet many companies have several.  Many of these allocations predate the RIRs and the ability to transfer those prior allocations has yet to be established.

Some of the smaller blocks (/24) are more valuable than others because they are grandfathered into the global distribution of routing information.

The RIRs have established allocate address blocks.  Are those rules based on a full consideration of all the competing interests? For example there are many smaller ISPs who complain that they can not obtain addresses to expand their businesses.

Many in the internet community consider NATs to be a violation of the end-to-end principle.  NATs can, for instance, make Voice-over-IP difficult.

From the point of view of those who route packets the issue is the number of prefixes (destination blocks).  The CIDR reports keep creeping up.  When I was at Cisco we were concerned that things would get “interesting” when the number of prefixes exceeded 200,000.  Today we are over 123,000.  It is difficult to extrapulate the growth curve - but we need to be concerned that the size of routing tables, as well as the time to propagate them and the time to stabilize/reconverge after a route failure, is increasing.  IPv6 will do little to solve these problems.  in fact because there are simply more address bytes to move around, IPv6 could exacerbate the problem.

With always-on connections, the distinction between static and dynamic is reduced - an address is consumed whether it is assigned dynamically or statically assigned.

When we look to the future of the internet as a utility we can easily conceive of fire and security alarm systems and voice-over-IP that will need IP addresses on a 24x7x365 basis.

I believe the article places too much faith in the RIR’s ability to consider all of the competing needs and issues, some of which involve significant decisions regarding economic policies.

ICANN was to have been the forum in which these concerns were to have been addressed.  Yet, ICANN has abandoned that role to the RIRs.  The RIRs have done a very good job so far.  But I am concerned that their focus and constituencies are too narrow and that the RIRs do not adequately hear some of the larger, softer issues.

Les Kirschner  –  Nov 9, 2005 8:41 AM

Don’t know about Bad Journalism, but I know a bit about Dumb Journalism. Have a look at http://members.iinet.net.au/~lk319386/index.html
It’s a site I whacked up in a hurry. I notified the radio station of the error and it vanished in a couple of hours, but no reply from them. Strange looking Australian Police, I think.
Regards, Les Kirschner.
.(JavaScript must be enabled to view this email address)

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Co-designer of the TCP/IP Protocols & the Architecture of the Internet




Sponsored byDNIB.com

IPv4 Markets

Sponsored byIPv4.Global

Threat Intelligence

Sponsored byWhoisXML API

Brand Protection

Sponsored byCSC

Domain Names

Sponsored byVerisign


Sponsored byVerisign

New TLDs

Sponsored byRadix