Digital Media Project-3

Dr. Jordan IsailovicEmail: jordan@jritechnology.com

Web site: http://www.jritechnology.com CPTWG 23 – II - 2005

Why do I care about the DMP?(Me and Digital Media Project)

Me as End user: I love country music; “Fair use”

• My home office• My car• My wife's car

My Course on CD: “Video Compression and MPEG Technology Fundamentals”

* Never sold to any individual, only to companies

Goals

• “Why can’t we all get along?” (Or something like this.)

– King - drag addict beaten by LA direst (after he was paid handsomely by tax payers money)

• This goal can be achieved by standardizing

• Appropriate protocols between value-chain users • At suitably identified interfaces

• Approach: “tool-kit” and “IDP Use Cases”

5th GA meeting: Major results

• 1. WD 2.0 of Interoperable DRM Platform, Phase I (IDP-1) specification

• 2. Call for Proposals for Stationary Audio and Video Devices

• 3. Development of IDP Reference Software started

• Further details at http://www.dmpf.org/project/ga05/results.html

What is next for me (maybe for you too)?

• Drive to San Diego before the NAB

• Looking forward to GA06• Date: 13-15 April

12 April: Study of SAV responses

• Host: DivX Networks

Abbreviations etc.• DMP - Digital Media Project • IDP - Interoperable DRM Platform• PAV - Portable Audio & Video Devices • SAV - Stationary Audio & Video Devices • Primitive Functions in IDP-1 WD 1.0

– Identify (Content, License, Device, Domain)– Represent (Content, Rights Expression)– Authenticate (Device)– Manage (Key, Domain)– Process (Encrypt)– Access (License)

Digital Media Project status report (After 5th General Assembly)

Information supplied by:Leonardo Chiariglione

The Digital Media Project

• Launched as Digital Media Manifesto in Jul 2003 • Manifesto published in Sep 2003

– http://www.chiariglione.org/manifesto/dmm.htm• Digital Media Project established in Dec 2003 as a non-profit

organisation– http://www.digital-media-project.org/

• The basic DMP position– Digital technologies are an asset of mankind – Creators and their proxies, intermediaries and end-users

should all benefit from them– This goal can be achieved by standardising

• Appropriate protocols between value-chain users supporting the functions they execute

• At suitably identified interfaces

• DMP develops an Interoperable DRM standard

Implementing the vision

• DMP specifications should enable innovation• DMP cannot standardise protocols for Functions

– Performed in existing value-chains • We do not know if today’s value-chains will continue to exist

– Performed in future value-chains • We do not know what future value-chains will be

• DMP can only standardise protocols for Primitive Functions performed by value-chain users because– Existing Functions are implemented as a combination of

Primitive Functions • Note that Primitive Functions are “re-used" across Functions

– Future Functions will still be combinations of• Existing Primitive Functions and• (Possibly) new Primitive Functions

The decisions at GA04

• DMP develops a Technical Specification called “Interoperable DRM Platform” (IDP)– IDP is a “tool-kit”, i.e. it contains normative

specification of elementary technologies (“tools”)

• The IDP Specification is developed in Phases– Phase I (IDP-1): specifies technologies for Portable

Audio & Video Devices (PAV) in April 2005– Phase II (IDP-2): specifies technologies for Stationary

Audio & Video Devices (SAV) in October 2005– Phase III (IDP-3): TBD

• IDP is complemented by “Use Cases”– To describe how to assemble IDP tools to build DMP DRM

Systems (e.g. PAV and SAV)

The decisions at GA05

• WD 2.0 of IDP-1 released for comments (still an early draft)– http://www.dmpf.org/project/ga05/idp-1/index.htm

• Call for Proposals on Stationary Audio and Video Devices issued– http://www.dmpf.org/project/ga05/sav_cfp.htm– Deadline for responses: 07 April 2005

• DMP Reference Software to be developed– License of use ideally based on Open Source principles

or at least allowing improvements and exploitation of the software

• TRU Call for Contributions to be issued at GA06

Some nomenclature

• A PAV is a Device capable of playing Governed Content obtained through a networked device

• A SAV is a Device capable of playing Governed Content obtained directly from a network. A SAV can also typically – Store Governed Content– Copy or Move Governed Content to another

SAV or to a PAV possibly after Adapting it– Export/Import Governed Content to/from a non

DMP DRM System.

SAV Requirements: End-users can

• Buy SAV Devices and smart cards from sellers of their choice

• Access Content – From different Service Providers – Via Broadcasting/Streaming/File download

• Perform the following Functions according to License terms– Play/Store Content – Play Stored Content – Use Stored Content at various levels of granularity– Move/Copy Stored Content to another SAV or PAV– Adapt Content– Export Stored Content e.g. to a removable media

Looking forward to GA06

• Venue: San Diego, CA• Date: 13-15 April

12 April: Study of SAV responses• Host: DivX Networks

Read more at

http://digital-media-project.org