The Digital Media Project  






Call for Proposals for additional DMP Technologies





Call for Proposals for additional DMP Technologies


Executive Summary

This document is a Call for Proposals for Solutions describing some or all of the component technologies needed to implement Interoperable DRM Platforms capable of Using Governed Content according to the requirements laid down in the attached document dmp1029. The precise meaning of “Governed Content” and other terms beginning with a capital letter used in this Call is given in the DMP Terminology (dmp1006).


This Call is issued by the Digital Media Project (DMP). More information about DMP can be found at Anybody, irrespective of its DMP membership, is entitled to respond to this Call. Deadline for responses is 15th of October 2007.


Proponents who are not DMP members will be invited to attend the 16th DMP General Assembly. The invitation is for the purpose of discussing the proposals. Non DMP members will be given access to all other proposals received in response to this Call.


Proponents are advised that DMP seeks technologies that are licensable on terms that are free, royalty-free or Reasonable and Non-Discriminatory (RAND). Submitters are strongly encouraged to identify the essential IP embedded in their proposals. Proposals the implementation of which requires the use of IPR that cannot be licensed on RAND terms or better will not be considered. Moreover DMP may request proponents to release to DMP a source code software implementation of (the parts of their) technologies that will be retained.


1          Introduction

The Digital Media Project (DMP) is a not-for-profit organisation registered in Geneva with the Mission to “promote continuing successful development, deployment and use of Digital Media that respect the rights of creators and rights holders to exploit their works, the wish of end users to fully enjoy the benefits of Digital Media and the interests of various value-chain players to provide products and services, according to the principles laid down in the Digital Media Manifesto”.


DMP operates according to a work plan whose current version (DMP0663) foresees the development and approval of


1.      Technical Specifications for Interoperable DRM Platform

a.       Phase I (IDP-1) in April 2005 – completed

b.      Phase II (IDP-2) in February 2006 – completed

c.       Phase III (IDP-3) in July 2007 – completed

2.      Reference software in January 2007

3.      Recommended Practices for End-to-End Conformance in July 2007

4.      Mapping of Traditional Rights and Usages to the Digital Space in July 2007

5.      Media Streaming Player Application Format (development done by ISO/IEC, expected completion in October 2007).


The “Interoperable DRM Platform (IDP)”, currently at version 3.0 and given by dmp1003, is not intended to be a monolithic standard aimed at satisfying specific application needs. It is a set of technologies – a toolkit – designed to satisfy the requirements of Primitive Functions that are executed by Users when doing business in the Value-Chain. Examples of the use of the technologies specified in the IDP to build application cases are provided by “Use Cases and Value Chains”, whose current version is given by dmp1004.


DMP is building the IDP in a step-by-step fashion. In July 2004 it issued a Call for Proposals on Portable Audio and Video Devices (PAV) using a set of requirements developed on the basis of an open process that seeks the involvement of all Value-Chain Users. In April 2005 DMP published the Phase I specification of the IDP (IDP-1). In January 2005 DMP issued a Call for Proposals on Stationary Audio and Video Devices (PAV) using a set of requirements developed with a similar process. In February 2006 DMP published the Phase II specification of the IDP (IDP-2). In February 2007 DMP published the version 2.1 specification. And in July 2007 the version 3.0 specification.


This Call for Proposals calls for technologies designed to satisfy the requirements of Primitive Functions beyond those already specified in IDP-3.0. These technologies will be added to those already existing in IDP-3.0. The resulting set of technologies will be called Interoperable DRM Platform, version 3.1 (IDP-3.1). The technologies should fit the general DMP requirements identified in IDP Functions and Requirements (dmp1029).

2          Antitrust statement on the Digital Media Project

In issuing this Call for Proposals the members of the Digital Media Project make explicit reference to the following clauses of the DMP Statutes that relate to antitrust and competition issues:


Art. 3, para. 5

The business of DMP shall not be conducted for the financial profits of its Members but for their mutual benefits. Discussions about sales levels, methods, channels of distribution, markets, customers, prices or profitability or any other topic which would restrict use of Digital Media are prohibited.


Art. 4.1, para. 3-5

The Members agree to respect all legal provisions and these Statutes concerning DMP. When developing DMP Approved Documents each applicant has to declare himself individually and collectively committed to open competition in the development of DMP Approved Documents. The Members are not restricted in any way from designing, developing, marketing and/or procuring the technologies developed.

Members are not bound to implement or use specific technology standards, or recommendations by virtue of participation in DMP.

Membership in DMP in no way obligates or requires a member to license its patents or technologies to others. If a member chooses to license its patents or technologies, membership in DMP in no way imposes, obligates or requires such member to offer such licenses on any particular terms.

3          Requirements for responding to this Call for Proposals

A proposal shall provide any or all of the following:


1.      Technologies that fulfil one or more IDP requirements relevant to the subject of this Call;

2.      Reference to other relevant standards and specifications, either ready or under development;

3.      Relationship of the proposed technologies with those already being specified in IDP-3.0;

4.      Comments on the appropriateness of the requirements and/or provision of additional IDP Requirements;

5.      Additional Use Cases.


Also, a proposal shall include all of the following:


1.      A completed Registration Form as found in Annex B;

2.      A completed Form of Annex C of which requirements are met and how.


Please note that:


1.      The sole purpose of the form in Annex C is to identify which requirements are satisfied by which Proponent.

2.      The merit of proposals will not be assessed on the number of requirements satisfied.


