May 2012 archive

DNSSEC Roadmap for the Deploy360 Programme

The Deploy360 Programme staff has been collecting requirements and feedback for DNSSEC-related content from the community here at the Deploy360 site, from within social networks and at our ION conferences.

Based on that feedback, this document is an analysis of the IPv6-related content that needs to be added to the Deploy360 Programme website. Each section lists two areas of content:

  • Requirements – content that must be added to the site for this section to be “complete” in terms of meeting the section’s education goal.
  • Enhancements – content that we would like to add to each section. This content may be added after the required content is complete or if additional funding, staff or volunteers can be found to assist with this content.

This is a living document that will be continually updated and changed as we complete listed items, discover new items we believe need to be added and/or receive feedback from the larger community about items that need to be added or removed from the list.  (And we welcome your feedback on these documents.)

The content listed below will either be curated (i.e. found on the Internet, verified for accuracy and pointed to with a review from the Deploy360 site) or will be created by the Deploy360 team in conjunction with partners and volunteers.

Separate from the content identified here, there is also the need to translate the content on the Deploy360 site into other languages.

Feedback on this roadmap is definitely welcome. Thank you.


DNSSEC Basics

Requirements:

  • Intro document – What DNSSEC is, why it matters, etc.
  • Information about how to ensure your local DNS server will pass along DNSSEC records
  • More information about the role of DS records within parent domains
  • Information about DANE and the value it brings
  • More information about the business reasons for using the added security of DNSSEC
  • Information about how SSL and DNSSEC can work together
  • Tutorials for how to use DNSSEC at various registrars (expanding the current list)
  • Guidance on DNSSEC key rollover
  • Information about establishing a DNSSEC Policy and Practice Statement (DPS)
  • DNSSEC RFC review

Enhancements:

  • Videos/screencasts of securing and signing your domain using various registrars
  • Animated video (Common Craft-style) that explains DNSSEC to regular audience
  • Assistance in editing/updating the DNSSEC HOWTO maintained by NLnet Labs
  • Marketing-type materials for internal advocates to champion DNSSEC

Case Studies

Requirements:

  • Case study (text) with a registry
  • Case study with a registrar making DNSSEC available to customers
  • Case studies with ISPs deploying DNSSEC-validating name servers
  • Case studies with multiple developers of different types of applications

Enhancements:

  • Video case studies with all of the above
  • Design and publish “deployment scenarios” for DNSSEC that are suited to specific industry segments rather than rely solely on case studies

Tools

Requirements:

  • Tutorial on how to add CZ.NIC DNSSEC extension to Microsoft IE
  • Tutorial/info about how to configure DNSSEC using
    • BIND
    • PowerDNS
    • Unbound
    • Windows 8
    • (other servers)
  • Pointers to more of the existing videos/screencasts about DNSSEC tools

Enhancements:

  • Videos/screencasts of adding DNSSEC extensions to Chrome, Firefox, IE
  • Videos/screencasts of configuring DNSSEC using the various nameservers

Training

Requirements:

  • Identification of further courseware available for open/free usage
  • Further identification of additional train-the-trainer courseware

Enhancements:

  • Creation of additional written courseware
  • Creation of deployment-focused e-learning / video tutorials
  • Ongoing webinar series offering IPv6 education
  • Develop and standardize a training package for DNSSEC that trainers and consultants can use as a base for educating their customers

Network Operators (including registries and registrars)

Requirements:

  • Guidelines for considerations for supporting DNSSEC
    • Include information about whether or not to validate at ISP-level
  • Case studies (previously covered above)
  • Questions to ask vendors regarding DNSSEC support
  • Pointers to databases of DNSSEC-enabled software and services
  • Information about DNSSEC automation software
  • Tutorial on DNSSEC deployment at the gTLD/ccTLD level

Enhancements:

  • Commissioned analyst whitepapers on DNSSEC
  • Videos/screencasts related to DNSSEC implementation at operator level
  • Funding to assist in adding DNSSEC capability to registry/registrar software

Developers

Requirements:

  • Guidelines/best practices for adding DNSSEC support to applications
  • Case studies (previously covered above)

