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

[encrypted-media] "tracked" sessions: document usage for limiting concurrent streams

From: None via GitHub <sysbot+gh@w3.org>
Date: Thu, 27 Aug 2015 22:37:28 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-103609166-1440715047-sysbot+gh@w3.org>
ddorwin has just created a new issue for 

== "tracked" sessions: document usage for limiting concurrent streams 
Given the complexity and relative inexperience of people in this group
 and the industry with using "tracked" sessions for limiting 
concurrent streams as well as open questions 
 it would be helpful to document how the “record of key usage times” 
provided by "tracked" sessions is intended to be used. This would be 
useful and important for members of this group to understand the 
feature and ensure it is adequately and accurately defined, authors 
considering using “tracked” sessions, and anyone else evaluating the 

Specific topics include:
* What times are expected
* Other assumed mechanisms, such as heartbeats and fire-and-forget 
end-of-session messages
* How to handle unexpected values or missing records
* Differentiating abuse/fraud from legitimate use cases
* Enforcement and/or clamping down to prevent abuse/fraud
* What happens in various use cases, such as non-graceful tab/browser 
closes, closing a laptop lid, and crashes.

It doesn’t necessarily need to be in the spec, but it needs to be 
somewhere that authors, implementers, and spec reviewers can 
reference. This issue tracks that need.

See https://github.com/w3c/encrypted-media/issues/84
Received on Thursday, 27 August 2015 22:37:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:49:05 UTC