10:59:04 RRSAgent has joined #edrm 10:59:04 logging to http://www.w3.org/2012/10/31-edrm-irc 10:59:30 naomi has joined #edrm 11:00:06 Zakim has joined #edrm 11:11:20 naomi has joined #edrm 12:14:35 Shinji has joined #edrm 12:17:09 hiroki has joined #eDRM 12:17:57 Kiyoshi has joined #edrm 12:18:10 naomi has joined #edrm 12:19:36 Kiyoshi has joined #edrm 12:25:14 adrianba has joined #edrm 12:25:26 RRAgent, draft minutes 12:25:45 • RRSAgent, draft minutes 12:25:53 RRSAgent, draft minutes 12:25:53 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html Shinji 12:26:02 jens has joined #eDRM 12:26:43 timeless has joined #eDRM 12:26:57 kawakami has joined #edrm 12:27:03 timeless has changed the topic to: Extended DRM requirements for content distribution 12:27:10 trackbot has joined #eDRM 12:27:10 Sorry... I don't know anything about this channel 12:27:10 If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group) 12:27:22 RRSAgent, make logs public 12:27:35 Alan has joined #edrm 12:27:44 Meeting: Extended DRM requirements for content distribution 12:28:06 Yanagiuchi has joined #eDRM 12:28:10 CF has joined #eDRM 12:28:26 kenji has joined #eDRM 12:28:28 smaug has joined #edrm 12:28:33 kawakami has left #edrm 12:28:51 kawakami has joined #eDRM 12:29:04 Meeting: Extended DRM requirements for content distribution 12:29:33 ddorwin has joined #edrm 12:29:44 kunio has joined #eDRM 12:30:51 toru: welcome to the DRM requirements 12:31:06 ... two goal - about DRM contents 12:31:13 i/Meeting/scribe: naomi 12:31:15 ... second is how to proceed to solve the problem 12:31:17 RRSAgent, draft minutes 12:31:17 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:31:19 markw has joined #eDRM 12:31:19 noriya has joined #eDRM 12:31:30 ... prepared presentaiton which contains overview of DRM 12:31:40 ... and usecases 12:31:45 s/presentaiton/presentation/ 12:31:47 ... welcome to questions and comments 12:31:55 RRS Agent, draft minutes 12:32:05 s/RRS Agent, draft minutes// 12:32:08 kikyoshi: proposor of this session 12:32:09 RRSAgent, draft minutes 12:32:09 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:32:35 ... motivation of this session is for next IPTV 12:32:38 Chair: Toru Kobayashi 12:32:39 s/kikyoshi/Kiyoshi/ 12:32:41 ... services needs a new platform 12:32:47 ... expected to use HTML5 browser 12:32:50 koji has joined #edrm 12:32:55 ... there are discussions EME 12:32:59 present+ Josh_Soref 12:33:03 ... HTML5 WG 12:33:11 Juhani has joined #eDRM 12:33:18 present+ Adrian_Bateman 12:33:21 ... want to clarify the issues of current problems and want to discuss the business situation 12:33:24 ... simple DRM issues 12:33:34 present+ Olli_Pettay 12:33:36 ... 1. content protection 12:33:41 present+ John_Simmons 12:33:43 ... has commercial issue like premium contents 12:33:54 ... should be important of DRM issue 12:34:00 Main discussion 2 point: Content potation and Copyright protection 12:34:00 ...2. contents issue 12:34:08 ... needs permissions of holder 12:34:15 shige_ has joined #edrm 12:34:36 ... EME 12:34:46 ... simple way to the content description and workflow 12:34:57 ... it's a simple model for the content protection 12:35:06 masao has joined #edrm 12:35:09 ... exchanged model should cover another extention model 12:35:18 ... many issues remains for DRM 12:35:28 ... copy right protection 12:35:34 ... content package for distributing contents 12:35:44 present+ Jens_Bachmann 12:35:44 ... but we don't know how to protect the contents 12:35:56 ... second, copy control for the multiscreen devices 12:36:04 ... such as TV and tablets 12:36:13 ttanaka2 has joined #edrm 12:36:14 ... remains how to manage content control 12:36:14 present+ Mark_Watson 12:36:16 present+ Bryan_Sullivan 12:36:20 present+ David_Dorwin 12:36:23 ...3. content protection issue 12:36:24 RRSAgent, draft minutes 12:36:24 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:36:25 kaz has joined #eDRM 12:36:34 ... special devices like security device 12:36:45 rrsagent, make log public 12:36:46 ... security issues might be solved by @@@ 12:36:51 koji_ has joined #edrm 12:36:57 ... usefulness for the content protection 12:37:16 rrsagent, draft minutes 12:37:16 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html kaz 12:37:39 masayuki: will talk about extended DRM 12:37:43 ... three usecases 12:37:52 ...1 multi-keys for package 12:38:11 ... music or closed caption or movie 12:38:22 ... keys for each contents is important 12:38:28 bryan has joined #edrm 12:38:42 ... all cases contents should be packaged in HTML5 12:38:46 futomi has joined #eDRM 12:39:14 ... 2. multi-screen - private to private (home use case) 12:39:35 ... movable/copyable content from TV/STV to tablet / smart phones 12:39:46 s/1 multi-key/Use case 1: multi-key/ 12:39:50 ... he/she can enjoy contents using mobiles in everywhere 12:39:55 ... smartphone outside 12:40:02 s/2. multi-screen/use case 2: multi-screen 12:40:14 Use case 2 multi-screen (in Home case and Home to Public(outside of the Home)) 12:40:17 ... can enjoy contents but some contents should be prohibite 12:40:22 present+ Kiyoshi_Tanaka, Toru_Kohayushi, Masayuki_Ihara, Toshiaki_Tanaka, Koji_Ishii, Shigeo_Okamoto, Masahito_Kawamori, Giles_Godam-Brown, Adam_Rees, Hiroshi_Yoshida 12:40:31 RRSAgent, draft minutes 12:40:31 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:40:43 ... PUblic to private (signage use case) - premier content from Signage to smart phone 12:40:56 s/RRAgent, draft minutes// 12:40:59 ... 3. Dongle as a service portal 12:41:01 s/• RRSAgent, draft minutes// 12:41:12 ... Dongle has two interfaces 12:41:17 s/Meeting: Extended DRM requirements for content distribution// 12:41:21 RRSAgent, draft minutes 12:41:21 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:41:26 ... important as 00 12:41:39 s/Sorry... I don't know anything about this channel// 12:41:47 s/If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group)// 12:41:59 RRSAgent, draft minutes 12:41:59 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:42:06 slejeune has joined #edrm 12:42:15 ... basic function of Dongle - Android-based set top box of USB stick size 12:42:26 ... GPU and Wi-fi based on SoC 12:42:35 ... HDMI and micro USB interface 12:42:44 ... USB based power supply (500mA) 12:43:07 s/3. Dongle/Use case 3: Dongle/ 12:43:08 ... writes software can be on Dongle 12:43:13 s/scribe:/Topic: Introduction/ 12:43:14 rrsagent, draft minutes 12:43:14 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html kaz 12:43:25 ... can be use a smartphone as a controller 12:43:33 ... unit case in Japan 12:43:40 ... NTT has group companies such as DoCoMo 12:43:49 present+ Kaz_Ashimura 12:43:51 rrsagent, draft minutes 12:43:51 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html kaz 12:43:52 ... selling special cell phone like Disney' 12:43:53 s/Topic: Introduction naomi/Scribe: naomi/ 12:43:59 i/Scribe:/Topic: Introduction/ 12:44:01 ... has special contents from Disney 12:44:04 Use case 3: Dongle as a small STB (Android Base, Full HD, HDMI I/F) 12:44:05 ... technical issues 12:44:19 wseltzer has joined #edrm 12:44:25 ... how to prohibiyt to cache decrypted sub-content? 12:44:39 i/talk about extended DRM/topic: Slides/ 12:44:43 ... how to protect a copyright in case of output to external devices 12:44:43 RRSAgent, draft minutes 12:44:43 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:44:56 ... how to control functions like fast-forward in playing streaming content 12:44:58 Technical issue (Multi-key, Multi-screen, Dongle(security module)) 12:45:02 ... second issue 12:45:18 ... Dongle (as asecure device) 12:45:28 ... how to define the interface 12:45:37 ... before and after pug-in 12:45:43 ... EME extensions 12:46:00 ... questions? 12:46:05 topic: Questions 12:46:10 shin has joined #eDRM 12:46:26 kaz: please provide explanation about EME 12:46:34 ... additional idea or approach 12:47:38 scribe: timeless 12:47:50 adrianba: my question is 12:47:51 tpacbot has joined #edrm 12:47:57 ... what needs to change 12:47:57 ... to EME 12:48:00 ... to support Multiple Keys 12:48:05 ... we believe it already supports multiple keys 12:48:14 ... the diagram already supports multiple key exchanges 12:48:19 ... what part do you think is missing? 12:48:44 pal has joined #edrm 12:48:47 kaz: EME extension idea 12:48:49 MD has joined #eDRM 12:48:53 tpacbot has joined #edrm 12:48:59 ... is already discussed within Media Task force of WebTV IG 12:49:04 ... and brought to HTML WG 12:49:09 adrianba: and David and Mark 12:49:21 kaz: they're wondering what should be added to this idea 12:49:34 AA: have they already discussed multiple QQ cases 12:49:51 adrianba: here we have generate key request, and key request 12:49:57 [ adrianba walks to screen and points out ] 12:49:58 jiro has joined #edrm 12:50:03 adrianba: those are two separate key exchanges 12:50:13 ... the design of the api supports multiple media key sessions 12:50:19 Takahiro has joined #edrm 12:50:21 ... and it supports sending data back to the license service 12:50:25 ... for negotiating the key 12:50:28 ... we support that 12:50:38 q+ 12:50:39 ... it's the responsibility of the UA, Media Stack, Content Decryption module 12:50:47 ... to apply the different keys to different pieces of media 12:50:51 ... one key 12:51:17 BB: in your scope 12:51:23 ... ability to do many kinds of cases 12:51:27 ... and types of combinations 12:51:34 ... not sure what should be done in your discussion 12:51:34 s/AA/masayuki/ 12:51:41 adrianba: there's a set of bugs 12:51:45 ... on the specification 12:51:49 s/AA:/masayuki:/ 12:51:51 ... those are the topics we're currently discussing 12:52:12 glenn: have you looked at the EME spec 12:52:20 Open EME bugs: http://tinyurl.com/7tfambo 12:52:22 ... and determined if it will satisfy your needs for multi key 12:52:25 ... and if not 12:52:42 CC: i'd like to clarify 12:52:49 s/BB:/kiyoshi:/ 12:52:51 ... this is a problem of extending the spec of EME 12:52:54 s/CC:/shigeo:/ 12:52:55 jbb has joined #edrm 12:53:00 ... or is this another thing out of scope of EME 12:53:12 kinji_ has joined #edrm 12:53:19 ... some communication carriers are not satisfied with EME 12:53:34 futomi has joined #eDRM 12:53:46 john: are you saying that the EME spec doesn't provide adequate content protection? 12:53:59 shigeo: DRM system itself isn't the problem 12:54:14 ... my general understanding is that DRM is outside of EME 12:54:18 ... EME is a kind of interface 12:54:29 adrianba: we're not proposing 12:54:33 ... to standardize a DRM system 12:54:36 ... in this diagram 12:54:41 ... the Content Decryption Module 12:54:50 ... encapsulates the way to interface a particular protection system 12:54:54 ... to EME 12:55:05 ... using EME, you can use whatever content protection mechanism you have available 12:55:14 ... it's true that EME doesn't guarantee any particular level of protection 12:55:20 ... that's provided by the protection system 12:55:26 ... if that's the only part that's missing 12:55:31 ... we say that's missing by design 12:55:33 ... we're asking 12:55:39 ... for the scenarios/UCs listed here 12:55:43 ... does the spec address them 12:55:49 ... or for the stuff that's missing 12:55:53 ... what do we need to add? 12:56:04 shigeo: 2 goals 12:56:10 ... DRM/solution 12:56:17 ... my question to NTT 12:56:31 ... you're saying it's a problem of EME or something else? 12:56:46 DD: our starting point is UCs 12:56:52 ... the method 12:57:00 ... i'm not sure if it will be EME or not 12:57:09 ack: Shinji 12:57:10 ... I'm aware of EME 12:57:19 s/DD:/toru:/ 12:57:21 ... i'd like to discuss UCs 12:57:32 ... if the 3 UCs are solved by EME 12:57:37 ... then, that's great 12:57:49 ... we're asking if EME covers these three UCs 12:57:56 shigeo: can you go back to the UCs? 12:58:02 q? 12:58:02 toru: 1. Packaged contents UCs 12:58:07 ... 2. Merged Content UCs 12:58:13 ... 3. Dongle model UCs 12:58:28 ddorwin: it seems like a lot of these are Policy or CDM protection capabilities 12:58:31 ... which is out of scope 12:58:32 ... or interop 12:58:37 ... In the final page 12:58:41 ... being media stack 12:58:47 ... but, each device has a browser+media stack 12:58:51 ... there's nothing special there 12:58:58 ... protection layer underneath 12:59:03 ... application layer owned by you 12:59:12 ack Shinji 12:59:20 Shinji: technical issues 12:59:31 ... Merged Packaged Content 12:59:39 ... we can get license include key 12:59:47 RRSAgent, draft minutes 12:59:47 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 12:59:50 ... secure model 12:59:54 ... browser extension DRM can separate 12:59:58 ... we are afraid to 13:00:06 ... interface of web browser and DRM 13:00:23 ... we'd rather make a tamper resistant thing in the Dongle 13:00:28 ... i'm not sure about EME issue 13:00:38 ... we think EME may be hard to solve these problems 13:00:44 ... we want to discuss 13:00:49 ... tomorrow, firday 13:00:52 s/firday/friday/ 13:00:59 ... to talk in more detail on 13:01:03 ... RRR 13:01:09 glenn: if i understand correctly 13:01:18 ... you're concerned about 13:01:20 ... how content 13:01:27 ... is processed and stored and further transmitted 13:01:34 ... after it is already in the browser implementation 13:01:43 ... while it's an issue in the big picture for DRM as a system 13:01:54 ... it isn't exposed to the application content/JS/authors directly 13:01:54 s/RRR/ Dongle for tamper registance/ 13:02:03 ... it's an implementation issue for the Browser/CDM module 13:02:10 ... which is outside the scope of the EME activity 13:02:16 ... they define CDM as an abstraction 13:02:19 ... not concretely 13:02:21 ... my question is 13:02:32 ... to what extent is the issue you're discussing in scope for W3C as a standards body 13:02:45 ... W3C traditionally doesn't get into the implementation details of browsers 13:02:53 ... what a browser does later is up to the browser 13:03:01 ... it's within the browser/after it gets to the browser 13:03:10 markw: Mark Watson, Netflix 13:03:11 s/registance/resistence/ 13:03:18 ... some of these are out of scope for EME 13:03:20 Present+ Magnus_Olsson, Naomi_Yoshizawa, Shinji_Ishii, Noriya_Sakamoto, Katsuhiko_Kawazoe 13:03:30 ... not just because they're out of scope for EME 13:03:41 ... we let the CDM exchange data with the server side DRM 13:03:55 ... you add a key, the message exchange can have anything it want 13:04:02 ... whether output protection should be engaged, or whatever 13:04:14 ... i think a lot of the things you're asking for are functional requirements on the CDM 13:04:18 ... take them to the DRM vendors 13:04:29 ... one thing i'd say about transferring content from one device to another 13:04:32 ... you have 2 options 13:04:38 ... transfer in encrypted form 13:04:44 ... and have the EME operate on the target form 13:04:52 Present+ Niroki_Yamada, Masao_Isshiki 13:04:53 ... or you can have a device where the browser decrypts 13:05:02 rrsagent, make minutes 13:05:02 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html adrianba 13:05:12 ... and then some other scheme is applied to transfer to the other display 13:05:19 s/Niroki/Hiroki/ 13:05:23 ... and then it's up to that other scheme to deal with it 13:05:27 rrsagent, draft minutes 13:05:27 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html kaz 13:05:38 ... communication between devices before they're decrypted by EME 13:05:54 FF: this highlighted module 13:06:01 [ EME extensions slide ] 13:06:08 s/FF/Kiyoshi/ 13:06:19 s/FF/Kiyoshi:/ 13:06:27 Kiyoshi: if you say this is already covered in EME discussion 13:06:32 RRSAgent, draft minutes 13:06:32 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 13:06:48 s|s/FF/Kiyoshi:/|| 13:06:54 Kiyoshi: we must study more 13:07:01 ... if you have additional comments on UCs 13:07:04 ... or additional UCs 13:07:09 ... or additional discussion points 13:07:11 ... please let us know 13:07:36 glenn: UCs of multiple key exchange is clearly in scope for EME 13:07:42 ... output control, second screen mode, sharing 13:07:48 ... is below CDM --- out of scope 13:07:53 ... as EME is currently defined 13:08:10 ... no one in W3C has proposed attempting to standardize interface between UA and CDM 13:08:42 Kiyoshi: we think of output control 13:08:46 ... UC is very sensitive 13:08:53 ... after decryption image/audio 13:08:57 ... is distributed 13:09:05 ... this is very dangerous point for content 13:09:11 ... we want to talk about this 13:09:16 q? 13:09:18 glenn: if a UA/browser 13:09:21 q+ john 13:09:27 ... wants to work with something 13:09:35 ... then they'll need to be certified with that vendor 13:09:41 ... that's outside the scope of EME 13:09:44 ack john 13:09:51 john: i was going to say something similar to glenn 13:09:51 Present+ Christian_Fuhrhop, Craig_Smithpeters, Pierre_Lemieux 13:09:59 ... DRM has rules for protecting content 13:10:04 ... treatment of output, etc. 13:10:09 ... that's within scope of DRM system 13:10:17 ... one DRM system might have higher robustness rules 13:10:23 ... different ways of expressing output protections 13:10:28 ... as markw was describing 13:10:38 ... EME was designed to be able to talk to different DRMs 13:10:42 ... in an interoperable way 13:10:51 ... so it's opaque to the application 13:11:07 ... but the security of the system is based on the security of the CDM 13:11:13 ... the security concerns 13:11:18 ... should be brought to the DRM provider 13:11:23 ... you can say you like EME 13:11:27 ... but express concern about CDM 13:11:51 GG: what kind of place would be suitable for discussing this issue? 13:11:58 s/GG/Toru 13:12:10 ... we need to add some functionality to discuss second screen 13:12:15 ... where should we go? 13:12:16 glenn: ITU 13:12:23 [ laughter ] 13:12:36 present+ Mohammed_Dadas 13:12:43 HH: assuming EME is the standard platform 13:12:47 ... is EME the platform? 13:12:59 s/HH/Masahito/ 13:13:00 s/HH:/masahito:/ 13:13:01 ... we may need something in addition to this 13:13:15 ... "Is EME _the_ framework?" 13:13:21 john: i think there are multiple UCs here 13:13:24 ... i think each UC 13:13:33 ... a JS app, would it have to behave differently to realize a UC? 13:13:36 ... if it would have to 13:13:49 ... as adrianba asked, what can you not do today? 13:13:53 jmr has joined #eDRM 13:13:57 ... if it's something that can't be done today 13:14:06 ... then talking to EME is the right place 13:14:11 ... but some UCs, like Dongle 13:14:15 ... strike me as not web-specific 13:14:20 ... they're talking about a DRM tech 13:14:32 ... i don't see it, personally, as a web question 13:14:37 ... as a DRM tech choice 13:14:41 ... if i had a dongle based DRM tech 13:14:45 ... i could develop a CDM 13:14:49 ... and the CDM would be used by EME 13:14:55 ... and that's how the dongle would be used by EME 13:15:00 ... but that wouldn't require changes to EME 13:15:08 ... imagine i have a DRM system that uses a Secure Processor 13:15:18 ... i have the same DRM system on another device w/o Secure Processor 13:15:25 ... the difference is transparent to the EME interface 13:15:35 ... logically, in an abstract sense, the dongle is like a secure processor 13:15:48 q? 13:15:50 ... i'd argue, that it'd be disadvantageous to allow the hardware architecture of the DRM 13:15:56 ... to dictate specifics of the EME interface 13:16:09 ... it'd be disadvantageous to allow that to surface to the EME interface 13:16:15 adrianba: to extend what john said 13:16:37 ... EME is designed to provide the interfaces to facilitate communication between the DRM platform and the License Service 13:16:54 ... for the same DRM system, different deployments will want to use different methods of communication to the license service 13:16:58 ... EME supports that 13:17:16 ... question i'd like to ask before "is there some place to go to ask your questions" 13:17:27 ... is: go through the UCs using EME 13:17:40 ... and give us feedback 13:17:46 ... "we can do 99% of the UCs using EME" 13:17:52 ... "but we can't do this" 13:17:58 ... if the piece you can't do, 13:18:11 ... then maybe there's a need to be discussed in Web&TV IG 13:18:14 ... at W3C 13:18:20 ... which collected our Requirements 13:18:26 ... if there were requirements that were missed 13:18:34 ... then i'd recommend that as the venue to continue the discussion 13:18:40 ... i'd request you understand scope of EME 13:18:44 ... and understand your scenario 13:18:48 ... to see how they're addressed 13:18:58 ... keeping in mind what john, ddorwin, markw said 13:19:01 ... that the DRM is out of scpoe 13:19:05 s/scpoe/scope/ 13:19:15 BB: i agree with 13:19:23 s/BB/masayuki/ 13:19:27 ... the part that dongle being a physical thing 13:19:33 ... connected/disconnected 13:19:38 ... Is there a more discussion point 13:19:46 ... to make a best use of physical item? 13:19:53 adrianba: i think john addressed some of your question 13:20:09 ... I'd say, how you determine if the hardware device is physically connected or not 13:20:16 ... is within scope of CDM and interface to platform 13:20:22 ... it's out of scope for work we're doing @W3C 13:20:29 ... one thing you mind come back to us with 13:20:42 ... is "there's a set of errors that can be communicated to the App via the EME spec" 13:20:48 ... "to indicate why there's a failure" 13:20:58 ... a failure reason may be "hardware device isn't physically present" 13:21:16 ... feedback you could provide is "it's not very easy to build an application to clearly communicate to the that that's the specific problem" 13:21:27 ... so we want to improve the failure reporting from EME 13:21:32 ... that's an example 13:21:42 toru: thank you very much 13:21:53 [ applause ] 13:22:16 masahito: i'm a CoChair of Web&TV IG 13:22:28 ... it'd make sense for us to re-review what we had and the EME proposal 13:22:31 ... thank you 13:22:55 [ adjourned ] 13:23:03 RRSAgent, draft minutes 13:23:03 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 13:23:26 s|s/AA:/masayuki:/|| 13:23:41 Takahiro has joined #edrm 13:23:55 s/ack: Shinji// 13:24:06 s|s/FF/Kiyoshi:/|| 13:24:08 RRSAgent, draft minutes 13:24:08 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 13:24:38 trackbot, end meeting 13:24:54 Zakim, bye 13:24:54 Zakim has left #edrm 13:24:56 trackbot, bye 13:24:56 trackbot has left #edrm 13:25:01 RRSAgent, draft minutes 13:25:01 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 13:25:23 s|s/FF/Kiyoshi:/x|| 13:25:25 RRSAgent, draft minutes 13:25:25 I have made the request to generate http://www.w3.org/2012/10/31-edrm-minutes.html timeless 13:25:44 RRSAgent, bye 13:25:44 I see no action items