Enhancements:

  • Videos/screencasts showing use of DNSSEC libraries
  • Creation of additional open source test tools and/or libraries

Content Providers

Requirements:

  • Case studies
  • Information about business case / value in using DNSSEC
  • Information about how to work with registrars in signing domains
  • Information about using content delivery networks (CDNs) that support DNSSEC
  • Information about DANE and other uses of DNSSEC

Enhancements:

  • (Same video screencasts as under DNSSEC Basics)

Consumer Electronics Manufacturers

Requirements:

  • Case studies
  • Information about business case / value in using DNSSEC
  • (similar information as with Developers in how to add DNSSEC support to a device)

Enhancements:

  • (Same video screencasts as under DNSSEC Basics and Developers)

 


Enterprise Customers

Requirements:

  • More material helping C-levels understand the need to deploy DNSSEC
  • Business case / cost benefit analysis support for DNSSEC
  • Case studies
  • (Tutorials on DNSSEC configuration as referenced earlier)

Enhancements:

  • Commissioned analyst whitepapers on DNSSEC
  • Videos/screencasts related to enterprise usage of DNSSEC
  • Slides / materials to help enterprise advocates promote DNSSEC within their enterprise

IPv6 Roadmap for the Deploy360 Programme

The Deploy360 Programme staff has been collecting requirements and feedback for IPv6-related content from the community here at the Deploy360 site, from within social networks and at our ION conferences.

Based on that feedback, this document is an analysis of the IPv6-related content that needs to be added to the Deploy360 Programme website. Each section lists two areas of content:

  • Requirements – content that must be added to the site for this section to be “complete” in terms of meeting the section’s education goal.
  • Enhancements – content that we would like to add to each section. This content may be added after the required content is complete or if additional funding, staff or volunteers can be found to assist with this content.

This is a living document that will be continually updated and changed as we complete listed items, discover new items we believe need to be added and/or receive feedback from the larger community about items that need to be added or removed from the list.  (And we welcome your feedback on these documents.)

The content listed below will either be curated (i.e. found on the Internet, verified for accuracy and pointed to with a review from the Deploy360 site) or will be created by the Deploy360 team in conjunction with partners and volunteers.

Separate from the content identified here, there is also the need to translate the content on the Deploy360 site into other languages.

Feedback on this roadmap is definitely welcome. Thank you.


IPv6 Basics

Requirements:

  • Introductory video explaining what IPv6 is all about (created or curated)
  • Simplified roadmap for how to deploy IPv6
  • Instructions for how to configure IPv6 on different operating systems and mobile devices
  • Suggestions to help validate the accuracy of IPv6 capability claims of vendor products
  • Pointing to existing lists of equipment known to work with IPv6
  • Basic guidelines for IPv6 security (open up a separate section on the site?)
  • Information on network planning with IPv6
  • Guidelines for IPv6 address allocation planning
  • IPv6 routing best practices
  • IPv6 RFC review
  • How to obtain IPv6 address allocations from the RIRs
  • IPv6 diagnostic and troubleshooting tools
  • Tutorial on how to set up an IPv6 test lab using tunnelbrokers and other systems

Enhancements:

  • Videos of IPv6 configuration on different operating systems and mobile devices
  • Video/screencast of setting up an IPv6 test lab
  • Pointers and reviews to books/ebooks related to IPv6
  • Animated video (Common Craft-style) that explains IPv6 to common audience
  • Videos/screencasts related to IPv6 security

IPv6 Case Studies

Requirements:

  • Case study (text) with a large ISP
  • Case study with a wireless ISP
  • Case studies with multiple developers of different types of applications
  • Case studies with multiple content providers
  • Case studies with consumer electronics manufacturers
  • Case studies with enterprises who have moved their networks to IPv6

Enhancements:

  • Video case studies with all of the above
  • Audio versions of the case studies
  • Slide presentation(s) summarizing these case studies
  • Webinars with case study participants
  • Design and publish “deployment scenarios” for IPv6 that are suited to specific industry segments rather than rely solely on case studies

IPv6 Training

