Thursday, 29 May 2014
- [Bug 25893] Offer Answer options should supported sendOnly and inactive media states.
- [Bug 25893] Offer Answer options should supported sendOnly and inactive media states.
- Re: IE implementing WebRTC?
- Re: IE implementing WebRTC?
- Re: IE implementing WebRTC?
- Re: IE implementing WebRTC?
- IE implementing WebRTC?
- [Bug 25893] Offer Answer options should supported sendOnly and inactive media states.
Wednesday, 28 May 2014
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
- Re: Sending very large chunks over the data channel
Tuesday, 27 May 2014
- Re: Update of Doodle for teleconf
- Re: Update of Doodle for teleconf
- Update of Doodle for teleconf
- [Bug 25893] Offer Answer options should supported sendOnly and inactive media states.
- Chairs' notes, May 20-21 WG meeting
- Re: [minutes] May 20-21 F2F
- [Bug 25893] New: Offer Answer options should supported sendOnly and inactive media states.
- [Bug 25892] New: SignalingStateChange event should be fired only if there is a change in signaling state.
- [Bug 25806] ice pool size
- Sending very large chunks over the data channel
- Re: Reminder: Disconnect between Streams and DataChannel API models
- Re: Reminder: Disconnect between Streams and DataChannel API models
Monday, 26 May 2014
- [Bug 25440] MediaStreamTrack.readyState has no muted attribute
- Re: [minutes] May 20-21 F2F
- Reminder: Disconnect between Streams and DataChannel API models
Friday, 23 May 2014
- Re: [minutes] May 20-21 F2F
- [Bug 25856] Add way to find out if a MST is isolated or becomes islocated
- Re: Isolated tracks
- Re: Isolated tracks
- Re: Isolated tracks
- Re: [minutes] May 20-21 F2F
Thursday, 22 May 2014
- Re: [minutes] May 20-21 F2F
- [minutes] May 20-21 F2F
- Re: Starting session early
- Re: Starting session early
- Isolated tracks
Wednesday, 21 May 2014
- [Bug 25840] Creating DataChannel with same label.
- [Bug 25859] New: Streams that become isolated generate errors on PC
- [Bug 25856] Add way to find out if a MST is isolated or becomes islocated
- [Bug 25856] Add way to find out if a MST is isolated or becomes islocated
- [Bug 25855] Clarification about conformance requirements phrased as algorithms
- [Bug 25856] New: Add way to find out if a MST is isolated or becomes islocated
- Re: Next steps on RTCRtpSender "doohickey" proposal
- [Bug 25855] Clarification about conformance requirements phrased as algorithms
- [Bug 25855] New: Clarification about conformance requirements phrased as algorithms
- What IRC channel will we use?
- Starting session early
- Re: Next steps on RTCRtpSender "doohickey" proposal
- [Bug 25837] throw error when setting invalid parameters to DTMF sender
- [Bug 25834] close is synchronous & idempotent
- Re: Fwd: [Bug 25834] close is synchronous& idopontent
- Re: Next steps on RTCRtpSender "doohickey" proposal
- [Bug 25836] add note about addtrack being async
- [Bug 25834] close is synchronous& idopontent
- [Bug 25841] DataChannel and DTMF methods should check for peerConnection closed state
- Fwd: [Bug 25834] close is synchronous& idopontent
- [Bug 25841] DataChannel and DTMF methods should check for peerConnection closed state
- [Bug 25841] DataChannel and DTMF methods should check for peerConnection closed state
- [Bug 25840] Creating DataChannel with same label.
- Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: Re: Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: [Bug 25840] New: Creating DataChannel with same label.
- [Bug 25833] change the definition of "enqueue a task" as EKR slides May 20
Tuesday, 20 May 2014
- [Bug 25834] close is synchronous& idopontent
- Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Re: [Bug 25840] New: Creating DataChannel with same label.
- Re: Tomorrow's meeting - early start possible
- Re: [Bug 25840] New: Creating DataChannel with same label.
- [Bug 25841] New: DataChannel and DTMF methods should check for peerConnection closed state
- [Bug 25840] New: Creating DataChannel with same label.
- Couple of inputs for errors Handling
- [Bug 25837] throw error when setting invalid parameters to DTMF sender
- [Bug 25837] New: throw error when setting invalid parameters to DTMF sender
- [Bug 25836] New: add note about addtrack being async
- [Bug 25835] New: when closing, all outstanding actions are cancelled and their callbacks are fired with a "cancelled" error
- [Bug 25834] New: close is synchronous& idopontent
- [Bug 25833] New: change the definition of "enqueue a task" as EKR slides May 20
- Fwd: Re: Re: Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: data API retransmission model
- Re: New issue: switching sources
- Tomorrow's meeting - early start possible
- Re: Re: New issue: switching sources
- Re: RE: New issue: switching sources
- RE: New issue: switching sources
- Re: New issue: switching sources
- Re: New issue: switching sources
- Re: New issue: switching sources
- Re: New issue: switching sources
- Re: New issue: switching sources
- Re: New issue: switching sources
- [Bug 25828] New: Need to add pc.canTrickle)
- Re: New issue: switching sources
- Re: data API retransmission model
- Re: New issue: switching sources
- Re: New issue: switching sources
- Re: Re: New issue: switching sources
- Re: New issue: switching sources
- Re: New issue: switching sources
- Re: New issue: switching sources
- Re: Updated Stats proposal - May 13
- Re: Syntax of new constraint proposal
- Re: Syntax of new constraint proposal
Monday, 19 May 2014
- New issue: switching sources
- Re: Re: Invitation: WebRTC Interim Day 1 @ Mon May 19, 2014 10:30am - 2:50pm (dcrocker@bbiw.net)
- [Bug 25811] New: Change extensible enum to dom strings
- Re: Updated Stats proposal - May 13
- [Bug 25807] Avoid sdpMangling by modifying codec preferences through API.
- [Bug 25808] New: add new acces for the active remote/local SDP
- [Bug 25807] New: Avoid sdpMangling by modifying codec preferences through API.
- Re: Updated Stats proposal - May 13
- [Bug 25806] ice pool size
- [Bug 25806] New: ice pool size
- Re: Re: Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: Re: Re: Re: Re: A proposal for returning STUN/TURN server errors to applications
- Re: Re: Re: Re: A proposal for returning STUN/TURN server errors to applications
- Re: A proposal for returning STUN/TURN server errors to applications
- Re: Re: Re: Re: A proposal for returning STUN/TURN server errors to applications
- Re: Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: Re: Re: A proposal for returning STUN/TURN server errors to applications
- Re: Re: Re: A proposal for returning STUN/TURN server errors to applications
- Re: Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: A proposal for returning STUN/TURN server errors to applications
- Re: Re: A proposal for returning STUN/TURN server errors to applications
- Comments on draft
- Re: Syntax of new constraint proposal
- Re: Dealing with isolation state mismatches
- Re: Syntax of new constraint proposal
- Re: A proposal for returning STUN/TURN server errors to applications
- Re: Syntax of new constraint proposal
- Re: Syntax of new constraint proposal
- Re: Re: A proposal for returning STUN/TURN server errors to applications
- Re: A proposal for returning STUN/TURN server errors to applications
- Re: Dealing with isolation state mismatches
- Re: Job lot of slides for next week
- Re: Syntax of new constraint proposal
- Re: A proposal for returning STUN/TURN server errors to applications
- Re: new DTLS key for call
- Re: [rtcweb] Default candidate pool size
- Re: Finishing off "rollback"
- Re: IDP protcols
- Re: Syntax of new constraint proposal
- Re: Syntax of new constraint proposal
Sunday, 18 May 2014
- Re: A proposal for returning STUN/TURN server errors to applications
- Re: A proposal for returning STUN/TURN server errors to applications
- Re: Dealing with isolation state mismatches
- Re: creation of pranswer
- Re: data API retransmission model
- Re: data API retransmission model
- Re: Syntax of new constraint proposal
- A proposal for returning STUN/TURN server errors to applications
- Re: data API retransmission model
- Re: new DTLS key for call
- Re: data API retransmission model
- Re: data API retransmission model
- Re: Syntax of new constraint proposal
- Re: data API retransmission model
- Re: new DTLS key for call
- new DTLS key for call
- Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: [rtcweb] Default candidate pool size
- Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Finishing off "rollback"
- data API retransmission model
- Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: [rtcweb] Default candidate pool size
- Re: requestIdentity
- Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: Syntax of new constraint proposal
- Stats Example
- Re: creation of pranswer
- Re: sdpMLineIndex in RTCPeerConnectionIceEvent
- Re: [rtcweb] Default candidate pool size
- Re: sdpMLineIndex in RTCPeerConnectionIceEvent
- Re: sdpMLineIndex in RTCPeerConnectionIceEvent
- Re: [rtcweb] Default candidate pool size
- Re: [rtcweb] Default candidate pool size
- IDP protcols
- sdpMLineIndex in RTCPeerConnectionIceEvent
- creation of pranswer
- Re: [rtcweb] Default candidate pool size
- Re: Syntax of new constraint proposal
- Syntax of new constraint proposal
- Re: Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Re: [rtcweb] Default candidate pool size
- Re: Avoid sdp mangling in WebRTC by setting codec preferences - review request.
- Draft proposal for setting codec preferences - draft-guduru-rtcweb-codec-preferences-00.txt
- Re: RTPSender/Receiver - The case for Constraints
Saturday, 17 May 2014
Friday, 16 May 2014
- RE: RTPSender/Receiver - The case for Constraints
- Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections
- RE: RTPSender/Receiver - The case for Constraints
- RE: RTPSender/Receiver - The case for Constraints
- Remote participation
- Re: RTPSender/Receiver - The case for Constraints
- Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections
- Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections
- Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections
- Re: Dealing with isolation state mismatches
- Re: RTPSender/Receiver - The case for Constraints
- Re: Any plan for zoom capacity in webRTC.
- Re: Any plan for zoom capacity in webRTC.
- Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections
- Re: Dealing with isolation state mismatches
- Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections
Thursday, 15 May 2014
Wednesday, 14 May 2014
Thursday, 15 May 2014
- Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections
- RTPSender/Receiver - The case for Constraints
- Re: Dealing with isolation state mismatches
- Agenda for the meeting Tue+Wed
- Re: Dealing with isolation state mismatches
- Re: Dealing with isolation state mismatches
- Re: Dealing with isolation state mismatches
- Re: Dealing with isolation state mismatches
- Re: Dealing with isolation state mismatches
- Re: Dealing with isolation state mismatches
- Re: Dealing with isolation state mismatches
- [Bug 25724] New: Allow garbage collection of closed PeerConnections
- Re: Dealing with isolation state mismatches
- Re: Updated Stats proposal - May 13
- Re: Dealing with isolation state mismatches
- Re: Updated Stats proposal - May 13
- Re: Dealing with isolation state mismatches
- Re: Updated Stats proposal - May 13
- Re: Job lot of slides for next week
- Re: Updated Stats proposal - May 13
- Re: Dealing with isolation state mismatches
- Dealing with isolation state mismatches
- requestIdentity
- Job lot of slides for next week
- Re: Updated Stats proposal - May 13
Wednesday, 14 May 2014
- Meeting recordings for upcoming interim
- Re: Updated Stats proposal - May 13
- Re: Updated Stats proposal - May 13
Tuesday, 13 May 2014
- Re: Updated Stats proposal - May 13
- Re: Updated Stats proposal - May 13
- Re: Updated Stats proposal - May 13
- Re: Updated Stats proposal - May 13
- Re: Updated Stats proposal - May 13
- Re: Updated Stats proposal - May 13
- Re: Re: [rtcweb] Default candidate pool size
- Updated Stats proposal - May 13
- Re: Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
- Re: Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
Monday, 12 May 2014
- Re: [rtcweb] Default candidate pool size
- Re: DataChannel: how to know the max size of the sending buffer?
- Default candidate pool size
Sunday, 11 May 2014
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
Saturday, 10 May 2014
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
Friday, 9 May 2014
- Re: Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
- Re: REMINDER: Joint Interim meeting May 19-21, 2014
- Re: Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
- Re: Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
- Re: Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
Thursday, 8 May 2014
- Re: Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
- Firefox automatically provides local ICE candidates (it does not fire onicecandidate)
- Re: REMINDER: Joint Interim meeting May 19-21, 2014
- Re: REMINDER: Joint Interim meeting May 19-21, 2014
- RE: REMINDER: Joint Interim meeting May 19-21, 2014
- Re: REMINDER: Joint Interim meeting May 19-21, 2014
- Re: REMINDER: Joint Interim meeting May 19-21, 2014
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Re: Next steps on RTCRtpSender "doohickey" proposal
- REMINDER: Joint Interim meeting May 19-21, 2014
- Re: Next steps on RTCRtpSender "doohickey" proposal
- [Bug 25497] RTCRtpSender / Receiver objects need to be added to the specification
- Re: renaming updateIce
- [Bug 25596] New: updateIce should be called setConfiguration
- Re: Next steps on RTCRtpSender "doohickey" proposal
- Next steps on RTCRtpSender "doohickey" proposal
- Re: renaming updateIce
- Re: DataChannel: how to know the max size of the sending buffer?
Wednesday, 7 May 2014
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- Re: DataChannel: how to know the max size of the sending buffer?
- DataChannel: how to know the max size of the sending buffer?
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- Re: [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
Tuesday, 6 May 2014
- [Bug 25579] New: State transitions are missing in RTCPeerConnections state transition diagram.
- [Bug 25576] New: steps for createDTMFSender() are missing.
Monday, 5 May 2014
- Re: Security considerations - a proposal
- [Bug 25545] New: Initialization of of RTCConfiguration while invoking RTCPeerConnection.getConfiguration should be updated.
- [Bug 25544] New: Options attribute of createOffer / createAnswer should be validated before processing.
Sunday, 4 May 2014
- Re: Proposed Change to RTCRtpSender "doohickey" proposal
- Re: Proposed Change to RTCRtpSender "doohickey" proposal
Saturday, 3 May 2014
Friday, 2 May 2014
- Re: renaming updateIce
- Re: renaming updateIce
- Re: renaming updateIce
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: Update of RTCRtpSender "doohickey" proposal
- RTCConfiguration and identity
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: Re: Update of RTCRtpSender "doohickey" proposal
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: renaming updateIce
- Agenda proposal for DC f2f meeting
- [Bug 25533] New: WebRTC spec should explicitly specify the state transition for cancelled offers.
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: Re: Update of RTCRtpSender "doohickey" proposal
- Re: Update of RTCRtpSender "doohickey" proposal
- [Bug 25531] New: Validation for requestIdentity attribute is missing.
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: Update of RTCRtpSender "doohickey" proposal
- Re: Update of RTCRtpSender "doohickey" proposal