<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Revenue Loss and Opportunities in Asia</title>
	<atom:link href="http://paytvblog.verimatrix.com/2009/12/revenue-loss-and-opportunities-in-asia/feed/" rel="self" type="application/rss+xml" />
	<link>http://paytvblog.verimatrix.com/2009/12/revenue-loss-and-opportunities-in-asia/</link>
	<description></description>
	<lastBuildDate>Thu, 24 Jun 2010 11:06:47 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom Munro</title>
		<link>http://paytvblog.verimatrix.com/2009/12/revenue-loss-and-opportunities-in-asia/comment-page-1/#comment-61</link>
		<dc:creator>Tom Munro</dc:creator>
		<pubDate>Sun, 10 Jan 2010 15:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://paytvblog.verimatrix.com/?p=158#comment-61</guid>
		<description>Good question. We’ve been DECE members from the beginning and are very supportive of the initiatives being developed, which often parallel our other standards effort participations. In particular, the DECE common container format will be a useful way to bring together a number of commercial threads that would otherwise potentially confuse consumers.

In the spirit of the DECE philosophy and again in the interests of a transparent consumer experience, supporting an umbrella DRM approach seems to be more appropriate right now than trying to fragment support and interoperability efforts. We are proactively working on a variety of DRM support directions in such a way that both service operators and consumer stand to benefit. As an example, we have already publicly demonstrated Marlin support in conjunction with the Open IPTV Forum, which is one approach to extend the revenue generation options of our existing pay-TV operator customers.

More broadly our DRM support includes all of the significant DECE systems under our MultiRights™ umbrella – e.g. from a VCAS head-end, we can support retail media delivery to Microsoft, Adobe, Marlin, and OMA devices in addition to support for our own CA clients and appropriate leverage of the rights locker function. The goal is being to provide a good consumer experience across the widest range of deployed CE devices, in a way that both service operators and users benefit.

I feel this topic needs further discussion. Look for a post dedicated to this topic post-CES.</description>
		<content:encoded><![CDATA[<p>Good question. We’ve been DECE members from the beginning and are very supportive of the initiatives being developed, which often parallel our other standards effort participations. In particular, the DECE common container format will be a useful way to bring together a number of commercial threads that would otherwise potentially confuse consumers.</p>
<p>In the spirit of the DECE philosophy and again in the interests of a transparent consumer experience, supporting an umbrella DRM approach seems to be more appropriate right now than trying to fragment support and interoperability efforts. We are proactively working on a variety of DRM support directions in such a way that both service operators and consumer stand to benefit. As an example, we have already publicly demonstrated Marlin support in conjunction with the Open IPTV Forum, which is one approach to extend the revenue generation options of our existing pay-TV operator customers.</p>
<p>More broadly our DRM support includes all of the significant DECE systems under our MultiRights™ umbrella – e.g. from a VCAS head-end, we can support retail media delivery to Microsoft, Adobe, Marlin, and OMA devices in addition to support for our own CA clients and appropriate leverage of the rights locker function. The goal is being to provide a good consumer experience across the widest range of deployed CE devices, in a way that both service operators and users benefit.</p>
<p>I feel this topic needs further discussion. Look for a post dedicated to this topic post-CES.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Petrocelli</title>
		<link>http://paytvblog.verimatrix.com/2009/12/revenue-loss-and-opportunities-in-asia/comment-page-1/#comment-60</link>
		<dc:creator>John Petrocelli</dc:creator>
		<pubDate>Thu, 07 Jan 2010 14:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://paytvblog.verimatrix.com/?p=158#comment-60</guid>
		<description>I notice Verimatrix is part of DECE.  What do you think of the DECE standard and why is verimatrix not an approved DECE DRM?</description>
		<content:encoded><![CDATA[<p>I notice Verimatrix is part of DECE.  What do you think of the DECE standard and why is verimatrix not an approved DECE DRM?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