Requirements:

  • Identification of courseware available for open/free usage
  • Further identification of IPv6 courses available
  • Train-the-Trainer courseware

Enhancements:

  • Creation of additional written courseware
  • Creation of deployment-focused e-learning / video tutorials
  • Ongoing webinar series offering IPv6 education
  • Develop and standardize a training package for IPv6 that trainers and consultants can use as a base for educating their customers

Network Operators

Requirements:

  • Guidelines for considerations for moving networks to IPv6
  • Case studies (previously covered above)
  • Questions to ask vendors regarding IPv6 support
  • Pointers to databases of IPv6-enabled equipment

Enhancements:

  • Commissioned analyst whitepapers on IPv6 migration
  • Videos/screencasts related to IPv6 transition
  • Materials related to IPv6 multihoming
  • Maintaining actual database of IPv6-enabled equipment
  • Marketing materials to help operators promote IPv6 to their customers

Developers

Requirements:

  • Guidelines for migrating applications or services to IPv6
  • Case studies (previously covered above)
  • Pointers to open source or reference implementations of IPv6
  • Pointers to IPv6 test tools and sites
  • Tutorials/considerations for operating in a dual-stack environment
  • Information about IPv6 transition mechanisms
  • Information about use of “Happy Eyeballs” (RFC 6555)

Enhancements:

  • Videos/screencasts showing use of IPv6 libraries
    • Commissioning of IPv6 shows on existing developer-focused video podcasts
  • Creation of open source test tools and/or libraries

Content Providers

Requirements:

  • Case studies
  • Information about using hosting providers that support IPv6
    • Listings of IPv6 hosting providers
    • Questions to ask your current hosting provider
  • Information/tutorials about using content delivery networks (CDNs) that support IPv6
  • Information/tutorials about using relay/proxy services to IPv6-enable content
  • Information/tutorials about transition technologies identified in RFC 6589

Enhancements:

  • Videos/screencasts demonstrating IPv6 at hosting providers
  • Videos/screencasts demonstrating use of CDNs with IPv6
  • Videos/screencasts demonstrating relay/proxy services
  • Videos/screencasts demonstrating transition technologies

Consumer Electronics Manufacturers

Requirements:

  • Case studies
  • Information about business case / value in using IPv6
  • (similar information as with Developers in how to add IPv6 support to a device)

Enhancements:

  • (Same video screencasts as under IPv6 Basics and Developers)

Enterprise Customers

Requirements:

  • More material helping C-levels understand the need to deploy IPv6
  • Business case / cost benefit analysis support for IPv6
  • Case studies
  • Practical guide to IPv6 address management tools
  • Information about different types of IPv6 address blocks (PA vs PI)

Enhancements:

  • Commissioned analyst whitepapers on IPv6 migration
  • Videos/screencasts related to enterprise usage of IPv6
  • Slides / materials to help enterprise advocates promote IPv6 within their enterprise

Additional Content

The following content was requested at ION events and does not currently have a section within the Deploy360 site.

Enhancements:

  • Information about consultants
  • Online forum for user discussion at the portal

Roadmap for the Deploy360 Programme

The Deploy360 Programme staff has been collecting requirements and feedback from the community here at the Deploy360 site, from within social networks and at our ION conferences.

Based on that feedback, we have outlined the IPv6-related and DNSSEC-related content that needs to be added to the Deploy360 Programme website:

These are living documents that will be continually updated and changed as we complete listed items, discover new items we believe need to be added and/or receive feedback from the larger community about items that need to be added or removed from the list.  (And we welcome your feedback on these documents.)

Within each roadmap, the invidual sections lists two areas of content:

  • Requirements – content that must be added to the site for this section to be “complete” in terms of meeting the section’s education goal.
  • Enhancements – content that we would like to add to each section. This content may be added after the required content is complete or if additional funding, staff or volunteers can be found to assist with this content.

The content listed on these roadmaps will either be curated (i.e. found on the Internet, verified for accuracy and pointed to with a review from the Deploy360 site) or will be created by the Deploy360 team in conjunction with partners and volunteers.

Separate from the content identified here, there is also the need to translate the content on the Deploy360 site into other languages.

