RE: V1 Issue Status

+ public-hme-editors

From: David Dorwin [mailto:ddorwin@google.com]
Sent: Monday, June 6, 2016 3:21 PM
To: Jerry Smith (WPT) <jdsmith@microsoft.com>
Cc: Mark Watson (watsonm@netflix.com) <watsonm@netflix.com>; Matt Wolenetz <wolenetz@google.com>; Paul Cotton <Paul.Cotton@microsoft.com>
Subject: Re: V1 Issue Status

Thanks, Jerry. Some updates from my side:

PRs: I merged #216 and #218. I fixed the issues Mark identified in #217, but it still needs an LGTM. I think #215 just needs a sentence added in two places per the PR discussion. Philippe has #213 (not listed) for issue #104; this is definitely not blocking.

Issues:

  *   #117: The bulk vast majority of the work is done here. I want to review the rest for inconsistencies this week, but we can consider it "done."
  *   #110: I'm now looking at this and will have an update soon.
  *   #181: I also want to review this for any remaining issues this week, but it should be mostly done.


On Mon, Jun 6, 2016 at 11:23 AM, Jerry Smith (WPT) <jdsmith@microsoft.com<mailto:jdsmith@microsoft.com>> wrote:
I did a quick pass through the open V1 issues:

Issue

Milestone

Title

Spec

PR in Review

Status

Current Assignee

#206

V1

Note "at risk" features in the specification before CR transition

EME

Awaiting PR

jdsmith3000

#176

V1

Add event handler attributes (e.g. onkeystatuseschange on MediaKeySession) needs implementation

EME

#215

PR in review

jdsmith3000

#168

V1

Privacy: Ensure the user can clear all identifiers and other data that might enable tracking needs review

EME

#216

PR ready for merge

ddorwin

#117

V1

Refine the definition of Distinctive Identifier needs implementation

EME

#218

PR ready for merge

ddorwin

#110

V1

Individualization text regarding device identifiers is overly broad and restrictive blocked

EME

Resolve with #117?

ddorwin

#85

V1

"tracked" sessions: architectural concerns pending resolution with TAG Interoperability

EME

Pending TAG

No one

#78

V1

Update reference from HTML5.0 to HTML 5.1 needs implementation

MSE

#84

PR in review

plehegar

#69

V1

Move VideoPlaybackQuality object to a separate extension spec needs implementation

MSE

Awaiting PR

wolenetz

#24

V1

suspending and notifying resumption of a download for a media element fetching from a MediaSource needs implementation

MSE

#85

PR in review

wolenetz

#18

V1

Should fetch algorithm failure trigger detaching from a media element? needs implementation

MSE

#86

PR in review

wolenetz

#5

V1

Seekable differs from non-MSE behavior interoperability needs implementation

MSE

Awaiting PR

wolenetz




Awaiting PR

3


PR in review

4


PR ready for merge

2



Pending TAG

1


Resolve with #117?

1



Total

11


I suggest we strive to complete and merge the “PR in review” and “PR ready to merge” (my take) items today, if possible.  That would leave 3 current V1 issues to resolve by this Thursday.

There are 8 V1NonBlocking issues open that may also have a Thursday deadline this week:

Issue

Milestone

Title

Spec

PR in Review

Status

Current Assignee

#221

V1NonBlocking

Complete review of security and privacy considerations sections help wanted needs review

EME

#220

V1NonBlocking

Resolve question of support for insecure contexts

EME

#219

V1NonBlocking

Add more specific text about ensuring the desired privacy and cryptographic properties of identifiers help wanted

EME

#197

V1NonBlocking

How should the capability to decode unencrypted media data be checked?

EME

#181

V1NonBlocking

Fix algorithm inconsistencies

EME

#217

#149

V1NonBlocking

initDataType matching needs to be more explicit to provide for future evolution Interoperability needs author input

EME

#104

V1NonBlocking

EME registry: Establish a update process & home

EME

#60

V1NonBlocking

WebM bytestream format is too restrictive around "random access points"

MSE


Jerry