Request for immediate triaging of new issues

Could the Editors please triage new incoming MSE and EME issues as quickly as possible and tag them with V1Editorial or VNext as appropriate so that we know how late arriving issues will be processed?  Editors should also feel free to use the "feature request" tag for any "late breaking" new feature requests.

This is especially true of new issues created by the Editors themselves.

The following issues need to be triaged and tagged with a milestone ASAP.

'waitingforkey' event has no inverse
https://github.com/w3c/encrypted-media/issues/284

"EME is not intended to be an interface to technical protection measures"
https://github.com/w3c/encrypted-media/issues/288

Restrict all interfaces to secure contexts
https://github.com/w3c/encrypted-media/issues/289

Consider making MSE attachment asynchronous
https://github.com/w3c/media-source/issues/104

Non-interoperable behavior regarding invalid ISOBMFF Init Segment
https://github.com/w3c/media-source/issues/110

Confusing duration change consequences and inconsistent outcome for user agents
https://github.com/w3c/media-source/issues/124

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329