--- a/mpreq/MPTF-CP-Requirements.html Wed Jun 13 15:51:47 2012 -0600
+++ b/mpreq/MPTF-CP-Requirements.html Wed Jun 13 16:55:54 2012 -0600
@@ -131,68 +131,80 @@
<h3>General</h3>
<section>
<h4>User Rights</h4>
- <p>Content protection methods must enable the rights of the user as specified in the agreement (See item 1 in Backgroud section above).</p>
+ <h5>Content protection methods must enable the rights of the user as specified in the agreement (See item 1 in Backgroud section above).</h5>
+ <p>The user should not be restricted from accessing content for which legal rights have been obtained.</p>
</section>
<section>
<h4>Owner Rights</h4>
- <p>Content protection methods must protect the rights of the content owners as specified in the agreement.</p>
+ <h5>Content protection methods must protect the rights of the content owners as specified in the agreement.</h5>
+ <p>The content owners control the legal rights to the content. If their rights are not protected, they are less likely to produce the high-value content that drives the commercial video business.</p>
</section>
<section>
<h4>Distributor Rights</h4>
- <p>Content protection methods must protect the rights of the distribution service provider as specified in the agreement.</p>
+ <h5>Content protection methods must protect the rights of the distribution service provider as specified in the agreement.</h5>
+ <p>Content distributors also have certain rights and obligations as specified in the agreement. Content must be protected in transit so as not to be intercepted and used without authorization.</p>
</section>
<section>
<h4>Container Format</h4>
- <p>The content protection system must not advantage one specific container format over another.</p>
+ <h5>The content protection system must not advantage one specific container format over another.</h5>
+ <p>Specifically, the choice of container format should not prevent the content protection system from operating.</p>
</section>
<section>
<h4>Mandatory Baseline</h4>
- <p>The content protection solution must support at least one mandatory method that can be used to enable interoperability between different systems.</p>
- <h5>This method should be unencumbered with IPR</h5>
+ <h5>The content protection solution must support at least one mandatory method that can be used to enable interoperability between different systems.</h5>
+ <p>Support for a baseline content protection solution allows at least one method for protected content to be distributed and used. This method should be unencumbered with IPR.</p>
</section>
<section>
<h4>Browser Independence</h4>
- <p>Content protection methods must work with "open source" browsers. Specifically, the interface defined by the proposed solution should be implementable in any browser without requiring any privileged information. This scope of this requirement is limited to the interface defined in the proposed solution.</p>
+ <h5>Content protection methods must work with "open source" browsers</h5>
+ <p>Specifically, the interface defined by the proposed solution should be implementable in any browser without requiring any privileged information. This scope of this requirement is limited to the interface defined in the proposed solution.</p>
</section>
<section>
<h4>HTML5 Compatibility</h4>
- <p>Content protection must be useable in HTML5</p>
+ <h5>Content protection must be useable in HTML5</h5>
+ <p>The implementation of content protection must be capable of running within an HTML5 environment. This means any browser supportive of HTML5 will be able to specify the parameters and use the appropriate tags to get the protected content to play back.</p>
</section>
<section>
<h4>Media Elements</h4>
- <p>(consensus not yet reached) Content protection must be useable with specific HTML5 features such as media elements (and features (such as timed tracks) within these elements).</p>
+ <h5>(consensus not yet reached) Content protection must be useable with specific HTML5 features such as media elements (and features (such as timed tracks) within these elements).</h5>
+ <p>Timed text tracks and other features of HTML5 media tags must work with protected media streams as described in this requirements document. The use of any of these features must not disable or prevent the use of a compliant implementation of protected media.</p>
</section>
<section>
<h4>Encrypted Content</h4>
- <p>(consensus not yet reached) Media element features that are available in an implementation must be available for encrypted content as well as unencrypted content.</p>
+ <h5>(consensus not yet reached) Media element features that are available in an implementation must be available for encrypted content as well as unencrypted content.</h5>
+ <p>This is the corrolary to the previous requirement. The use of any compliant content protection system must not disable or prevent the use of any particular media element features.</p>
</section>
<section>
<h4>Identifiable Content Protection Method</h4>
- <p>The particular content protection method required to use the content must be identifiable.</p>
+ <h5>The particular content protection method required to use the content must be identifiable.</h5>
+ <p>It must be possible to deduce from the media stream which content protection system (if any) is required to decrypt the media stream.</p>
</section>
<section>
<h4>Common Parameters</h4>
- <p>Any parameters required for use of the content protection method must be identified and specifiable.</p>
+ <h5>Any parameters required for use of the content protection method must be identified and specifiable.</h5>
+ <p>It must be possible to determine from the media stream, the parameters that must be specified in order to decrypt the protected media stream. The primary parameters must be common across different content protection systems so that the unique details of the protection method are not required to be known in advance.</p>
</section>
<section>
<h4>Common Errors</h4>
- <p>Specific errors relevant to content protections must be identified and reportable.</p>
+ <h5>Specific errors relevant to content protections must be identified and reportable.</h5>
+ <p>It must be possible to determine from the media stream, the possible errors that may occur in the decoding of the protected media stream. The primary errors must be common across different content protection systems so that the unique details of the protection method are not required to be known in advance</p>
</section>
<section>
<h4>Adaptive Bit Rate Media</h4>
- <p>The content protection method must be compatible with the (new) media source element as described in the adaptive bit rate proposal.</p>
+ <h5>The content protection method must be compatible with the (new) media source element as described in the adaptive bit rate proposal.</h5>
+ <p>The content protection method must work with adaptive bit rate streaming as well as traditional non-adaptive streaming methods. This ensures that the content protection systems will work with emerging streaming media types.</p>
</section>
<section>
Binary file mpreq/mpreq.xcodeproj/project.xcworkspace/xcuserdata/cstevens.xcuserdatad/UserInterfaceState.xcuserstate has changed