- From: Eric Rescorla <ekr@rtfm.com>
- Date: Mon, 22 Oct 2012 07:02:15 -0700
- To: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
- Cc: public-webrtc@w3.org
Stefan, We also need to plan some time to discuss Identity (this was discussed on the call the other day, but I guess it got lost). I think it's in pretty good shape but there are some smaller issues that are still open, I think. Here's an agenda item: * Identity * Provider registration * Message passing details * Priority order * Interaction with certificate-based authentication This seems like about 60 minutes worth of stuff. Thanks, -Ekr On Mon, Oct 22, 2012 at 5:57 AM, Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> wrote: > The proposed agenda is now on the meeting Wiki: > http://www.w3.org/2011/04/webrtc/wiki/October_29_-_October_30_2012#Agenda > > We've added one topic: Implementation/test status > > Stefan for the chairs > > > On 10/17/2012 02:28 PM, Stefan Hakansson LK wrote: >> >> All, >> >> we've put together a draft agenda for the f2f meeting, see below. Please >> let us know what you think. Should something be removed, something added? >> >> Also, we have proposed who will be responsible for each session. If you >> have been assigned to something you for some reason don't want to do >> please let us know. Also, if you would like to be involved in the >> preparation of one or more sessions, let us know that. >> >> Stefan for the chairs >> >> Monday morning 0830--1200 >> ========================= >> * welcome and stuff >> >> * API functionality (MediaStream related) that has been discussed but is >> not currently supported, what of this should we support in v1? - Stefan >> >> ** Sender side (all per track) >> *** Priority >> *** bw >> *** width/height >> *** agc toggle switch >> *** bw/cong. feedback >> >> ** Receiver side >> *** reject certain or all tracks in offer >> **** should app be able to? >> *** inform the sender of used / useful width/height >> *** tell the sender that a stream/track is not played >> (paused/unattached/ended) >> >> ** Not certain what side >> *** Control of AEC (echo cancellation) >> >> ** Agree on what of the above we need >> *** What in v1; what we can move to v2 but “make room for” in v1; what >> we can’t see need for >> *** One time, or possible to change? >> >> ** Discussion leads to requirements to IETF on SDP and RTCP capabilities >> >> >> * Coffee break 1030-1045 >> >> * SDP handling - Martin T, Cullen >> ** How long is an SDP created with createOffer/Answer valid? >> ** Rollback funtionality >> *** at setLocal(offer) at offerer >> *** at setRemote(offer) at answerer >> *** at setLocal(answer) at answerer >> *** at setRemote(answer) at offerer >> *** What does an application do to recover when the UA rejects the set* >> call? >> >> >> >> * Lunch 1200-1300 >> >> Monday afternoon 1300-1800 >> ========================== >> * General error handling principles - Anant >> >> * Call flows - Cullen’s sample flows - Cullen >> ** Walk through a flow or two, verify that we understand what the >> transitions mean >> >> * Stats - Harald >> ** Conclude stats model >> ** Specific stats for >> *** Transports >> *** ICE addresses / address pairs >> *** ??? >> >> * Conclude DTMF (we hope) - Harald, Justin >> >> * Finish for the day >> >> >> Tuesday morning 0830-1200 >> ========================= >> * API functionality for remove stream - Harald >> ** Empty indices in local/remoteStreams or not? >> >> * States - Cullen, Justin >> ** PeerConnection >> ** ICE agent >> ** What is exposed to application? >> >> * End of WebRTC WG meeting (afternoon is Media Capture) >> >> > >
Received on Monday, 22 October 2012 14:03:24 UTC