Skip to content

DMCA Evolution: Forum Solicits Input on Possible Changes to Notice and Takedown Procedures

June 12, 2014


The Digital Millennium Copyright Act’s (DMCA) “notice and takedown” procedure and the attendant “safe harbor” protections afforded to service providers often spark controversy and debate. Originally designed as a way to balance the interests of copyright holders and online service providers, the DMCA’s 14 year history has demonstrated that well-intended laws can quickly become outdated and misused.  Often DMCA notices are sent by, or on behalf of, competitors seeking to damage another party’s business, or by those who do not understand basic “fair use” concepts.  On the other hand, DMCA safe harbor can be manipulated and invoked by parties that Congress never intended to protect from copyright infringement liability.

Change is in the air, however, at least for traditional DMCA notice and takedown procedures. Recently, the United States Patent and Trademark Office opened a public forum in pursuit of ideas for improving the notice and takedown process explicated by the DMCA. The forum was to be the first of a series of such, all geared towards the ultimate goal of increased efficiency, as well as continued protection for copyright holders, under the DMCA. The public discussion came after a green paper released in July 2013 by the Department of Commerce’s Internet Policy Task Force examined problems with the current notice and takedown process.

The purpose of the forum, according to Patrick Ross, a USPTO spokesman, was to solicit input to answer the questions raised by rights holders, service providers and the public at large, as addressed in the green paper.

The speakers were from a diverse cross-section of those affected by the DMCA: The Software Alliance, the Computer and Communications Industry Association, the Artists Rights Society, Google and many others.

One of the most common complaints from rights holders, according to the forum, is the inability of small and medium-sized artists or enterprises (SME’s) to keep up with infringement of their work. A proposed solution to this was the encouragement of collective representation for infringement research.

Additionally, one of the main and pressing topics examined at the forum was whether standardization of forms for the notice and takedown procedure would be helpful, both to rights holders and service providers. Overall, many of the participants believed that standard forms for notices seemed a good beginning, but certainly not a good end. The feeling at the forum was that there remained much work to be done. Several of the speakers, both service providers and rights holders, stressed the need to maintain balance in any solution designed to bring more efficiency to the DMCA, so that both sides would find value in the notice and takedown procedures.

Another possible solution discussed was creating “Trusted Submitter” programs, something Google has done, to more efficiently process DMCA notices. More diverse solutions were offered as well, such as the potential creation of a certification mark or badge for Internet search results, to alert consumers which pages were authorized or licensed sites for the particular intellectual property being searched for.

Given the large volume of notices received by most service providers, which often makes responding in a timely fashion difficult and costly, this is a great moment in time to examine better and more efficient methods of protecting copyrights online. The DMCA has been an important tool, for both rights holders and service providers alike, and may need to be updated to continue as such.

As discussed at the forum, it is important to keep in mind the balancing of interests that goes into any intellectual property issues on the Internet. Rights holders must be given a fair and easy way to prevent and police infringement, while online service providers must have an opportunity to efficiently and easily handle incoming notices.  Those who abuse the notice and takedown process must also be held accountable.

()

Back To Top
Search