public-webrtc@w3.org from January 2018 by author

Adam Bergkvist via GitHub

• [webrtc-pc] Pull Request: RTCRtpSender: Specify advise about framerate for disabled/muted tracks (Thursday, 11 January)

Alexandre GOUAILLARD

• Re: WPT test dependencies (Wednesday, 31 January)

Bernard Aboba

• RE: RTCIceTransport Test (Wednesday, 31 January)
• RE: WPT test dependencies (Wednesday, 31 January)
• Re: other features (Friday, 26 January)
• Re: other features (Thursday, 25 January)
• Re: need more developer feedback (Thursday, 25 January)
• RE: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• RE: What would you like to see in WebRTC next? A low-level API? (Tuesday, 23 January)
• Re: QUIC use cases (Friday, 19 January)
• Re: Streams API (WHATWG document) (Tuesday, 16 January)
• RE: QUIC use cases (Monday, 15 January)
• RE: QUIC use cases (Monday, 15 January)
• RE: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• For discussion at the January 11 virtual interim: WebRTC-Quic and WebRTC-ICE drafts (Tuesday, 9 January)
• REMINDER: WEBRTC WG Virtual Interim, January 11, 2018 at 16:00 UTC (Monday, 8 January)
• RE: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)
• RE: Towards a new charter for the WebRTC Working Group (Tuesday, 2 January)
• RE: Towards a new charter for the WebRTC Working Group (Tuesday, 2 January)

Bernard Aboba via GitHub

• [webrtc-pc] Need <section> around RTCIceTransport dictionaries (Tuesday, 30 January)
• [webrtc-pc] Pull Request: Need <section> around dictionaries under RTCRtpSender (Tuesday, 30 January)
• [webrtc-pc] Pull Request: replaceTrack "negotiation needed" clarification (Monday, 8 January)
• [webrtc-pc] Pull Request: Whether KeyingMaterial internal slot can be stored and retrieved (Monday, 8 January)
• [webrtc-pc] Pull Request: Underlying data transport explanation (Monday, 8 January)
• [webrtc-pc] Pull Request: addTrack cannot reuse a sender whose transceiver is stopped (Thursday, 4 January)
• [webrtc-pc] Pull Request: Remove reference from RTPSender to RTCPeerConnection (Thursday, 4 January)
• [webrtc-pc] Pull Request: Validation of reordered readonly parameters in setParameters (Wednesday, 3 January)
• [webrtc-pc] Pull Request: Maximum message size slightly incorrect (Wednesday, 3 January)
• [webrtc-pc] Pull Request: replaceTrack: Never negotiate when replacing an ended track? (Tuesday, 2 January)

Byron Campen

• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)

Christer Holmberg

• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Sunday, 14 January)

Cullen Jennings

• Re: What would you like to see in WebRTC next? A low-level API? (Monday, 29 January)
• Re: other features (Friday, 26 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Friday, 26 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Friday, 26 January)
• Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src (Thursday, 18 January)

Cullen Jennings (fluffy)

• Re: Towards a new charter for the WebRTC Working Group (Friday, 26 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Friday, 26 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Friday, 26 January)
• ML in WebApps (Friday, 26 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Friday, 26 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Friday, 26 January)

Dominique Hazael-Massieux

• Re: need more developer feedback (Thursday, 25 January)

Emil Ivov

• Re: What would you like to see in WebRTC next? A low-level API? (Thursday, 25 January)

Eric Rescorla

• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)

Göran Eriksson AP

• Re: ML in WebApps (Monday, 29 January)
• Re: ML in WebApps (Monday, 29 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)

Harald Alvestrand

• Re: RTCIceTransport Test (Wednesday, 31 January)
• Re: WPT test dependencies (Wednesday, 31 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Monday, 29 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Monday, 29 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Sunday, 28 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Sunday, 28 January)
• Re: webRTC and Content Security Policy connect-src (Wednesday, 17 January)
• Re: webRTC and Content Security Policy connect-src (Wednesday, 17 January)
• Alternatives to GetDeletedStats() (Wednesday, 17 January)
• Re: webRTC and Content Security Policy connect-src (Tuesday, 16 January)
• Re: Streams API (WHATWG document) (Tuesday, 16 January)
• Re: QUIC use cases (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Sunday, 14 January)
• Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src (Friday, 12 January)