Also, a proposal may include:


1.      Evidence of an implementation (e.g. an accompanying demonstrator) including a detailed documented description of the system, and any other relevant information;

2.      Means to test conformance of an implementation;

3.      Any other additional information relevant to help the evaluation of the submission.

4          How to respond

All parties that believe they possess technologies that are relevant for this Call for Proposals and that satisfy the requirements laid out in dmp1029, hereinafter called “Solutions”, are invited to submit proposals for consideration by DMP. These parties do not necessarily have to be DMP members. The full list of what proponents will be expected to submit can be found below.

Proposals are to be received by:


Digital Media Project Secretariat

Eurescom GmbH


Wieblinger Weg 19

69123 Heidelberg



+49 6221 98 94 47



either by postal mail or (preferred) electronically, by 2006/03/31T23:00 GMT.

Proposals are to be formatted as Word or HTML documents. If submitted by mail, they must be provided on an ISO9660 CD-R.


Pre-registration is encouraged, as it will help in planning the evaluation process. Please use Annex A to pre-register, fill it out, and send it as an email attachment or by fax or email to the DMP Secretariat by 2006/03/15.

5          Handling of Proposals

The DMP Secretariat will post the Proposals to the password-protected DMP web site on 2007/10/16.


The DMP experts will evaluate the proposals, with the help of proponents, against the requirements given in dmp1029.


For each identified technology the evaluation will lead to either a selection of one proposal or of relevant elements from different proposals and their integration, and to the development of the 1st Working Draft (WD1) of the IDP-3.1 Specification.


However, for each technology DMP reserves the right to adopt none, one, or a combination of several proposals. All decisions will be made according to the DMP Procedures of Work.

Notwithstanding the rule of attendance at General Assemblies by DMP members only, proponents will be admitted to GA14 irrespective of their membership in DMP. Attendance in further General Assemblies, however, will require membership in DMP.

6          Evaluation criteria

Solutions that will be given preference (in no specific order) include:


·        Solutions that are based on, or built upon, open standards;

·        Solutions free of royalties and licensing fees (other than optional maintenance fees);

·        Solutions that are demonstrable (e.g. working demonstrators);

·        Solutions that are scalable in functionality;

·        Solutions exploiting commonalities and similarities among and between the various requirements and showing how they take advantage of such similarities and commonalities;

·        Solutions providing a cohesive integrated approach to as many requirements as possible as opposed to individual and non-integrated Solutions to individual requirements;

·        Solutions that integrate easily with those being specified in IDP-2.1 (dmp1029).

7          General Terms and Rules

Interoperability: DMP Technical Specifications intend to realise DRM Interoperability defined as the ability of DMP Governed Content to be Used by Devices. Note, however, that IDP is a toolkit specification.

Choice of technologies: DMP will strive to leave the choice of technologies as wide as possible while preserving Interoperability and will resort to specific choices only when so forced by the state of technology.

Integration: while the role of DMP is to specify component technologies and their integration to support specific Use Cases, as a rule DMP does not develop the specification of technologies.

Severability: Proponents can respond to one or any number of requirements given in DMP0651. DMP may decide to choose a single Solution from one Proponent or select different technologies from different Proponents and build a single solution therefrom.

Reduction of scope: for the purpose of developing the IDP-2 specification according to the work plan DMP may decide to reduce the scope of functionalities given in the work plan.

Enlargement of scope: DMP may decide to make slight enlargements to the scope of technologies identified in the work plan. DMP may decide to make only internal Calls for Proposals to acquire the necessary technologies for the enlargements.

Maintenance: Maintenance of the Technical Specification and associated software shall be the responsibility of DMP.

Conformance: The DMP work plan  foresees the development of Recommended Practices for End-to-End Conformance (EEC) as a separate DMP Approved Document. Proponents are, however, encouraged to provide technical elements to achieve this goal.

8          Source code and IPR

Proponents are advised that, upon acceptance by DMP for further evaluation, DMP may require that software support for certain parts of any proposed technology be made available in source code. Software relating to standards or publicly available specifications that are referenced in a proposed Solution will not be the subject of such a request. This code will be included in a DMP Technical Specification, in the form of Reference Software. DMP will have the copyright of the reference software that is provided by proponents or especially developed by DMP, and this may be employed by users of the standard to make products. Commitment to provide such software is required by GA17 (January 2008). Actual availability in that case is required by GA18 (April 2008). If Proponents feel that any aspects of their technology should not be made available in source code, then they should clearly state which aspects and why in their submissions should be exempted from the need to provide Reference Software.


All Solutions must be licensable at least on a Fair and Non-Discriminatory basis. Proposals the implementation of which requires the use of IPR that cannot be licensed at RAND terms or better will not be considered.


Publication of the IDP Technical Specification resulting from selection of a Solution, parts from different Solutions and their integration shall be the responsibility of DMP. Proponents will provide any license to DMP necessary for publishing the IDP Specification.


If a Trademark will be associated with the IDP or Use Case Technical Specifications, it will be owned and administered by DMP.


Annex A: Pre-Registration Form




Contact name:




Phone number:








Title of submission:


CfP areas addressed



Annex B: Registration Form




Contact name:




Phone number:






Title of submission:














IPR status


Essential IP





Time requested for presentation (subject to review by organisers):


Demo intended:

yes / no

Equipment and other support required for demo:













Annex C: Areas covered by the submission

Legend:            F=fully covered

                        P=partly covered

                        N=not covered