W3C home > Mailing lists > Public > public-html-media@w3.org > May 2015

Re: Concurrent streams: detection vs enforcement

From: Joe Steele <steele@adobe.com>
Date: Tue, 5 May 2015 17:14:19 +0000
To: Mark Watson <watsonm@netflix.com>
CC: "public-html-media@w3.org" <public-html-media@w3.org>
Message-ID: <50913EF4-6EF5-4229-B139-CCFA1214DA16@adobe.com>
That change makes sense to me.

> On May 5, 2015, at 9:18 AM, Mark Watson <watsonm@netflix.com> wrote:
> 
> I wonder if we should make it even clearer that the license renewal mechanism is targeted at *enforcement* of concurrent streams, wheras the key release mechanism is targeted at *detection* of abuse ?
> 
> Presently, the wiki titles are:
> "Limited concurrent streams via license renewal"
> 
> and
> 
> "Limited concurrent streams via key release"
> 
> I suggest we change these to:
> 
> "Enforcement of concurrent stream limits via license renewal"
> 
> and
> 
> "Detection of concurrent stream usage via key release"
> 
> It's worth noting, if there is still concern that the detection mechanism eventually getting used for enforcement, that the arguments against license renewal (UX, scalability) don't apply if enforcement is restricted just to those accounts where abuse has been detected.
> 
> Shall I make this change to the wiki ?
> 
> ...Mark
> 
> 



Received on Tuesday, 5 May 2015 17:14:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 May 2015 17:14:53 UTC