The Digital Media Project | |||
Source |
L. Chiariglione |
Date: |
2004/07/15 |
Title |
Call for Proposals for Portable Audio and Video Devices |
No. |
0145/Osaka |
Call for Proposals for Portable Audio and Video Devices
Executive Summary
This document is a Call for Proposals (CfP) for Solutions describing an implementation of Portable Audio and Video (PAV) Devices capable of using Governed Content according to the requirements laid down in the attached document DMP0146. The precise meaning of “Governed Content” and other terms used in this CfP is given in the attached document DMP0147.
This Call is issued by the Digital Media Project (DMP). More information about DMP can be found in the attached document DMP0148. Anybody, irrespective of its DMP membership, is entitled to respond to this Call. Deadline for responses is 20th of October 2004.
Proponents who are not DMP members will be invited to attend the DMP General Assembly to be held in Barcelona on 27th to 29th of October and to the pre-meeting on 26th of October to discuss the proposals and will be given access to the other proposals.
Proponents are advised that DMP seeks Solutions, or parts of Solutions that are licensable on a Fair and Non-Discriminatory basis. Moreover DMP may request proponents to release to DMP a source code software implementation of (the parts of their) Solution that will be retained.
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”. Please see the attached document DMP0148 for more information about DMP.
DMP operates according to a work plan whose current version foresees the development and approval of Technical Specifications for an Interoperable DRM Platform (IDP) and Interoperable End-user Devices (IED) in October 2005 and the development and approval of Recommended Practices for End-to-End Conformance (EEC) in July 2006.
In response to urgent needs from the industry DMP has decided that it will develop Technical Specifications for Interoperable End-user Devices, called Portable Audio and Video Devices (PAV), that possess a subset of features of full-fledged Interoperable End-user Devices, the most important being the ability to deal with Governed Content in an interoperable way.
DMP has defined the requirements for PAVs with the participation of a broad range of interested parties. Solutions for PAVs are the target of this Call for Proposals that invites submissions that fulfil some or all of these requirements. PAV Technical Specifications are planned for a fast track development, and will be approved in April 2005.
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.
A proposal shall provide any or all of the following:
Also, a proposal shall include all of the following:
The sole purpose of this form is to identify which requirements are satisfied by which Proponent. The merit of proposals will not be assessed on the number of requirements satisfied.
Also, a proposal may include:
All parties that believe they possess relevant technologies for Portable Audio and Video Devices that satisfy the requirements laid out in DMP0146, 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
Schlosswolfsbrunnen Weg 35
D-69118 Heidelberg
Germany
Fax |
+49 6221 98 94 47 |
|
secretariat@digital-media-project.org |
either by postal mail or (preferred) electronically, by 2004/10203T23:00 GMT.
Proposals are to be formatted as Word or HTML documents. If submitted by mail, they must be provided on a 1.44 MByte floppy disk or 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 2004/09/15.
The DMP Secretariat will post the Proposals to the password-protected DMP web site on 2004/10/21.
An ad hoc meeting of DMP experts will be held on 26 October in Barcelona to hear presentations made by proponents. Therefore all proponents, irrespective of their DMP membership, will be given access to all other proponents’ proposals.
Starting with the ad hoc meeting and continuing to GA04 (27-29 October) at the same venue, the DMP experts will evaluate the proposals, with the help of proponents, against the PAV requirements given in DMP0146.
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 PAV Technical Specification based upon the responses to this Call.
However, 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 GA04 irrespective of their membership in DMP. Attendance in further General Assemblies, however, will require membership.
Solutions that will be given preference (not in any specific order) include:
Interoperability: With its PAV Specifications DMP intends to realise the first step to DRM Interoperability defined as the ability DMP Governed Content to be Used by Devices. Note, however, the possible existence of Profiles.
Profiling: This Call for Proposals makes reference to a broad range of technologies. DMP may decide that the PAV Technical Specification will include “Profiles”, i.e. DMP-recognised subsets of PAV technologies that can be implemented in Interoperable PAV Devices.
Choice of technologies: DMP will strive to let 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: DMP’s role is to specify solutions which integrate component technologies. As a rule DMP does not develop and specify component technologies.
Severability: Proponents can respond to one or any number of requirements given in DMP0146. 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 PAV specification according to the work plan (April 2005) DMP may decide to reduce the scope of functionalities given in DMP0146
Enlargement of scope: DMP may decide to make slight enlargements to the scope of technologies identified in DMP0146. 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 PAV Technical Specification will include the means for determining conformance of Devices, services and applications to the PAV Technical Specification. Proponents are encouraged to provide technical elements to achieve this goal. However, DMP may decide to make a further Call for Proposals specifically for PAV Conformance purposes.
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 the PAV Technical Specification, in the form of Reference Software and will be an integral part of the PAV Technical Specification. DMP will have the copyright of the reference software and this may be employed by users of the standard to make products. Commitment to provide such software is required by GA04 (October 2004). Actual availability in that case is required by GA05 (January 2005). 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.
All Solutions must be licensable on a Fair and Non-Discriminatory basis.
Publication of the PAV 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 PAV Specification.
If a Trademark will be associated with the PAV Technical Specification, it will be owned and administered by DMP.
Year |
Mo. |
Day |
Time (GMT) |
Event/Action |
2004 |
07 |
15 |
|
GA03 (Osaka Meeting). This Call for Proposals is published |
|
09 |
15 |
|
Pre-registration deadline using form in Annex A (encouraged) to be sent by email or fax to DMP Secretariat |
|
10 |
20 |
23:00 |
Proposals in Word or HTML to be received by DMP Secretariat either by postal mail or (preferred) electronically. If submitted by mail, they must be provided on a 1.4MB floppy disk or an ISO9660 CD-R |
|
10 |
26 |
|
DMP Ad-Hoc Meeting for evaluation of proposals. Proponents are invited to present proposals and participate in discussions |
|
10 |
27-29 |
|
GA04 (Barcelona Meeting). Working Draft 1 produced |
|
10 |
29 |
|
Commitment to provide Reference Software |
2005 |
01 |
26-28 |
|
GA05 (venue TBD). Working Draft 2 produced |
|
01 |
24 |
|
Delivery of Reference Software |
|
04 |
13-15 |
|
GA06 (venue TBD). PAV Technical Specifications approved |
Company: |
|
Contact name: |
|
Address: |
|
Phone number: |
|
Fax: |
|
Email: |
|
|
|
Title of submission: |
|
CfP areas addressed |
|
Company: |
|
Contact name: |
|
Address: |
|
Phone number: |
|
Fax: |
|
Email: |
|
Title of submission: |
|
Abstract:
|
|
IPR status |
|
Time requested for presentation (subject to review by organisers): |
|
Demo intended: |
yes / no |
Equipment and other support required for demo: |
|
Name:
Date:
Signature:
Legend: F=fully covered
P=partly covered
N=not covered
# |
Requirement |
Covered (F/P/N) |
Comments |
1 |
Information representation |
|
|
1.1 |
Identification |
|
|
1.1.1 |
Data identification |
|
|
1.1.2 |
User identification |
|
|
1.1.3 |
Device identification |
|
|
1.1.4 |
Content format and device capability identification |
|
|
1.2 |
Content structure |
|
|
1.3 |
Digital representation of Use Data |
|
|
1.4 |
Digital representation of Rights Expressions |
|
|
2 |
Establishing trust |
|
|
2.1 |
Authentication |
|
|
2.1.1 |
Authenticating Users |
|
|
2.1.2 |
Authenticating Devices |
|
|
2.2 |
Verification of integrity |
|
|
2.2.1 |
Verification of the integrity of Content, Use Data and Executables |
|
|
2.2.2 |
Verification of the integrity of the Device software |
|
|
2.3 |
Certification |
|
|
2.3.1 |
Certifying Users |
|
|
2.3.2 |
Certifying Devices |
|
|
3 |
Management |
|
|
3.1 |
Key management |
|
|
3.2 |
Domain management |
|
|
3.3 |
Discovery of Device capabilities |
|
|
3.4 |
Managing confidentiality of User and Use Data |
|
|
4 |
Encryption technology |
|
|
5 |
Processing Content |
|
|
5.1 |
Copy/Move |
|
|
5.2 |
Backup/Restore |
|
|
5.3 |
Export |
|
|
5.4 |
Import |
|
|
5.5 |
Transferring Content to an external rendering device via a secure transport mechanism |
|
|
6 |
Support for payment methods and mechanisms |
|
|
7 |
Conformance issues |
|
|
7.1 |
Rights Expressions |
|
|
7.2 |
Enforcing Rights Expressions |
|
|
7.3 |
Tamper resistance |
|
|