Download Compliance Rules for WMDRM10 for Network Devices Transmitters

© 2010 Microsoft Corporation. All rights reserved.
COMPLIANCE RULES FOR
WMDRM 10 FOR NETWORK DEVICES TRANSMITTERS
1. DEFINITIONS
The following terms have the meanings set forth below. Other initially capitalized terms
not defined in these compliance rules have the meanings ascribed to them in the License
Agreement.
1.1
“Analog Component Video Output” means the set of three YPrPb
consumer electronics analog connectors.
1.2
“Analog Computer Monitor Output” means a connector for an analog
monitor typically found and associated with a PC and which carries
uncompressed analog video signals. The term expressly includes those
outputs known as VGA, SVGA, XGA, DVI Analog, and various nonstandardized analog monitor connections which have been implemented
by manufacturers, and expressly does not include such typical consumer
electronics connectors as YPrPb, S-Video and consumer RGB, whether or
not such connectors are found on any PC.
1.3
“Certificate” means a unique WMDRM object used to assess trust.
1.4
“Certificate Chain” means a collection of Certificates that assess trust back
to the Root Certificate.
1.5
“Company” means an entity licensed under a License Agreement to
develop Licensed Products.
1.6
“Consistent with the Microsoft Implementation” means the Licensed
Product (i) provides equivalent functionality to the Microsoft
Implementation, (ii) equals or exceeds the robustness of the Microsoft
Implementation, and (iii) maintains compatibility and interoperability with
the Microsoft Implementation.
1.7
“Content” means digital audio (including, but not limited to, timelinesynchronized audio, music, voice, or sounds), and /or digital video.
1.8
“Content Key” means a symmetric key or keys used to encrypt and
decrypt WMDRM Content.
1.9
“Cryptographic Keys” means Content Key, Integrity Key, Device Keys
and Device Certificate Signing Keys.
1.10
“Cryptographically Random” means unpredictable, in that no polynomialtime algorithm, given any sequence of bits, can guess the succeeding K
Compliance Rules for WMDRM 10
for Network Devices Transmitters
1
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
bits with probability greater than ½^K + 1/P(K) for any (positive)
polynomial P and sufficiently large K.
1.11
“DRI” means the OpenCable Digital Receiver Interface Protocol.
1.12
“HTTP” means HyperText Transfer Protocol.
1.13
“IP” means Internet Protocol which is a network layer protocol.
1.14
“IPv4” means “Internet Protocol Version 4”.
1.15
“IPv6” means “Internet Protocol Version 6”.
1.16
“License Agreement” means an agreement under which Microsoft licenses
entities to develop and distribute WMDRM-ND Transmitters that include
implementations of WMDRM-ND.
1.17
“Licensed Product” means a hardware device or software application (or
other software component, which may be a separately identifiable subset
of a software application or operating system), that (i) implements
WMDRM-ND functionality subject to a License Agreement and (ii) may
be capable of Transmitting.
1.18
“Media Transfer Protocol” or “MTP” means Microsoft’s Media Transfer
Protocol for device control, metadata exchange and media transfer.
1.19
“Microsoft Implementation” means the implementation of WMDRM-ND
functionality provided as source code, binaries, technical documentation
including but not limited to the Windows Media DRM for Network
Devices specification, tools and/or sample files as provided to the
Company under the License Agreement.
1.20
“WMDRM-ND Tuner” means either a WMDRM-ND Transmitter as an
MS PBDA or a WMDRM-ND Transmitter as an MS OCUR.
1.21
“Nonce” means a value that is non-repeating and Cryptographically
Random.
1.22
“Package” means the process of encrypting content into WMDRM
Content.
1.23
“Protected Time Source” means a time source that cannot be easily
circumvented.
1.24
“Receive” means to obtain WMDRM Licenses from a WMDRM-ND
Transmitter.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
2
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
1.25
“Revocation Data” means version numbers, certificate revocation lists,
system renewability messages or other data necessary to execute
revocation as described in these compliance rules.
1.26
“Revocation Data Timestamp” means the date and time information stored
to determine the time interval since last receipt of Revocation Data.
1.27
“Revocation Information Version” means a number included in WMDRM
Policy that identifies a particular version of Revocation Data.
1.28
“Robustness Rules” means the Robustness Rules for WMDRM 10 for
Devices, as amended from time to time by Microsoft.
1.29
“Root Certificate” means a Certificate controlled by Microsoft that is
trusted by the Licensed Product.
1.30
“RTSP” means Real Time Streaming Protocol.
1.31
“Security Level” means a number in the WMDRM Policy associated with
specific WMDRM Content that specifies the minimum security level
necessary for a Licensed Product to be able to acquire a WMDRM License
for the WMDRM Content.
1.32
“Transmit” means to transport WMDRM Licenses to a WMDRM-ND
Receiver.
1.33
“USB” means Universal Serial Bus.
1.34
“WMDRM” means Windows Media Digital Rights Management
technology.
1.35
“WMDRM Base License” means a reference WMDRM Policy from
which a WMDRM License is derived Consistent with the Microsoft
Implementation.
1.36
“WMDRM Content” means Content that has been encrypted using
WMDRM.
1.37
“WMDRM
1.38
“WMDRM-ND” means WMDRM for Network Devices.
1.39
“WMDRM Policy” means the description of the actions permitted and/or
required for or with audio or audiovisual content that has been encrypted
License” means a data structure that contains, but is not
limited to, an encrypted Content Key or an encrypted key used to decrypt
a Content Key associated with specific WMDRM Content, and WMDRM
Policy associated with specific WMDRM Content.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
3
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
using WMDRM and restrictions on those actions as contained in the
associated WMDRM License.
1.40
“WMDRM-ND Protocol” means a protocol used by WMDRM-ND
Transmitters and WMDRM-ND Receivers to Transmit and/or Receive.
1.41
“WMDRM-ND Receiver” means a product authorized by Microsoft to
Receive.
1.42
“WMDRM-ND Registration Seed” means a value generated by a
WMDRM-ND Transmitter used to derive WMDRM-ND Session Keys as
defined in the Microsoft Implementation.
1.43
“WMDRM-ND Transmitter” means a product authorized by Microsoft to
Transmit.
1.44
“WMDRM-ND Transmitter as an MS OCUR” means a WMDRM-ND
Transmitter that is manufactured in accordance with the specification for
OpenCable Unidirectional Receiver Host Device issued by CableLabs
(OCUR-I04-060622) and is paired with a CableCARD.
1.45
“WMDRM-ND Transmitter as an MS PBDA” means a Licensed
WMDRM-ND Transmitter device that is manufactured in accordance with
Microsoft’s PBDA specification.
1.46
“XMR License” means a WMDRM License using the Extensible Media
Rights binary data schema.
2. SCOPE. These compliance rules apply to Licensed Products implementing
WMDRM-ND Transmitter functionality. These compliance rules set forth the
requirements pursuant to which Licensed Products must enforce the WMDRM controls
for Transmitting.
3. REQUIREMENTS FOR WMDRM-ND TRANSMITTERS
3.1
Functionality. When a Licensed Product implements any WMDRM-ND
functionality, it must do so in a manner Consistent with the Microsoft Implementation.
This requirement is in addition to all of the specific compliance rules set forth in this
document. In the event of a conflict between how the Microsoft Implementation
implements a given WMDRM-ND functionality and how a specific compliance rule in
this document describes how such functionality must be implemented, the compliance
rule takes precedence.
3.2
Architecture. All WMDRM functionality implemented in a Licensed
Product must be executed in its entirety on a single device.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
4
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
3.3
Communication Protocol. The Licensed Product must use one of the
following as the communication protocol to interact with a WMDRM-ND Receiver in a
manner Consistent with the Microsoft Implementation: MTP over USB, HTTP over IP,
RTSP over IP, or DRI over IP.
3.4
Random Number Generator. The Licensed Product must implement
and make use of a random number generator that is Cryptographically Random. For the
avoidance of doubt, linear congruential random number generators are not acceptable.
3.5
Cryptographic Keys. The Licensed Product must use a secure
Cryptographically Random number generator to generate the Symmetric Keys.
3.6
Timer. The Licensed Product must implement a timer with at least one
(1) millisecond granularity.
3.7
No Circumvention. Licensed Products must not, directly (including
without limitation through the use of WMDRM-ND or any feature or functionality
thereof) or indirectly (including without limitation through any device or application
offered, sold, or marketed for use with the Licensed Product), (a) provide access to and/or
display WMDRM Content in any manner inconsistent with these compliance rules or (b)
otherwise circumvent the rights and restrictions associated with WMDRM Content.
3.8
WMDRM-ND Certificates.
3.8.1 Certificate Chain. Licensed Products must verify the validity of
the associated WMDRM-ND Receiver’s Certificate Chain Consistent with the Microsoft
Implementation. If the verification fails, the Licensed Product must not Transmit to the
associated WMDRM-ND Receiver.
3.8.2 Certificates and Keys. Licensed Products must only use
Cryptographic Keys and Certificates in a manner Consistent with the Microsoft
Implementation.
3.8.3 Root Trust Authority. Licensed Products must verify that the
WMDRM-ND Receiver Certificate inherits its trust from the Root Certificate. If the
verification of the WMDRM-ND Receiver Certificate fails, the Licensed Product must
not Transmit to the associated WMDRM-ND Receiver.
3.8.4 Security Level. Licensed Products must verify that the Security
Level of the WMDRM-ND Receiver is no less than the Security Level of the WMDRM
Policy for the requested WMDRM Content. If the verification of the Security Level fails,
the Licensed Product must not Transmit to the associated WMDRM-ND Receiver.
4. RULES FOR TRANSMITTING
.
4.1
Proximity Detection Policy
Compliance Rules for WMDRM 10
for Network Devices Transmitters
5
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
4.1.1 Round Trip Time (RTT) Verification. Licensed Products must
verify that the RTT between the Licensed Product and the associated WMDRM-ND
Receiver, as measured Consistent with the Microsoft Implementation, is no more than
seven (7) milliseconds computed with at least one (1) millisecond resolution time source.
4.1.2 Time To Live (TTL). When Transmitting over IPv4 networks,
Licensed Products must set the TTL to three (3) in IPv4 header of the proximity
challenge message.
4.1.3 Hop Count. When Transmitting over IPv6 networks, Licensed
Products must set the Hop Count to three (3) in IPv6 header of the proximity challenge
message.
4.1.4 Revalidation of WMDRM-ND Receivers. Licensed Products
must require a WMDRM-ND Receiver to successfully complete a proximity challenge at
least once every forty-eight (48) hours. If the associated WMDRM-ND Receiver has not
successfully completed a proximity challenge at least once in the preceding forty-eight
(48) hour period, the Licensed Product must not Transmit to the associated WMDRMND Receiver.
4.1.5 Nonce. Licensed Products must verify that the Nonce received
from the WMDRM-ND Receiver is equivalent to the Nonce sent by the Licensed
Product. If the verification of the Nonce fails, the Licensed Product must not Transmit to
the associated WMDRM-ND Receiver.
4.2
Revocation Data
4.2.1 Revocation Data. Licensed Products must verify the validity of
the Revocation Data, including but not limited to Revocation Information Version
structure, Consistent with the Microsoft Implementation. If the verification fails, the
Licensed Product must not Transmit.
4.2.2 WMDRM-ND Receiver Revocation. Licensed Products must
verify that none of the Certificates in the Certificate Chain associated with the WMDRMND Receiver appears in the Revocation Data. If any of the Certificates in the Certificate
Chain are present in the Revocation Data, the Licensed Product must not Transmit to the
associated WMDRM-ND Receiver.
4.2.3 Revocation Data Freshness. In addition to complying with
Sections 4.2.1 and 4.2.2, Licensed Products implementing a WMDRM-ND Transmitter
as an MS OCUR must not Transmit to the associated WMDRM-ND Receiver unless the
Issued Time on the Revocation Information Version structure is no more than ninety (90)
days prior to the current date/time received from a Protected Time Source. For the
avoidance of doubt, when the condition in this Section 4.2.3 is not met, a Licensed
Product implementing both WMDRM-ND Transmitter and WMDRM-ND Transmitter as
an MS OCUR may Transmit if (i) the Licensed Product is functioning in the capacity of a
WMDRM-ND Transmitter (not as an MS OCUR) and (ii) the Licensed Product is in
compliance with Sections 4.2.1 and 4.2.2.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
6
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
4.3
Transmitting to Concurrent WMDRM-ND Receivers
4.3.1 WMDRM-ND Transmitter. Except as otherwise required by
Section 4.3.2, Licensed Products must enforce that at most ten (10) WMDRM-ND
Receivers are able to Receive concurrently.
4.3.2 WMDRM-ND Transmitter as an MS OCUR. Notwithstanding
Section 4.3.1, Licensed Products when functioning in the capacity of a WMDRM-ND
Transmitter as an MS OCUR must enforce that at most one (1) WMDRM-ND Receiver is
able to Receive concurrently.
4.3.3 WMDRM-ND Transmitter as an MS PBDA. Notwithstanding
Section 4.3.1, Licensed Products when functioning in the capacity of a WMDRM-ND
Transmitter as an MS PBDA must enforce that at most one (1) WMDRM-ND Receiver is
able to Receive concurrently.
4.4
WMDRM-ND Protocol Messages
4.4.1 Implementation. Licensed Products must implement all
WMDRM-ND Protocol messages Consistent with the Microsoft Implementation.
4.4.2 WMDRM-ND Registration Seed. Licensed Products must use a
Cryptographically Random number generator to generate any WMDRM-ND Registration
Seed.
4.4.3 Nonce. Licensed Products must use a Cryptographically Random
number generator to generate the Nonce.
5. RULES FOR PACKAGING CONTENT
5.1
Compatibility. If Licensed Product Packages Content in a format
supported by Windows Media Player, Licensed Product must Package Content such that
it can be played back in the most recent public final release of Windows Media Player
from Microsoft. When accessed in Windows Media Player, WMDRM Content Packaged
by the Licensed Product must not cause instability, reliability, or quality problems any
more than identical content encoded with the most recent public final release of Windows
Media Encoder from Microsoft.
6. RULES FOR XMR LICENSE CREATION AND DELETION
Licensed Products may manage XMR Licenses Consistent with the Microsoft
Implementation, provided that all requirements in this Section 6 are met.
6.1
XMR Specification. Licensed Products that create XMR Licenses must
follow all the rules in this document as well as the Windows Media DRM Extensible
Media Rights Specification.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
7
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
6.2
Allowed XMR License Object Values. Licensed Products must comply
with the following restrictions on XMR License object fields specified in this Section 6.2
and may only be assigned the values specified herein.
6.2.1 Allowed Output Protection Level Restriction Values. If an
Output Protection Level field is assigned in an XMR License, it must be one of the
allowed values corresponding to the applicable field as listed in Table 1. Section 5.2 of
the Compliance Rules for Windows Media DRM 10 for Network Devices Receiver
Applications describes each allowed Output Protection Level value.
Table 1: Allowed Output Protection Level Restriction Values
Output Protection Level Field Name
Minimum Digital Compressed Audio
Output Protection Level
Minimum Uncompressed Digital Audio
Output Protection Level
Minimum Compressed Digital Video
Output Protection Level
Minimum Uncompressed Digital Video
Output Protection Level
Minimum Analog Video Output
Protection Level
Allowed Values
100, 150, 200, 250, 300
100, 150, 200, 250, 300
400, 500
100, 250, 270, 300
100, 150, 200
6.2.2 Allowed Minimum Security Level Values. A Minimum Security
Level field of the Minimum Environment Restriction object must be assigned in every
XMR License, and must be one of the values indicated in Table 2.
Table 2: Allowed Security Levels
Allowed Value
Players and devices
150 Devices that do not support
Windows Media DRM. DRM
protection is removed when the
Content is transferred to such a
device.
1000 Player applications based on
Windows Media Format 9.5 SDK
and earlier that do not meet
additional requirements for level
2000.
Devices based on Windows Media
Portable Device DRM v1.
Devices based on Windows CE
4.2 and later.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
8
Example
Devices that support Windows
Media-based Content but not
protected Content
Windows Media Player v6.4,
Windows Media Player v7
Windows Media Player for
Pocket PC or SmartPhone
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
Allowed Value
Players and devices
Example
2000 Player applications based on
Windows Media Format 7.1 Series
SDK or later, and that follow a
Windows Media Player v7.1
stricter set of Content protection
and later
guidelines than applications at
level 1000.
Portable media devices that
Devices based on Windows Media
support Windows Media DRM
DRM 10 for Portable Devices.
10 for Portable Devices
Devices based on Windows Media Windows Media Connect
DRM 10 for Network Devices.
devices
6.2.3
Source ID.
6.2.3.1
If a Licensed Product is Transmitting in connection
with WMDRM Content originating from one of the sources described in Table 3, the
Licensed Product must set the Source ID field of the Source ID object to the value
indicated in Table 3 corresponding to that source.
Table 3: Source ID
Allowed Value
Source Descriptions
1
Macrovision
2
CGMS-A
4
OpenCable Unidirectional Receiver (OCUR)
257
CPRM, CPPM
258
DTCP
259
OMA/CMLA
262
AACS (pre-recorded)
263
AACS (recordable)
265
DTCP at no greater than 520,000 pixels per frame
266
Integrated Services Digital Broadcasting
6.2.3.2
Licensed Products must not set the Source ID field of
the Source ID Object to 265 for Content with an Effective Resolution of greater than
520,000 pixels per frame.
6.2.4 Restricted Source ID. If a Licensed Product is Transmitting in
connection with WMDRM Content originating from one of the sources described in
Compliance Rules for WMDRM 10
for Network Devices Transmitters
9
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
Table 4, the Licensed Product must include a Restricted Source ID object in the XMR
License
Table 4: Allowed Source IDs for Restricted Source ID object
Source ID Field Value
4
Source Descriptions
OpenCable Unidirectional Receiver
(OCUR)
6.2.5 Allowed Revocation Information Version Values. If the
Licensed Product is a WMDRM-ND Transmitter as an MS OCUR, it must set the RIV
field of the Revocation Information Version object in the XMR License to the value of
the Sequence Number field in the Revocation Information Version structure from Section
4.2.3 of these rules.
6.2.6 Extended Analog Video Output Protection. If a Video Output
Protection GUID and corresponding Binary Configuration Data field is specified in the
Analog Video Output Configuration object in an XMR License, it must be a combination
of the values indicated in Table 5 below.
6.2.6.1
If the Licensed Product is a WMDRM-ND Tuner, then
it is allowed to specify an Analog Video Output Configuration Restriction Object with a
Video Output Protection ID field containing the value {2098DE8D-7DDD-4BAB-96C632EBB6FABEA3}.
6.2.6.2
If the Licensed Product is a WMDRM-ND Transmitter
as an MS PBDA, and if the Analog Video Output Configuration Protection Restriction
Object is specified in the WMDRM-ND License, then field values must be limited to
values listed in Table 5.
6.2.6.3
If a Licensed Product is required under Section 6.2.3.1
above, to set the Source ID field of the Source ID object to a value of 266, then the
Licensed Product must also include in the WMDRM-ND License an Explicit Analog
Video Output Protection Container Object with both: (i) an Analog Video Output
Configuration Restriction object with a Video Output Protection ID field containing the
value {811C5110-46C8-4C6e-8163-C0482A15D47E} and a Binary configuration data
field containing the value 520000 and (ii) an Analog Video Output Configuration
Restriction object with a Video Output Protection ID field containing the value
{D783A191-E083-4BAF-B2DA-E69F910B3772} and a Binary configuration data field
containing the value 520000.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
10
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
Table 5: Extended Analog Video Output Protection Values
GUID
Configuration Data
{C3FD11C6-F8B7-4d20-B0081DB17D61F2DA}
{2098DE8D-7DDD-4bab96C6-32EBB6FABEA3}
{811C5110-46C8-4C6e-8163C0482A15D47E}
{D783A191-E083-4BAFB2DA-E69F910B3772}
0, 1, 2, 3
0, 1, 2, 3
520000
520000
Output Protection
Description
AGC and Color Stripe
Explicit Analog Television
Output Restriction
Image constraint for Analog
Component Video Output
Image constraint for Analog
Computer Monitor Output
6.2.7 Allowed Minimum Copy Protection Level Values. If the
Minimum Copy Protection Level of the Copy Protection Level Restriction object is
assigned a value in an XMR License, it must be one of the values indicated in Table 6.
Table 6: Allowed Minimum Copy Protection Level Values
Allowed Value
Minimum Copy Protection Permitted
300
Copy to PD-DRM devices and WMDRM-PD devices
400
Copy to WMDRM-PD devices only
6.2.8 Allowed Copy Count Values. If the Copy Count field of the
Copy Count Restriction object is assigned a value in an XMR License, it must be less
than or equal to 250.
6.2.9 Copy Policy 2 Container. If the Copy Policy Container Object is
specified in the WMDRM-ND License then the Copy Policy 2 Container Object is not
allowed to be specified. The Copy Policy 2 Container Object may be specified only if
the Licensed Product is a WMDRM-ND Transmitter as an MS PBDA.
6.2.9.1
Copy Count 2 Restriction. If the Copy Count 2
Restriction Object is specified in the WMDRM-ND License then the allowed values for
Copy Enabler Type Object’s Copy Enabler Type field must be limited to values
described in Table 6 (Copy Enabler Type Object Values).
6.2.9.2
Copy Enabler Type. If the Copy Enabler Type Object
is specified in the WMDRM-ND License then the allowed values for the Copy Enabler
Type field must be limited to values listed in Table 7 (Copy Enabler Type Object
Values).
Table 7: Copy Enabler Type Object Values
Allowed Value
{CE480EDE-516B-40b3-90E1D6CFC47630C5}
Compliance Rules for WMDRM 10
for Network Devices Transmitters
Description
Copy to PC
11
28 April 2010
© 2010 Microsoft Corporation. All rights reserved.
Allowed Value
{6848955D-516B-4eb0-90E88F6D5A77B85F}
{C3CF56E0-7FF2-4491-809F53E21D3ABF07}
{C3FD11C6-F8B7-4D20-B0081DB17D61F2DA}
{CDD801AD-A577-48DB-950E46D5F1592FAE}
Description
Copy to device
ISDB Copy-10
Content Scrambling System (CSS)
Content Protection Recordable Media (CPRM)
6.2.9.3
Move Enabler Type. If the Move Enabler Object is
specified in the XMR License, then the Minimum Move Protection Level field must be
set to a value limited to a value listed in Table 8 (Move Enabler Type Object Values).
Table 8: Move Enabler Type Object Values
Allowed Value
Description
500
Move using an Internet service authorized by Microsoft.
6.2.10 Cannot Persist. If the Licensed Product is functioning as a
WMDRM-ND Transmitter (not as an MS OCUR) it must set the CannotPersist bit in the
Rights field of the Rights Setting Object to a value of 1.
Compliance Rules for WMDRM 10
for Network Devices Transmitters
12
28 April 2010