Dan York

Just a guy in Vermont trying to connect all the dots...

Author's posts

As An Author, Why I Truly Hate Ebook DRM

DayAgainstDRMAs an author of multiple technical books, and a prolific online writer, I care a lot about intellectual property issues as they pertain to my content. On one level, you might think I would be extremely concerned about people stealing and re-using my content. And don't get me wrong... I am concerned. I choose distribution licenses carefully and I have pursued those who have scraped my content to simply wrap it in ads.

But I do NOT see "DRM" as the answer.

As a reader and as an author, I truly hate Digital Rights Management (DRM) for ebooks and look forward to the day when it ceases to exist. My latest book, "Migrating Applications to IPv6" was published DRM-FREE by O'Reilly and I plan to publish all future books DRM-free as well.

So on this "Day Against DRM", let me clearly state WHY as an author I am against DRM:

1. DRM Is Anti-Reader

DRM starts from the premise that all readers are slimeballs and thieves. That they will steal a book rather than pay for it. That readers are inherently untrustworthy and need to be monitored, policed, checked.

Is that really the relationship I want with my readers?

Do I really think that all my readers are crooks?

With a printed book, as a reader, when I buy a book, it is mine. I have a piece of dead trees that I can read wherever I want. In a chair. In bed. Outside under a tree. In the bathroom. On a train. In a hammock. In a car. At night. In the morning.

Wherever. Whenever.

Beyond that, I can give my book to someone else. I can lend it to a friend. I can let my wife read it. Or my daughter. Or my mother or father. I can... (gasp)... sell that book to someone. Or I can donate it to a library or church or book sale.

It is my book, to do with it as I will.

With "ebooks", the argument is that they are so much easier to pass around. That because it is electronic bits, the book can be emailed or otherwise sent to people. It can be published on websites. It can be sold by people other than the author/publisher. It can "escape" from the control of the author and publisher.

All of which is true.

But is DRM really the answer? Is treating all people as thieves and locking down the content really the answer?

Now, granted, there is a grain of truth in there... some readers will steal a book, but would they have paid for it in the first place? Some people will steal paper books from bookstores and libraries, too! Some people will steal books from other people.

Some people are thieves - but just because of that, does it warrant treating all people as thieves?

2. DRM Locks Readers In To Platforms

Every time you buy a book for the Amazon Kindle, you are just that much more locked in to Amazon's "walled garden". If you decide you are tired of the Kindle and want to try another reader, sorry...

... you can't take your books with you!

They are locked to the Kindle. Now, yes, you can use the Kindle "app" on your PC or other device (like an iPad), but you are still locked in to Amazon's Kindle ecosystem.

This is the beauty and genius of the whole scheme from Amazon's point of view. Make it super-simple for people to buy and read ebooks... and get a whole generation of people locked in to your ereader platform.

And then Amazon gets to use its power as platform to bully publishers and authors so that in the end Amazon gets higher profits. If pretty much the only route to readers winds up being through the Kindle ecosystem, then Amazon gets to dictate how your ebooks get distributed - and at what cost.

Authors get screwed. Publishers get screwed. Ultimately readers get screwed. But Amazon makes a healthy profit.

Lest you think I am purely anti-Amazon, I'm not... they're just the biggest. Barnes & Noble's Nook, Apple's iBookstore, the Kobo reader... any of them can equally lock you in with DRM... and all of them would probably love to have the kind of lock-in that Amazon has right now!

With DRM-free ebooks, we can read them on whatever platform you want - and change ereaders and devices. We are not locked in!

[UPDATE: In a comment to this post, a reader named Markus points out another downside to DRM-enabled ebook platforms - a platform can easily "unpublish" an ebook. The ebook can just "disappear" and be removed both from the online service and also from your own ereader. Remotely. Without any involvement on your part. Gone. Because you are locked into the platform's infrastructure and don't own your ebook, you are completely at the mercy of the platform operator.]

