public-webrtc@w3.org from June 2018 by subject

[webrtc-pc] addTransceiver should throw on closed peer connection.

[webrtc-pc] Can RTCStatsReport use a union type instead of object?

[webrtc-pc] detecting a remote ICE restart?

[webrtc-pc] does rtcrtpheaderextensionparameters need a direction?

[webrtc-pc] Firing signalingstatechange early and synchronously invites trouble

[webrtc-pc] Investigate stopping SRD and createAnswer

[webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?

[webrtc-pc] Legacy getRemoteStreams() in Unified Plan

[webrtc-pc] Order of RTCRtpSendParameters.encodings is not described

[webrtc-pc] pc.close() almost stops transceivers fully.

[webrtc-pc] Pull Request: Add note on use of partial interface for readability.

[webrtc-pc] Pull Request: Adding note about potential consequences of stopping a transceiver.

[webrtc-pc] Pull Request: Adding note about the dangers of RTCDataChannelInit.negotiated.

[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.

[webrtc-pc] Pull Request: addTransceiver: check [[isClosed]]

[webrtc-pc] Pull Request: Clarify rejection rules for peerIdentity promise

[webrtc-pc] Pull Request: Do "process removal of remote track" steps when stopping a transceiver.

[webrtc-pc] Pull Request: Fire signalingstatechange later at end of SLD/SRD algorithm like other events

[webrtc-pc] Pull Request: Fix link to timeOrigin

[webrtc-pc] Pull Request: Have addTransceiver throw on closed peer connection.

[webrtc-pc] Pull Request: Have pc.close() set connection states to "closed".

[webrtc-pc] Pull Request: It's not that hard to run tidy

[webrtc-pc] Pull Request: Mark a couple of references as normative

[webrtc-pc] Pull Request: move handling of rtcpmuxpolicy from constructor to setConfiguration

[webrtc-pc] Pull Request: Refactor description of identity validation in setRemote

[webrtc-pc] Pull Request: Remove default identity provider

[webrtc-pc] Pull Request: Splits Identity into its own specification.

[webrtc-pc] Pull Request: Unify stop transceiver steps.

[webrtc-pc] Pull Request: Update a receiver's set of remote streams when "a=msid" lines change.

[webrtc-pc] Pull Request: Update copyright to encompass 2018

[webrtc-pc] Pull Request: Update web-platform-tests URLs

[webrtc-pc] rename RTCIceCandidate.ip to address?

[webrtc-pc] RTCIceTransport.component is at the wrong abstraction layer

[webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface

[webrtc-pc] RTCPriorityType is not documented at all

[webrtc-pc] RTCRtpReceiver.getStreams() and RTCRtpSender.getStreams()

[webrtc-pc] Should remote tracks stop() when the PC is close()-ed?

[webrtc-pc] Split Identity into its own specification

[webrtc-pc] Unable to figure out which receivers are "active".

[webrtc-stats] Input/output resolution and audio energy

[webrtc-stats] Pull Request: Add TLS version and TLS group to RTCTransportStats

[webrtc-stats] Pull Request: Added list of forbidden stats for isolated streams.

[webrtc-stats] Pull Request: Clarify role of editors draft for CR transition request

Call for Exclusions: WebRTC 1.0: Real-time Communication Between Browsers

Change of Team Contact in Web Real-Time Communications WG

Changes in editing team

default components versus custom components

Face-to-Face Agenda Update

Hangouts (Re: Face-to-Face Agenda Update)

Link to June 19 slide deck

Logistics, F2F meeting

Low latency video in WebRTC

Name The Bird: An example Use machine learning use case for WebRTC

Raw data API - 3 - Encoded data

Raw data API - 6 - Encoders/decoders

Raw data APIs - 2 - Access to unencoded data

Real Time Text implementation

Reminder: F2F WEBRTC meeting - signup

Revised agenda for F2F meeting in Stockholm June 19-20, 2018

RTT implementation

RTT implementation = Real-Time Text implementation

Slides for June 20 session

Summary of decisions at the June 19-20 f2f

Summary of e2e encryption discussions

SV: Re: RTT implementation = Real-Time Text implementation

To Stream or not to Stream

To Stream or not to Stream (payload encryption use cases)

to stream the impossible stream (Knee deep in the wasm nonsense)

To WASM or not to WASM (Re: Raw data API - 6 - Encoders/decoders)

TPAC 2018 registration now open

Updated CR for WebRTC 1.0

Use case summary

Use cases / requirements for raw data access functions

WebRTC in workers

webrtc nv and whatwg streams

WebRTC NV use case Mobility and cost of access

WebRTC NV Use Cases

Weekly github digest (WebRTC WG specifications)

YouTube recordings of Stockholm meeting

Last message date: Saturday, 30 June 2018 12:30:46 UTC