Wednesday, 31 January 2018
- [webrtc-stats] new commits pushed by vr000m
- [webrtc-stats] Pull Request: tidy checks, missed in latest PRs.
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-pc] Respec issue: Locked to too old version?
- Closed: [webrtc-stats] averageRTCPInterval should be averageRtcpInterval
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-stats] Work through implications of simulcast on the receiver side
- Re: [webrtc-stats] Work through implications of simulcast on the receiver side
- Re: [webrtc-stats] Define object lifetimes and mention end-of-life emission
- Re: [webrtc-stats] Add per layer stats for SVC
- Re: [webrtc-stats] Typo - RTCLocalAudioStreamTrackStats should inherit from RTCAudioSenderStats
- Re: [webrtc-stats] Typo - RTCLocalAudioStreamTrackStats should inherit from RTCAudioSenderStats
- Re: [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries
- Re: [webrtc-stats] Cleanup: reformat the sections
- [webrtc-stats] Work through implications of simulcast on the receiver side
- Re: [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries
- Re: [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries
- Re: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
- Closed: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
- Closed: [webrtc-stats] Deleting framesCorrupted
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-stats] fix camel case averageRtcpInterval and also put in RTCInboundRTPStreamStats
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-stats] Add fecPacketsSent/Received
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-stats] What happens when a partial keyFrames is received?
- Closed: [webrtc-stats] packetsDuplicated is not reported in an RTCP Report
- [webrtc-stats] new commits pushed by vr000m
- Closed: [webrtc-stats] Definitions from MSE need re-targeting
- Re: [webrtc-pc] Respec issue: Locked to too old version?
- Re: [webrtc-pc] Respec issue: Locked to too old version?
- [webrtc-stats] Typo - RTCLocalAudioStreamTrackStats should inherit from RTCAudioSenderStats
- [webrtc-stats] Cleanup: reformat the sections
- Re: [webrtc-pc] Sort out unmute and BYE
- [webrtc-stats] Pull Request: Define object lifetimes and mention end-of-life emission
- Re: [webrtc-stats] Rename RTCRTPStreamStats to RTCRtpStreamStats?
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] Respec issue: Locked to too old version?
- Closed: [webrtc-pc] Respec issue: Locked to too old version?
- [webrtc-pc] new commits pushed by vivienlacourba
- Re: [webrtc-pc] Upgrade to respec 1.9.0.2
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- [webrtc-pc] Pull Request: Upgrade to respec 1.9.0.2
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- [webrtc-pc] Respec issue: Locked to too old version?
- [webrtc-pc] Pull Request: Add "statslifetimeended" event
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- [webrtc-pc] Sort out unmute and BYE
- Re: [webrtc-pc] WHATWG streams for data channel messages
Tuesday, 30 January 2018
- [webrtc-pc] Need <section> around RTCIceTransport dictionaries
- [webrtc-pc] Pull Request: Need <section> around dictionaries under RTCRtpSender
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- [webrtc-stats] Pull Request: fix for timestamp for remote and local objects
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] Need <section> around dictionaries under RTCRtpSender
- [webrtc-pc] Need <section> around dictionaries under RTCRtpSender
- [webrtc-pc] Pull Request: Gating 'unmute' events on track with transceiver direction.
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
Monday, 29 January 2018
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- [webrtc-pc] Direction is not readonly
- Re: [webrtc-pc] Integrate CSP access control into algorithms
- Re: [webrtc-pc] Codify refusing to generate an empty Offer
- Re: [webrtc-pc] Codify refusing to generate an empty Offer
- Re: [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- [webrtc-pc] Pull Request: Pending remote updated by setRemote.
- Re: [webrtc-pc] Codify refusing to generate an empty Offer
- [webrtc-pc] Codify refusing to generate an empty Offer
Sunday, 28 January 2018
Saturday, 27 January 2018
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
Friday, 26 January 2018
- [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
Thursday, 25 January 2018
- Closed: [webrtc-pc] specify legacy onaddstream?
- Closed: [webrtc-pc] When to fire events triggered by setRemoteDescription.
- Re: [webrtc-pc] onmute then onunmute can fire before negotiation completes
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Closed: [webrtc-pc] canTrickleIceCandidiates question
- Closed: [webrtc-pc] Clarify that "disconnected" is transient.
- Re: [webrtc-pc] Clarify that "disconnected" is transient.
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] WHATWG streams for data channel messages
- [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries
- [webrtc-stats] Pull Request: fix camel case averageRtcpInterval and also put in RTCInboundRTPStreamStats
- [webrtc-stats] Pull Request: FEC sent and received metrics
- [webrtc-stats] Pull Request: moved packetsDuplicated to the right dictionary
- [webrtc-stats] Deleting framesCorrupted
Wednesday, 24 January 2018
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] RTPRtcSender: provided properties to get related MediaStreamTrackId and media type
- Re: [webrtc-stats] Remove references to MSE. Fixes #161
- Re: [webrtc-stats] RTCCodecStats in every getStats() is redundant.
- Re: [webrtc-stats] Remove references to MSE. Fixes #161
- Closed: [webrtc-stats] Rename "objectDeleted" to something else.
- Re: [webrtc-stats] Rename "objectDeleted" to something else.
- Re: [webrtc-stats] terminology: rename mediaType to kind
- Re: [webrtc-stats] Lifetime of RTPStreamStats
- Re: [webrtc-stats] Lifetime of RTPStreamStats
- Re: [webrtc-stats] CodecType "encode" / "decode" needs to default to "both"
- Closed: [webrtc-stats] CodecType "encode" / "decode" needs to default to "both"
- Re: [webrtc-stats] CodecType "encode" / "decode" needs to default to "both"
- Re: [webrtc-stats] CodecType "encode" / "decode" needs to default to "both"
- Re: [webrtc-stats] Stats need to mark up which members are required
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] RTCCodecStats in every getStats() is redundant.
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Missing definition of "deleted". When exactly do stats get deleted?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Fixes #161
- [webrtc-stats] Pull Request: Fixes #161
- Closed: [webrtc-stats] RTCCodecStats in every getStats() is redundant.
- Re: [webrtc-stats] RTCCodecStats in every getStats() is redundant.
Tuesday, 23 January 2018
- Re: [webrtc-stats] Missing definition of "deleted". When exactly do stats get deleted?
- Re: [webrtc-stats] RTCCodecStats in every getStats() is redundant.
- [webrtc-stats] RTCCodecStats in getStats() is redundant.
- Re: [webrtc-pc] Multiple SRDs may leave streams and tracks in unexpected state.
- [webrtc-stats] averageRTCPInterval should be averageRtcpInterval
- [webrtc-stats] Stats need to mark up which members are required
- [webrtc-stats] CodecType "encode" / "decude" needs to default to "both"
- Re: [webrtc-pc] Multiple SRDs may leave streams and tracks in unexpected state.
- [webrtc-stats] Lifetime of RTPStreamStats
Monday, 22 January 2018
- Closed: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- [webrtc-pc] Multiple SRDs may leave streams and tracks in unexpected state.
- Re: [webrtc-pc] Defer SRD add/remove tracks until right before firing track events.
- Re: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
- Closed: [webrtc-stats] Is bytesReceived really available for RTCRemoteInboundRTPStreamStats?
- Re: [webrtc-stats] moved bytes and packets received counters
- [webrtc-stats] terminology: rename mediaType to kind
- [webrtc-pc] Pull Request: Properly defined direction when creating transceiver.
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
Friday, 19 January 2018
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] Data channel closing procedure
- Re: [webrtc-pc] Integrate CSP access control into algorithms
- [webrtc-pc] Integrate CSP access control into algorithms
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
Thursday, 18 January 2018
- Re: [webrtc-pc] Data channel closing procedure
- [webrtc-pc] Pull Request: Clarify that "disconnected" is transient (editorial)
- [webrtc-pc] Clarify that "disconnected" is transient.
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Closed: [webrtc-pc] Why is RTCRtpSynchronizationSource.voiceActivityFlag required-but-nullable?
- Re: [webrtc-pc] WebRTC bypass CSP connect-src policies
- Closed: [webrtc-pc] Should we require a reference from RTPSender to RTCPeerConnection?
- Re: [webrtc-pc] Data channel closing procedure
- Closed: [webrtc-pc] order of transceivers, senders/receivers?
- Closed: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Closed: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] Effect of mute/disable on on-the-wire framerate is not described
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] Do not consider direction in "need negotiation" evaluation for replaceTrack
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] RTCDtlsTransportState enum descriptions are lacking
- Re: [webrtc-pc] replaceTrack "negotiation needed" clarification
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] Private key access?
- Re: [webrtc-pc] Add support for WebRTC Data Channel in Workers
- [webrtc-pc] Private key access?
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Using setConfiguration() to add application certificates to an RTCPeerConnection post-construction?
- [webrtc-pc] Pull Request: Passing receiver when constructing track event in 'Processing Remote …
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- Re: [webrtc-pc] Define pc.getTransceivers() et al to be in insertion order.
- Re: [webrtc-pc] replaceTrack "negotiation needed" clarification
- Re: [webrtc-pc] onmute then onunmute can fire before negotiation completes
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-stats] Missing definition of "deleted". When exactly do stats get deleted?
- Re: [webrtc-stats] Rename sender/receiver/track stats
- Re: [webrtc-stats] Missing definition of "deleted". When exactly do stats get deleted?
Wednesday, 17 January 2018
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- [webrtc-stats] Missing definition of "deleted". When exactly do stats get deleted?
- Re: [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] WHATWG streams for data channel messages
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-pc] Add direction change as reason for "mute" event
- Re: [webrtc-pc] Add direction change as reason for "mute" event
- [webrtc-stats] new commits pushed by alvestrand
- [webrtc-stats] new commits pushed by vr000m
- [webrtc-stats] Add fecPacketsSent/Received
- [webrtc-pc] Add direction change as reason for "mute" event
- Re: [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
- Re: [webrtc-stats] Rename RTCRTPStreamStats to RTCRtpStreamStats?
- Re: [webrtc-stats] Rename sender/receiver/track stats
- Re: [webrtc-stats] Rename "objectDeleted" to something else.
- Re: [webrtc-stats] Rename "objectDeleted" to something else.
- Re: [webrtc-stats] Rename sender/receiver/track stats
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Rename sender/receiver/track stats
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] moved bytes and packets received counters
- Closed: [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
- [webrtc-stats] new commits pushed by vr000m
- [webrtc-stats] new commits pushed by alvestrand
- Re: [webrtc-stats] Rename sender/receiver/track stats
- Re: [webrtc-stats] Rename sender/receiver/track stats
- [webrtc-stats] Rename sender/receiver/track stats
- Re: [webrtc-stats] Additional description of audioLevel
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
- Re: [webrtc-stats] Remove reference to RTCRtpSynchronizationSource.audioLevel.
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-pc] WHATWG streams for data channel messages
- [webrtc-pc] Pull Request: Convert audioLevel to double.
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
Tuesday, 16 January 2018
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- [webrtc-pc] Editorial: PendingRemoteDescription is set by....
- Re: [webrtc-stats] Add per layer stats for SVC
Monday, 15 January 2018
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Maximum message size slightly incorrect
- Closed: [webrtc-pc] Maximum message size slightly incorrect
- Re: [webrtc-pc] Maximum message size slightly incorrect
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] Maximum message size slightly incorrect
Sunday, 14 January 2018
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
Saturday, 13 January 2018
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] WHATWG streams for data channel messages
Friday, 12 January 2018
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] WHATWG streams for data channels
- Re: [webrtc-pc] WHATWG streams for data channels
- Re: [webrtc-pc] WHATWG streams for data channels
Thursday, 11 January 2018
- [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- [webrtc-pc] Pull Request: Make audioLevel and voiceActivityFlag optional and non-nullable.
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-pc] WHATWG streams for data channels
- Re: [webrtc-pc] WHATWG streams for data channels
- Re: [webrtc-pc] WHATWG streams for data channels
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- [webrtc-stats] Rename "objectDeleted" to something else.
- Re: [webrtc-pc] Effect of mute/disable on on-the-wire framerate is not described
- [webrtc-stats] Define timestamps in terms of performance.origin
- Re: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
- Re: [webrtc-pc] Why is RTCRtpSynchronizationSource.voiceActivityFlag required-but-nullable?
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-pc] Define pc.getTransceivers() et al to be in insertion order.
- Re: [webrtc-pc] Maximum message size slightly incorrect
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] replaceTrack: Clarify how the UA determines if negotiation is needed
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] RTCDataChannel.bufferedAmount description confusing
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- [webrtc-pc] Pull Request: RTCRtpSender: Specify advise about framerate for disabled/muted tracks
- [webrtc-pc] Do not consider direction at "need negotiation" evaluation for replaceTrack
- Re: [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
- [webrtc-stats] Rename RTCRTPStreamStats to RTCRtpStreamStats?
- [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
Wednesday, 10 January 2018
- Re: [webrtc-stats] Need DSCP information for outgoing RTP streams
- Re: [webrtc-pc] editorial: media api introduction
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-pc] editorial: media api introduction
- Re: [webrtc-stats] Enable continuous publication
- Closed: [webrtc-stats] Need DSCP information for incoming RTP streams
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-stats] Need DSCP information for outgoing RTP streams
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-stats] Enable continuous publication
- [webrtc-stats] new commits pushed by vivienlacourba
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-stats] Enable continuous publication
- [webrtc-stats] Enable continuous publication
- Re: [webrtc-stats] WiFi Stats.
- Re: [webrtc-stats] "record<RTCQualityLimitationReason, double> qualityLimitationDurations" has invalid type
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Adds per-DSCP packet counters to RTP streams
- Re: [webrtc-stats] Introduction to RTP stream statistics
- Re: [webrtc-stats] moved bytes and packets received counters
- Re: [webrtc-stats] Additional description of audioLevel
- Closed: [webrtc-stats] We need "sender" and "receiver" stats, not "track" stats
- Re: [webrtc-stats] RTCMediaStreamTrackStats is four dictionaries in one
- Closed: [webrtc-stats] RTCMediaStreamTrackStats is four dictionaries in one
- Re: [webrtc-stats] We need "sender" and "receiver" stats, not "track" stats
- [webrtc-stats] new commits pushed by alvestrand
- Re: [webrtc-stats] Add "sender" and "receiver" stats.
- Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
- Re: [webrtc-stats] Pivot from "track" to "sender" and "receiver" stats.
- Re: [webrtc-stats] Pivot from "track" to "sender" and "receiver" stats.
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-stats] Split RTCMediaStreamTrackStats into four dictionaries.
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] Possibly racy replaceTrack()
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] editorial: media api introduction
- Re: [webrtc-stats] Split RTCMediaStreamTrackStats into four dictionaries.
- Re: [webrtc-stats] Pivot from "track" to "sender" and "receiver" stats.
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-pc] editorial: media api introduction
- Re: [webrtc-pc] Possibly racy replaceTrack()
- [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
Tuesday, 9 January 2018
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-pc] Possibly racy replaceTrack()
- Re: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
- Re: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
- Re: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
- Re: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
- Re: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
- Re: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-pc] Add support for WebRTC Data Channel in Workers
- Re: [webrtc-pc] Possibly racy replaceTrack()
- [webrtc-pc] Possibly racy replaceTrack()
- Re: [webrtc-pc] RTCPriorityType combines relative bitrate with QoS priority, which applications may not want.
Monday, 8 January 2018
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-pc] editorial: media api introduction
- Re: [webrtc-pc] editorial: media api introduction
- [webrtc-pc] Pull Request: replaceTrack "negotiation needed" clarification
- Re: [webrtc-pc] Data channel closing procedure
- Re: [webrtc-pc] Whether KeyingMaterial internal slot can be stored and retrieved
- [webrtc-pc] Pull Request: Whether KeyingMaterial internal slot can be stored and retrieved
- [webrtc-pc] Pull Request: Underlying data transport explanation
- [webrtc-stats] Pull Request: Introduction to RTP stream statistics
- Re: [webrtc-pc] canTrickleIceCandidiates question
- Re: [webrtc-pc] canTrickleIceCandidiates question
- [webrtc-pc] canTrickleIceCandidiates question
- [webrtc-pc] new commits pushed by dontcallmedom
- Re: [webrtc-stats] Adds per-DSCP packet counters to RTP streams
- Re: [webrtc-pc] RTPRtcSender: provided properties to get related MediaStreamTrackId and media type
- Re: [webrtc-pc] RTPRtcSender: provided properties to get related MediaStreamTrackId and media type
- [webrtc-stats] Pull Request: Adds per-DSCP packet counters to RTP streams
Sunday, 7 January 2018
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
Saturday, 6 January 2018
- Re: [webrtc-pc] RTPRtcSender: provided properties to get related MediaStreamTrackId and media type
- Re: [webrtc-pc] RTPRtcSender: provided properties to get related MediaStreamTrackId and media type
- Re: [webrtc-pc] RTPRtcSender: provided properties to get related MediaStreamTrackId and media type
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
Friday, 5 January 2018
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-stats] WiFi Stats.
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- [webrtc-pc] Pull Request: Defer SRD add/remove tracks until right before firing track events.
Thursday, 4 January 2018
- Re: [webrtc-stats] WiFi Stats.
- [webrtc-pc] Pull Request: Define pc.getTransceivers()) et al to be in insertion order.
- Re: [webrtc-pc] Why is RTCRtpSynchronizationSource.voiceActivityFlag required-but-nullable?
- [webrtc-pc] new commits pushed by alvestrand
- Closed: [webrtc-pc] addTrack can reuse a sender whose transceiver is stopped
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] Maximum message size slightly incorrect
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Closed: [webrtc-pc] At risk text in wrong location
- Re: [webrtc-pc] At risk text in wrong location
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- Closed: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- Re: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- Re: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- Re: [webrtc-pc] Make promise rejection/enqueing consistent
- Re: [webrtc-pc] Should we require a reference from RTPSender to RTCPeerConnection?
- Re: [webrtc-pc] replaceTrack: Never negotiate when replacing an ended track?
- Re: [webrtc-stats] WiFi Stats.
- Re: [webrtc-pc] Using setConfiguration() to add application certificates to an RTCPeerConnection post-construction?
- Re: [webrtc-pc] At risk text in wrong location
- [webrtc-pc] Pull Request: addTrack cannot reuse a sender whose transceiver is stopped
- Re: [webrtc-pc] example 14: render before verifying the remote fingerprint?
- [webrtc-pc] Pull Request: Remove reference from RTPSender to RTCPeerConnection
- [webrtc-pc] Pull Request: Move operations queue definition paragraph to right section (editorial)
- Re: [webrtc-pc] enqueue an operation: is executing async?
- Closed: [webrtc-pc] Ordering of stream "addtrack"/"removetrack" events vs. "track" event
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
Wednesday, 3 January 2018
- Re: [webrtc-pc] addTransceiver woes
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] Pull Request: Validation of reordered readonly parameters in setParameters
- Closed: [webrtc-pc] replaceTrack and removeTrack: Synchronous?
- Re: [webrtc-pc] replaceTrack and removeTrack: Synchronous?
- Re: [webrtc-pc] RTCCertificate Interface should (or should not) be backed up.
- Re: [webrtc-pc] RTCCertificate Interface should (or should not) be backed up.
- [webrtc-pc] Pull Request: Maximum message size slightly incorrect
- Re: [webrtc-pc] Should we require a reference from RTPSender to RTCPeerConnection?
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] Should we require a reference from RTPSender to RTCPeerConnection?
- [webrtc-pc] Should we require a reference from RTPSender to RTCPeerConnection?
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-stats] WiFi Stats.
- [webrtc-stats] WiFi Stats.
- Re: [webrtc-pc] specify legacy onaddstream?
- Re: [webrtc-pc] When to fire events triggered by setRemoteDescription.
- Re: [webrtc-stats] packetsDuplicated is not reported in an RTCP Report
- Re: [webrtc-stats] Stats for Audio network adaptation
- Closed: [webrtc-stats] Stats for Audio network adaptation
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-stats] Audio/Video sync follow-up
- Closed: [webrtc-stats] Audio/Video sync follow-up
- Re: [webrtc-stats] Is bytesReceived really available for RTCRemoteInboundRTPStreamStats?
- Re: [webrtc-stats] Pivot from "track" to "sender" and "receiver" stats.
- Re: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- Re: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- Re: [webrtc-pc] replaceTrack and removeTrack: Synchronous?
- Closed: [webrtc-pc] Consider using generic algorithm
- Re: [webrtc-pc] Consider using generic algorithm
- Re: [webrtc-pc] example 14: render before verifying the remote fingerprint?
- Re: [webrtc-pc] Example 14 never sends any media
- [webrtc-pc] enqueue an operation: is executing async?
Tuesday, 2 January 2018
- Re: [webrtc-pc] example 14: render before verifying the remote fingerprint?
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] addTransceiver woes
- [webrtc-pc] Pull Request: replaceTrack: Never negotiate when replacing an ended track?
- Re: [webrtc-pc] replaceTrack: Never negotiate when replacing an ended track?
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] Example 14 never sends any media
- Re: [webrtc-pc] Example 14 never sends any media
- Re: [webrtc-pc] replaceTrack: Never negotiate when replacing an ended track?
- Closed: [webrtc-pc] Section 4.3.3: optional methods
- Re: [webrtc-pc] Section 4.3.3: optional methods
- Closed: [webrtc-pc] `parameters` not defined in `setParameters` algorithm
- Re: [webrtc-pc] `parameters` not defined in `setParameters` algorithm
- Re: [webrtc-pc] Consider using generic algorithm
- Re: [webrtc-pc] Make promise rejection/enqueing consistent
- Re: [webrtc-pc] example 14: render before verifying the remote fingerprint?
- Re: [webrtc-pc] example 14: render before verifying the remote fingerprint?
- Re: [webrtc-pc] replaceTrack and removeTrack: Synchronous?
- Re: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- Re: [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- Re: [webrtc-pc] Should rollback fire addtrack/removetrack events?
- [webrtc-pc] example 14: render before verifying the remote fingerprint?
- Re: [webrtc-pc] replaceTrack and removeTrack: Synchronous?
- [webrtc-pc] Example 14 never sends any media
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] addTransceiver woes
- Re: [webrtc-pc] addTransceiver woes