Day against DRM: save 50% on my BGP ebook and 7999 other O'Reilly ebooks today

▼ Today, May 6th, is International Day Against DRM. Digital Rights Management restricts what you, the consumer, can do with the digital content you buy. In the beginning it doesn't seem so bad, but then a device breaks and it turns out you can't take your content with you on a different device. But I especially worry about forgotten content in the future that will stay forgotten in the future as it's locked down by long forgotten DRM schemes. Read all about it at defectivebydesign.org.

The good news is that O'Reilly has been using DRM-free formats such as PDF and ePub for their electronic books for years. And today, you can buy 8000 O'Reilly ebook titles at 50% off!

That of course includes my book "BGP": today, you only pay $16.

Remember, if you're going to do our BGP training course (the next one is June 2nd), a paper copy of the book is included. But if you prefer to have the DRM-free ebook instead, buy it today at the 50% discount. You can then use the ebook and not get the paper book during the training course and you'll save € 25.

Permalink - posted 2014-05-06

Nikon and Apple apply radically different color management to photos

▼ The other day I had a discussion about whether to use the "standard" sRGB color space or a larger color space for my digital photos. My thinking was that because my monitors are limited to sRGB (or less) anyway, I'm not going to see any colors that fall outside what an sRGB file can encode. So there's no immediate need to use a bigger color space such as Adobe RGB 1998. Here's the same photo taken with my Nikon D7100, the left one using sRGB and the right one using Adobe RGB 1998 (they are mousoverable):

(If you have a screen that doesn't do better than sRGB and your browser and operating system do proper color management, the colors in the two photos should look identical. If the right one looks duller, your software doesn't do proper color management. If your screen is better than sRGB and your software does proper color management, the colors in the photo on the right should look more saturated.)

(I actually had a hard time making sure the files are really different. They are. Use Firefox and the setting gfx.color_management.mode = 0 in about:config as explained here, restart Firefox, load this page and you'll see.)

I could of course use Adobe RGB anyway in anticipation of better hardware in the future. The trouble is that not all hard- and software uses color management properly. If something along the way then interprets an Adobe RGB file as an sRGB file, the results will be worse.

Anyway, I then looked at what the JPEG and raw files that come out of the camera look like. The camera can record more color information than what can be stored in a file that uses an sRGB color profile, so when creating an sRGB JPEG file, the camera must reduce the color gamut somehow. The camera can also produce raw files, which is basically a dump of the data straight from the image sensor. Preview, Apple's image viewing/conversion tool, interprets those files as Adobe RGB 1998, but then of course also has to reduce the color gamut in order to display the file. And it does that very differently from how Nikon does it:

So it looks like Nikon just dials down the saturation of the colors, while Apple "clips" the very saturated colors that fall outside the sRGB color space. It's hard to say which approach is superior, but they are very different.

Permalink - posted 2014-05-04

With North America out of IPv4, do we trade, translate or transition to IPv6?

▼ It's official: for all intents and purposes, North America is out of IPv4 addresses. Two of the four other regions have been in that situation for some time, and Latin America will be joining North America, Europe and Asia in about a month. That leaves Africa, which still has almost 50 million IPv4 addresses, which are used up at a rate of 5 - 10 million a year.

Does this mean that if you're running a business that requires a regular infusion of new IP addresses, it's time to relocate to Africa?

Not quite. The Internet Engineering Task Force saw all of this coming twenty years ago—which they should, having hobbled TCP/IP with a meager 32-bit address space for a maximum of about 4 billion IPv4 addresses. But they fixed that with IPv6, which increases the address length to no less than 128 bits for a near-infinite number of addresses.

Unfortunately, a system that only speaks the new IPv6 can't directly talk to a system that only speaks the current IPv4. So giving people just IPv6 means they can't talk to the 97% of internet users or the 90% of top 500 web sites that haven't adopted the new protocol yet.

But don't start looking for apartments in Nairobi or Casablanca just yet: it's also possible to trade IPv4 addresses. The big question is: to what degree will that solve the lack of available IPv4 addresses? We know that Microsoft and Amazon have bought large numbers of IPv4 addresses, and there have also been larger numbers of small exchanges. The going rate seems to be around $10 an address, which is expected to go up to about $30.

Microsoft and Amazon run cloud services where large numbers of virtual machines need IP addresses, which they probably couldn't get the "normal" way. In the Asia-Pacific region, there have also been exchanges of small and medium-sized IPv4 blocks. Obviously, paying $2560 for a "/24" (256 addresses), which is the smallest usable block of IPv4 addresses, is not a big deal for content providers.

However, the big ISPs and telcos that use IP addresses by the hundreds of thousands or millions haven't entered this market so far. The big question is: will they? Until now, a company like Comcast paid pennies per address for its multi-million blocks of IPv4 addresses. Having to pay $30 for an IPv4 address to give to every new customer would be a big hit to their bottom line. Worse, what if a year later the going rate is $60? And then $120, and so on? (And I'm not even talking about the headache of having to acquire more and more smaller and smaller blocks as the years progress.)

Rather than spend $30,000,000 on a million IPv4 addresses, a big ISP could probably spend a lot less on Carrier Grade NAT (CGN) equipment that makes it possible for multiple users to share a single IPv4 address. They still 100,000 addresses to connect a million new customers, but they probably have that kind of address space in reserve, or if not, they can take it from existing users and put those behind the CGN, too.

In the meantime, more and more ISPs are rolling out IPv6 for their users. Today, IPv6-only connectivity is not good enough to replace regular IPv4 connectivity, but the day that it will be is approaching. Even today being limited to just IPv6 connectivity for an hour or two wouldn't be too inconvenient for me. Sure, I wouldn't be able to read many news sites or post to Twitter, but I can get my email over IPv6, visit Google, Facebook, Wikipedia.

So my advice to HP: if you can get a billion dollars for those 33 million IPv4 addresses you're holding (after buying DEC), take it. You'll wish you had when IPv6 reaches critical mass and people start asking themselves why they're still bothering with that arcane 1980s network protocol. However, I'm not an economist, but I would think having millions of IPv4 addresses enter the market would lower the price.

Bottom line: small amounts of IPv4 address space will always be available in some form. But assuming you'll be able to either buy low or sell high many thousands or even millions of IPv4 addresses at any point in the future is a risky bet.

This article also appeared on the Kalorama blog. Also see this post on the topic by Louis Sterchi over there.

Permalink - posted 2014-04-28 - 🇳🇱 Nederlandse versie