How To Win (DMCA) Exemptions And Influence Policyby Seth Finkelstein (EFF 2001 Pioneer Award winner for censorware decryption)
What is this?
The Digital Millennium Copyright Act (DMCA) is extensively known now, being perhaps the most hated Internet law since the Communications Decency Act censorship legislation. The DMCA's chilling effects have been widely publicized, and seem only to increase. One of the few parts of the DMCA which even attempts to moderate its far-reaching restrictions, is a provision which directs the Copyright Office of the Library of Congress to make an inquiry regarding adverse effects of one of the DMCA's prohibition on circumvention. If adverse effects are established, this office then has the power to "exempt certain classes of works from the prohibition against circumvention of technological measures that control access to copyrighted works."
These Library of Congress DMCA proceeding are to be done every three years. The last round took place in 2000. The upcoming round is the next one, for results in 2003. The schedule is that "Written comments are due by December 18, 2002", and in response to those comments "Reply comments are due by February 19, 2003." These comments are intended to be evaluated in hearings "in the spring of 2003", and depending on the results, there may then be a request for more comments.
The key documents involved are as follows:
This is a chance for an ordinary person to influence the process of policy-making, and perhaps convince the Library of Congress to grant an exemption. The author of this article (Seth Finkelstein) was one of the commenters responsible in 2000 for persuading the Library of Congress to grant one of the two exemptions determined, allowing circumvention in order to access censorware blacklists.
Why do it?
There's a common view of technical people, that participation in government falls somewhere between functionally useless and morally perverse. It's easy to deride the clueless congresscreatures, and take comfort in an idea of building an uncensorable realm located in some other dimension. And it's not encouraging to be one letter in a pile of mail to a Senator, or a few dollars versus the economic clout of copyright industries. But not all aspects of influencing government are so one-sided and unbalanced.
To begin with, making a submission in this DMCA rulemaking process is comparatively easy. Whatever gains are made, are won at a trivially small cost. This is a matter of drafting a letter, with some thought and detail. It's not a multi-million dollar lobbying campaign. It's not a lawsuit which drains someone's life. It's not anyone going to jail. Rather, it's essentially drafting a letter, the same commitment as happens every single day on so many mailing-lists and weblogs.
But unlike letters to congressional offices, these public comments are
truly read by the people who make the policy. That is in fact one of
the most astonishing aspects visible in the text of the earlier
rulemaking results. The policy-maker may not have agreed with the
arguments, may in fact have dismissed them; but there's enough
referencing and mention of the reasons for the results so as to make
it clear that the viewpoints of the public were heard. And
this consideration doesn't even require a large
What is in play?
Only one part of the DMCA is affected here (quoting the 2002 notice of inquiry):
The statutory focus of this rulemaking is limited to one subsection of section 1201: the prohibition on the conduct of circumvention of technological measures that control access to copyrighted works. ... The Librarian has no authority to limit either of the anti-trafficking provisions contained in subsections 1201(a)(2) or 1201(b).
Roughly, the only DMCA aspect which can be softened is the prohibition on accessing material. Nothing about making tools can be changed. That is, this rulemaking CANNOT make distributing DeCSS code, or eBook access programs, into an exempt act. It's clearly stated that the only effects which may be considered, relate to the access circumvention provision. This rulemaking is about doing, not coding or distributing. Those other provisions are a battle for another time.
Nonetheless, even though coding and distributing are not in play here, it's worthwhile to have as strong a record in favor of exemptions as is possible. This is for the simple reason that it may help when those next battles are fought.
What is to be done?
In order to get an exemption, there must be a "showing that the prohibition has a substantial adverse effect on noninfringing uses of a particular class of works.". Proponents have the burden of proof. The specific details are (emphasis added):
Translation: No ranting from any Libertarian Book-Of-Rand. No repetitions of "I own it and I can do whatever I want with it". There is no interest in hearing an argument about whether a license is a valid contract, or the abstract meaning of freedom and property and fair-use rights. That won't work, and will likely just waste the writer's energy and the reader's time.
Further, note the emphasis on using a "class of works". Again, this rulemaking is not about theoretical considerations. One must identify a concrete category of material. In the last round, some proposals were rejected as not being a "class of works". This idea is discussed extensively in terms of requirements, such as (emphasis added):
The Librarian found that the statutory language required that the Librarian identify a "class of works" primarily based upon attributes of the works themselves, and not by reference to some external criteria such as the intended use or the users of the works. The phrase "class of works" connotes that the shared, common attributes of the "class" relate to the nature of authorship in the "works." Thus a "class of works" was intended to be a "narrow and focused subset of the the broad categories of works of authorship *** identified in section 102." ... The starting point for a proposed exemption of a particular class of works must be the section 102 categories of authorship: literary works; musical works; dramatic works; pantomimes and choreographic works; pictorial, graphic and sculptural works; motion pictures and other audiovisual works; sound recordings; and architectural works.
While the word "class" isn't used in a computer-science sense here, just as a way to think about this for technical people, the portion discussing "shared, common attributes" could almost be taken straight from object-oriented programming definitions. In brief, the above passage might be translated as that the exemption shouldn't focus on what businesspeople call the "use case", but rather what computer-scientists call the "design pattern". That is, while the intended use is important as the basis for the exemption, the exemption itself has to be constructed in terms of a class (of works).
For example, consider censorware blacklists. The "use case" is research, investigation, and so, regarding what censorware in fact has on the blacklists. But the "class of works" is "compilations consisting of lists of websites blocked by filtering software applications".
So don't talk about fair-use as a principle in itself. Rather, focus on practical problems affecting a specific "class of works", as in perhaps "public domain works released on CSS-protected DVD disks".
This is not a situation where quantity (whether votes or money) is the key aspect. Rather, it's a case where a detailed, well-constructed, presentation can have an effect. And this is why an ordinary person can make a difference here. Better, if done properly, the requirements can even play into a technical person's strengths in formulating an argument which needs to meet certain specifications. It's just critical to keep in mind that this concerns empirical effects, not ideological axioms.
In fact, when read properly, the documentation for the rulemaking is in effect a design chart:
In addition to the necessary showing discussed above, in order to make a prima facie case for a proposed exemption, certain critical points must be established. First, a proponent must identify the technological measure that is the ultimate source of the alleged problem, and the technological measure must effectively control access to a copyrighted work. Second, a proponent must specifically explain what noninfringing activity the prohibition on circumvention is preventing. Third, a proponent must establish that the prevented activity is, in fact, a noninfringing use under current law.
The important aspect here is to organize the plea for an exemption into what lawyers call a "fact-pattern":
For example, in the specific instance of censorware ("filtering software"):
After this organization, there's unfortunately another "specification" (emphasis added):
All of this boils down to a requirement to argue that the exemption won't do more harm than good. That is, it's not enough just to find a fair-use application somewhere, anywhere. It's necessary to argue that the exemption won't turn into a figleaf to justify wholesale copyright infringement.
Again, for censorware, the case might proceed in outline that
The more these kinds of points are substantiated, the better. What's being done here is much closer to an analytic examination of various "test cases", than political theorizing.
How to do it
The Librarian wants comments organized in a certain way:
First, the commenter should identify the particular class of works that is being proposed as an exemption, followed by a summary of the argument for the exemption. The commenter should then specify the facts and evidence providing a basis for this exemption and any legal arguments in support of the exemption. Finally, the commenter may include in the comment any additional information or documentation which supports the commenter's position. If a commenter proposes that more than one class of works be exempted, each individual class proposed should be numbered and followed by a summary of the argument for that proposed class and the factual support and legal arguments in support of that class. This format of class/summary/facts/argument should be sequentially followed for each class of work proposed as necessary.
Note programmers see this all the time. It's the basic boilerplate in terms of standards for organizing parts of project. That is, roughly:
And if you have more than one class, make sure you follow best-practices and organize all class-specific material locally within its class, instead of scattering portions globally anywhere. That's quite straightforward.
Submissions can be done very conveniently, using the Copyright Office Comment submission form. It's worth looking over this form before starting, since the arrangement of the form is itself practically a summary of the requirements. Besides submitter's information, there are text boxes for:
The file attachment is described as follows:
Preferred format: text saved as PDF (.pdf). Other permissible formats: Microsoft Word Version 2000 or earlier (.doc), WordPerfect 9 or earlier (.wpd), or ASCII text (.txt). Written comments must follow the format described in the Notice of Inquiry
This submission box has a nice little link to a small requirements summary, which is worth reading. The underlying message - no theoretical ranting; they mean it.
Some background information on the details of the DMCA can be found at the Chilling Effects website, particularly the anticircumvention section. And see also the EFF's DMCA archive. It's important to thoroughly read the Copyright Office 2002 notice of inquiry. This is all the typically unpleasant but often necessary task of reading the documentation.
The reason to become involved in this process is very simple. The lawsuit you prevent may be your own.
Please send any questions or comments to email@example.com.