3. DRM Adds Unneeded Complexity

Want to see how badly DRM screws up the reader experience? Check out these instructions for how to get started with ebooks that you borrow from your library - specifically take a look at these slides about how to borrow ebooks with a Nook or Sony Reader.

Hello???

You have to be seriously committed to wanting to borrow ebooks to go through all these steps! It's crazy! And then to have to go through many of those steps each and every time you want to borrow an ebook?

FAIL

And all because libraries must include DRM in order to make the books available to their readers.

This kind of complexity exists with DRM ebooks... except of course for the platforms that make it so insanely easy, at the price of locking you in.

4. DRM Stifles Innovation

We have "ereader" devices and software... we have "epublishing" tools... but we could always use better and more innovative tools. Right now there is undoubtedly someone out there building an insanely awesome reader that will just blow our minds. Or figuring out a way to make ebooks more accessible to people who can't read... maybe converting them to audio in new ways. Or figuring out a way to translate books into other languages on the fly....

Maybe someone's coming up with a reader that will let you display the contents of an ebook inside a pair of glasses so that you could just be sitting there on a train reading a book with just your glasses on.

The inventors and entrepreneurs of the world can be out there doing all this... but then the moment they want to make these products publicly available and working with all ebooks... BOOM... they run into the issue that they have to deal with DRM on ebooks!

That means licensing someone's DRM-reading software.

Which means big bucks...

... and probably kills any type of business model they may have.

Goodbye insanely amazing reader... it will linger on the side as something that can work with DRM-free content like Project Gutenberg books, O'Reilly books... and those from a few other publishers who have gone DRM-free.

Why stifle the innovation?

Why not make it so that the inventors out there can do anything with ebooks? Why not get rid of the DRM so that they can figure out new and amazing things to do with ebooks?

STOP RESTRICTING CREATIVITY!

5. DRM Will Ultimately Impact Sales

People are buying zillions of ebooks right now. More from some publishers than print books. It's a new space... everyone's excited... everyone's doing it. It's incredibly convenient.

Sooner or later, though, readers are going to figure out that they are getting royally screwed.

They will figure out that they don't "own" their DRM'd books. That they have effectively leased them. That they can't use them on other computers or ereaders.

They will be pissed off, angry.

And they may stop buying... or at least changing their buying habits.

Why set readers up for failure? Why?

Why not make it so that they can keep buying and buying and buying?

I know that I personally would buy far more ebooks if I knew I could "own" the ebook. I believe that ultimately more people will be in this mindset.

