Everyone who is reasonable about the DRM debate agrees that DRM is not going to keep protected content off the filesharing networks forever. All DRM will eventually be broken and, at the very least, the analog hole will for the forseeable future remain an open path for copyright infringement. However, let's assume for the nonce that DRM can significantly delay the spread of protected content onto filesharing networks.
This leads to one of the problems with DRM that I've noted before (Speed Bumps on Your Car). DRM typically outlives its usefulness:
Long after DRM has provided whatever "speed bump" effect it can, consumers are still inhibited from many perfectly legitimate uses of a work. Indeed, many of the costs of DRM are backloaded. DRM likely doesn't create much of an initial issue for many. However, down the line, when people purchase new PCs or devices, DRM is likely to make transfers from old to new devices more difficult or impossible. Looked at from a long term perspective, DRM seems an extremely poor choice if all you're interested in is short term benefit.
Microsoft is soon to unleash a new DRM technology code-named "Janus" (Rental Nation). What's special about Janus? Well, Microsoft isn't the first developer to create DRM with this capability, but they are the biggest (Microsoft to Publicly Preview New DRM Technology):
Janus includes a "secure clock" that is designed to time-out subscription content for which a customer's license has expired.
How long before the latest music has managed to become widely available on the filesharing networks? A few weeks, months? Why not have the DRM time-out over a set period, such as 3 months? Such a strategy would certainly indicate that those using DRM are doing so only in order to reduce piracy. It would treat honest customers with a lot more respect than they are getting now. Heck, it might even become a copynorm. People would certainly be more supportive of a DRM strategy that was more narrowly targeted at infringers and infringed on fewer of their rights.
Of course, I doubt that any major content producer would adopt such a strategy. Why? Because I don't think that the purpose of DRM is to reduce piracy (Why Use DRM If It Doesn't Work? and Potemkin Village - What Secrets DRM Encryption is Really Hiding).
I doubt it would be that easy to get around the "secure clock" functionality. If it were, as you noted, then one could just as easily set back the clock and extend the life of limited availability files.
In any case, I'm sure someone would come up with something that would work ... until it was broken. But isn't that the way DRM works today?
Posted by Ernest Miller on June 23, 2004 07:19 PM | Permalink to CommentI think my (intended) point was the difference between a one-time break and a repeated break. I only need to break the (time) protection once to remove the DRM forever, but I have to break it every time I want to listen to the file if that file will be "expired" if I don't.
... Did that make (better) sense this time? :| I realize that I don't always communicate what I want to as well as I'd like to think I do... :)
Posted by Steven on June 24, 2004 07:55 PM | Permalink to Comment
There's (at least) one other problem with that idea, though.
Quick, how long does it take to set up a two-computer network, a network time server (set for whatever address the other computer might use to verify the current time), set the clock ahead on both a few years, and load up the DRM'd content on the first computer?
Voila, an instant DRM removal system!
No, I can see why they have it set to expire the content instead of the DRM... though this idea might also be usable to extend a DRM'd document's life span as well. That'd be more inconvenient for the user, though.
Posted by Steven on June 23, 2004 07:02 PM | Permalink to Comment