Re: [w3ctag/design-reviews] Write up the Secure Stop issue for ddorwin (#73)

Hi TAG, all,

I'm sure the WG is always happy to have any and all technical feedback, but
the feature has not changed at all since the last TAG review and (unless I
missed it) the WG has not asked for a TAG review, so I am not sure if one
is necessary ?

...Mark

On Thu, Jul 23, 2020 at 1:16 PM Xiaohan Wang <notifications@github.com>
wrote:

> As requested, filling out the current issue template here:
>
> *Title*: TAG review of EME "persistent-usage-record" session
>
> *Summary*: Support a new MediaKeySessionType “persistent-usage-record
> session”, for which the license and key(s) are not persisted and for which
> a record of key usage is persisted when the keys available within the
> session are destroyed.
>
>    - Explainer¹ (minimally containing user needs and example code):
>    https://github.com/xhwang-chromium/encrypted-media/blob/pur-session/persistent-usage-record-session-explainer.md

>    - Specification URL:
>       - As in latest EME editors draft:
>       https://w3c.github.io/encrypted-media/

>       - Diff against the current EME spec: w3c/encrypted-media#462
>       <https://github.com/w3c/encrypted-media/pull/462>
>    - Tests: https://wpt.fyi/results/encrypted-media

>    - Security and Privacy self-review²:
>    https://github.com/xhwang-chromium/encrypted-media/blob/pur-session/persistent-usage-record-session-tag-security-and-privacy.md

>    - GitHub repo: https://github.com/w3c/encrypted-media/

>    - Primary contacts (and their relationship to the specification):
>       - Joey Parrish, @joeyparrish <https://github.com/joeyparrish>,
>       [Google]
>       - Greg Freedman, @gregwfreedman <https://github.com/gregwfreedman>,
>       [Netflix]
>       - Xiaohan Wang, @xhwang-chromium
>       <https://github.com/xhwang-chromium>, [Google]
>       - Mark Watson, @mwatson2 <https://github.com/mwatson2>, [Netflix]
>    - Organization(s)/project(s) driving the specification: Google, Netflix
>    - Key pieces of existing multi-stakeholder review or discussion of
>    this specification:
>       - Previous TAG discussion: #73
>       <https://github.com/w3ctag/design-reviews/issues/73>
>       - Previous W3C meeting discussion:
>       https://www.w3.org/2019/07/02-me-minutes.html#item07

>    - External status/issue trackers for this specification (publicly
>    visible, e.g. Chrome Status):
>       - https://chromestatus.com/feature/5638708017496064

>
> *Further details*:
>
>    - I have reviewed the TAG's API Design Principles
>    <https://w3ctag.github.io/design-principles/>
>    - The group where the work on this specification is currently being
>    done: Media Working Group
>    - Major unresolved issues with or opposition to this specification:
>    None
>
> We'd prefer the TAG provide feedback as (please delete all but the desired
> option):
>
> 💬 leave review feedback as a *comment in this issue* and @-notify
> @xhwang-chromium <https://github.com/xhwang-chromium>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3ctag/design-reviews/issues/73#issuecomment-663210837>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABZ57CZUT5JVADBFAJYYBFDR5CLCZANCNFSM4BPUJXFQ>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/73#issuecomment-663239380