Windows Media DRM Device Porting Kit Review

1. Windows Media DRM Device Porting Kit Review Scott Plette Program ManagerMedia Technology Group splette @ microsoft.com Microsoft Corporation

2. Session Outline • Windows Media DRM Device Porting Kits Today • Current DRM Ecosystem and Components • Consumer Scenarios Enabled • Windows Media DRM 10 for Portable Devices • Windows Media DRM 10 for Network Devices • Play From Device Porting Kit • New consumer scenarios • Overview of design and timeline • Next steps…

3. Windows Media DRM Device Ecosystem WM DRM for PortableDevices WM Rights Manager Format SDK Authorization Protected Content WM DRM for Network Devices Distribution Content Server

4. Windows Media DRM Platform Components • DRM for Portable Devices • For devices that are designed to store and play back audio/video content • DRM for Network Devices • Designed for any home network device intended to extend playback of audio/video content from a PC • Windows Media Rights Manager SDK • Allows content owners to specify Rights (usage rules) • Windows Media Format SDK • Used by media players that support WM DRM content

5. Windows Media DRM Consumer Scenarios • Music Purchase • Purchase a track or entire album for a fixed fee • Music Subscription • For a monthly fee, unlimited music downloads and transfer • Movie Rental • For a fee, access a movie on a PC or device for a limited time

6. Adoption of WM DRM on Devices is Growing! • Multiple portable and network devices are available on the market today • New devices are poised to enter the market shortly • Subscription services are coming online • There are already over 100 licensees of DRM device porting kits • Licensee list: http://wmlicense.smdisp.net/wmdrm10/ • Check out http://www.playsforsure.com for the latest list of devices

7. WM DRM 10 for Portable Devices • Portable version of Windows Media DRMfor devices • Acquire and store licenses/content, access offline • Device Examples: Portable Media Device, Cell Phone,STB, PDA, etc. • Similar features to the PC • No change to content encryption format: existing contentjust works • Access content using licenses with state (Expiration, Play Count) • Supports many of the new WM DRM PC features • Secure • Keys individualized per OEM, per device • Compromised or non-compliant devices can be revoked

8. WM DRM for Portable Devices Requirements • Cryptography and Signing algorithms • Block Cipher – WMDRM Algorithm which includes • Data Encryption Standard (DES) with 56-bit keys in 8 byte blocks • Rivest Cipher 4 (RC4) with 64-bit keys with Byte Streams • Public Key Infrastructure (PKI) is ECC with 160/80-bit PrivKey/PubKey • This is the private key and the Portable Device must store it securely. • Hashing algorithm is Secure Hashing Algorithm 1 (SHA-1) • Hashed Message Authentication Code (HMAC) is FIPS 198 • Local Storage • Local storage required for content and DRM Data Stores • Unique serial number required (to prevent device cloning) • Expiration requires device implements real time clock • Code Size • With all optional features enabled • 37KB Working Set (RAM) • 190KB Code Size (ROM)

9. Windows Media DRM 10 – Network Devices • Portable version of Windows Media DRM for network devices • Specification available – covers Key Exchange, Crypto,Protocol Mappings • ANSI C Porting Kit available, includes source code, specs, tools… • Stream content from a Windows XP PC • Device Examples: Digital Media Receiver, STB, Net DVD Player, Media Center Extender, etc. • Supported over UPnP, HTTP Protocols • Policy • Works with existing and new content • All DRM content is accessible – policy is enforced on PC • Device may only play back content, not allowed to persist content • Devices must register with the PC and establish proximity

10. WM DRM for Network Devices Requirements • Cryptography and Signing algorithms • Block Cipher - Advanced Encryption Standard (AES) with 128-bit keys • Public Key Infrastructure (PKI) is a 1024-bit RSA • Hashing algorithm is Secure Hashing Algorithm 1 • Message Authentication Code (MAC) is SHA-1 with 1024-bit RSA encryption and AES One-Key Cipher Block Chaining MAC 1 (OMAC1) • Local Storage • Storage must be provided for the Digital Media Receiver (DMR) and any CA certificates in the chain • May use storage to extend network buffer during streaming and playback • May not persist content for later playback • Disconnecting from PC stops all playback, flushes buffers.

11. Expanding the Ecosystem • Sharing music on portable devices is difficult • Policy prohibits content from being copied from a device • Portable devices do not interoperate with network devices • New Consumer Scenario • Users download purchase or subscription DRM content • The content is copied to a portable device that supportsWM DRM PD 10 • A user wishes to play music from his portable device on aDigital Music Receiver (DMR) at a friend’s house • The DMR enumerates all available content on the portable device • Music is “streamed” from the device over the USB connection to the DMR where it is decrypted and played

12. Expanding the Ecosystem Portable Media Device (PMD) PC Copy Content WMDRM-PD over USB WMDRM-ND over HTTP Stream Content WMDRM-ND over MTP/ USB or HTTP WM DRM for Network Devices

13. Play From Device Porting Kit • Enable Portable Devices and Media Servers to stream WM DRM content • Specification currently in development • ANSI C Porting Kit includes source code, specs, tools • Content to be streamed over MTP/USB or UPnP, HTTP protocols • Devices will transcript from WMDRM to AES before transmission • WM DRM ND devices will need to support MTP for USB scenario • Policy • Works with existing and new content • All DRM content is accessible – policy is enforced on device • Network device may only play back content, not allowedto persist content • Proximity detection will be required

14. Overview of Design and Timeline • Play From Device PK is still in design phase • Portable and Network Devices will communicate using the Media Transfer Protocol • Requires Network devices to implement MTP initiation when connected via USB • Network devices will need to support USB to host connected portable devices • Performance requirements for portable devices are a concern • Design decisions are focusing on minimizingperformance impact • We need your feedback! • Porting Kit planned for availability in 4th quarterof 2005

15. Call to Action • Help Microsoft understand your requirements for DRM on devices • What scenarios do you wish to support? • What new devices are you planning? • When will they be available in the market? • What are their performance abilities? • How can we help support your device efforts? • What problems do you experience when porting Microsoft technologies?

16. Community Resources • Windows Hardware & Driver Central (WHDC) • www.microsoft.com/whdc/default.mspx • Technical Communities • www.microsoft.com/communities/products/default.mspx • Non-Microsoft Community Sites • www.microsoft.com/communities/related/default.mspx • Microsoft Public Newsgroups • www.microsoft.com/communities/newsgroups • Technical Chats and Webcasts • www.microsoft.com/communities/chats/default.mspx • www.microsoft.com/webcasts • Microsoft Blogs • www.microsoft.com/communities/blogs

17. Additional Resources • Email – askdmd @ microsoft.com • Getting started with WM DRM • http://www.microsoft.com/windowsmedia/drm • Licensing DRM technologies for devices • http://www.microsoft.com/windows/windowsmedia/licensing/drmlicensing.aspx • Current Device DRM licensees • http://wmlicense.smdisp.net/wmdrm10/ • White Papers • http://www.microsoft.com/windows/windowsmedia/knowledgecenter/technicalarticles.aspx#digitalrightsmanagement • Related Sessions • How To Design a PlaysForSure Device • Windows Media Connect and PlaysForSure for network Devices • Cellular Phone Connectivity in Longhorn • Media Transfer Protocol Implementation Details

19. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.