Harald Alvestrand via GitHub

• [webrtc-stats] Work through implications of simulcast on the receiver side (Wednesday, 31 January)
• [webrtc-stats] Pull Request: Define object lifetimes and mention end-of-life emission (Wednesday, 31 January)
• [webrtc-pc] Respec issue: Locked to too old version? (Wednesday, 31 January)
• [webrtc-pc] Pull Request: Add "statslifetimeended" event (Wednesday, 31 January)
• [webrtc-pc] Need <section> around dictionaries under RTCRtpSender (Tuesday, 30 January)
• [webrtc-pc] Codify refusing to generate an empty Offer (Monday, 29 January)
• [webrtc-stats] averageRTCPInterval should be averageRtcpInterval (Tuesday, 23 January)
• [webrtc-stats] Stats need to mark up which members are required (Tuesday, 23 January)
• [webrtc-stats] CodecType "encode" / "decude" needs to default to "both" (Tuesday, 23 January)
• [webrtc-stats] Lifetime of RTPStreamStats (Tuesday, 23 January)
• [webrtc-pc] Integrate CSP access control into algorithms (Friday, 19 January)
• [webrtc-pc] Private key access? (Thursday, 18 January)
• [webrtc-pc] Editorial: PendingRemoteDescription is set by.... (Tuesday, 16 January)
• [webrtc-stats] Define timestamps in terms of performance.origin (Thursday, 11 January)
• [webrtc-stats] Enable continuous publication (Wednesday, 10 January)
• [webrtc-stats] Pull Request: Introduction to RTP stream statistics (Monday, 8 January)
• [webrtc-stats] Pull Request: Adds per-DSCP packet counters to RTP streams (Monday, 8 January)
• [webrtc-pc] Should we require a reference from RTPSender to RTCPeerConnection? (Wednesday, 3 January)

henbos via GitHub

• [webrtc-stats] Rename sender/receiver/track stats (Wednesday, 17 January)
• [webrtc-stats] Rename "objectDeleted" to something else. (Thursday, 11 January)
• [webrtc-stats] Rename RTCRTPStreamStats to RTCRtpStreamStats? (Thursday, 11 January)
• [webrtc-stats] RTCRTPStreamStats should have senderId/receiverId (Thursday, 11 January)
• [webrtc-pc] Possibly racy replaceTrack() (Tuesday, 9 January)
• [webrtc-pc] "a=msid" line should contain sender/receiver IDs, not track IDs (Thursday, 4 January)

Iñaki Baz Castillo

• Re: What would you like to see in WebRTC next? A low-level API? (Thursday, 25 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Tuesday, 23 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Sunday, 14 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: Towards a new charter for the WebRTC Working Group (Wednesday, 10 January)

jan-ivar via GitHub

• [webrtc-pc] Multiple SRDs may leave streams and tracks in unexpected state. (Monday, 22 January)
• [webrtc-pc] Pull Request: Clarify that "disconnected" is transient (editorial) (Thursday, 18 January)
• [webrtc-pc] Clarify that "disconnected" is transient. (Thursday, 18 January)
• [webrtc-stats] Missing definition of "deleted". When exactly do stats get deleted? (Wednesday, 17 January)
• [webrtc-pc] Pull Request: Convert audioLevel to double. (Wednesday, 17 January)
• [webrtc-pc] Pull Request: Make audioLevel and voiceActivityFlag optional and non-nullable. (Thursday, 11 January)
• [webrtc-pc] Pull Request: Defer SRD add/remove tracks until right before firing track events. (Friday, 5 January)
• [webrtc-pc] Pull Request: Define pc.getTransceivers()) et al to be in insertion order. (Thursday, 4 January)
• [webrtc-pc] Pull Request: Move operations queue definition paragraph to right section (editorial) (Thursday, 4 January)

Justin Uberti

