Questions about description of CDMs

<plh> Jerry: we started with a list of things that are acceptable and additional notes on implementation considerations

<plh> ... except for the bold part, everything was agreed upon

<plh> Paul: PLH, how does it look?

<plh> PLH: looks good, where would it go?

<plh> PLH: once we have a draft

http://www.w3.org/TR/encrypted-media/#implementation-requirements

"This section defines implementation requirements - for both user agents and Key Systems, including the CDM and server - that may not be explicitly addressed in the algorithms."

plh: Where do we put this material to make the intent clear? Should we add a note to the Security and Privacy sections to the this new material in the Implementation Requirements section?

Jerry: The Security section is mostly about external attacks. Why would a pointer there be useful?
... I could see a pointer from the Privacy section.

plh: Maybe we should consider adding a SOTD paragraph outlining where to find material about Implementation Requirements, Security and Privacy.

David: We just need to figure out where the new text goes and how to refer to it.

plh: Having a SOTD pointer to the three places AND adding the new text is the min bar.

Proposed Plan:

1. Add the new proposed text to Section 8 Implementation Requirements.

2. Add a para to Section 1 Introduction emphasizing the content of the sections on Implementation Requirements, Security and Privacy.

<plh> https://github.com/w3c/encrypted-media/pull/394

<plh> https://github.com/w3c/encrypted-media/issues/383

3. Modify PR 394 to NOT change the SOTD and to add material to Section 1 Introduction

<plh> https://github.com/w3c/encrypted-media/issues/407

4. Open a /github.com/w3c/encrypted-media/issues/407 to request/new issue to request//github.com/w3c/encrypted-media/issues/407 to request some new text as suggested by the Editors

scribe: and this text will be added to Section 8 Implementation Requirements

5. Open a new issue about the CDM definition that covers its Internet access.

<plh> 383 and 407 can be cleaned up separately

<plh> and then have a new pull request

6. Land PR 394 and one or issue 407.

7. Create a PR for the new issue on top of the above two landed changes so plh can evaluate that PR with the Team.

plh: Can we do this plan before Jun 12. ie in 6 days

STarting points are a) changing the 394 PR and b) opening the new issue from step 5.

plh will do a) today.

Issue 407 applies to Step 5 and we need step 4 done.

Jerry: will do Open a new issue to request some new text as suggested by the Editors

Step 1 is the solution to the new issue that Jerry will open.

plh and Paul to meet after June 12.

EME proposed changes

https://github.com/w3c/encrypted-media/pulls

<plh> https://github.com/w3c/encrypted-media/pull/399

PR 399 is assigned to plh and he will merge it.

<plh> https://github.com/w3c/encrypted-media/pull/401

<plh> 401 doesn't affect any test

Editors are okay with PR 401. plh will merge PR 401.

<plh> https://github.com/w3c/encrypted-media/pull/392

David: Breaking change in PR 392 and is not part of V1.

PR 394 was discussed above.

https://github.com/w3c/encrypted-media/pull/374 is also V.Next.

EME open issues

<plh> https://github.com/w3c/encrypted-media/issues/407

<ddorwin> https://github.com/w3c/encrypted-media/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20milestone%3AV1Editorial%20no%3Aassignee%20

<ddorwin> https://github.com/w3c/encrypted-media/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20milestone%3AV1NonBlocking%20no%3Aassignee%20

<plh> https://github.com/w3c/encrypted-media/issues/406

HTML issue 928 https://github.com/w3c/html/issues/928

See https://github.com/w3c/encrypted-media/issues/406

Note is in http://www.w3.org/TR/encrypted-media/#unencrypted-in-band-support-content

Editors will look at ISSUE-406. Mark will comment.

HTML issue 928 https://github.com/w3c/html/issues/928

plh: We cannot obsolete the OBJ tag. They might resolve ISSUE-928 in HTML 5.3 startin in July.

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/new issue https://github.com/w3c/encrypted-media/issues/407 to request/new issue to request/
Succeeded: s/in July/startin in July/
Present: markw ddorwin plh jdsmith Paul_Cotton
No ScribeNick specified.  Guessing ScribeNick: paulc
Inferring Scribes: paulc
Agenda: https://lists.w3.org/Archives/Public/public-hme-editors/2017Jun/0000.html

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 06 Jun 2017
Guessing minutes URL: http://www.w3.org/2017/06/06-html-media-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.