Saturday, 30 June 2018
Friday, 29 June 2018
- Re: Low latency video in WebRTC
- [webrtc-pc] RTCRtpReceiver.getStreams() and RTCRtpSender.getStreams()
- [webrtc-pc] Unable to figure out which receivers are "active".
Thursday, 28 June 2018
Wednesday, 27 June 2018
- [webrtc-pc] detecting a remote ICE restart?
- [webrtc-stats] Pull Request: Add TLS version and TLS group to RTCTransportStats
- Re: WebRTC in workers
- Re: WebRTC in workers
Tuesday, 26 June 2018
- Re: WebRTC in workers
- Re: Low latency video in WebRTC
- Weekly github digest (WebRTC WG specifications)
- Re: Low latency video in WebRTC
- Re: Low latency video in WebRTC
- Re: Low latency video in WebRTC
- Re: Low latency video in WebRTC
- [webrtc-stats] Pull Request: Clarify role of editors draft for CR transition request
- Summary of decisions at the June 19-20 f2f
Monday, 25 June 2018
- [webrtc-pc] Should remote tracks stop() when the PC is close()-ed?
- [webrtc-pc] RTCIceTransport.component is at the wrong abstraction layer
Saturday, 23 June 2018
- Re: Summary of e2e encryption discussions
- Re: WebRTC in workers
- Re: Summary of e2e encryption discussions
- Re: Summary of e2e encryption discussions
- Re: WebRTC in workers
Friday, 22 June 2018
- [webrtc-pc] Pull Request: Splits Identity into its own specification.
- [webrtc-pc] Split Identity into its own specification
- Re: Summary of e2e encryption discussions
- Re: Summary of e2e encryption discussions
- Re: Summary of e2e encryption discussions
- Re: WebRTC in workers
- Re: Summary of e2e encryption discussions
- WebRTC in workers
- Summary of e2e encryption discussions
Thursday, 21 June 2018
- YouTube recordings of Stockholm meeting
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Updated CR for WebRTC 1.0
- [webrtc-stats] Input/output resolution and audio energy
- Call for Exclusions: WebRTC 1.0: Real-time Communication Between Browsers
- Re: WebRTC NV Use Cases
- [webrtc-pc] rename RTCIceCandidate.ip to address?
- [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
Wednesday, 20 June 2018
- Re: Low latency video in WebRTC
- Re: Low latency video in WebRTC
- SV: Re: RTT implementation = Real-Time Text implementation
- [webrtc-pc] Pull Request: Adding note about the relationship between tracks of senders/receivers.
- [webrtc-pc] Pull Request: Adding note about when ICE restarts are recommended.
- Re: Low latency video in WebRTC
- Re: Low latency video in WebRTC
- [webrtc-pc] Pull Request: Update a receiver's set of remote streams when "a=msid" lines change.
- Re: Low latency video in WebRTC
- Re: Low latency video in WebRTC
- Re: Low latency video in WebRTC
- [webrtc-pc] Pull Request: Update copyright to encompass 2018
- [webrtc-pc] Pull Request: move handling of rtcpmuxpolicy from constructor to setConfiguration
- Re: Low latency video in WebRTC
- [webrtc-pc] Pull Request: Fix link to timeOrigin
- Re: Low latency video in WebRTC
Tuesday, 19 June 2018
Wednesday, 20 June 2018
Tuesday, 19 June 2018
- [webrtc-pc] Pull Request: Do "process removal of remote track" steps when stopping a transceiver.
- [webrtc-pc] Pull Request: Adding note about the dangers of RTCDataChannelInit.negotiated.
- [webrtc-pc] Pull Request: Adding note about potential consequences of stopping a transceiver.
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: RTT implementation = Real-Time Text implementation
- Weekly github digest (WebRTC WG specifications)
- Re: RTT implementation = Real-Time Text implementation
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- RE: Real Time Text implementation
- Slides for June 20 session
- Re: RTT implementation = Real-Time Text implementation
- Re: RTT implementation
- Re: WebRTC NV Use Cases
- RE: WebRTC NV Use Cases
- Re: RTT implementation
- Re: Face-to-Face Agenda Update
- Re: WebRTC NV Use Cases
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- RE: WebRTC NV Use Cases
- Re: RTT implementation
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Re: Hangouts (Re: Face-to-Face Agenda Update)
- Hangouts (Re: Face-to-Face Agenda Update)
- Re: Face-to-Face Agenda Update
- RE: RTT implementation
- Link to June 19 slide deck
- Re: Face-to-Face Agenda Update
- [webrtc-pc] Pull Request: Remove default identity provider
- [webrtc-pc] Pull Request: Clarify rejection rules for peerIdentity promise
- [webrtc-pc] Pull Request: Refactor description of identity validation in setRemote
- Re: WebRTC NV Use Cases
- Re: Face-to-Face Agenda Update
- [webrtc-pc] Pull Request: It's not that hard to run tidy
- [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
Monday, 18 June 2018
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- Re: To Stream or not to Stream
- Re: WebRTC NV Use Cases
- Re: WebRTC NV use case Mobility and cost of access
- Re: default components versus custom components
- Re: WebRTC NV use case Mobility and cost of access
- Re: default components versus custom components
- Re: To Stream or not to Stream
- Re: Logistics, F2F meeting
- Logistics, F2F meeting
- Re: Face-to-Face Agenda Update
- Re: Face-to-Face Agenda Update
- Re: To Stream or not to Stream
Sunday, 17 June 2018
Friday, 15 June 2018
- WebRTC NV use case Mobility and cost of access
- Re: To Stream or not to Stream
- Re: default components versus custom components
- RE: To Stream or not to Stream
- RE: default components versus custom components
- Re: To WASM or not to WASM (Re: Raw data API - 6 - Encoders/decoders)
- Re: To Stream or not to Stream (payload encryption use cases)
- Re: To Stream or not to Stream
- Re: Changes in editing team
- TPAC 2018 registration now open
- Name The Bird: An example Use machine learning use case for WebRTC
- Changes in editing team
- Re: To WASM or not to WASM (Re: Raw data API - 6 - Encoders/decoders)
- Re: To Stream or not to Stream (payload encryption use cases)
- Re: Raw data API - 6 - Encoders/decoders
- [webrtc-pc] Order of RTCRtpSendParameters.encodings is not described
- To WASM or not to WASM (Re: Raw data API - 6 - Encoders/decoders)
- [webrtc-pc] Pull Request: Unify stop transceiver steps.
- [webrtc-pc] pc.close() almost stops transceivers fully.
- RE: To Stream or not to Stream (payload encryption use cases)
- Re: To Stream or not to Stream
- Re: to stream the impossible stream (Knee deep in the wasm nonsense)
- RE: To Stream or not to Stream
Thursday, 14 June 2018
- [webrtc-pc] Pull Request: addTransceiver: check [[isClosed]]
- [webrtc-pc] Pull Request: Have addTransceiver throw on closed peer connection.
- [webrtc-pc] addTransceiver should throw on closed peer connection.
- Re: To Stream or not to Stream
- Re: To Stream or not to Stream
- RE: Raw data API - 6 - Encoders/decoders
- RE: To Stream or not to Stream
- Re: To Stream or not to Stream
- Re: To Stream or not to Stream
- Re: To Stream or not to Stream
- Re: Raw data API - 6 - Encoders/decoders
- Re: To Stream or not to Stream
- Re: To Stream or not to Stream
- [webrtc-stats] Pull Request: Added list of forbidden stats for isolated streams.
- Re: To Stream or not to Stream
- TPAC 2018 registration now open
- To Stream or not to Stream
- Re: Raw data API - 6 - Encoders/decoders
- Re: Raw data API - 6 - Encoders/decoders
- Re: Raw data API - 6 - Encoders/decoders
- Re: Raw data API - 6 - Encoders/decoders
- Re: Raw data API - 6 - Encoders/decoders
- [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: Raw data API - 6 - Encoders/decoders
- Re: Raw data API - 6 - Encoders/decoders
- Re: Raw data API - 6 - Encoders/decoders
Wednesday, 13 June 2018
Tuesday, 12 June 2018
- Weekly github digest (WebRTC WG specifications)
- Re: Change of Team Contact in Web Real-Time Communications WG
- Change of Team Contact in Web Real-Time Communications WG
- [webrtc-pc] Pull Request: Update web-platform-tests URLs
Monday, 11 June 2018
- Re: WebRTC NV Use Cases
- Use case summary
- Re: WebRTC NV Use Cases
- Re: WebRTC NV Use Cases
- [webrtc-pc] RTCPriorityType is not documented at all
- Reminder: F2F WEBRTC meeting - signup
Sunday, 10 June 2018
Saturday, 9 June 2018
- Re: webrtc nv and whatwg streams
- Re: webrtc nv and whatwg streams
- Re: webrtc nv and whatwg streams
- webrtc nv and whatwg streams
Friday, 8 June 2018
- Re: Revised agenda for F2F meeting in Stockholm June 19-20, 2018
- Revised agenda for F2F meeting in Stockholm June 19-20, 2018
- Revised agenda for F2F meeting in Stockholm June 19-20, 2018
Thursday, 7 June 2018
- [webrtc-pc] Pull Request: Have pc.close() set connection states to "closed".
- [webrtc-pc] Pull Request: Fire signalingstatechange later at end of SLD/SRD algorithm like other events
Wednesday, 6 June 2018
Tuesday, 5 June 2018
- Weekly github digest (WebRTC WG specifications)
- [webrtc-pc] Firing signalingstatechange early and synchronously invites trouble
Monday, 4 June 2018
- [webrtc-pc] Pull Request: Mark a couple of references as normative
- [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?