Feedback on these roadmaps is definitely welcome.

New Infographic on IPv6-Enabled Sites in Top 1 Million Alexa sites

How many of the top 1 million websites (according to Alexa) are using IPv6? Hackertarget.com, a provider of online security scanning services, released an infographic summarizing their research. As they say on their page:

Analysis of IPv6 enabled sites was conducted in March 2012. We have analysed the Alexa Top 1 Million sites and looked for the presence of AAAA DNS records indicating an IPv6 enabled site.

Once determined we then looked at the hosting locations, net block owners, web servers and operating systems in use. The following infographic summarises the results from the analysis.

I found a number of interesting points through the stats, such as the higher percentage of German websites with IPv6. In looking at the list of “number of IPv6 enabled site by netblock owner”, I found it interesting that the top 4 (on the bottom of the chart) seem to be two German hosting providers, a Russian hosting provider and then the Cloudflare content delivery network (CDN) – demonstrating, to me, the value of getting hosting providers and CDNs to deploy IPv6 connectivity.

It’s good that Hackertarget.com conducted this survey in March 2012 prior to World IPv6 Launch on June 6 and it would be great if they do this a month or two after World IPv6 Launch so that we could see a comparison.  We do know, for instance, that the number of sites in the Alexa top 1 million with IPv6-enabled corporate web sites will expand from the four listed here, purely based on the number of sites already signed up to participate in World IPv6 Launch.

Kudos to the Hackertarget.com team for putting this together… (and you can see the larger version by clicking on the image).

Browse more infographics.

 

Spelling Counts In Infographics!

Spelling counts! Always! Even in trendy things like "infographics"... you need to always check, check and re-check to make sure that things are spelled correctly[1].

Always.

Period. Full stop.

This morning brought a perfect illustration of this... a friend on Twitter pointed to an infographic about VoIP and telecom trends, another topic I'm interested in. I would have gladly retweeted the infographic - and would have perhaps embedded it in a blog post.

Except for one minor little detail in the headline:

Spelling counts

