16:03:09 RRSAgent has joined #webrtc 16:03:09 logging to http://www.w3.org/2012/02/28-webrtc-irc 16:03:15 + +46.1.07.14.aabb 16:03:32 zakim, aabb is Adam_Bergkvist 16:03:32 +Adam_Bergkvist; got it 16:04:05 +[Microsoft] 16:04:05 Scribe: Josh_Soref 16:04:06 adambe has joined #webrtc 16:04:19 Zakim, [Microsoft] contains trackbot 16:04:20 +trackbot; got it 16:04:35 +??P6 16:04:47 Travis_MSFT has joined #webrtc 16:04:49 Zakim, [Microsoft] no longer contains trackbot 16:04:49 -trackbot; got it 16:04:52 Zakim, [Microsoft] contains Travis_MSFT 16:04:52 +Travis_MSFT; got it 16:05:12 Topic: Agenda 16:05:57 Chairs: stefanh, Harald_Alvestrand 16:06:22 Meeting: Media Capture Task Force teleconference 16:06:31 s/stefanh/Stefan/ 16:06:38 Topic: Scenarios 16:06:58 Travis_MSFT: Thank you to everyone who was able to review the document and provide feedback 16:07:00 Zakim, mute me 16:07:00 Josh_Soref should now be muted 16:07:14 ... there was a request from the DAP WG to publish it as a FPWD 16:07:19 ... that notice went out about a week ago 16:07:30 ... darobin has volunteered to do the publishing work 16:07:38 there is the same request from the webrtc group 16:07:47 ... he was on vacation, and i believe he'll get it out some time this week 16:07:52 burn: This is a document 16:08:06 ... I understood that documents that aren't Specifications don't get FPWD 16:08:08 +??P7 16:08:12 ... and instead get published as Notes 16:08:18 Travis_MSFT: I had the same concern 16:08:27 ... Initially I marked it up differently 16:08:30 Zakim, +??P7 is me 16:08:30 sorry, nstratford, I do not recognize a party named '+??P7' 16:08:33 ... If you have an issue, let's talk about it 16:08:41 burn: I agree it should be published 16:08:51 ... I was just surprised to see FPWD for a non REC track document 16:08:57 Zakim, ??P7 is me 16:08:57 +nstratford; got it 16:09:15 stefanh: I acted on darobin's suggestion of doing FPWD 16:09:24 http://www.w3.org/2005/10/Process-20051014/ -- Process Document 16:09:34 burn: this is based on my 13 years of experience in W3C 16:09:41 ... but darobin also has lots of experience in W3C 16:09:46 ... I'll just talk with darobin 16:09:59 stefan 16:10:05 hta: I just want it to be pushed out 16:10:11 s/hta/stefan/ 16:10:21 s/stefan/stefanh/ 16:10:35 Travis_MSFT: the document hasn't changed significantly since I did the CfC 16:10:46 ... Josh_Soref gave feedback but indicated it wasn't critical to FPWD 16:10:55 ... If I have time, I may squeeze them in before publication 16:11:01 stefanh: The next point, is on the next step 16:11:09 ... is there any activity we can make to get more input 16:11:11 q? 16:11:20 q+ to note that FPWD is one way to get more input 16:11:24 Travis_MSFT: I had a suggestion 16:11:37 ... I know we originally proposed this document so we could unify on a set of scenarios and goals 16:11:40 ... for this TF 16:11:52 ... what we have today is a document that has a really good description of a high level usage scenario 16:11:59 ... what I think the next steps for the document are 16:12:04 ... is to use the scenarios we've agreed on 16:12:12 ... to extract the functional requirements for the API 16:12:20 ... I know we're focusing on getUserMedia() 16:12:38 ... but next we should focus on the features that media streams will need 16:12:51 ... does that sound reasonable? 16:12:55 stefanh: does that sound reasonable? 16:13:10 s/does that sound reasonable?/to me that sounds reasonable/ 16:13:13 adambe: I agree 16:13:28 RRSAgent, draft minutes 16:13:28 I have made the request to generate http://www.w3.org/2012/02/28-webrtc-minutes.html Josh_Soref 16:13:44 hta 16:13:54 hta: Given that we aren't starting with a clean slate 16:14:03 ... we'll want to aim for a non disruptive approach 16:14:09 Travis_MSFT: i agree with that sentiment 16:14:12 ... one approach we could take 16:14:26 ... i could take an action item to attempt to draft some requirements 16:14:30 ... and we could keep iterating 16:14:36 hta: yes 16:14:46 ... do you think you should write up a list that includes the WebRTC UCs? 16:14:52 ... or anything in addition to those? 16:15:00 Travis_MSFT: i think that's certainly worth a shot 16:15:12 Travis_MSFT: I can certainly look into them again 16:15:22 hta: it would be nice if we had a single list of requirements 16:15:26 Travis_MSFT: i agree 16:15:51 ACTION Travis_MSFT to Draft a setup of initial requirements based on the WebRTC and the Scenarios document 16:15:51 Sorry, couldn't find user - Travis_MSFT 16:16:00 ACTION Travis to Draft a setup of initial requirements based on the WebRTC and the Scenarios document 16:16:00 Sorry, couldn't find user - Travis 16:16:10 ACTION stefanh to action Travis to Draft a setup of initial requirements based on the WebRTC and the Scenarios document 16:16:10 Sorry, couldn't find user - stefanh 16:16:18 ACTION hta to action Travis to Draft a setup of initial requirements based on the WebRTC and the Scenarios document 16:16:19 Created ACTION-25 - Action Travis to Draft a setup of initial requirements based on the WebRTC and the Scenarios document [on Harald Alvestrand - due 2012-03-06]. 16:16:27 q? 16:16:28 q- 16:16:36 Topic: Capabilities/Constraints 16:16:54 Zakim, unmute me 16:16:54 Josh_Soref should no longer be muted 16:17:39 i/I had a suggestion/Josh_Soref: to note that FPWD is one way to get more input/ 16:17:55 rrsagent, make logs public 16:18:22 burn: Even though I suspect many people have read this document 16:18:27 http://lists.w3.org/Archives/Public/public-media-capture/2012Feb/0041.html 16:18:34 ... I think it would be helpful for me to go over this to make sure we're on the same page 16:18:38 RRSAgent, draft minutes 16:18:38 I have made the request to generate http://www.w3.org/2012/02/28-webrtc-minutes.html Josh_Soref 16:18:51 burn: my task was to come up with an API for capabilities 16:19:00 ... Capabilities and Hints are fairly closely tied together 16:19:19 ... I've always had that opinion, but I hadn't found a way to explain this 16:19:26 ... I spoke with fluffy 16:19:37 ... App Developer = Web Developer 16:19:46 ... When a web developer says "i need a video of a certain size" 16:19:53 ... When they're told "that's just a hint" 16:20:05 ... that's frustrating for application authors 16:20:21 ... we tried to design a way to make it workable for both the Browser (UA implementer) 16:20:24 ... and the App Developer 16:20:34 ... that amounts to Constraints 16:20:51 ... the goal was to develop Constraints that we a way for a Web Developer to express what they'd like 16:20:57 ... in a meaningful way to the browser 16:21:02 ... but also a way to express preferences 16:21:12 ... so if they couldn't get THIS, then try to get me THIS 16:21:26 ... and also to provide a way for the Web Developer to specify a minimum 16:21:40 ... the browser also needs to be able to handle Congestion on the Network 16:21:47 ... or User resizing their screen 16:21:58 ... it would be unfortunate for the browser to have to go back to the Application author 16:22:02 ... and get a new answer 16:22:11 ... we think that a Constraint structure satisfies these requirements 16:22:18 ... I'm going to talk about this Constraint structure 16:22:36 ... There's a possibility that we need to distinguish between Constraints for Peer connections 16:22:51 ... and Constraints for just getting media in the first place (not using a Peer connection) 16:23:00 ... I believe that this design can work for both 16:23:14 ... but we may need some things to make the different cases easier 16:23:21 ... With respect to the Constraint API 16:23:29 ... I don't think there's much to an API beyond an API for hints 16:23:45 ... I suggest that it should be in the place where we discussed hints 16:23:56 ... I propose that we use an ordered list of Key-Value-Pair 16:24:02 ... approximately Key-Value-Pair 16:24:11 ... for "is it mandatory" -- we'll talk about that later 16:24:24 ... You specify with a priority, a specific constraint 16:24:28 ... Skip past XXX 16:24:32 ... in the email 16:24:39 ... you'll see that I have a JSON list here 16:24:46 ... with 0...5 keys, those are priority orderings 16:24:53 ... 0 is the highest priority 16:25:05 ... there are priority numberings, and then specific constraints 16:25:25 Example: 16:25:25 {0:{video-min-height:600, mandatory:true}, 16:25:25 1:{video-max-aspectratio:1.333333333333}, 16:25:25 2:{video-min-timebetweenrefframes:20}, 16:25:25 3:{video-max-bandwidth:500, mandatory:true}, 16:25:25 4:{video-min-framerate:30}, 16:25:27 5:(video-autowhitebalance:on}} 16:25:33 [ burn explains the Example ] 16:25:43 burn: I'm specifying a minimum height of 600 pixels 16:25:57 Cathy has joined #webrtc 16:25:58 ... a browser will if it has to choose between an aspect ratio or a height constraint 16:26:18 ... i've indicated that I've preferred that it meet the height constraint (because the priority is higher) 16:26:40 ... I've also indicated a mandatory flag on some constraints 16:26:55 ... for my application, i don't want to start without that minimum height and that maximum bandwidth 16:27:04 ... i want an error from the browser instead 16:27:11 ... indicating which couldn't be satisfied 16:27:15 ... Before I continue 16:27:22 ... are there any questions? 16:27:30 adambe: I have a question about Mandatory 16:27:42 ... there's a Mandatory at position 0 and a Mandatory at position 3 16:27:57 ... how does it relate to the optional item at position 1? 16:28:00 burn: that's correct 16:28:13 ... because i don't think bandwidth relates to aspect ratio 16:28:22 ... I think a more interesting thing is between 2 and 3 16:28:30 adambe: XX2 16:28:45 burn: the priority ordering is to be used to resolve conflicts between constraints 16:28:52 ... there's likely a conflict between height and aspect-ratio 16:29:09 ... I think you're asking why not list mandatory before optional 16:29:26 ... I could as an application author put them with 1 and 2 after 3 16:29:31 ... but i don't really care 16:29:36 Travis_MSFT: it might be interesting 16:29:47 ... to talk through an algorithm for evaluating the examples 16:29:51 s/examples/example/ 16:29:58 burn: I'll talk about it loosely 16:30:02 ... i don't have it written out 16:30:09 ... please don't hold me to being a computer 16:30:14 ... approximately speaking 16:30:19 ... as an implementer, reading through this 16:30:27 ... you would attempt to satisfy every constraint 16:30:36 ... starting with the lowest number (highest priority) 16:30:41 ... if you satisfy it, you move on 16:30:53 ... if you don't satisfy it, and it's marked as mandatory, you must fail 16:31:31 burn: out of all the possible video resolutions i can choose 16:31:47 ... i am able to choose one that can satisfy this constraint 16:31:56 Zakim, mute me 16:31:56 Josh_Soref should now be muted 16:32:02 Travis_MSFT: you might look at your available video formats 16:32:11 ... and you'd narrow things down 16:32:19 fluffy has joined #webrtc 16:32:25 ... you'd present to the user 16:32:28 ... or fail if you run out of things 16:32:35 +fluffy 16:32:39 terry: Terry, From Mozilla 16:32:49 ... you might be able to satisfy each in isolation 16:32:52 ... but not in combination 16:32:59 Zakim, who is on? 16:32:59 I don't understand your question, Josh_Soref. 16:33:04 Zakim, who is on the call? 16:33:04 On the phone I see Harald_Alvestrand, Dan_Burnett, Josh_Soref (muted), [Mozilla], stefanh, Adam_Bergkvist, [Microsoft], ??P6, nstratford, fluffy 16:33:07 [Microsoft] has Travis_MSFT 16:33:14 s/Terry/Tim Terriberry/ 16:33:23 burn: for all the ones I marked as mandatory, i need them 16:33:40 ... if i could satisfy min-height or max-bandwidth, but not both 16:33:45 ... we could talk about that 16:33:52 ... but i'd like to talk about that later 16:34:02 Zakim, [Mozilla] has Tim_Terriberry 16:34:02 +Tim_Terriberry; got it 16:34:22 burn: Tim_Terriberry, is it ok if we note that and come back to it? 16:34:37 terry: that's fine 16:34:43 burn: as you're narrowing 16:34:51 ... if the constraint you're processing leaves you with the empty set 16:34:57 ... and that constraint was not mandatory 16:35:12 ... then i think the process should undo that constraint and move on to the next step 16:35:19 Travis_MSFT: because it isn't a mandatory constraint 16:35:28 ... there isn't a need to satisfy that particular constraint 16:35:33 ... and you continue processing 16:35:41 burn: and the ones that are higher priority matter more 16:35:54 burn: we should say that the algorithm processes these in priority order 16:36:29 XX3: you're going to run into the problem of a conflict between a priority order optional constraint 16:36:33 ... and a mandatory constraint 16:36:42 fluffy: I think you want to do mandatory constraints first 16:36:43 Zakim, ??P6 is me 16:36:43 +tim; got it 16:36:58 XX4: I think fluffy 's suggestion makes more sense than burn 's 16:37:01 burn: I'm fine with that 16:37:14 ... when I proposed this approach 16:37:24 ... it was based on SSML 1.0 16:37:37 -nstratford 16:37:54 ... when we discussed this, we didn't discuss this very in detail 16:38:05 ... we may be able to change the structure 16:38:12 ... all mandatory before optional 16:38:23 adambe: [...] 16:38:38 burn: I wanted to do clarifying questions first 16:38:50 XX5: we can design the algorithm down the road 16:39:04 burn: Travis_MSFT was trying to talk through an algorithm to understand what we're doing 16:39:08 Travis_MSFT: and that's been met 16:39:17 burn: are there any other clarifying questions about constraints? 16:39:19 [ none ] 16:39:28 burn: ok, then let's go on to the capabilities 16:39:42 ... a call to getCapabilities() 16:40:05 ... this was supposed to be focusing on the Fully Trusted case 16:40:11 +??P7 16:40:12 ... that's what anant was talking about in the previous call 16:40:27 ... i didn't attempt at all to even attempt to describe things for the less trusted case 16:40:42 Zakim, ??P7 is me 16:40:42 +nstratford; got it 16:40:45 ... it returns a JS Array for each device/media stream/channel 16:40:52 ... we may need to figure out how to describe that 16:40:56 ... for now i put it per device 16:41:05 ... for each device, it's going to list all of the relevant constraints 16:41:12 ... but they're the constraints for the device 16:41:30 ... camera 1 has no resolution less than 800 16:41:38 ... no smaller resolution than 600 16:41:39 q+ 16:41:51 ... similarly for camera 2 16:42:01 adambe: his is specific constraints 16:42:05 ... this is not a profile 16:42:10 ... you can't expect all of these to work together 16:42:14 burn: correct 16:42:28 ... it doesn't mean that 800x600 is a valid resolution 16:42:33 ... and i did this on purpose 16:42:51 ... for camera 2, i intentionally picked values where with and height don't match up 16:43:00 ... you're likely to get 1920x1080 16:43:06 ... or 1600x1200 16:43:10 Travis_MSFT: i like this 16:43:32 ... you've anonymized the camera names 16:43:44 ... and you've forced the authors to decide what the want 16:43:48 burn: that was the intent 16:44:19 ... for your application, you know what's important 16:44:36 ... you may want a maximum,... if you're doing a thumbnail, you may not want something 2000px wide 16:44:50 Travis_MSFT: there are no units here 16:44:57 ... is that because each thing has a defined unit? 16:45:03 burn: if you scroll up in the email 16:45:08 ... for every constraint, i give a unit 16:45:12 ... i had us skip over that 16:45:21 ... but i think it's extremely important to specify the unit 16:45:50 Travis_MSFT: can you give an example of XX7 16:46:06 burn: possibly someone may want width in display centimeters instead of px 16:46:14 Travis_MSFT: which they could figure out on their own 16:46:22 burn: we tried not to go overboard on a list of constraints 16:46:29 ... i'm not even saying this is the initial set 16:46:42 ... i knew if i didn't come up with a reasonable number of example constraints 16:46:46 ... i'd get yelled at 16:46:50 Travis_MSFT: i'm not proposing 16:47:01 ... i like having unitless when i get data back 16:47:06 ... because my code will do math on it 16:47:20 fluffy: I have a hard time thinking of an example 16:47:30 ... say you wanted both px and cm 16:47:38 ... we could just add a new constraint width-in-cm 16:48:04 Travis_MSFT: should we plan ahead and call it video-min-width-px 16:48:14 s/XX7/wanting different units for a given field/ 16:48:22 burn: i don't think we need to focus on that now 16:48:34 ... are there any other clarification questions at this point? 16:48:35 q? 16:48:48 Travis_MSFT: the getCapabilities() is that a call that can be called at any time 16:49:00 burn: I tihnk that question is orthogonal to this discussion 16:49:08 s/tihnk/think/ 16:49:20 ... it's important, but i purposefully left that out of this discussion 16:49:32 ... there are other people better suited for discussing thta 16:49:35 s/thta/that/ 16:49:51 ... there may be something for working out the reduced privilege case 16:49:59 ... and that's something we can work out later 16:50:02 Travis_MSFT: i agree with that 16:50:09 ... in my opinion, it sounds very reasonable 16:50:24 ... and it seems that we could adapt for a Non-Trusted Environment 16:50:28 q 16:50:30 s/q// 16:50:31 q? 16:50:36 Zakim: ack me 16:50:41 s/Zakim: ack me// 16:50:43 Zakim, ack me 16:50:43 unmuting Josh_Soref 16:50:44 I see no one on the speaker queue 16:51:49 josh: are we ok with the ua scaling/padding out? 16:51:57 tim: my answer would be no 16:52:04 ... the QT apis that Apple have 16:52:14 ... if you ask for a particular resolution 16:52:22 ... it will give you something 16:52:26 ... and there's no way to shut this off 16:52:38 ... i think it's a terrible thing from an app developer's perspective 16:53:37 Travis_MSFT: i'm holding a BlackBerry device 16:53:49 ... i'm browsing a min-video-width of an hd size 16:53:57 ... the hardware on my device can't stream that 16:54:08 ... it's doing a disservice to the user 16:54:15 ... because the UA follows the letter of the law 16:54:34 I think the answer is different for manditory vs no manditory constraints. 16:54:55 ... i'm ok with the UA doing things differently 16:55:05 adambe: i think web developers will use these constraints cautiously 16:55:13 ... because they will lock people out of their services 16:55:14 q? 16:55:30 q+ 16:55:43 josh: you're being way overoptimistic 16:55:45 fluffy: can you give us a specific case for lying? 16:55:46 q- 16:58:19 xx8: xx9 16:58:28 Travis_MSFT: the case you described as a downgrade of constraints 16:58:34 ... willfully violating the minimum constraints 16:58:41 fluffy: i don't know how to design a browser that second guesses 16:58:42 ... are there cases of wanting to violate the maximum constraints? 16:58:47 q+ 16:59:05 tim: for example downgrading from hd to thumbnail is certainly possible 16:59:16 ... but there's often a serious case of performance impact 16:59:25 We really need to be clear if these are manditory constrainst we are atalking about. 16:59:27 ... the app needs to know about that 16:59:42 ... in principle, i don't have a problem with the UA lying on behalf of the User 16:59:54 ... i can certainly see sticking a pref somewhere for an expert user 17:00:03 ... in practice, i don't think the pref will be flipped 17:00:12 burn: i think in the small mobile device 17:00:23 ... the browser will lie when it thinks it's in the best interest of the User 17:00:27 ... and that's fine 17:00:42 ... i've chosen to use a version of Safari on my iPhone with this little screen 17:01:00 Travis_MSFT: there's often an option on mobile devices to "browse the mobile web" or "browse the desktop web" 17:01:04 ... it's essentially lying 17:01:07 burn: and that's right 17:01:12 fjh has joined #webrtc 17:01:29 ... there are definitely times when i want to scroll the screen for the features 17:01:34 fluffy: i don't consider that lying 17:01:38 [ PC explanation ] 17:01:52 +[IPcaller] 17:02:02 Me 17:02:04 zakim, [IPcaller] is me 17:02:04 +fjh; got it 17:02:12 Present+ Frederick_Hirsch 17:02:13 [ SCRIBE WILL HAVE TO FIX MINUTES ] 17:02:24 tim = tim panton 17:02:30 derf = tim terriberry 17:02:33 just for the record :-) 17:02:36 tim: about mandatory, or non mandatory constraints, in the context of the UA lying 17:02:47 ... i don't have an opinion 17:02:57 Travis_MSFT: in context of that discussion, i wasn't limiting my discussion to either case 17:03:10 ... given the API in the proposal, any constraint can become a mandatory constraint 17:03:11 zakim, who is here? 17:03:11 On the phone I see Harald_Alvestrand, Dan_Burnett, Josh_Soref, [Mozilla], stefanh, Adam_Bergkvist, [Microsoft], tim, fluffy, nstratford, fjh 17:03:14 [Microsoft] has Travis_MSFT 17:03:14 [Mozilla] has Tim_Terriberry 17:03:14 On IRC I see fjh, Cathy, Travis_MSFT, adambe, RRSAgent, stefanh, Zakim, burn, nstratford, hta, tim, Josh_Soref, ed, derf, rektide, trackbot, dom 17:03:17 rrsagent, generate minutes 17:03:17 I have made the request to generate http://www.w3.org/2012/02/28-webrtc-minutes.html fjh 17:03:29 ... whichever constraint the UA may choose to deceive the application 17:03:34 ... it could apply to any of them 17:03:44 tim: i have a feeling there is a difference, but i'm not sure what it is 17:03:52 ... i have a feeling it's worse to lie about a mandatory constraint 17:03:55 ... but i can't justify that 17:04:11 Travis_MSFT: the good news from this discussion is that there's tacit agreement that this is a good idea 17:04:16 Josh_Soref: which this 17:04:28 burn: is there anyone who doesn't like this general approach? 17:04:36 hta: i like this approach 17:04:40 Travis_MSFT: i also like it 17:05:01 ... i second the notion that there may be a set of constraints which are different between getUserMedia() and Peer 17:05:11 ... possibly with considerable overlap 17:05:25 ... I like the idea of keeping the list of constraints in a single place 17:05:30 stefanh: there seems to be support for this 17:05:41 ... burn: how do you propose that we move forward? 17:05:53 burn: the next step is to rewrite this to address the mandatory-optional structure 17:06:01 q+ negative values for mandatory? :) 17:06:10 q+ to suggest negative values for mandatory? :) 17:06:16 ack tim 17:06:17 -nstratford 17:06:37 burn: then we need to split out the constraints and design a document for IANA to make the registry 17:06:50 q? 17:06:52 ... go ahead and create a registry 17:06:56 ack me 17:06:56 Josh_Soref, you wanted to suggest negative values for mandatory? :) 17:07:27 Josh_Soref: the simplest approach for splitting mandatory from optional is to move the mandatory to the negative space (you're currently 0 based) 17:07:45 adambe: i think that you don't need the numbering 17:07:54 burn: I think for mandatory, i don't think you need a priority ordering 17:08:00 ... either they're all satisfied, or they aren't 17:08:08 ... i don't like explicit numbers either 17:08:30 ... when you look at JS arrays, they're really lists with lengths 17:08:44 adambe: you actually used an Object not an Array... 17:09:13 ... you can use an object with a list 17:09:19 burn: I showed it as an object 17:09:26 ... it would be better to show it in list notation 17:09:34 Travis_MSFT: a List in JS gives you indices for free 17:09:37 burn: ... 17:09:55 ... I had object in my head because i was trying to figure out how to squeeze Mandatory in there 17:10:00 +??P7 17:10:04 ... We can create two list 17:10:12 fluffy: I like two lists 17:10:22 ... on mandatory needing to be ordered 17:10:30 ... say you ask for X and not X 17:10:36 ... as mandatory 17:10:40 ... obviously you get an error 17:10:58 Zakim, ??P7 is me, calling from a WebRTC enabled browser, hence the coming and going 17:10:58 I don't understand you, nstratford 17:11:01 ... if we define an error as listing everything you haven't met 17:11:07 Zakim, ??P7 is me 17:11:07 +nstratford; got it 17:11:33 Travis_MSFT: in the current syntax, you have to do Mandatory: true 17:11:39 ... which makes it explicit that it's mandatory 17:11:53 ... if you have two pure lists, it's hard to see which is the mandatory list 17:12:06 adambe: { mandatory: [...], optional: [...]} 17:12:44 hta: you could use [....,mandatory-above-this-line,....] 17:12:47 burn: i'd rather two lists 17:12:53 ... it's easier to process 17:12:58 ... if you look through mandatory 17:13:01 ... and then optional 17:13:13 Travis_MSFT: if you don't have mandatory constraints, you don't need to specify that list 17:13:24 stefanh: maybe we could leave the details later 17:13:37 ... was there a decision to move forward? 17:13:41 ... i think so 17:13:47 burn: one thing that isn't clear is... 17:13:51 ... where the definition should go 17:14:11 burn: there's a registry that will define constraints 17:14:18 ... but that isn't defining what a constraint structure is 17:14:24 ... as used in getUserMedia/.... 17:14:39 Travis_MSFT: i'd propose we put the Algorithm and what we've defined here into the getUserMedia spec 17:14:43 stefanh: I agree 17:14:53 burn: i'm fine with that 17:15:01 ... i just want to define it in one place 17:15:08 ... and reference it from everywhere else 17:15:17 Travis_MSFT: getUserMedia or another deliverable 17:15:28 ... (getUserMedia doesn't cover Peer) 17:15:39 adambe: now we're specifying the case 17:15:48 ... where you're a developer fiddling around with all the settings 17:15:56 ... should we also have comments about defaults? 17:16:14 ... i had a comment before about developers not using this because they'd be locking people out 17:16:24 burn: to me, if you don't ask for anything, the browser can do anything 17:16:42 fluffy: i think it'd be better to specify defaults 17:16:52 ... video specify is it using the largest/smallest? 17:17:02 ... audio is easier to pick defaults 17:17:20 adambe: i think defaults should be good 17:17:30 ... you should need a reason to not use defaults 17:17:49 fluffy has joined #webrtc 17:17:50 burn: my silence is agreement 17:18:02 ... i don't have a problem with the group discussing it after i put a basic framework in place 17:18:04 hta: that works for me 17:18:19 Travis_MSFT: thinking ahead 17:18:33 ... this general system seems like it would work great for recording different media streams 17:18:42 ... i think this is heading in the right direction 17:19:00 ACTION burn to flesh this out 17:19:01 Created ACTION-26 - Flesh this out [on Daniel Burnett - due 2012-03-06]. 17:19:25 ACTION burn to work to create a draft with fluffy to create an IANA registry 17:19:25 Created ACTION-27 - Work to create a draft with fluffy to create an IANA registry [on Daniel Burnett - due 2012-03-06]. 17:19:38 burn: the registry can be created empty 17:19:50 ... and we can discuss in W3C later filling it out 17:19:55 Travis_MSFT: i'm also an available resource 17:20:01 burn: i may take you up on that 17:20:11 ... in talking with fluffy, the draft 0 deadline is Monday 17:20:39 RRSAgent, draft minutes 17:20:39 I have made the request to generate http://www.w3.org/2012/02/28-webrtc-minutes.html Josh_Soref 17:20:50 burn: because of that, i may need to focus on the Registry first 17:21:13 ... don't panic if i don't get the other part done next week 17:21:17 Topic: AOB 17:21:37 stefanh: when should we have the next call? 17:22:32 DAP has a F2F Mar 19-23 17:22:52 WebApps has a F2F Apr 9-13 17:23:11 IETF has a Meeting Mar 25-30 17:24:25 burn: We need to do it after the IETF meeting, and we'll need a doodle 17:24:45 ACTION hta to create a doodle for the next meeting 17:24:45 Created ACTION-28 - Create a doodle for the next meeting [on Harald Alvestrand - due 2012-03-06]. 17:24:48 April 4-9 is Easter week. 17:25:04 [ Apr 9-13 is Passover too ] 17:25:26 stefanh: I will be leaning on Anant after MWC 17:25:54 MWC is Feb 27-Mar 1 17:26:32 burn: if anant can get something together in the next week, then we could have a productive call in 2 weeks 17:26:40 ... otherwise we need to wait until after IETF 17:26:45 ... and we can coordinate that by email 17:27:05 stefanh: thanks everyone for great input 17:27:11 ... and thanks to Josh_Soref for scribiing 17:27:17 s/scribiing/scribing/ 17:27:22 Travis_MSFT: great discussion 17:27:22 tim has left #webrtc 17:27:23 -fjh 17:27:25 -fluffy 17:27:25 -Harald_Alvestrand 17:27:26 [ adjourned ] 17:27:27 -tim 17:27:27 -[Mozilla] 17:27:29 -Adam_Bergkvist 17:27:29 -Dan_Burnett 17:27:30 -nstratford 17:27:30 -[Microsoft] 17:27:33 -stefanh 17:27:42 trackbot, end meeting 17:27:42 Zakim, list attendees 17:27:42 As of this point the attendees have been +47.41.44.aaaa, Dan_Burnett, Josh_Soref, Harald_Alvestrand, stefanh, +46.1.07.14.aabb, Adam_Bergkvist, trackbot, Travis_MSFT, nstratford, 17:27:46 ... fluffy, Tim_Terriberry, tim, fjh 17:27:50 RRSAgent, please draft minutes 17:27:50 I have made the request to generate http://www.w3.org/2012/02/28-webrtc-minutes.html trackbot 17:27:51 RRSAgent, bye 17:27:51 I see no action items