Wednesday, 31 January 2018
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-stats] Pull Request: tidy checks, missed in latest PRs.
- RE: RTCIceTransport Test
- Re: RTCIceTransport Test
- RE: WPT test dependencies
- Re: WPT test dependencies
- [webrtc-stats] Work through implications of simulcast on the receiver side
- RTCIceTransport Test
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-stats] Typo - RTCLocalAudioStreamTrackStats should inherit from RTCAudioSenderStats
- [webrtc-stats] Cleanup: reformat the sections
- Re: WPT test dependencies
- [webrtc-stats] Pull Request: Define object lifetimes and mention end-of-life emission
- [webrtc-pc] Pull Request: Upgrade to respec 1.9.0.2
- [webrtc-pc] Respec issue: Locked to too old version?
- [webrtc-pc] Pull Request: Add "statslifetimeended" event
- Re: WPT test dependencies
- [webrtc-pc] Sort out unmute and BYE
- Re: WPT test dependencies
Tuesday, 30 January 2018
- [webrtc-pc] Need <section> around RTCIceTransport dictionaries
- [webrtc-pc] Pull Request: Need <section> around dictionaries under RTCRtpSender
- [webrtc-stats] Pull Request: fix for timestamp for remote and local objects
- Weekly github digest (WebRTC WG specifications)
- [webrtc-pc] Need <section> around dictionaries under RTCRtpSender
- [webrtc-pc] Pull Request: Gating 'unmute' events on track with transceiver direction.
- Date and time for February WebRTC VI
Monday, 29 January 2018
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-pc] Direction is not readonly
- Re: ML in WebApps
- Re: ML in WebApps
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-pc] Pull Request: Pending remote updated by setRemote.
- [webrtc-pc] Codify refusing to generate an empty Offer
Sunday, 28 January 2018
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
Friday, 26 January 2018
- Re: ML in WebApps
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: other features
- [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated?
- Re: other features
- Re: other features
- Re: Towards a new charter for the WebRTC Working Group
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- ML in WebApps
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
Thursday, 25 January 2018
- Re: What would you like to see in WebRTC next? A low-level API?
- [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
- Re: need more developer feedback
- [webrtc-stats] Deleting framesCorrupted
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: need more developer feedback
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: other features
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: other features
- Re: need more developer feedback
- Re: What would you like to see in WebRTC next? A low-level API?
Wednesday, 24 January 2018
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- [webrtc-stats] Pull Request: Fixes #161
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: Doodle for February 2018 VI - reminder
- RE: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
Tuesday, 23 January 2018
- Re: What would you like to see in WebRTC next? A low-level API?
- RE: What would you like to see in WebRTC next? A low-level API?
- Re: What would you like to see in WebRTC next? A low-level API?
- What would you like to see in WebRTC next? A low-level API?
- Weekly github digest (WebRTC WG specifications)
- [webrtc-stats] RTCCodecStats in getStats() is redundant.
- [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"
- [webrtc-stats] Lifetime of RTPStreamStats
Monday, 22 January 2018
- [webrtc-pc] Multiple SRDs may leave streams and tracks in unexpected state.
- [webrtc-stats] terminology: rename mediaType to kind
- [webrtc-pc] Pull Request: Properly defined direction when creating transceiver.
Friday, 19 January 2018
- Re: QUIC use cases
- Re: QUIC use cases
- Re: QUIC use cases
- Re: QUIC use cases
- Re: QUIC use cases
- Re: QUIC use cases
- Re: QUIC use cases
- [webrtc-pc] Integrate CSP access control into algorithms
- Re: QUIC use cases
Thursday, 18 January 2018
- Re: QUIC use cases
- [webrtc-pc] Pull Request: Clarify that "disconnected" is transient (editorial)
- [webrtc-pc] Clarify that "disconnected" is transient.
- Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src
- [webrtc-pc] Private key access?
- [webrtc-pc] Pull Request: Passing receiver when constructing track event in 'Processing Remote …
Wednesday, 17 January 2018
- [webrtc-stats] Missing definition of "deleted". When exactly do stats get deleted?
- [webrtc-stats] Add fecPacketsSent/Received
- [webrtc-pc] Add direction change as reason for "mute" event
- Doodle for February 2018 VI
- Re: webRTC and Content Security Policy connect-src
- Re: Alternatives to GetDeletedStats()
- [webrtc-stats] Rename sender/receiver/track stats
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Alternatives to GetDeletedStats()
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- [webrtc-pc] Pull Request: Convert audioLevel to double.
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
Tuesday, 16 January 2018
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Weekly github digest (WebRTC WG specifications)
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- [webrtc-pc] Editorial: PendingRemoteDescription is set by....
- Re: webRTC and Content Security Policy connect-src
- Re: Streams API (WHATWG document)
- Re: Streams API (WHATWG document)
Monday, 15 January 2018
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: QUIC use cases
- Re: webRTC and Content Security Policy connect-src
- Re: QUIC use cases
- Re: QUIC use cases
- Re: Towards a new charter for the WebRTC Working Group
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- [minutes] WebRTC WG Virtual Interim 11 January 2018
- RE: QUIC use cases
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: QUIC use cases
- Re: webRTC and Content Security Policy connect-src
- RE: QUIC use cases
- Re: webRTC and Content Security Policy connect-src
Sunday, 14 January 2018
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
Saturday, 13 January 2018
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Fwd: Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
Friday, 12 January 2018
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src
- Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src
- Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: Towards a new charter for the WebRTC Working Group
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- Re: webRTC and Content Security Policy connect-src
- webRTC and Content Security Policy connect-src
Thursday, 11 January 2018
- [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats
- [webrtc-pc] Pull Request: Make audioLevel and voiceActivityFlag optional and non-nullable.
- [webrtc-stats] Rename "objectDeleted" to something else.
- [webrtc-stats] Define timestamps in terms of performance.origin
- [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
- [webrtc-stats] Rename RTCRTPStreamStats to RTCRtpStreamStats?
- [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
Wednesday, 10 January 2018
- Re: QUIC and WebRTC Comments
- Re: QUIC and WebRTC Comments
- Re: QUIC and WebRTC Comments
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: QUIC and WebRTC Comments
- [webrtc-stats] Enable continuous publication
- Re: QUIC and WebRTC Comments
- Re: Towards a new charter for the WebRTC Working Group
- RE: QUIC and WebRTC Comments
- Re: QUIC and WebRTC Comments
- Re: QUIC and WebRTC Comments
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: QUIC and WebRTC Comments
- Re: QUIC and WebRTC Comments
- QUIC and WebRTC Comments
- [webrtc-pc] "track" event will fire extra times if applying multiple remote offers
Tuesday, 9 January 2018
- Re: Towards a new charter for the WebRTC Working Group
- Weekly github digest (WebRTC WG specifications)
- Re: For discussion at the January 11 virtual interim: WebRTC-Quic and WebRTC-ICE drafts
- [webrtc-pc] Possibly racy replaceTrack()
- For discussion at the January 11 virtual interim: WebRTC-Quic and WebRTC-ICE drafts
Monday, 8 January 2018
- [webrtc-pc] Pull Request: replaceTrack "negotiation needed" clarification
- [webrtc-pc] Pull Request: Whether KeyingMaterial internal slot can be stored and retrieved
- [webrtc-pc] Pull Request: Underlying data transport explanation
- REMINDER: WEBRTC WG Virtual Interim, January 11, 2018 at 16:00 UTC
- Re: Towards a new charter for the WebRTC Working Group
- [webrtc-stats] Pull Request: Introduction to RTP stream statistics
- [webrtc-pc] canTrickleIceCandidiates question
- [webrtc-stats] Pull Request: Adds per-DSCP packet counters to RTP streams
Saturday, 6 January 2018
- Re: Towards a new charter for the WebRTC Working Group
- RE: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
- Re: Towards a new charter for the WebRTC Working Group
Friday, 5 January 2018
Thursday, 4 January 2018
- [webrtc-pc] Pull Request: Define pc.getTransceivers()) et al to be in insertion order.
- [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs
- [webrtc-pc] Pull Request: addTrack cannot reuse a sender whose transceiver is stopped
- [webrtc-pc] Pull Request: Remove reference from RTPSender to RTCPeerConnection
- [webrtc-pc] Pull Request: Move operations queue definition paragraph to right section (editorial)
Wednesday, 3 January 2018
- [webrtc-pc] Pull Request: Validation of reordered readonly parameters in setParameters
- [webrtc-pc] Pull Request: Maximum message size slightly incorrect
- [webrtc-pc] Should we require a reference from RTPSender to RTCPeerConnection?
- [webrtc-stats] WiFi Stats.
- [webrtc-pc] enqueue an operation: is executing async?
Tuesday, 2 January 2018
- Re: Towards a new charter for the WebRTC Working Group
- RE: Towards a new charter for the WebRTC Working Group
- [webrtc-pc] Pull Request: replaceTrack: Never negotiate when replacing an ended track?
- Weekly github digest (WebRTC WG specifications)
- Re: Towards a new charter for the WebRTC Working Group
- [webrtc-pc] example 14: render before verifying the remote fingerprint?
- [webrtc-pc] Example 14 never sends any media
- Re: Towards a new charter for the WebRTC Working Group
- RE: Towards a new charter for the WebRTC Working Group