16:15:20 RRSAgent has joined #drm 16:15:20 logging to http://www.w3.org/2014/10/29-drm-irc 16:15:26 Zakim has joined #drm 16:15:52 Topic: TPAC session - Legal Restrictions, DRM and the W3C 16:16:03 Chair: DOB 16:16:21 Scribe: olivier 16:17:02 Noriya has joined #DRM 16:17:17 dob: introducing the topic 16:17:39 [round of introduction] 16:17:52 JCVerdie, MStar 16:18:23 Noriya has joined #drm 16:19:00 dob: note that often technologist find DRM a problem implementation-wise 16:19:13 Paul Cotton, co-chair HTML WG, Microsoft 16:19:20 Noriya has joined #drm 16:19:39 Jerry Smith, Microsoft 16:19:52 Haakon Bratsberg, Opera 16:20:16 James Stewart, British Gov 16:20:31 So Vang, NAB 16:20:44 (NAB represents broadcasters) 16:20:54 David Dorwin, Google, editor EME spec 16:21:04 Bogdan, Microsoft 16:21:15 JP Abello, Nielsen 16:21:20 Mark Watson, Netflix 16:21:26 Ruinan Sun, Huawei 16:21:37 Noriya Sakamoto, Toshiba 16:21:55 John Foliot, invited expert, focus on accessibilitty 16:21:59 s/tty/ty/ 16:22:06 jcverdie_ has joined #drm 16:22:25 Deborah Kaplan 16:22:36 ddorwin has joined #drm 16:22:38 Rigoh Wenning, legal counsel W3C 16:22:57 haakonfb has joined #drm 16:22:59 dob: broad audience for this, some people coming to find out where we are 16:23:06 rrsagent, make logs world 16:23:19 Ruinan has joined #drm 16:23:27 dob: current solution is EME 16:23:42 EME spec -> http://www.w3.org/TR/encrypted-media/ 16:23:54 dob: want to talk about legal restrictions around DRM 16:24:35 ... general improvement in copyright control 16:24:39 paulc has joined #drm 16:25:03 ... typically copyright control attemps to compell a consumer to do something different to the range of ability they would otherwise have 16:25:13 ... e.g want to play DVD in another country 16:25:54 ... attempts to have copyright control which fit consumer behaviour more closely, fit with expectations of consumers and what they want to do with content on the web 16:26:25 ... bucket of connected issues - privacy, accessibility 16:26:44 ... some particularly fine points causing problems, but does not strike to the heart of the issue of controlling copy, access, usage 16:27:07 rrsagent, draft minutes 16:27:07 I have made the request to generate http://www.w3.org/2014/10/29-drm-minutes.html olivier 16:27:45 EME outstanding bugs: http://tinyurl.com/7tfambo 16:27:53 dob: my area of interest - issues of user controll contorl of your own device, restrictions of what can be done on your device 16:29:06 haakonfb1 has joined #drm 16:29:35 Attendees: DOB, olivier, JCVerdie, paulc, Jerry, haakonb, James, So, Ddorwin, Bogdan, Noriya, jfoliot, Deborah, Rigo 16:30:16 dob: criminal sanction when breaking (and witnessing, etc) DRM 16:30:39 ddorwin has joined #drm 16:30:49 ... would be nice to sketch out that area 16:31:09 Agenda+ Consumer irritations 16:31:21 Agenda+ Privacy, Accessibility 16:31:34 Agenda+ Philosophical issues 16:31:41 Agenda+ Legal issues 16:32:10 dob: any preference on which topic to address 16:32:39 jfoliot: as advocate for accessibility, realise that in the past most DRM were looked at a system 16:33:06 ... was a problem for accessibility as user needed to modify the system to address disability 16:33:26 Re EME and Accessibility: see https://www.w3.org/Bugs/Public/show_bug.cgi?id=27054 16:33:28 ... EME is different - mitigation in focus on just the content and not the player and ecosystem 16:34:20 ... on why I think w3c should continue work on this - PF group will look at the specs through the lens of impact on people with disabilities 16:34:46 ... we can't stop a spec in its track, but carry a large stick, so if something is going to introduce a lot of accessibility issues we have a mandate to raise it 16:34:50 ddorwin has joined #drm 16:35:20 ... we want to make sure anything that emerges will not clash with non-discrimination laws 16:35:54 ... while I understand that in principle DRM is distateful, but if we are going to work on a tech best to work on it at W3C 16:36:12 deborah: we are at a point where we can make things better 16:36:28 ... content providers are not going to make content available in a way that is not protected 16:36:53 ... if we can deliver that content in a way that is standards based, works with accessible viewer/reader, can use accessible tools 16:37:27 ... alternative would be proprietary and would not see accessibility prioritised 16:38:25 dob: area of influence of w3c is in the wrapper 16:39:02 jfoliot: because of the way we can provide support material e.g captions 16:39:26 ... technology being moved forward in way that these can be in-band, or in separate track and coming from 3rd party source 16:39:26 dkaplan3 has joined #drm 16:40:03 ... concern about that - if the media asset and captions are encrypted with different CDM, what then? 16:40:11 ... at least here I can ask that question 16:40:14 jystewart has joined #drm 16:41:22 ... example - we are adding requirements for deaf/blind people 16:41:32 ... requires screen reader - many available on the market 16:41:58 ... for average production company they would not be able to take proprietary solution and test with assistive tech 16:42:23 ... standard promises interop 16:42:36 markw has joined #drm 16:42:49 paulc: dropped link to bug related to EME and accessibility, raised by TAG -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=27054 16:43:12 ... requirement to have similar accessibility as you would without EME 16:43:27 ... no-one has identified any concrete changes yet 16:43:57 dob: part of legal issues around restrictions and limitations revolves around access/accessibility 16:44:05 ... ability to format-shift 16:44:25 ... part of the challenge is that content is not available to the rest of the interface but could be accessed (legally) and transformed 16:44:46 ... TAG is raising this issue but we do not have model for how video could be transformed 16:45:05 paulc: if you remove EME what changes here? 16:45:13 dob: the fact that it would be illegal 16:45:50 haakonfb has joined #drm 16:46:30 [scribe missed conversation, technical issues with IRC client] 16:46:58 deborah: legal question on fair use for right to transform for accessibility reason 16:47:16 ... case law not yet established 16:48:05 dob: tension you've got is that would be perceived as a straw to suck content out 16:48:25 deborah: international copyright law not yet covering this 16:48:43 ... nothing the W3C can do right now 16:49:24 dob: there is something normative here happening - discussion on using HTTPS to convey content (for privacy) 16:50:05 ... one of the bugs raised is that it is often necessary to identify user 16:50:20 ... general concern that traffic may identify user uniquely 16:50:29 ... suggestion that communication be encrypted 16:50:58 ... issues around that - practicality, role of w3c in raising and solving one set of privacy issues around DRM 16:51:40 paulc: similar to discussion at IETF - discussed, answer was no 16:52:17 dkaplan3 has joined #drm 16:52:32 ... some people believe https MUST be used, other think it should be a SHOULD at most 16:52:43 EME bug on usage of HTTPS: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26332 16:53:19 olivier: explain that requiring https throws things like caching out of the window 16:53:39 paulc: that was the main argument against making TLS mandatory 16:53:40 Rossen_ has joined #drm 16:54:15 rigo has joined #drm 16:54:26 JF has joined #drm 16:54:30 mark: practical issues concerning us is almost the opposite 16:54:57 ... large volume of content, would have impact on capacity 16:55:12 ... we don't actually like people caching our content 16:55:30 ... causes hard to debug customer problems 16:56:06 paulc: expect we will see this request made in other places - not just for media 16:56:45 ddorwin: point to next session on privacy 16:57:08 ... monitoring etc 16:57:17 rigo: there is no option of not doing it 16:58:06 mark: discussion of cost of flipping switch 16:59:31 dob: feel that there is similar interaction between consensus (privacy) and awareness of challenges 17:00:22 ... want to make sure we talk about issues that are outside of w3c 17:00:35 ... broader copyright issue with accessibility 17:00:57 ... problems would largely go away if legal framework was reformed 17:01:19 mark: want to go back to specific issue with DRM and privacy 17:01:31 ... mitigation on identifiers 17:01:49 ... discussion would not have happened if we hadn't been doing this in w3c 17:02:27 rigo: do you plan to expose rights metadata? 17:03:05 ... everyone agreed (at workshop - date?) that it would be good. 17:03:24 paulc: relationship to DRM? should probably be solved for any data 17:03:31 rigo: sounds like a great semantic web project 17:04:03 jfoliot: emergence of schema.org somewhat solves that 17:04:14 ... was talking with Chaals on using metadata for accessibility 17:04:30 ... technology is emergent, need to solve this for all data on web 17:04:52 ... locking mechanism for encrypted content - serving metadata would add value 17:05:22 dob: closed format or DRM means no way of deriving metadata 17:05:27 ... so you need a system to ask 17:05:56 ... people wanting to copy-control also want to control metadata too 17:06:20 ... because it may be a revenue opportinuty (e.g what's playing on the radio) 17:06:45 Attendee+ MichaelGood 17:07:02 michael: how does EME address customer irritation? 17:07:16 mark: use case of content subscription 17:07:42 ... understanding that you do not own content 17:07:52 ... EME would work for this use case alone 17:08:07 ddorwin: we are using it for rental and purchases 17:08:17 ... there is a difference there 17:08:35 ... "buying" on the web is different 17:09:15 mark: issues when advertising does not match reality. not "getting a digital copy" 17:09:48 jfoliot: worked at Capital record - through the years music did not change but carriers did 17:09:57 ... when you buy, you buy the carrier, not the content 17:10:15 ... consumer irritants often about player being locked down 17:10:22 ... putting malicious software in the player 17:11:40 olivier: similar feeling about EME - adding malicious software to inherently open software - until now 17:12:24 jfoliot: you are not going to convince everybody - but think that we can work to fix this perception problem 17:13:01 ... need to do a better job at transparency / explaining the reality of the pain points 17:13:16 ... less of a technical problem than a marketing problem 17:14:24 paulc: AD BREAK - consider attending HTML WG meeting on Friday morning 17:14:31 ... start at 9 17:14:39 ... triage EME bugs 17:15:11 ddorwin: public-restrictedmedia mailing-list where things such as fair use are being discussed 17:15:46 dob: do think a lot of these things are within purview of w3c - we can discuss issues of e.g accessibility and wider legal context 17:15:50 See http://www.w3.org/community/restrictedmedia/ and http://lists.w3.org/Archives/Public/public-restrictedmedia/ 17:16:02 ... even though mostly engineering, good to have such discussions 17:16:08 RRSAgent, make minutes 17:16:08 I have made the request to generate http://www.w3.org/2014/10/29-drm-minutes.html olivier 17:17:30 Present: DOB, olivier, JCVerdie, paulc, Jerry, haakonb, James, So, Ddorwin, Bogdan, Noriya, jfoliot, Deborah, Rigo, MichaelGood 17:17:37 rrsagent, make minutes 17:17:37 I have made the request to generate http://www.w3.org/2014/10/29-drm-minutes.html olivier 17:26:15 paulc has joined #drm 17:26:22 rrsagent, generate the minutes 17:26:22 I have made the request to generate http://www.w3.org/2014/10/29-drm-minutes.html paulc 17:26:28 haakonfb has joined #drm 17:35:38 haakonfb1 has joined #drm 17:41:45 rigo has left #drm 17:43:17 jcverdie has joined #drm 17:43:58 jcverdie has joined #drm 17:45:53 haakonfb has joined #drm 17:46:52 haakonfb has left #drm 17:46:56 jcverdie_ has joined #drm 17:47:01 jcverdie_ has left #drm 17:49:17 olivier has left #drm 18:02:59 ddorwin has joined #drm 18:04:17 ddorwin1 has joined #drm 18:07:34 jcverdie has joined #drm 18:07:38 jcverdie has left #drm