Tuesday, 28 February 2017
- Re: [webrtc-stats] Remove separation of received consent and connectivity requests.
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
- Closed: [webrtc-stats] Discrepancies between RTCRtpCodecParameters and RTCCodecStats naming
- Re: [webrtc-stats] moving roundTripTime from outbound to inbound
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-stats] Need priority information for MediaStreamTracks
- Re: [webrtc-stats] Consistent marker for "non-active" object?
- [webrtc-stats] Need advice for handling obsolete stats
- Re: [webrtc-stats] Related to outgoing and incoming bitrate estimates on a candidate pair
- [webrtc-stats] RTCTransportStats packet counters
- Re: [webrtc-stats] RTCIceCandidatePairStats packet counters
- Re: [webrtc-stats] Remove separation of received consent and connectivity requests.
- [webrtc-stats] RTCIceCandidatePairStats packet counters
- Re: [webrtc-stats] aligning codec types with webrtc-pc
- [webrtc-stats] Unclear if the request encompasses consent checks or not
- [webrtc-stats] new commits pushed by alvestrand
- Re: [webrtc-stats] Remove separation of received consent and connectivity requests.
- Re: [webrtc-stats] Remove separation of received consent and connectivity requests.
- Re: [webrtc-stats] Remove separation of received consent and connectivity requests.
- Re: [webrtc-stats] Make a RTCMediaStreamTrackStats object per track attachment
- Re: [webrtc-stats] frameWidth/frameHeight: use last decoded value
- [webrtc-stats] Pull Request: Issue 97
- Re: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
- [webrtc-stats] Pull Request: fixes issue with TURN URL protocol
- Closed: [webrtc-stats] Need consistent name for RTT estimate on RTCRTPStreamStats and on ICECandidatePair
- Re: [webrtc-stats] Need consistent name for RTT estimate on RTCRTPStreamStats and on ICECandidatePair
- Re: [webrtc-stats] aligning codec types with webrtc-pc
- [webrtc-stats] Pull Request: aligning codec types with webrtc-pc
- Re: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
- [webrtc-stats] Pull Request: moving roundTripTime from outbound to inbound
- [webrtc-stats] Pull Request: removed cancelled and renamed inprogress with in-progress.
- Re: [webrtc-stats] Remove separation of received consent and connectivity requests.
- Re: [webrtc-stats] Remove separation of received consent and connectivity requests.
- Re: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
Monday, 27 February 2017
- Re: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
- Re: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
- [webrtc-stats] Pull Request: Remove separation of received consent and connectivity requests.
- Re: [webrtc-stats] Not clear how to differentiate between received connectivity checks and consent requests
- Re: [webrtc-pc] NetworkError event is not defined and might not be needed
Sunday, 26 February 2017
- Re: [webrtc-pc] Indicators of usage and data flow (PING review)
- Closed: [webrtc-pc] Indicators of usage and data flow (PING review)
- Closed: [webrtc-pc] Information available prior to permission prompt (PING review)
- Re: [webrtc-pc] Information available prior to permission prompt (PING review)
- Re: [webrtc-stats] Adding remoteTimestamp to RTCRtpStreamStats.
Saturday, 25 February 2017
- Re: [webrtc-pc] Clarify which timestamp RTCStats.timestamp represents.
- Re: [webrtc-pc] RTCStats timestamp source ambiguous
- Re: [webrtc-pc] RTCStats timestamp source ambiguous
- [webrtc-pc] Pull Request: Clarify which timestamp RTCStats.timestamp represents.
- [webrtc-stats] Pull Request: Adding remoteTimestamp to RTCRtpStreamStats.
Friday, 24 February 2017
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- [webrtc-pc] Pull Request: Make RTCDataChannel.id nullable and describe when it's set.
Thursday, 23 February 2017
- Re: [webrtc-pc] RTCRtcpMuxPolicy of "negotiate" should be marked as an "at-risk" feature
- Re: [webrtc-pc] RTCRtcpMuxPolicy of "negotiate" should be marked as an "at-risk" feature
- Re: [webrtc-pc] Advanced Peer-to-peer Example
- Re: [webrtc-pc] RTCRtcpMuxPolicy of "negotiate" should be marked as an "at-risk" feature
- Re: [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-pc] Advanced Peer-to-peer Example
- Re: [webrtc-pc] Advanced Peer-to-peer Example
- Re: [webrtc-pc] RTCStats timestamp source ambiguous
- Re: [webrtc-pc] Specify when a data channel's ID is assigned, and what the `id` attribute returns when no ID is assigned.
- Re: [webrtc-pc] Parameters for packetization interval
- Re: [webrtc-pc] Specify how media is centered, cropped, and scaled. Fixes #305
- [webrtc-pc] Pull Request: Specify when random mid generation happens
- [webrtc-pc] Pull Request: Specify how transceivers get their mids in setLocal/Remote
- Re: [webrtc-pc] RTCRtcpMuxPolicy of "negotiate" should be marked as an "at-risk" feature
- Re: [webrtc-pc] get/setParameters does not have a parameter for packetization interval
- Re: [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-stats] Stat for how many adaptation changes occur for a video track
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Add stat to RTCTransportStats for ICE role (controlling or controlled)
Wednesday, 22 February 2017
- Re: [webrtc-pc] Parameters for packetization interval
- Re: [webrtc-stats] RTCIceCandidatePairStats.writable/readable: redundant?
- [webrtc-stats] RTCIceCandidatePairStats.writable/readable: redundant?
- Re: [webrtc-stats] Add stat to RTCTransportStats for ICE role (controlling or controlled)
Tuesday, 21 February 2017
- Re: [webrtc-pc] "Hybrid" OAuth solution.
- Re: [webrtc-pc] Separated auth dictionaries for STUN/TURN (issue 714)
- Re: [webrtc-pc] Support for OAuth in TURN credentials (Issue 714 patch)
- [webrtc-stats] Add stat to RTCTransportStats for ICE role (controlling or controlled)
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-pc] Support for OAuth in TURN credentials (Issue 714 patch)
- Re: [webrtc-pc] Separated auth dictionaries for STUN/TURN (issue 714)
Monday, 20 February 2017
- Re: [webrtc-pc] Clarify that it is possible to send the same track in several copies.
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Clarify that it is possible to send the same track in several copies.
Friday, 17 February 2017
- Re: [webrtc-pc] Add support for WebRTC Data Channel in Workers
- Closed: [webrtc-pc] Receive a track multiple times
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Need Custom Error for IdP
- [webrtc-pc] Pull Request: maxSimulcastStreams attribute in RTCRtpCodecCapability
- Re: [webrtc-pc] "Hybrid" OAuth solution.
- Re: [webrtc-pc] Switch to sender and receiver getStats selectors.
- Re: [webrtc-stats] Stat for audio playout delay
- Re: [webrtc-stats] Stat for how many audio stream packets are expanded when packets are lost (and lost and the user is speaking)
- Re: [webrtc-stats] Stat for audio playout delay
- Re: [webrtc-pc] "Hybrid" OAuth solution.
- Re: [webrtc-stats] Stat for audio playout delay
- [webrtc-pc] Pull Request: "Hybrid" OAuth solution.
Thursday, 16 February 2017
- Re: [webrtc-pc] Mention that codecs can be reordered or removed but not modified.
- Re: [webrtc-pc] Mention that codecs can be reordered or removed but not modified.
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Need IDP Invalid Token
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Need IDP Expired Token error
- Re: [webrtc-pc] Specify how media is centered, cropped, and scaled. Fixes #305
- Re: [webrtc-pc] Clarify that it is possible to send the same track in several copies.
- Re: [webrtc-pc] Clarify that it is possible to send the same track in several copies.
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stat for how many adaptation changes occur for a video track
- Re: [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-pc] Handing SDP with more than one identity
- Re: [webrtc-pc] Information available prior to permission prompt (PING review)
- Re: [webrtc-pc] Indicators of usage and data flow (PING review)
- Re: [webrtc-pc] Clarify reasoning behind and mitigation of privacy issues (PING review)
- Re: [webrtc-pc] add IdP token expired error
- Re: [webrtc-pc] add IdP invalid token error
- Re: [webrtc-pc] RTCRtcpMuxPolicy of "negotiate" should be marked as an "at-risk" feature
- [webrtc-pc] Pull Request: maxSimulcastStreams attribute in RTCRtpCodecCapability
Wednesday, 15 February 2017
- Re: [webrtc-pc] Don't fire events on a closed peer connection
- [webrtc-pc] Pull Request: Don't fire events on a closed peer connection
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-pc] sdpFmtpLine isn't very convenient
- Re: [webrtc-pc] Mention that codecs can be reordered or removed but not modified.
- Re: [webrtc-pc] add IdP token expired error
- Re: [webrtc-pc] add string for extra info about idpErrors
- Re: [webrtc-pc] add IdP invalid token error
- Re: [webrtc-pc] add IdP token expired error
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-stats] Stat for camera input framerate of local video tracks
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-stats] Stat for how many adaptation changes occur for a video track
- Re: [webrtc-stats] Unclear which framerate "framePerSecond" represents
- Closed: [webrtc-stats] Stat for audio acceleration/expand rate?
- Re: [webrtc-stats] Stat for audio acceleration/expand rate?
- Re: [webrtc-stats] Need priority information for MediaStreamTracks
- Re: [webrtc-stats] Stat for how many audio stream packets are expanded when packets are lost (and lost and the user is speaking)
- Re: [webrtc-stats] Stat for how many audio stream packets are expanded when packets are lost (and lost and the user is speaking)
- Re: [webrtc-stats] Stat for audio acceleration/expand rate?
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-stats] Stat for audio acceleration/expand rate?
- Re: [webrtc-stats] Stat for audio acceleration/expand rate?
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-pc] Align getAlgorithm return value with Web Crypto
Tuesday, 14 February 2017
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-stats] Stat for how many adaptation changes occur for a video track
- Re: [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-stats] Stat for audio playout delay
- Re: [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-stats] Stat for how many audio stream packets are expanded when packets are lost (and lost and the user is speaking)
- Re: [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-stats] Stat for audio acceleration rate?
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- [webrtc-pc] Pull Request: Switch to sender and receiver getStats selectors.
- Re: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Don't fire events on a closed peer connection
Monday, 13 February 2017
- Re: [webrtc-pc] Need to describe that codecs can be removed or reordered, but not modified
- Re: [webrtc-pc] sdpFmtpLine isn't very convenient
- Re: [webrtc-pc] Need to describe that codecs can be removed or reordered, but not modified
- [webrtc-pc] Pull Request: add IdP token expired error
- [webrtc-pc] Pull Request: add IdP invalid token error
- [webrtc-pc] new commits pushed by fluffy
- [webrtc-pc] Pull Request: add string for extra info about idpErrors
Sunday, 12 February 2017
- Re: [webrtc-pc] Should IDP Login error cary the idpLoginUrl
- Re: [webrtc-pc] Define how long should the IdP timeout timer should be
- Re: [webrtc-pc] Need Custom Error for IdP
- Re: [webrtc-pc] Handing SDP with more than one identity
- Re: [webrtc-pc] Handing SDP with more than one identity
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- Re: [webrtc-pc] strawman text to show how unverfieid media would work
- [webrtc-pc] Pull Request: strawman text to show how unverfieid media would work
- Re: [webrtc-pc] Mention that codecs can be reordered or removed but not modified.
- [webrtc-pc] Pull Request: Mention that codecs can be reordered or removed but not modified.
- [webrtc-pc] Need to describe that codecs can be removed or reordered, but not modified
- Re: [webrtc-pc] sdpFmtpLine isn't very convenient
- Re: [webrtc-pc] get/setParameters does not have a parameter for packetization interval
- Re: [webrtc-pc] sdpFmtpLine isn't very convenient
- [webrtc-stats] new commits pushed by vr000m
- Closed: [webrtc-stats] Need description for `remoteSource` member of `RTCMediaStreamTrackStats`
- Closed: [webrtc-stats] Where is the API?
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-pc] getParameters does not have a parameter for packetization interval
Saturday, 11 February 2017
- Re: [webrtc-pc] Specify how media is centered, cropped, and scaled. Fixes #305
- [webrtc-pc] Pull Request: Specify how media is centered, cropped, and scaled. Fixes #305
Friday, 10 February 2017
- [webrtc-pc] sdpFmtpLine isn't very convenient
- Re: [webrtc-pc] getParameters does not have a parameter for packetization interval
- Re: [webrtc-stats] RTCPeerConnection.getStats: What to do with 'selector' argument?
- Re: [webrtc-pc] getParameters does not have a parameter for packetization interval
- Re: [webrtc-pc] getParameters does not have a parameter for packetization interval
- Re: [webrtc-pc] getParameters does not have a parameter for packetization interval
- Re: [webrtc-pc] getParameters does not have a parameter for packetization interval
- [webrtc-pc] getParameters does not have a parameter for packetization interval
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-stats] RTCRTPStreamStats.mediaTrackId, RTCMediaStreamStats.trackIds
- Re: [webrtc-pc] Don't fire events on a closed peer connection
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] RTCPeerConnection.getStats: What to do with 'selector' argument?
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
Thursday, 9 February 2017
- Re: [webrtc-pc] Add Error Object
- Re: [webrtc-pc] Need IDP Invalid Token
- Re: [webrtc-pc] Advanced Peer-to-peer Example
- [webrtc-pc] Don't fire events on a closed peer connection
- Re: [webrtc-pc] Advanced Peer-to-peer Example
- Closed: [webrtc-pc] Effect of a BYE on RtpReceiver.track
- Closed: [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Closed: [webrtc-pc] OpenSource WebRTC IdP
- Re: [webrtc-pc] OpenSource WebRTC IdP
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] RTCRtcpMuxPolicy of "negotiate" should be marked as an "at-risk" feature
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] "track" event shouldn't fire for a "recvonly" description.
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-stats] Stat for retransmitted bytes
- Re: [webrtc-pc] Add an explicit stats selection algorithm.
- Re: [webrtc-pc] Receive a track multiple times
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-pc] Mark negotitate in RTCRtcpMuxPolicy at risk
- Re: [webrtc-pc] Fix inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Re: [webrtc-pc] Effect of a BYE on RtpReceiver.track
- [webrtc-pc] Pull Request: Clarify that it is possible to send the same track in several copies.
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
Wednesday, 8 February 2017
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Privacy & Security self review
- Re: [webrtc-stats] Privacy & Security self review
- Re: [webrtc-stats] Privacy & Security self review
- Re: [webrtc-pc] Receive a track multiple times
- [webrtc-pc] Pull Request: Mark negotitate in RTCRtcpMuxPolicy at risk
- Re: [webrtc-pc] Guidance for extending objects vs extending Stats needed
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] RTCCodecStats.implementation... per-codec, per-stream?
- Closed: [webrtc-stats] RTCCodecStats.implementation... per-codec, per-stream?
- Closed: [webrtc-stats] Why is ssrc a DOMString?
- Re: [webrtc-stats] Why is ssrc a DOMString?
- [webrtc-stats] new commits pushed by alvestrand
- Re: [webrtc-stats] Stat for audio playout delay
- Re: [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-stats] Stat for camera input framerate of local video tracks
- Re: [webrtc-pc] Ensure that "track" event is only fired for "send" direction m-sections.
- Re: [webrtc-stats] Definitions from MSE need re-targeting
- Re: [webrtc-stats] Definitions from MSE need re-targeting
- Re: [webrtc-stats] Stat for camera input framerate of local video tracks
- Re: [webrtc-stats] Definitions from MSE need re-targeting
- Re: [webrtc-stats] Stat for retransmitted bytes
- Re: [webrtc-stats] Stat for audio playout delay
- Re: [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-stats] Stat for how much time it takes to encode video
Tuesday, 7 February 2017
- Re: [webrtc-pc] Processing remote MediaStreamTracks without MediaStreams info
- Closed: [webrtc-pc] Processing remote MediaStreamTracks without MediaStreams info
- Re: [webrtc-pc] Processing remote MediaStreamTracks without MediaStreams info
- Re: [webrtc-stats] Stat for audio playout delay
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stat for retransmitted bytes
- Re: [webrtc-stats] Stat for camera input framerate of local video tracks
- Closed: [webrtc-stats] Stat for target and actual encoding bitrate
- Re: [webrtc-stats] Stat for target and actual encoding bitrate
- Re: [webrtc-stats] Stat for target and actual encoding bitrate
- Re: [webrtc-stats] Definitions from MSE need re-targeting
- [webrtc-stats] Definitions from MSE need re-targeting
- Re: [webrtc-stats] Stat for camera input framerate of local video tracks
- Re: [webrtc-pc] Support assertions that identify the recipient
- [webrtc-pc] OpenSource WebRTC IdP
- Re: [webrtc-pc] Support assertions that identify the recipient
- Re: [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Re: [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-pc] Information available prior to permission prompt (PING review)
- Re: [webrtc-pc] Indicators of usage and data flow (PING review)
- Re: [webrtc-pc] Clarify reasoning behind and mitigation of privacy issues (PING review)
- Re: [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-pc] Clarify reasoning behind and mitigation of privacy issues (PING review)
- Re: [webrtc-pc] Clarify reasoning behind and mitigation of privacy issues (PING review)
- Re: [webrtc-pc] Clarify reasoning behind and mitigation of privacy issues (PING review)
- Re: [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Re: [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Re: [webrtc-stats] Stat for adaptation reason
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] Pull Request: Ensure that "track" event is only fired for "send" direction m-sections.
- Re: [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone
Monday, 6 February 2017
- Re: [webrtc-pc] Receive a track multiple times
- Re: [webrtc-pc] "track" event shouldn't fire for a "recvonly" description.
- [webrtc-pc] Pull Request: Fix inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Re: [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone
- Re: [webrtc-stats] Stat for adaptation reason
- [webrtc-stats] Stat for adaptation reason
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-stats] RTCCodecStats needs `transportId` and `isRemote` to give it context
- [webrtc-stats] Stat for camera input framerate of local video tracks
- Re: [webrtc-stats] Unclear which framerate "framePerSecond" represents
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] RTCCodecStats needs `transportId` and `isRemote` to give it context
- Re: [webrtc-pc] Align getAlgorithm return value with Web Crypto
- Closed: [webrtc-pc] Ambiguous wording in addIceCandidate
- Re: [webrtc-pc] Ambiguous wording in addIceCandidate
- Re: [webrtc-pc] Effect of a BYE on RtpReceiver.track
Saturday, 4 February 2017
- [webrtc-pc] "track" event shouldn't fire for a "recvonly" description.
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
Friday, 3 February 2017
- Re: [webrtc-stats] Unclear which framerate "framePerSecond" represents
- Re: [webrtc-stats] What should `availableOutgoingBitrate`/`availableOutgoingBitrate` be for candidate pairs not in use?
- [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-stats] Make a RTCMediaStreamTrackStats object per track attachment
- Re: [webrtc-stats] Unclear which framerate "framePerSecond" represents
- Re: [webrtc-stats] What should `availableOutgoingBitrate`/`availableOutgoingBitrate` be for candidate pairs not in use?
Thursday, 2 February 2017
- Re: [webrtc-stats] Not clear how to differentiate between received connectivity checks and consent requests
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Clarify wording on TypeError from addIceCandidate.
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Closed: [webrtc-pc] Event when a transceiver is stopped via remote action
- Closed: [webrtc-pc] Change SetLocalDescription to require unchanged offer/answer string
- Closed: [webrtc-pc] currentRemoteDescription.sdp -- does it need to match the last SDP set via setRemoteDescription?
- Closed: [webrtc-pc] The RTCPeerConnectionIceErrorEvent constructor should have an optional init dict
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] Add offerToReceive* as legacy extensions
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] Effect of a BYE on RtpReceiver.track
- Re: [webrtc-pc] Clarify wording on TypeError from addIceCandidate.
- Re: [webrtc-stats] Not clear how to differentiate between received connectivity checks and consent requests
- Re: [webrtc-stats] Why is ssrc a DOMString?
- [webrtc-stats] Pull Request: Changes type of RTCRTPStreamStats.ssrc from string to unsigned long.
- [webrtc-stats] Pull Request: frameWidth/frameHeight: use last decoded value
Wednesday, 1 February 2017
- [webrtc-stats] Stat for target and actual encoding bitrate
- [webrtc-stats] Stat for retransmitted bytes
- Re: [webrtc-stats] Stat for likelihood of echo
- [webrtc-stats] Stat for likelihood of echo
- Re: [webrtc-stats] Stat for how many audio stream packets are expanded when the user is speaking
- Re: [webrtc-stats] Stat for how many audio stream packets are expanded when the user is speaking
- Re: [webrtc-stats] Stat for how many adaption changes occur for a video track
- [webrtc-stats] Stat for how many audio stream packets are expanded when the user is speaking
- [webrtc-stats] Stat for audio playout delay
- [webrtc-stats] Stat for how much time it takes to encode video
- Re: [webrtc-stats] Remove references saying "defines an API"