Friday, 31 August 2012
- Re: Tally status (number of people), Friday at 15:34 GMT
- Re: DataChannels API
- RE: Transport change in MS Proposal
- Re: DataChannels API
- Re: Poll for preferred API alternative
- RE: Transport change in MS Proposal
- DataChannels API
- Re: Transport change in MS Proposal
- Re: Transport change in MS Proposal
- RE: Transport change in MS Proposal
- Tally status (number of people), Friday at 15:34 GMT
- Re: Poll for preferred API alternative
- Re: Poll for preferred API alternative
- Re: Poll for preferred API alternative
Thursday, 30 August 2012
- Re: Poll for preferred API alternative
- RE: Poll for preferred API alternative
- Re: ICE in MS Proposal
- Re: On the subject of complexity
- Re: Poll for preferred API alternative
- RE: ICE in MS Proposal
- Re: On the subject of complexity
- Re: ICE in MS Proposal
- Re: On the subject of complexity
- RE: ICE in MS Proposal
- On the subject of complexity
- Re: Clarification of alternatives (Re: Poll for preferred API alternative)
- Re: Poll for preferred API alternative
- Re: Poll for preferred API alternative
- Doodle for new Telco
- Re: Poll for preferred API alternative
- Re: Stats interface - modelling on IndexedDB API?
- Stats interface - modelling on IndexedDB API?
- [minutes] August 28 teleconf
- [minutes] August 28 teleconf
- RE: [rtcweb] H.264 SVC and BUNDLE
- External libraries
- Clarification of alternatives (Re: Poll for preferred API alternative)
- Re: Poll for preferred API alternative
Wednesday, 29 August 2012
- Re: Poll for preferred API alternative
- Re: Poll for preferred API alternative
- Re: I'm confused (Re: Poll for preferred API alternative)
- Re: Transport change in MS Proposal
- Re: ICE in MS Proposal
- Re: I'm confused (Re: Poll for preferred API alternative)
- Transport change in MS Proposal
- RE: [rtcweb] H.264 SVC and BUNDLE
- RE: [rtcweb] H.264 SVC and BUNDLE
- ICE in MS Proposal
- RE: [rtcweb] H.264 SVC and BUNDLE
- H.264 SVC and BUNDLE
- Re: I'm confused (Re: Poll for preferred API alternative)
- RE: Poll for preferred API alternative
- I'm confused (Re: Poll for preferred API alternative)
- ADMIN: Technical questions (Re: Poll for preferred API alternative)
- Re: Poll for preferred API alternative
- Re: Poll for preferred API alternative
- RE: Poll for preferred API alternative
- Re: Poll for preferred API alternative
- Re: Poll for preferred API alternative
- Re: Poll for preferred API alternative
- Poll for preferred API alternative
Tuesday, 28 August 2012
- Re: The main issue with SDP - Was: Initial notes on MS proposal
- Re: The main issue with SDP - Was: Initial notes on MS proposal
- Re: [Moderator Action (size limit exceeded)] Slides for MS API presentation part
- Re: The main issue with SDP - Was: Initial notes on MS proposal
- RE: The main issue with SDP - Was: Initial notes on MS proposal
- Re: The main issue with SDP - Was: Initial notes on MS proposal
- The main issue with SDP - Was: Initial notes on MS proposal
- Re: Microsoft API Proposal
- RE: Microsoft API Proposal
- Re: Summary of API for ICE State Reporting
- Agenda and details tonight's telco
- Fwd: Slides for tomorrow
- Registration for Next F2F (Fwd: TPAC 2012 Registration)
- Re: Microsoft API Proposal
- Re: Error handling description (Re: First agenda proposal webrtc telco)
Monday, 27 August 2012
- (should be) Re: Initial notes on MS proposal
- RE: Microsoft API Proposal
- RE: Summary of API for ICE State Reporting
- Re: On a particular design meme
- Re: On a particular design meme
- RE: On a particular design meme
- Re: Microsoft API Proposal
- RE: Microsoft API Proposal
- RE: First agenda proposal webrtc telco
- Re: Error handling description (Re: First agenda proposal webrtc telco)
- Error handling description (Re: First agenda proposal webrtc telco)
- Re: First agenda proposal webrtc telco
- Re: On a particular design meme
- Re: What is the closing state for?
- RE: First agenda proposal webrtc telco
- Re: First agenda proposal webrtc telco
- Re: Summary of API for ICE State Reporting
- Re: First agenda proposal webrtc telco
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: IdP API Text
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: IdP API Text
- IdP API Text
Sunday, 26 August 2012
- Re: First agenda proposal webrtc telco
- Re: First agenda proposal webrtc telco
- Re: Summary of API for ICE State Reporting
- Re: First agenda proposal webrtc telco
- Summary of API for ICE State Reporting
- Re: First agenda proposal webrtc telco
Saturday, 25 August 2012
- Re: Microsoft API Proposal
- Re: Microsoft API Proposal
- Re: Microsoft API Proposal
- Re: Microsoft API Proposal
- Details webrtc telco Aug 28th
Friday, 24 August 2012
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: What is the closing state for?
- Re: What is the closing state for?
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- Re: First agenda proposal webrtc telco
- What is the closing state for?
Wednesday, 22 August 2012
Tuesday, 21 August 2012
- Re: First agenda proposal webrtc telco
- Re: First agenda proposal webrtc telco
- Re: First agenda proposal webrtc telco
- First agenda proposal webrtc telco
- Updated Working Draft of WebRTC
- RE: Do we need two ways of identifying m-lines?
Monday, 20 August 2012
- Re: On a particular design meme
- Re: Do we need two ways of identifying m-lines?
- Re: Do we need two ways of identifying m-lines?
- Re: Do we need two ways of identifying m-lines?
Sunday, 19 August 2012
Saturday, 18 August 2012
Friday, 17 August 2012
- On a particular design meme
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: Proposed update of Milestones
- Re: Proposed update of Milestones
Thursday, 16 August 2012
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: some comments on the IDL in the WebRTC spec
- Re: Proposed update of Milestones
- Re: Proposed update of Milestones
- Re: Proposed update of Milestones
- Re: some comments on editor's draft
- Next webrtc WG Telco
- Re: Proposed update of Milestones
Wednesday, 15 August 2012
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- RE: Proposed update of Milestones
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: Proposed update of Milestones
- Re: Proposed update of Milestones
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- [Bug 18485] Change DTMF API to be on PeerConnection
Tuesday, 14 August 2012
- RE: some comments on editor's draft
- Re: some comments on editor's draft
- Proposed update of Milestones
- Re: Stats proposal, updated
- Re: [Bug 17109] New: TURN server API changes
- [Bug 18443] getUserMedia() Test Error in Chrome
- [Bug 18443] getUserMedia() Test Error in Chrome
- Re: [Bug 17109] New: TURN server API changes
Monday, 13 August 2012
- Re: Call for proposals on agenda items
- RE: Call for proposals on agenda items
- Re: Making RTCSessionDescription and RTCIceCandidate much more flexible
- Re: Summary of desired spec updates (Was: summary of some ongoing discussions)
- Re: Stats proposal, updated
- Re: CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- [Bug 18485] Change DTMF API to be on PeerConnection
- [Bug 18443] getUserMedia() Test Error in Chrome
- [Bug 18335] PeerConnection should inherit EventTarget
- [Bug 17249] SdpType usage must be chosen
- [Bug 17109] TURN server API changes
- Re: [Bug 17109] New: TURN server API changes
- Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- Re: [MARKETING] [Bug 18486] Let RTCSessionDescription take a Dictionary parameter
- Re: [MARKETING] [Bug 18486] Let RTCSessionDescription take a Dictionary parameter
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [MARKETING] Call for proposals on agenda items
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- [Bug 18486] Let RTCSessionDescription take a Dictionary parameter
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: Call for proposals on agenda items
- Re: Call for proposals on agenda items
- Re: Doodle for next Telco for Webrtc wg
Sunday, 12 August 2012
Thursday, 9 August 2012
Saturday, 11 August 2012
Friday, 10 August 2012
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- RE: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- [Bug 18516] New: MediaStream should extend EventTarget, not mix it in
Thursday, 9 August 2012
- Re: Microsoft API Proposal
- Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- Re: Microsoft API Proposal
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: DTMF
- RE: Microsoft API Proposal
- Re: Microsoft API Proposal
- RE: Microsoft API Proposal
- Re: Microsoft API Proposal
- Re: Microsoft API Proposal
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
Wednesday, 8 August 2012
Monday, 6 August 2012
Tuesday, 7 August 2012
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
Wednesday, 8 August 2012
- Re: DTMF
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- Re: [Bug 18485] Change DTMF API to be on PeerConnection
- [Bug 18485] Change DTMF API to be on PeerConnection
- [Bug 18485] Change DTMF API to be on PeerConnection
- Call for proposals on agenda items
- Doodle for next Telco for Webrtc wg
- Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- Re: DTMF
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: DTMF
Tuesday, 7 August 2012
- Re: ICE in Javascript (Re: Microsoft API Proposal)
- RE: ICE in Javascript (Re: Microsoft API Proposal)
- Re: DTMF
- ICE in Javascript (Re: Microsoft API Proposal)
- Re: DTMF
- RE: Microsoft API Proposal
- Re: Initial notes on MS proposal
- Initial notes on MS proposal
- Re: Microsoft API Proposal
- Re: [Bug 18335] New: PeerConnection should inherit EventTarget
- Re: DTMF
- RE: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: Microsoft API Proposal
- Re: Microsoft API Proposal
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
Monday, 6 August 2012
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- [Bug 15861] API for JS interaction with congestion control
- RE: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- RE: Microsoft API Proposal
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Microsoft API Proposal
- Re: Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
- CHANGE: [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
Saturday, 4 August 2012
- Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
- Re: Making RTCSessionDescription and RTCIceCandidate much more flexible
- [Bug 18486] New: Let RTCSessionDescription take a Dictionary parameter
- CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection
Friday, 3 August 2012
- [Bug 18485] New: Change DTMF API to be on PeerConnection
- [Bug 17596] Can we have an method fast peerconnection reconstruction?
- Re: Making RTCSessionDescription and RTCIceCandidate much more flexible
- Re: Making RTCSessionDescription and RTCIceCandidate much more flexible