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

Concurrent streams: detection vs enforcement

From: Mark Watson <watsonm@netflix.com>
Date: Tue, 5 May 2015 09:18:59 -0700
Message-ID: <CAEnTvdCpa8gvwSY7uAQH1Zj6KN5u6g2_L2SLRE4bGJAz9xSiYg@mail.gmail.com>
To: "public-html-media@w3.org" <public-html-media@w3.org>
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 16:19:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 May 2015 16:19:27 UTC