• Re: ML in WebApps (Friday, 26 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Thursday, 25 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Thursday, 25 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: QUIC use cases (Friday, 19 January)
• Re: QUIC use cases (Thursday, 18 January)

karthikbr82 via GitHub

• [webrtc-stats] Typo - RTCLocalAudioStreamTrackStats should inherit from RTCAudioSenderStats (Wednesday, 31 January)
• [webrtc-stats] RTCCodecStats in getStats() is redundant. (Tuesday, 23 January)
• [webrtc-stats] WiFi Stats. (Wednesday, 3 January)

Lennart Grahl

• Re: need more developer feedback (Thursday, 25 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: QUIC use cases (Monday, 15 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 13 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 13 January)
• Fwd: Re: Towards a new charter for the WebRTC Working Group (Saturday, 13 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 13 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Towards a new charter for the WebRTC Working Group (Friday, 12 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: Towards a new charter for the WebRTC Working Group (Monday, 8 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)

Lorenzo Miniero

• Re: Towards a new charter for the WebRTC Working Group (Thursday, 11 January)

Martin Thomson

• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 31 January)
• Re: webRTC and Content Security Policy connect-src (Wednesday, 17 January)
• Re: webRTC and Content Security Policy connect-src (Tuesday, 16 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: Towards a new charter for the WebRTC Working Group (Tuesday, 2 January)
• Re: Towards a new charter for the WebRTC Working Group (Monday, 1 January)

Michael Tuexen

• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: QUIC use cases (Friday, 19 January)
• Re: QUIC use cases (Monday, 15 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)

na-g via GitHub

• [webrtc-pc] RTCRtpContributingSource.audioLevel has different type and range than similar fields in webrtc-stats (Thursday, 11 January)

Peter Thatcher

• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• What would you like to see in WebRTC next? A low-level API? (Tuesday, 23 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: Towards a new charter for the WebRTC Working Group (Wednesday, 10 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: Towards a new charter for the WebRTC Working Group (Wednesday, 10 January)
• Re: Towards a new charter for the WebRTC Working Group (Wednesday, 10 January)
• Re: QUIC and WebRTC Comments (Wednesday, 10 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)

Philipp Hancke

• Re: WPT test dependencies (Wednesday, 31 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Thursday, 25 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Thursday, 25 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)

Philipp Hancke via GitHub

• [webrtc-stats] terminology: rename mediaType to kind (Monday, 22 January)
• [webrtc-pc] canTrickleIceCandidiates question (Monday, 8 January)
• [webrtc-pc] enqueue an operation: is executing async? (Wednesday, 3 January)
• [webrtc-pc] example 14: render before verifying the remote fingerprint? (Tuesday, 2 January)

Randell Jesup

• Re: QUIC use cases (Friday, 19 January)
• Re: QUIC use cases (Friday, 19 January)
• Re: QUIC use cases (Monday, 15 January)
• Re: Towards a new charter for the WebRTC Working Group (Tuesday, 9 January)

Roman Shpount

• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Tuesday, 23 January)
• Re: webRTC and Content Security Policy connect-src (Tuesday, 16 January)
• Re: webRTC and Content Security Policy connect-src (Tuesday, 16 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: Towards a new charter for the WebRTC Working Group (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)

Sergio Garcia Murillo

• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 31 January)
• Re: WPT test dependencies (Wednesday, 31 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Monday, 29 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Friday, 26 January)
• Re: other features (Friday, 26 January)
• Re: other features (Thursday, 25 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: webRTC and Content Security Policy connect-src (Wednesday, 17 January)
• Re: webRTC and Content Security Policy connect-src (Wednesday, 17 January)
• Re: webRTC and Content Security Policy connect-src (Wednesday, 17 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: webRTC and Content Security Policy connect-src (Monday, 15 January)
• Re: Towards a new charter for the WebRTC Working Group (Saturday, 13 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)

stefan hakansson via GitHub

• [webrtc-pc] Sort out unmute and BYE (Wednesday, 31 January)
• [webrtc-pc] Pull Request: Gating 'unmute' events on track with transceiver direction. (Tuesday, 30 January)
• [webrtc-pc] Direction is not readonly (Monday, 29 January)
• [webrtc-pc] Pull Request: Pending remote updated by setRemote. (Monday, 29 January)
• [webrtc-pc] Pull Request: Properly defined direction when creating transceiver. (Monday, 22 January)
• [webrtc-pc] Pull Request: Passing receiver when constructing track event in 'Processing Remote … (Thursday, 18 January)
• [webrtc-pc] Add direction change as reason for "mute" event (Wednesday, 17 January)
• [webrtc-pc] Do not consider direction at "need negotiation" evaluation for replaceTrack (Thursday, 11 January)
• [webrtc-pc] Example 14 never sends any media (Tuesday, 2 January)

Stefan Håkansson LK

• Date and time for February WebRTC VI (Tuesday, 30 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Monday, 29 January)
• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: Doodle for February 2018 VI - reminder (Wednesday, 24 January)
• Doodle for February 2018 VI (Wednesday, 17 January)
• Re: webRTC and Content Security Policy connect-src (Tuesday, 16 January)
• Re: webRTC and Content Security Policy connect-src (Tuesday, 16 January)

Stephen Farrell

• Re: webRTC and Content Security Policy connect-src (Wednesday, 17 January)

T H Panton

• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 24 January)
• Re: QUIC use cases (Friday, 19 January)
• Re: QUIC use cases (Friday, 19 January)
• Re: QUIC use cases (Friday, 19 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: webRTC and Content Security Policy connect-src (Friday, 12 January)
• webRTC and Content Security Policy connect-src (Friday, 12 January)
• Re: Towards a new charter for the WebRTC Working Group (Thursday, 11 January)
• Re: Towards a new charter for the WebRTC Working Group (Thursday, 11 January)
• Re: Towards a new charter for the WebRTC Working Group (Thursday, 11 January)
• Re: Towards a new charter for the WebRTC Working Group (Wednesday, 10 January)
• Re: For discussion at the January 11 virtual interim: WebRTC-Quic and WebRTC-ICE drafts (Tuesday, 9 January)
• Re: Towards a new charter for the WebRTC Working Group (Tuesday, 2 January)
• Re: Towards a new charter for the WebRTC Working Group (Tuesday, 2 January)

Taylor Brandstetter

• Re: Ban ICE-LITE? webRTC and Content Security Policy connect-src (Friday, 12 January)

Taylor Brandstetter via GitHub

• [webrtc-stats] When are "fractionLost", "packetsLost, " "jitter", and other RFC3550-based stats updated? (Friday, 26 January)
• [webrtc-pc] "track" event will fire extra times if applying multiple remote offers (Wednesday, 10 January)

Toshiya Nakakura

• Re: What would you like to see in WebRTC next? A low-level API? (Wednesday, 31 January)

Varun Singh

• Re: Alternatives to GetDeletedStats() (Wednesday, 17 January)

Varun Singh via GitHub

• [webrtc-stats] Pull Request: tidy checks, missed in latest PRs. (Wednesday, 31 January)
• [webrtc-stats] Cleanup: reformat the sections (Wednesday, 31 January)
• [webrtc-stats] Pull Request: fix for timestamp for remote and local objects (Tuesday, 30 January)
• [webrtc-stats] video packet counters should be moved out from RTCRTPStreamStats to appropriate dictionaries (Thursday, 25 January)
• [webrtc-stats] Pull Request: fix camel case averageRtcpInterval and also put in RTCInboundRTPStreamStats (Thursday, 25 January)
• [webrtc-stats] Pull Request: FEC sent and received metrics (Thursday, 25 January)
• [webrtc-stats] Pull Request: moved packetsDuplicated to the right dictionary (Thursday, 25 January)
• [webrtc-stats] Deleting framesCorrupted (Thursday, 25 January)
• [webrtc-stats] Pull Request: Fixes #161 (Wednesday, 24 January)
• [webrtc-stats] Add fecPacketsSent/Received (Wednesday, 17 January)

Vivien Lacourba

• [minutes] WebRTC WG Virtual Interim 11 January 2018 (Monday, 15 January)

Vivien Lacourba via GitHub

• [webrtc-pc] Pull Request: Upgrade to respec 1.9.0.2 (Wednesday, 31 January)

W3C Webmaster via GitHub API

• Weekly github digest (WebRTC WG specifications) (Tuesday, 30 January)
• Weekly github digest (WebRTC WG specifications) (Tuesday, 23 January)
• Weekly github digest (WebRTC WG specifications) (Tuesday, 16 January)
• Weekly github digest (WebRTC WG specifications) (Tuesday, 9 January)
• Weekly github digest (WebRTC WG specifications) (Tuesday, 2 January)

webmaster

• RTCIceTransport Test (Wednesday, 31 January)

westhawk

• Re: Towards a new charter for the WebRTC Working Group (Saturday, 6 January)

Last message date: Wednesday, 31 January 2018 23:05:07 UTC