15:48:31 RRSAgent has joined #webrtc 15:48:31 logging to http://www.w3.org/2013/01/10-webrtc-irc 15:48:33 RRSAgent, make logs world 15:48:35 Zakim, this will be RTC 15:48:35 ok, trackbot; I see UW_WebRTC()11:00AM scheduled to start in 12 minutes 15:48:36 Meeting: Web Real-Time Communications Working Group Teleconference 15:48:36 Date: 10 January 2013 15:52:43 stefanh has joined #webrtc 15:54:40 Chair: stefanh, hta 15:56:27 UW_WebRTC()11:00AM has now started 15:56:34 + +1.403.244.aaaa 15:56:51 + +1.908.578.aabb 15:57:05 Zakim, code? 15:57:05 the conference code is 9782 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), dom 15:57:26 hta has joined #webrtc 15:58:06 mreavy has joined #webrtc 15:58:07 jesup has joined #webrtc 15:58:14 burn has joined #webrtc 15:58:36 +Dan_Burnett 15:58:46 zakim, I am Dan_Burnett 15:58:46 ok, burn, I now associate you with Dan_Burnett 15:58:47 Milan_Patel has joined #webrtc 15:58:48 + +46.8.50.51.aacc 15:58:57 + +46.1.07.14.aadd 15:59:02 zakim, aacc is me 15:59:03 +hta; got it 15:59:13 zakim, aadd is me 15:59:13 +stefanh; got it 15:59:18 + +972.9.957.aaee 15:59:23 fluffy has joined #webrtc 15:59:28 +Milan_Patel 15:59:52 +??P51 15:59:53 Zakim, ??P51 is me 15:59:53 +dom; got it 16:00:07 dan_romascanu has joined #webrtc 16:00:15 Agenda, and some stuff: http://www.w3.org/2011/04/webrtc/wiki/Teleconferences#Thu.2C_Jan_10_2013 16:00:17 + +1.972.999.aaff 16:00:56 + +91.22.39.14.aagg 16:00:57 nstratford has joined #webrtc 16:01:02 Zakim, I am Stefan_Hakansson 16:01:02 sorry, stefanh, I do not see a party named 'Stefan_Hakansson' 16:01:12 + +1.703.334.aahh 16:01:37 - +91.22.39.14.aagg 16:01:46 DanD has joined #WebRTC 16:01:52 Zakim, aahh is me 16:01:52 +derf; got it 16:01:59 +Dan_Druta 16:02:06 adambe has joined #webrtc 16:02:13 + +46.1.07.14.aaii 16:02:15 aaff may be me 16:02:19 + +1.630.423.aajj 16:02:28 Zakim: aaii is me 16:02:55 zakim, who is here? 16:02:55 On the phone I see +1.403.244.aaaa, +1.908.578.aabb, Dan_Burnett, hta, stefanh, +972.9.957.aaee, Milan_Patel, dom, +1.972.999.aaff, derf (muted), Dan_Druta, +46.1.07.14.aaii, 16:02:59 ... +1.630.423.aajj 16:02:59 On IRC I see adambe, DanD, nstratford, dan_romascanu, fluffy, Milan_Patel, burn, jesup, mreavy, hta, stefanh, RRSAgent, Zakim, richt, dom, derf, ed, trackbot, heath, Dweezahr, 16:02:59 ... Josh_Soref 16:03:00 Zakim, aaff is probably dan_romascanu 16:03:00 +dan_romascanu?; got it 16:03:06 Zakim, aaii is adambe 16:03:07 +adambe; got it 16:03:07 + +1.610.889.aakk 16:03:37 zakim, aakk is me 16:03:37 +jesup; got it 16:03:39 Zakim, aaaa is fluffy 16:03:39 +fluffy; got it 16:03:41 Richard has joined #webrtc 16:03:49 Zkaim, aaaa is fluffy 16:03:56 Zakim, aaaa is fluffy 16:03:56 sorry, fluffy, I do not recognize a party named 'aaaa' 16:04:12 zakim, aaaa is me 16:04:12 sorry, fluffy, I do not recognize a party named 'aaaa' 16:04:25 thanks dom 16:04:36 + +91.22.39.14.aall 16:06:39 ScribeNick: adambe 16:06:52 stefanh: let's get started 16:06:59 http://www.w3.org/2011/04/webrtc/wiki/Teleconferences#Thu.2C_Jan_10_2013 16:07:01 ... I've pasted the link to the agenda 16:07:02 tuexen has joined #webrtc 16:07:03 + +33.6.85.56.aamm 16:07:11 ... any comments/objections to the agenda 16:07:13 Agenda: http://www.w3.org/2011/04/webrtc/wiki/Teleconferences#Thu.2C_Jan_10_2013 16:07:28 Topic: Minutes approval 16:07:29 ... we need to aprove the minutes 16:07:35 ... any objections? 16:07:37 +[Mozilla] 16:07:40 minutes: http://lists.w3.org/Archives/Public/public-webrtc/2012Dec/0048.html 16:07:57 ... I consider the minutes approved 16:08:11 ... we're ending the technical session at the hour 16:08:14 JeromeMarcon has joined #webrtc 16:08:21 + +1.425.893.aann 16:08:26 Topic: Statistics API 16:08:29 ... and discuss how we use the f2f time in February 16:08:39 juberti has joined #webrtc 16:08:40 hta: I'm assuming that everyone has read the proposal 16:08:41 -> http://lists.w3.org/Archives/Public/public-webrtc/2012Dec/att-0013/RTCWEBStatsv2.pdf Stats API proposal 16:08:47 Zakim, who's here? 16:08:47 On the phone I see fluffy, +1.908.578.aabb, Dan_Burnett, hta, stefanh, +972.9.957.aaee, Milan_Patel, dom, dan_romascanu?, derf (muted), Dan_Druta, adambe, +1.630.423.aajj, jesup, 16:08:51 ... +91.22.39.14.aall, +33.6.85.56.aamm, [Mozilla], +1.425.893.aann 16:08:51 On IRC I see juberti, JeromeMarcon, tuexen, Richard, adambe, DanD, nstratford, dan_romascanu, fluffy, Milan_Patel, burn, jesup, mreavy, hta, stefanh, RRSAgent, Zakim, richt, dom, 16:08:51 ... derf, ed, trackbot, heath, Dweezahr, Josh_Soref 16:09:04 Zakim, aann is juberti 16:09:04 +juberti; got it 16:09:10 ... the most important part is that we've changed the returned report 16:09:15 - +91.22.39.14.aall 16:09:19 ... away from the local - report format 16:09:20 + +1.831.440.aaoo 16:09:25 ... into a rtc stats object 16:09:32 ... with operators 16:09:48 ... the second part is documentation format 16:09:58 matthew has joined #webrtc 16:10:01 ... we use WebIDL to describe what the data objects are 16:10:24 ... the third part is a few suggestions for stat objects 16:10:33 ... that would be part of an actual implementation 16:10:48 adam has joined #webrtc 16:10:50 ... I hope for this meeting that we can get agreement that the approach is right enough 16:11:10 ... and that we can get it into the spec 16:11:38 +33.6.85.56.aamm = Jerome Marcon 16:11:39 ... we can work out the the details as we move on 16:11:39 - +1.908.578.aabb 16:11:44 Zakim, aamm is JeromeMarcon 16:11:44 +JeromeMarcon; got it 16:11:46 ... that was the intro.. questions? 16:11:48 q+ 16:11:52 adam has changed the topic to: http://www.w3.org/2011/04/webrtc/wiki/Teleconferences 16:12:00 s/WebIDL/WebIDL dictionaries/ 16:12:06 ack jesup 16:12:13 +[IPcaller] 16:12:21 jesup: in general I don't have a problem with the design 16:12:30 Zakim, [IPcaller] is me 16:12:31 +nstratford; got it 16:12:32 ... how much data could be associated with these objectsL 16:12:39 s/L/?/ 16:12:57 ... there might be cases where you want hight detail.. it could be a lot of data 16:13:05 + +91.22.39.14.aapp 16:13:21 ... we need to make sure people understand that stats could generate a lot of data 16:13:37 hta: we will end up with quite a few objects 16:13:44 ... defaul will be grab em all 16:13:55 Zakim: who's here 16:14:05 ... probably in the 10s of kb range 16:14:20 + +44.190.881.aaqq 16:14:25 jesup: we have the space issue.. may not be that big 16:14:32 Zakim: who's here? 16:14:52 ... grabing a lot of data that you don't need can hurt you 16:14:56 hta: yes 16:15:19 ... I'm been thinking of this in 10s of seconds basis 16:15:22 AndyH has joined #webrtc 16:15:32 q+ 16:15:39 ... if ppl want to do this 100 times a second we're in trouble 16:15:45 Zakim, who's here? 16:15:45 On the phone I see fluffy, Dan_Burnett, hta, stefanh, +972.9.957.aaee, Milan_Patel, dom, dan_romascanu?, derf (muted), Dan_Druta, adambe, +1.630.423.aajj, jesup, JeromeMarcon, 16:15:48 ... [Mozilla], juberti, +1.831.440.aaoo, nstratford, +91.22.39.14.aapp, +44.190.881.aaqq 16:15:48 On IRC I see AndyH, adam, matthew, juberti, JeromeMarcon, tuexen, Richard, adambe, DanD, nstratford, dan_romascanu, fluffy, Milan_Patel, burn, jesup, mreavy, hta, stefanh, 16:15:48 ... RRSAgent, Zakim, richt, dom, derf, ed, trackbot, heath, Dweezahr, Josh_Soref 16:15:57 q+ 16:15:57 jesup: I'm worried about the size of deep copy operatios 16:15:59 ack fluffy 16:16:09 fluffy: I think this is an issue in selecting stats 16:16:11 Zakim, [Mozilla] is me 16:16:11 +adam; got it 16:16:25 ... I have a nit with the timestamp 16:16:29 ... otherwise, I like it 16:16:39 juberti: I like this too 16:16:43 cullen++ 16:16:52 ... the question is how we select stats 16:17:09 ... We could have an option to say "just give me ICE stats" 16:17:15 ... transport info 16:17:30 ... maybe we need a more general way to express what we want to collect stats about 16:17:49 hta: the selector object started of as an any type 16:18:29 ... to make it flexible 16:18:50 juberti: I don't know how the syntax would look 16:19:17 hta: I'd like to look at the use cases 16:19:43 stefanh: any more comments questions? 16:20:00 ... ppl seem to be pretty happy with this 16:20:30 [the WebIDL has syntax errors, but I assume the editors will take care of it] 16:20:33 ... does anyone have anything against integrating the API into the spec 16:20:41 fluffy: I can do that 16:21:18 q+ to ask about implementation plans 16:21:18 stefanh: I conclude that we should start integrating the new stats API into the spec 16:21:22 I think the action is roughly me to move the API part of RTCWEBStatsv2.pdf proposal into spec 16:21:34 stefanh: nex topic is error handling 16:21:35 q- 16:21:39 Topic: Error handling 16:21:40 burn: I sent some slides to the list 16:21:47 http://www.w3.org/2011/04/webrtc/wiki/File:20130110error_handling.pdf 16:21:55 -> http://www.w3.org/2011/04/webrtc/wiki/File:20130110error_handling.pdf Error Handling slides 16:22:18 tuexen has left #webrtc 16:22:18 ... before december there hadn't been so much discussion about error handling 16:22:31 ... the behaviour wasn't consistent between our documents 16:23:03 Agreed justin's suggestion is an option and solves the size issue. If you need links to other parts, you could tell it to include the other part. Downside is complexity. Perhaps use selection only for adding non-baseline items (packet-level stats, histogram data, etc) 16:23:05 ... I'll cover the main topics 16:23:14 that was on the stats issue 16:23:27 q? 16:23:47 q- 16:23:48 stefanh has joined #webrtc 16:25:02 ... anant had proposed.. exceptions and callbacks 16:25:29 ... detectable within < 50 ms should be an exception 16:25:40 fluffy: we talked about that and discarded it 16:26:08 burn: we throw an exception on a bad argument 16:26:16 ... and at illegal state 16:26:30 ... otherwise we use the error callback 16:26:47 q+ 16:26:48 ... I want to make sure we agree on this 16:26:51 q+ 16:27:02 hta: two comments 16:27:28 [based on https://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#error-names-0, the name should be INVALID_STATE_ERR rather than INVALID_STATE] 16:27:57 [TypeMismatch is enforced by WebIDL in any case] 16:28:25 ... there might be other cases than bad arguments and state 16:28:47 q+ to remind that the thumbrule is about context-dependent or not 16:28:52 q- 16:28:57 burn: browsers could do better but our guidelines says don't do that 16:29:37 fluffy: last time we came to the conclusion time wasn't relevant here 16:29:43 Zakim, who's noisy? 16:29:44 cullen++ 16:29:54 dom, listening for 10 seconds I heard sound from the following: JeromeMarcon (36%), fluffy (29%), +91.22.39.14.aapp (53%) 16:29:59 ... it's more about on which thread something is executed 16:30:02 Zakim, mute aapp 16:30:02 +91.22.39.14.aapp should now be muted 16:31:03 +1 to juberti 16:31:05 q- 16:31:10 juberti: I agree with fluffy that it shouldn't be based on a time 16:31:14 juberti++ 16:31:48 ... exceptions are programming errors and exceptions are runtime errors 16:32:05 second exceptions should be error callbacks 16:33:26 burn: we should change the quidelines to say that exceptions are thrown on programming errors 16:33:42 PROPOSED RESOLUTION: exceptions are thrown upon programming errors (for example invalid argument types or call in an invalid state); other errors are pushed as error callbacks 16:33:43 q+ 16:33:44 fluffy: I find this very abstract 16:34:20 burn: we need guidelines to avoid this discussion again 16:35:05 q- 16:35:21 dom: I don't think we're changing the guidelines.. perhaps reformulating them 16:36:45 fluffy: I think we're missing too much people in this call 16:37:05 ... to change what we decided in a meeting with a lot more people 16:37:22 " So decided that invalid_state will be a callback no exception" http://www.w3.org/2012/10/29-webrtc-minutes.html#item04 16:37:35 stefanh: could someone propose a change based on what we've talked about in this meeting 16:38:34 fluffy: I don't think we've agreed to anything here 16:38:51 stefanh: I think we need specific text in the form of an email 16:39:00 action justin: draft guideline text 16:39:00 Created ACTION-79 - Draft guideline text [on Justin Uberti - due 2013-01-17]. 16:39:39 burn: I went through the document that doesn't have callbacks 16:40:08 ... the resulting list is on slide 7 16:40:39 ... I've underlined 4 of them 16:40:51 ... but I don't remember fully what that meant 16:41:26 [updateIce makes reference to a "failure callback", but it's not clear which callback, since updateIce itself doesn't take a callback param http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-RTCPeerConnection-updateIce-void-RTCConfiguration-configuration-MediaConstraints-constraints ] 16:41:34 +juberti 16:41:57 ... question: do updateIce and addIceCandidate need callbacks 16:42:17 juberti: I don't think these specific methods need callbacks 16:42:41 s/these specific methods need/addIceCandidate needs/ 16:43:08 fluffy: thread boundaries might need to be crossed to find out if a candidate have a bad line number 16:43:36 (could also be an oniceerror event) 16:43:51 juberti: an exception wouldn't be appropriate in that case 16:44:14 dom: we colud have an ice error event 16:45:01 juberti: +1 16:45:02 timpanton has joined #webrtc 16:45:24 juberti: we should report errors consistently between addIceCandidate() and, e.g., setLocalDesc 16:45:29 q+ 16:45:38 burn: I agree with juberti 16:46:24 juberti: events happen asyc that may not be a result of a function call 16:46:52 timpanton has left #webrtc 16:47:29 fluffy: I think we're fairly consistent on this 16:47:36 q? 16:47:40 q- 16:47:51 jesup: I think this sounds resonable 16:48:10 q+ 16:48:19 q- 16:48:21 justin++ 16:48:21 justin said it 16:48:27 +1 16:48:45 juberti: we need the success callback to know when we can stop waiting for the error callback 16:49:33 one function call -> leads to one callback (either error or success) 16:49:39 dom: the success callback might not give much.. we could go with one callback for both cases 16:49:50 burn: we've talked about this before 16:50:00 ... the first thing would always be to check for an error 16:50:17 dom: I remember that conclusion 16:50:30 ... but that might have been under other circumstanses 16:51:18 dom: in geolocation you get the position in the success callback 16:51:29 q+ 16:51:35 q- 16:52:08 [hixie recently highlighted the pain of having a useless parameter in pushState] 16:52:15 same for createOffer and createAnswer 16:53:45 q+ 16:53:47 q+ 16:54:22 adambe: do we need to listen to the success cb and not continue before we get it or is it OK to ignore it 16:54:52 q- 16:55:07 q- 16:55:26 dom: I'm not aware of any other web api that does this, but this may not be the best time to bring up this discussion again 16:55:33 q? 16:55:39 Zakim: ack me 16:55:45 q? 16:55:49 q- adambe 16:57:22 q+ 16:57:27 "getIdentityAssertion Initiates the process of obtaining an identity assertion." http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-RTCPeerConnection-getIdentityAssertion-void 16:57:45 fluffy: ask ekr to clarify if getIdentityAssertion() need callbacks 16:58:08 burn: that operation is optional 16:58:30 [I think burn should send his analysis by email to kickstart the discussions :) ] 16:58:36 ... I would encourage other ppl to look at this as well 16:59:17 ... anything that updates sdp needs to be queued 17:00:02 burn: if something needs to queue, it can't return right away 17:00:21 juberti: anything that mutaates sdp would fall into that bucket 17:00:33 stefanh: but not until createOffer is issued right? 17:00:58 juberti: I agree that addIceCandidate might need a callback for completeness 17:01:35 [the constructor should also have a callback then, shouldn't it?] 17:01:35 ... udateIce takes the same arguments as the PeerConnection constructor 17:01:47 ... and it doesn't have a error callback 17:01:55 q? 17:01:59 ... we might want to change addIceCandidate 17:02:09 be right back 17:02:13 -juberti 17:02:17 re updateIce, the spec says "an RTCError object of type INCOMPATIBLE_CONSTRAINTS is provided to the failure callback if the constraints could not be successfully applied." 17:02:18 fluffy: if you give a bad password to the turn server 17:02:39 ... we need an error for that case 17:02:59 createDataChannel is supposed to be synchronous; it (for consistency with WebSockets) it fires an onopen when the channel opens and the object can't be used to transfer until then 17:04:00 burn: there are other proposals for error handling 17:04:07 ... ppl should review them 17:04:16 + +1.425.893.aarr 17:04:56 hta: juberti and I can look at it with our chrome eyes 17:05:05 Zakim, aarr is +juberti 17:05:05 ++juberti; got it 17:05:09 ... I wolud like to hear an opinion from Mozilla 17:05:20 Zakim, aarr is juberti 17:05:20 sorry, juberti, I do not recognize a party named 'aarr' 17:05:29 Zakim, +juberti is juberti 17:05:29 +juberti; got it 17:05:35 burn: anyone from Mozilla on the call? 17:05:48 ACTION: juberti to review needs for callback and errors callbacks in webrtc (with hta) 17:05:48 Created ACTION-80 - Review needs for callback and errors callbacks in webrtc (with hta) [on Justin Uberti - due 2013-01-17]. 17:05:55 ACTION: jesup to review needs for callback and errors callbacks in webrtc (with hta) 17:05:55 Error finding 'jesup'. You can review and register nicknames at . 17:06:04 jesup: we will look at it as a team (at Mozilla) 17:06:54 ACTION: derf to review needs for callback and errors callbacks in webrtc (with hta) 17:06:54 Created ACTION-81 - Review needs for callback and errors callbacks in webrtc (with hta) [on Timothy Terriberry - due 2013-01-17]. 17:06:59 fluffy: we need to go through all calls and sort out what needs to produce errors 17:07:08 - +1.831.440.aaoo 17:07:20 burn: we want this to be consistent between the specs 17:07:44 burn: that's all about error handling for today 17:08:04 (was on call, but have conflict now) 17:08:10 stefanh: we're moving on to the organizational section 17:08:12 ScribeNick: fluffy 17:08:17 Topic: Scribing procedures 17:08:28 Discussion around scribing procedures 17:08:32 -> http://lists.w3.org/Archives/Public/public-webrtc/2013Jan/0035.html A proposal on minute-takers for the WEBRTC WG meetings 17:08:34 see HTA proposal to list 17:09:22 We are not getting volunteers,, so we make a random list and work down it 17:10:07 Dan: when someone scribes, their names goes to bottom of the list. If someone is not there or presenting, they stay at top of the list 17:10:37 charis: plan to use that proposal 17:10:47 Next topic: schedule 17:11:14 chairs wondering about WG LC in Q3 this year 17:11:28 hta: this depends on output of GUM 17:11:36 s/Next topic/Topic/ 17:11:44 … can not sent GUM to LC until after face 17:12:07 stefanh: have dependencies on IETF specs 17:12:37 hta: some of it can be done without IETF being done, some of it we can not 17:13:29 dom: Our charter says we would be done by now and we need to update and review by AC 17:13:52 … A lot of people with expectation need fought estimates of when this will be done 17:14:15 … If we have reasonable objectives, it will easier to focus on getting things done 17:15:35 zakim, who is making noise? 17:15:46 hta, listening for 11 seconds I heard sound from the following: fluffy (14%) 17:16:23 fluffy: suggest we write down a schedule to try and estimate when we would be done 17:16:24 ACTION: stefanh to develop more granular estimate for schedule of WebRTC with hta 17:16:24 Created ACTION-82 - Develop more granular estimate for schedule of WebRTC with hta [on Stefan Håkansson - due 2013-01-17]. 17:17:45 hta: It's not the work that is creating long time line , it is the periods of waiting. Possible to get done faster, if people, especially editors rapid turn around cycle and people, especially chairs, keep the formal things that need to be done lined up and moving. We need to work on that, as always 17:18:22 Topic: F2F 17:18:27 Topic: face to face meeting 17:18:43 -> http://lists.w3.org/Archives/Public/public-webrtc/2013Jan/0000.html Proposed Interim Agenda from EKR 17:19:12 stefanh: EKR proposed to use more time on media capture on email to list. What do people think of that? 17:19:25 crikets: 17:19:33 -dan_romascanu? 17:19:46 justing: makes sense to finish that 17:20:01 still here 17:20:03 s/justing/juberti/ 17:20:40 hta: The more we can get things like error handling sketch out, the better 17:22:08 stefanh: on the webrtc part of EKR's proposal 17:22:29 … chairs will use this as starting point for more detailed agenda 17:26:47 Fluffy asked about good standing process. Dom and other explained a bit. Chairs hope to never need to use it. 17:27:30 -dom 17:27:31 -JeromeMarcon 17:27:33 -juberti 17:27:34 -adambe 17:27:34 -adam 17:27:35 -Milan_Patel 17:27:35 -stefanh 17:27:35 -Dan_Druta 17:27:36 - +972.9.957.aaee 17:27:36 -fluffy 17:27:36 -hta 17:27:36 -Dan_Burnett 17:27:37 -jesup 17:27:37 -derf 17:27:37 -nstratford 17:27:46 RRSAgent, draft minutes 17:27:46 I have made the request to generate http://www.w3.org/2013/01/10-webrtc-minutes.html dom 17:28:05 Zakim, list participants 17:28:05 As of this point the attendees have been +1.403.244.aaaa, +1.908.578.aabb, Dan_Burnett, +46.8.50.51.aacc, +46.1.07.14.aadd, hta, stefanh, +972.9.957.aaee, Milan_Patel, dom, 17:28:06 RRSAgent, draft minutes 17:28:06 I have made the request to generate http://www.w3.org/2013/01/10-webrtc-minutes.html dom 17:28:09 ... +1.972.999.aaff, +91.22.39.14.aagg, +1.703.334.aahh, derf, Dan_Druta, +46.1.07.14.aaii, +1.630.423.aajj, dan_romascanu?, adambe, +1.610.889.aakk, jesup, fluffy, 17:28:09 ... +91.22.39.14.aall, +33.6.85.56.aamm, +1.425.893.aann, juberti, +1.831.440.aaoo, JeromeMarcon, nstratford, +91.22.39.14.aapp, +44.190.881.aaqq, adam, +1.425.893.aarr 17:28:15 Zakim, who's on the call? 17:28:15 On the phone I see +1.630.423.aajj, +91.22.39.14.aapp (muted), +44.190.881.aaqq 17:28:20 Zakim, drop aajj 17:28:20 +1.630.423.aajj is being disconnected 17:28:22 - +1.630.423.aajj 17:28:23 Zakim, drop aaqq 17:28:23 +44.190.881.aaqq is being disconnected 17:28:25 - +44.190.881.aaqq 17:28:26 Zakim, drop aapp 17:28:26 +91.22.39.14.aapp is being disconnected 17:28:27 UW_WebRTC()11:00AM has ended 17:28:27 Attendees were +1.403.244.aaaa, +1.908.578.aabb, Dan_Burnett, +46.8.50.51.aacc, +46.1.07.14.aadd, hta, stefanh, +972.9.957.aaee, Milan_Patel, dom, +1.972.999.aaff, 17:28:27 ... +91.22.39.14.aagg, +1.703.334.aahh, derf, Dan_Druta, +46.1.07.14.aaii, +1.630.423.aajj, dan_romascanu?, adambe, +1.610.889.aakk, jesup, fluffy, +91.22.39.14.aall, 17:28:28 ... +33.6.85.56.aamm, +1.425.893.aann, juberti, +1.831.440.aaoo, JeromeMarcon, nstratford, +91.22.39.14.aapp, +44.190.881.aaqq, adam, +1.425.893.aarr 17:28:36 RRSAgent, draft minutes 17:28:36 I have made the request to generate http://www.w3.org/2013/01/10-webrtc-minutes.html dom 17:28:53 s/Zakim: who's here//g 17:29:18 s/Topic: F2F// 17:29:20 RRSAgent, draft minutes 17:29:20 I have made the request to generate http://www.w3.org/2013/01/10-webrtc-minutes.html dom 17:33:54 trackbot, end meeting 17:33:54 Zakim, list attendees 17:33:54 sorry, trackbot, I don't know what conference this is 17:34:02 RRSAgent, please draft minutes 17:34:02 I have made the request to generate http://www.w3.org/2013/01/10-webrtc-minutes.html trackbot 17:34:03 RRSAgent, bye 17:34:03 I see 5 open action items saved in http://www.w3.org/2013/01/10-webrtc-actions.rdf : 17:34:03 ACTION: justin to draft guideline text [1] 17:34:03 recorded in http://www.w3.org/2013/01/10-webrtc-irc#T16-39-00 17:34:03 ACTION: juberti to review needs for callback and errors callbacks in webrtc (with hta) [2] 17:34:03 recorded in http://www.w3.org/2013/01/10-webrtc-irc#T17-05-48 17:34:03 ACTION: jesup to review needs for callback and errors callbacks in webrtc (with hta) [3] 17:34:03 recorded in http://www.w3.org/2013/01/10-webrtc-irc#T17-05-55 17:34:03 ACTION: derf to review needs for callback and errors callbacks in webrtc (with hta) [4] 17:34:03 recorded in http://www.w3.org/2013/01/10-webrtc-irc#T17-06-54 17:34:03 ACTION: stefanh to develop more granular estimate for schedule of WebRTC with hta [5] 17:34:03 recorded in http://www.w3.org/2013/01/10-webrtc-irc#T17-16-24