Oops. :-(

The problem is that misspelling "Telecom" as "Telecome" immediately makes the entire graphic suspect to me. If this is the level of error-checking they had in the graphic, what does this mean about their data?

Now granted, the data might be perfectly fine and this was just a case of someone not proofreading the headline... but it immediately makes me wonder... and makes me NOT want to retweet it or otherwise pass it along.

That includes not wanting to embed the graphic in a blog post... because I don't want typos on MY site!

And so one spelling error in the headline causes the creator of the infographic to lose the small bit of additional publicity I would have given it... and perhaps others will have the same reaction resulting in a larger loss.

Spelling always counts!

Always!

P.S. And no, I have not linked to the infographic in question from this post as I'd like to give them a chance to correct it... and I did send them a tweet about the typo, too.

[1] Unless, of course, the spelling mistakes are deliberate to illustrate a point or are part of a character in a story, etc.


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


Video: What is the role of the IETF? How does it help the Internet and open standards?

What does the Internet Engineering Task Force (IETF) do? What role does it play in setting Internet standards?

As readers are probably aware, I've been a long-time supporter and advocate of the IETF's work on open standards, writing about it both here on Disruptive Telephony and previously quite extensively over on Voxeo's Speaking of Standards blog. In my new role with the Internet Society Deploy360 Programme, of course, I'm even more directly involved and am now regularly attending IETF meetings.

For those who aren't familiar with the IETF, I recently came across this great video that explains the basics of what the IETF does:

The IETF is a great organization that is truly open to anyone to get involved. All you need to do is sign up for one of the mailing lists for one of the working groups and start reading and then participating. You can also attend one of the face-to-face IETF meetings to get even more involved.

Anyway, if you're not familiar with the IETF, do check out this video as it is a great intro!


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


Want An Awesome Summer Internship? Apply Now For the 2012 Deploy360 Internship!

Are you a college/university student looking for a summer internship where you can make a difference? Are you passionate about the need for the open Internet? Do like explaining technology to people?

Here at the Internet Society Deploy360 Programme we are currently taking applications for a summer intern to help us continue building our online content related to real-world deployment information for IPv6 and DNSSEC. This is a communications-focused internship where you’ll be helping the larger Internet community by:

  • Creating tutorials about how to deploy IPv6 and DNSSEC tools and services.
  • Finding news items related to IPv6 and DNSSEC and writing brief articles about those items for the Deploy360 blog.
  • Working with network operators, developers, content providers and enterprises to create written case studies outlining how the organization deployed IPv6 or DNSSEC.
  • Finding and reviewing online resources that we can add to our ever-growing repository of IPv6- and DNSSEC-related content

The beauty of this position is that there is plenty of flexibility to incorporate your interests. If you are interested in working with companies to develop business-related case studies – or are interested in writing longer whitepapers, that can be a large part of the role. If you have a passion for creating tutorials, that can be your focus. If you’d really like to create videos or screencasts, we have a place for that kind of content, too. The role can also include some work with web design, site organization, etc. As a small team we have a great amount of flexibility.

The cool thing is that you can see that you are helping people in terms of the comments and feedback we receive as people use the resources we’re developing and pointing to in order to actually get IPv6 or DNSSEC deployed. You’re not spending your summer working on internal projects that you wonder who will ever see. The work we do is public and visible to everyone.

Note, too, that your content, articles, etc., will also be published under your name directly on the Deploy360 site, creating a body of work you can easily reference for future employers or other projects.

A few more details:

  • This is a paid 60-day internship that will take place during June, July and/or August 2012, depending upon your schedule.
  • The position will be located in our Reston, Virginia, office.
  • You will be working on a daily basis with the other members of the Deploy360 team and will be highly engaged via chat, email, etc. This isn’t an internship where you sit at a desk in some basement corner – you will be very much part of the team.

Interested? Here’s how to apply:

  • Send an email to “d360intern@isoc.org” with information about your background and why you think you would be an excellent fit for the role.
  • In particular, if you’ve done anything with IPv6 (set up a test network?) or DNSSEC (signed a domain?) let us know that. While you don’t absolutely need to have knowledge of IPv6 or DNSSEC, it would obviously be helpful if you do. (And we can guarantee you that you will know probably more than you ever cared to know about them by the end of the internship! :-) )
  • Want to impress us? Find a recent article about IPv6 or DNSSEC that we haven’t written about on our blog and send us a writing sample of how you might create a brief blog post reviewing that article. Or go through our site and send some ideas about what we’re missing. Or create a screencast video illustrating one of our written tutorials… anything along those lines that help us see in a real form the kind of content you’d create for the site.
  • Above all, show us that you’re passionate about helping take away the pain of deploying these new technologies and helping people learn. We want people who want to make a difference and accelerate the adoption and deployment of open standards!

We’re looking to fill this internship position shortly and already have candidates to consider… so let us know soon if you are interested – the position is only open until we find someone we think is awesome!

New Statistics on IPv6-enabled BitTorrent Peers In P2P Networks

IPv6-enabled BitTorrent PeersEric Vyncke continues to crank out interesting visualizations of IPv6-related statistics.  We’d previously written about his daily IPv6 statistics, but now he’s out with new statistics about IPv6 usage within BitTorrent P2P networks.

Based on work documented in an Internet Draft, draft-vyncke-ipv6-traffic-in-p2p-networks, Eric’s interactive map is interesting to use.  At the time of this blog post, using the map you can see the following percentages of BitTorrent peers in these countries:

  • France:  3.9%
  • Romania:  1.64%
  • China:  1.09%
  • US:  0.7%

As to why the focus on BitTorrent, Eric notes:

Please note that RFC 3484 (address selection) does not apply to BitTorrent as peers are identified only by IP addresses, this, means that Teredo and even the mostly historic 6to4 are used when available. Therefore, this maps shows how many end-users could contact an IPv6-only server.

It is interesting research as another way to seek to understand the availability of IPv6 connectivity.  Kudos to Eric for making these statistics available, and it will be very interesting to see how this trends over time, particularly with World IPv6 Launch happening in just under a month on June 6, 2012!

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?