MPTF/MPTF Discussions/Delivery to ip

From Web and TV IG

Submitter: CableLabs


Tracker Issue ID: ISSUE-51


Description: THIS HAS BEEN MERGED INTO ISSUE 40

High-value content is delivered to a range of consumer devices. These devices differ in several dimensions relevant to content protection:

  1. Hardware and software accessibility. For example, desktop personal computer hardware, buses and software are easily accessed and changed compared to smartphones with tightly controlled software environments and difficult to access hardware internals.
  2. General purpose vs purpose built user agent. A browser designed for general purpose use may contain limited, or no, content protection mechanisms whereas a purpose built user agent, for a connected TV or an application downloaded from a service provider for instance, might contain more content protection mechanisms or ones with associated license fees.
  3. Field upgrade ability. A range of software and firmware upgrade security exists from none to secure firmware to signed applications.
  4. Hardware support for content protection. Some devices will have no hardware support for content protection while others might have secure microprocessors or one time programmable memory.


Motivation:

  1. Content owners and service providers want to deliver content to devices that are in popular use by consumers. These devices represent a wide range of capabilities and potential threat opportunities with regard to content protection. A user agent needs to provide a common API to the content protection mechanisms used across this range of capabilities and potential threats.


Dependencies:


What needs to be standardized

See Common content security technical requirements.

Comments:

Retrieved from "https://www.w3.org/2011/webtv/wiki/index.php?title=MPTF/MPTF_Discussions/Delivery_to_ip&oldid=1342"