The Digital Media Project

 

Source

L. Chiariglione

Title

Comments on "Requirements for Interoperable DRM Platforms"

No.

031012chiairglione01

 

Commented text is in italic


1. Introduction

The DRM requirements contained herein are proposed as a draft document in response to DC1 P1, “Develop RQ for DC2” with DC2 being, “Interoperable DRM platforms”. 

and "End user devices".

The authors would like to note that although the scope of DC2 is end-end, this document concentrates primarily on the End-user interface.  However, it is expected that many of the same requirements will be found in other parts of the end-end chain as well but further study and discussion among DMP participants is required to ensure completion of directive DC1 P1. 

What is the meaning of "completion of directive DC1 P1"

Also, it is suggested by the authors that for each requirement listed, an example Use case be identified to include in the document for informational purposes.

By all means this is required! See below for further requests.

2. Requirements for Interoperable DRM Platforms

The following requirements 1, 3, 4 and 5 are not only requirements that the DMP DRM shall provide specifications for but also what any implementation claiming compliance to the DMP DRM specifications shall implement. 

 The requirements found in 2 are requirements that DMP DRM shall provide specifications for but a given device can either implement or not depending on Conditions for access it is expected or able to honor. The traditional user rights in 6 are requirements that DMP DRM shall provide specifications for and any implementation claiming compliance to the DMP DRM specifications shall technically support, however the configurations to activate the requirements in 6 are not universally required to be implemented but should be at least implemented to comply with regional legal systems.

Can we then renumber RQ 2 as 5 and RQs 3, 4, 5 as RQs 2, 3, 4?

 1.   DMP DRM shall support the use of an unlimited number of configurable DRM technologies to be applied to a DMP DRM compliant bitstream/file depending on application requirements.

I understand that this stems from the general RQ that end-users should be able to access any source of content. But the way it is formulated seems more a solution that a RQ.

2.   DMP DRM shall provide specifications for DMP DRM compliant implementations supporting the following functionalities as determined by Rights expressions and Conditions associated with a given DMP DRM compliant bitstream/file.

a.   DMP DRM shall support the transfer over unsecure channels of governed DMP DRM compliant bitstreams/files while in a cleartext state.

Where does this RQ come from?

b.   DMP DRM shall support a DMP bitstream/file to exist in a DRM governed state unless stored in or accessed from a DMP DRM compliant device or virtual environment.

What purpose does this RQ serve?

c.  DMP DRM shall support the persistent binding or association of an individual person or entity with DMP DRM compliant bitstreams/files.

Why don't we introduce the therm User as in MPEG-21?

d.   DMP DRM shall support the anonymous acquisition and use of DMP DRM compliant bitstreams/files.

Why do we have to specify this? It seems more like a TRU.

e.   DMP DRM shall support the transfer of DMP DRM compliant bitstreams/files on DMP DRM compliant devices.

This seems natural, to the border of pleonasm.

f.   DMP DRM shall support the storage and transfer of DMP DRM compliant bitstreams/files on non-DMP DRM compliant devices.

Why is this needed?

g.   DMP DRM shall support the transfer of DMP DRM compliant bitstreams/files between one given DMP DRM compliant DRM implementation and another DMP DRM compliant DRM implementation.

Gobi Desert scenario, I guess? ;-)

h.  DMP DRM shall support trust relationships to be determined as existing between DMP DRM compliant devices, applications, services, and DMP DRM compliant bitstreams/files.

Shall we make it the first?

3.   Although a DMP compliant bitstream/file shall be able to be transmitted in cleartext, it shall be transmission-agnostic, able to exist as a file or be transmitted by wire or wireless, and it shall by packetisable over TCP/IP and other packet-based transport protocols, e.g. MPEG-2 TS.

I do not understand the relationship between the sentence Although...cleartext, and the rest.

4.   DMP DRM shall support the persistent association of Rights Expressions and Conditions to DMP DRM compliant bitstreams/files.

OK

5.   DMP DRM shall support the persistent and unique identification of DMP DRM compliant bitstreams/files and their derivatives.

OK

6.   DMP DRM shall technically support the implementation of the following traditional user rights in a manner that is extendable for additional rights and is configurable to legal mandates imposed by regional jurisdictions.

a.   DMP DRM shall technically support the implementation of the use of DMP DRM compliant bitstreams/files for review, editorial or other critical works.

OK

b.   DMP DRM shall technically support the implementation of the "First sale" principle.

This seems to me is an example of a case where one does indeed need to effect this "mapping from the analogue to the digital space" because if this principle is taken literally there is no means to have digital media economy

c.   DMP DRM shall technically support the implementation of the right to quote.

Is this not 6.a. above?

d.   DMP DRM shall technically support the implementation of the loan, transfer by intent (including by inheritance or last will and testament), or deletion of DMP DRM compliant bitstreams/files.

OK

 What happened of the other TRUs in the DMM?

  1. Right to make personal copy

  2. Right to choose playback device

  3. Right to privacy

  4. Richt to access works whose copyright has expired