(DRM proponents, of course, believe that all people are sheep and will just continue to buy through locked-down DRM'd platforms because of the convenience. Sadly, they may be right.)

6. DRM Halts The Spread Of Ideas

Finally, DRM stops the spread of ideas and information. With DRM-free books, they can spread to people who would not have - or could not have - paid for the book in the first place. There are people in impoverished areas who cannot afford ebooks. There are people in countries where ebooks are not available through the major distribution channels. [UPDATE: There are people who would like to borrow an ebook from their library but are unable to do so in some cases because DRM makes it difficult.]

This is admittedly where it gets a bit tricky.

In my case, the kinds of books I have written so far are informational and for more niche technical audiences. I don't expect to ever get rich from them. I don't expect to pay my mortgage, send my kids to college, or anything like that. I might get a few nice dinners out of the proceeds or maybe buy a new computer... but that's about it. I'm realistic because there are only so many people out there who really care about things like IPv6 or VoIP security.

I write to help people understand topics. I write to contribute to the discussions going on. I write to help people learn.

So if someone really couldn't afford to buy my ebooks, can't get them in their region because of distribution issues, or can't borrow my ebook from their library, I'm personally okay if they wind up getting the book somehow. For me getting the ideas out there is most important.

I realize that some authors (and more importantly publishers) may be entirely profit-focused and want to squeeze every single penny out that they can... and so they have a different view.

The point, though, is that DRM prohibits these ideas from spreading where they wouldn't have gone.

In the end...

I guess I go back to my comments at the beginning - I believe that most people are NOT thieves... and if they have the opportunity to purchase an ebook in the channel of their choice for the ereader of their choice at a reasonable cost, they will do so.

I believe DRM is not the answer and that there are other ways and means to pursue those who violate intellectual property rights and copyrights. I don't want a world in which we are locked into specific ereader platforms.

I want readers to be able to purchase - and own - my books. And as a reader, I want that kind of trust relationship with authors and publishers.

So on this day, I encourage you to think about how DRM creates a defective and negative experience for readers... and to:

  • Buy DRM-free ebooks where you can. (Update: Here's a list.)

  • Ask publishers and authors if you can get their ebooks DRM-free.

  • Think seriously about the choice of ereader you are using and what the long-term impacts will be.

  • If you are an author, ask your publisher if you can make your ebooks DRM-free... or consider another publisher... or consider self-publishing without DRM.

  • Raise this topic with others, so that they can be aware of the choices they are making when they use ereaders and purchase ebooks.

The future of ebooks is in OUR hands, as readers, authors and publishers. Let's make it a good one!


UPDATE #1: In the comment thread on Hacker News for this post, user spatten pointed out this list of dealers and publishers with DRM-free ebooks. (By the way, that Hacker News comment thread does make for interesting reading.)

UPDATE #2: Two other excellent posts on the topic have come out yesterday and today:

I particularly liked this line of Mike's post: "Obscurity is more of an enemy than piracy." Tim O'Reilly expanded on this point way back in 2006.


If you found this post interesting or useful, please consider either:


EFF’s Coders’ Rights Video: Do It For The Kittens!

Sooooo… the Electronic Frontier Foundation (EFF), of which I am a member, sends out a promotional video for their Coders’ Rights Project that involves… kittens???

While I support the Coders’ Rights Project and applaud their creativity, this video feels a bit forced… kind of like “everyone loves kitten videos, so we just need a kitten video!

What do you think?

ICANN Seeking Participants and Speakers for DNSSEC Workshop June 27 in Prague

ICANN 44 logoOur friends over at the DNSSEC Deployment Initiative have noted that ICANN issued a Call for Participation for their upcoming DNSSEC Workshop on June 27, 2012, in Prague, Czech Republic, as part of the ICANN 44 meetings happening there. This is a similar workshop to the excellent DNSSEC workshop at ICANN 43 that I attended and spoke at in March in Costa Rica.

While I can’t attend this meeting personally, I highly recommend attending if you are interested in deploying DNSSEC.

The folks at ICANN are seeking presentations on the following topics:

1. DNSSEC activities in Europe

2. ISPs and Validation

3. The realities of running DNSSEC

4. DNSSEC and Enterprise Activities

5. When unexpected DNSSEC events occur

6. DNSSEC in the wild

7. DANE and other DNSSEC applications

They are also seeking participants for something called “The Great DNSSEC Panel Quiz” that sounds like it could be entertaining!

More information and submission guidelines can be found in the Call for Participation. The deadline is May 10th to submit a speaking proposal, so time is short!

Updates Submitted For “Migrating Applications To IPv6” Book

Very early this morning, I submitted a range of updates to the book to O’Reilly’s production team. As this is the first formal update I’ve made, I’m not sure of the exact process from here, but at some point soon the updated content will be available as part of the normal book.  I’ll post about it here on the site when it’s ready, and anyone who bought the ebook directly from O’Reilly will be automagically notified about how to download the updates.

Here’s a snapshot of the changes I made to the book:

  • Added new section on recent events and changes that make it critical for application developers to be thinking about IPv6.
  • Added section on connecting to DNS servers over IPv6 and about DNS and DHCPv6
  • Added sidebar about RFC 5952, “A Recommendation for IPv6 Address Text Representation”
  • Expanded text about “Happy Eyeballs” algorithm and included mention of RFC 6556 for testing for happy eyeballs.
  • Added brief info about lessons learned from World IPv6 Day
  • Added info about World IPv6 Launch in 2012
  • Added new section on testing resources
  • Added new section about setting up an IPv6 test network
  • Updated IPv6 NAT info to point to RFC 6296
  • Added warning about SMTP’s way of showing IPv6 addresses
  • Added additional resources, including a new section about some informational RFCs that may be of interest to application developers.

I’m pleased with how it came out… there’s been a great amount of new information added in the last few months that will be helpful for application developers and it was great to incorporate that into the book.

Next up, I’d like to add some images that illustrate some of the points in the book… but that’s the next update…

… and please do let me know if you have suggestions for additions you’d like to see in the book, either as a comment here or via email.

Cisco Blog: 5 Steps For Building Your IPv6 Address Plan

Cisco Blog siteToday over on Cisco’s “Borderless Networks” blog, Jim Bailey had a great post up tackling the issue around how you create a plan for your IPv6 address space: “Integrating IPv6 Into Your Network: Five Steps for Building Your IPv6 Address Plan“.

Guidance on planning your IPv6 addressing is definitely a topic I have in our queue to add to our list of IPv6 resources, and Jim’s post hits the main points in my mind.  The primary point, to me, is:

Do NOT be shackled by legacy IPv4 thinking!

Just because IP address allocation “was always done this way” in IPv4 doesn’t mean that you have to carry those same allocation processes across into IPv6. You have a chance to think about it a bit differently.

He also makes the point that you need to think about how you assign IPv6 addresses. Are you going to use stateless address autoconfiguration (SLAAC)? or DHCPv6? (or a combination thereof)

The post is a good read and the topic is worth thinking about as you plan your IPv6 networks.

P.S. And with World IPv6 Launch coming up in just over a month, are you getting your IPv6 network ready?

Slides: Carrier Grade NAT (CGN) Observations and Recommendations

What is Carrier Grade NAT (CGN) all about?[1] What are the problems associated with using it? What role, if any, should it play in networks during the transition from IPv4 to IPv6?

At the recent North American IPv6 Summit, Chris Grundemann of Cable Labs addressed exactly these points – and now has published a blog post with his CGN slides and some additional commentary:

Carrier Grade NAT Slides

It’s a good set of slides looking at a challenging issue. For some ISPs who are lagging behind with moving to IPv6, CGN looks like an attractive option to bypass IPv6 and just stay with IPv4.  But as Chris notes, their testing found that a good number of popular services, including VoIP and online gaming, would break or at least have degraded performance in typical CGN deployments.

Chris also notes that he is available to speak with anyone interested in learning more about CGN. Thanks to Chris for making these slides available for us all to see.

 

[1] CGN is also sometimes referred to as “Large Scale NAT” or “LSN”.

Friday Video – IPv6: The Internet for Generations to Come

Yes, “IPv6: The Internet for Generations to Come,” is a slickly produced Cisco marketing video… but hey, it’s well-done and talks about World IPv6 Launch on June 6, 2012!  We need more videos out there with messages like this one…

…and I mean, really, you have to love the passion of Cisco Fellow Mark Townsley in this video!

P.S. Got a suggestion for another video we should feature on a Friday afternoon? Please let us know.  We’re still looking for that “IPv6 and kittens” video that we’d like to help go viral! ;-)

DNSsexy.net – News from the DNS blogosphere

Looking for news about DNS and DNSSEC that is happening around the Internet? If so, check out:

dnssexy.net

DNSsexy is a news aggregation site built and maintained by Jan-Piet Mens that pulls together DNS-related items from a variety of blogs and news sources. Do note that this is DNS in general… so it covers a wide range of DNS topics, not just the DNSSEC we cover here.

You can view the latest news by going to the site – or by adding the aggregated RSS feed into Google Reader or whatever feed reader you use.

I’ve found it quite a useful way to stay up on the many DNS posts happening around the Internet. Thanks to Jan-Piet Mens for setting up and maintaining the site!

Today’s VUC Call All About The "FreeSWITCH Cookbook" – Noon US Eastern

Today at noon US Eastern on the VoIP Users Conference (VUC) Call for Friday, April 27th, the group will discuss the brand new "FreeSWITCH Cookbook"[1] published by PACKT Publishing. The four authors of the book, who are also leaders of the FreeSWITCH project, will apparently be joining the call.

While Asterisk generally gets most of the "open source VoIP" buzz, the folks at the FreeSWITCH project have been working away on their own solution. As they will say, FreeSWITCH performs a different role than Asterisk and is used in different contexts.

FreeSWITCH has become quite a powerful platform and I'm looking forward to learning more about what is going on with the project right now.

You can join the live call via SIP, Skype or the regular old PSTN. There is also an IRC backchannel that gets heavy usage during the call. It will be recorded so you can always listen later.

As noted on the VUC page for today's call, the show will also be simulcast in video using Google+ video and YouTube. If you are interested in joining the video side of the call, please follow the instructions on the page.

[1] In full disclosure, this is an affiliate link with Amazon and if you actually purchase the book I receive a tiny amount of money. If you think this influences what I write here, you clearly haven't been reading my site. :-)


If you found this post interesting or useful, please consider either:


Comcast Formally Launches IPv6 Home Networking Pilot

This is huge! In a pair of blog posts today Comcast formally launched its IPv6 “Home Networking Pilot”:

As I explained in an earlier post about this impending launch, support for home networks is a critical step for getting IPv6 more widely deployed, particularly as we collectively prepare for World IPv6 Launch on June 6, 2012. As Jason Livingood explains in his post (my emphasis added in bold):

Just as with our standalone computer support for IPv6, customer home networking is also native dual stack. This means that eligible customers will be provisioned with IPv6 addresses in addition to their IPv4 address. We maintain our commitment to the goal of a seamless transition to IPv6 and strongly believe that native dual stack is the best approach for our customers. We also believe that this strategy will over time will meaningfully differentiate our service from our competitors in a way that customers will greatly appreciate. Our native dual stack Xfinity Internet service will provide customers with direct IPv4 and IPv6 access, without the need to use a tunnel, proxy, network address translator, or other inefficient, outdated, and error-prone middlebox. That means customer Internet access will continue to be direct and fast. And because middlebox solutions are not used, customers avoid the risk that certain applications slow down, fail to work, or experience other annoying errors. Since two of the main reasons customers buy our Xfinity Internet service is reliability and the speed — and this approach ensures that we maintain both while other ISPs may face challenges doing so over time — we think our strategic approach to IPv6 will be a winner in the marketplace in the coming years.

John Jason Brzozowski hits a similar note in his post:

Native dual stack support remains central to Comcast deployment of IPv6, which means that customers who are enabled with IPv6 for home networking will be provisioned with IPv6 in addition to IPv4. This approach allows us to avoid the near term use of other types of transition technologies like tunnel and large scale Network Address Translation (NAT). Our experience and industry best practices continue to suggest that native dual stack offers the best path to a seamless IPv6 transition and an optimal customer experience, which is paramount to Comcast.

John Jason also makes a key point that not all home routers currently fully support IPv6 and directs customers to Comcast’s MyDeviceInfo site for the current list of devices Comcast has tested with IPv6.

As Jason Livingood explains, this initial launch will occur in a few of Comcast’s pilot markets but then will be expanded as rapidly as possible to other Comcast subscribers.

For us as an industry this is outstanding news… and many congratulations to Jason, John Jason and their teams!

Now lets see the rest of the ISPs out there join Comcast in providing this level of IPv6 support!