Saturday, 30 June 2018
Friday, 29 June 2018
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Splits Identity into its own specification.
- Re: [webrtc-pc] RTCRtpReceiver.getStreams() and RTCRtpSender.getStreams()
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Closed: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] RTCRtpReceiver.getStreams() and RTCRtpSender.getStreams()
- [webrtc-pc] RTCRtpReceiver.getStreams() and RTCRtpSender.getStreams()
- [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
Thursday, 28 June 2018
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Closed: [webrtc-pc] Update mandatory to implement stats based on stats dictionary renames
- Closed: [webrtc-pc] RTP Media API section should describe how tracks for senders/receivers relate to each other.
- [webrtc-pc] new commits pushed by taylor-b
- Closed: [webrtc-pc] Update for structured cloning changes in HTML
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Standard should provide some guidance for when an application should perform an ICE restart
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- [webrtc-pc] Investigate stopping SRD and createAnswer
- Closed: [webrtc-pc] Default identity provider
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] The same connection.peerIdentity promise can be resolved multiple times
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] setRemoteDescription should fail if target peer identity is set but no a=identity in SDP
- Closed: [webrtc-pc] pc.close() almost stops transceivers fully.
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] addTransceiver should throw on closed peer connection.
- Re: [webrtc-pc] RTCIceTransport.component is at the wrong abstraction layer
- Re: [webrtc-stats] Add TLS version and TLS group to RTCTransportStats
- Re: [webrtc-pc] It's not that hard to run tidy
- Re: [webrtc-pc] Refactor description of identity validation in setRemote
- Re: [webrtc-stats] Added list of forbidden stats for isolated streams.
- Re: [webrtc-pc] detecting a remote ICE restart?
Wednesday, 27 June 2018
- Re: [webrtc-pc] detecting a remote ICE restart?
- [webrtc-pc] detecting a remote ICE restart?
- Re: [webrtc-stats] Add TLS version and TLS group to RTCTransportStats
- Re: [webrtc-stats] Input/output resolution and audio energy
- [webrtc-stats] new commits pushed by alvestrand
- Closed: [webrtc-pc] Stats & isolated streams
- Re: [webrtc-stats] Add TLS version and TLS group to RTCTransportStats
- [webrtc-stats] Pull Request: Add TLS version and TLS group to RTCTransportStats
Tuesday, 26 June 2018
- [webrtc-stats] new commits pushed by dontcallmedom
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- [webrtc-stats] Pull Request: Clarify role of editors draft for CR transition request
Monday, 25 June 2018
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about potential consequences of stopping a transceiver.
- Re: [webrtc-pc] RTCIceTransport.component is at the wrong abstraction layer
- Re: [webrtc-pc] Should remote tracks stop() when the PC is close()-ed?
- Closed: [webrtc-pc] Should remote tracks stop() when the PC is close()-ed?
- Re: [webrtc-pc] Should remote tracks stop() when the PC is close()-ed?
- Re: [webrtc-pc] Should remote tracks stop() when the PC is close()-ed?
- [webrtc-pc] Should remote tracks stop() when the PC is close()-ed?
- [webrtc-pc] RTCIceTransport.component is at the wrong abstraction layer
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- Re: [webrtc-pc] Splits Identity into its own specification.
Sunday, 24 June 2018
- Re: [webrtc-pc] Splits Identity into its own specification.
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- Re: [webrtc-stats] Input/output resolution and audio energy
Friday, 22 June 2018
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- Re: [webrtc-pc] Splits Identity into its own specification.
- Re: [webrtc-pc] Splits Identity into its own specification.
- [webrtc-pc] Split Identity into its own specification
- [webrtc-pc] Pull Request: Splits Identity into its own specification.
Thursday, 21 June 2018
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- Re: [webrtc-pc] rename RTCIceCandidate.ip to address?
- [webrtc-stats] Input/output resolution and audio energy
- Closed: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Add a "panel test" to track implementation status
- Re: [webrtc-stats] Add a "panel test" to track implementation status
- [webrtc-pc] rename RTCIceCandidate.ip to address?
- Re: [webrtc-stats] Add a "panel test" to track implementation status
- Re: [webrtc-stats] Work through implications of simulcast on the receiver side
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-stats] Add stat for inputAudioLevel, before the audio filter
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
Wednesday, 20 June 2018
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Order of RTCRtpSendParameters.encodings is not described
- [webrtc-pc] Pull Request: Adding note about the relationship between tracks of senders/receivers.
- Re: [webrtc-pc] Standard should provide some guidance for when an application should perform an ICE restart
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Re: [webrtc-pc] Adding note about when ICE restarts are recommended.
- Closed: [webrtc-pc] Some JSEP "applying a description" steps can't occur in parallel.
- Re: [webrtc-pc] Some JSEP "applying a description" steps can't occur in parallel.
- [webrtc-pc] Pull Request: Adding note about when ICE restarts are recommended.
- [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: move handling of rtcpmuxpolicy from constructor to setConfiguration
- Closed: [webrtc-pc] processing remote MediaStreamTracks -- stopping the transceiver to reject them
- Re: [webrtc-pc] processing remote MediaStreamTracks -- stopping the transceiver to reject them
- [webrtc-pc] new commits pushed by alvestrand
- [webrtc-pc] Pull Request: Fix link to timeOrigin
- Re: [webrtc-pc] Can RTCStatsReport use a union type instead of object?
- Closed: [webrtc-pc] Can RTCStatsReport use a union type instead of object?
- Re: [webrtc-pc] Can RTCStatsReport use a union type instead of object?
- [webrtc-pc] Can RTCStatsReport use a union type instead of object?
- Re: [webrtc-pc] Adding note about the dangers of RTCDataChannelInit.negotiated.
Tuesday, 19 June 2018
- Re: [webrtc-pc] Treat rejected m= sections (port of 0) as having "inactive" direction.
- [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: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
- Re: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Closed: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Re: [webrtc-pc] Ambiguities with BUNDLE and ICE
- Closed: [webrtc-pc] Ambiguities with BUNDLE and ICE
- Re: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Re: [webrtc-pc] Lifetime of pc.PeerIdentity
- Re: [webrtc-pc] Specifying third party IdP for validating assertion
- [webrtc-pc] Pull Request: Remove default identity provider
- Re: [webrtc-pc] 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-pc] The same connection.peerIdentity promise can be resolved multiple times
- [webrtc-pc] Pull Request: It's not that hard to run tidy
- Re: [webrtc-pc] How is port number specified when verifying peer identity's assertion?
- Re: [webrtc-pc] Section 10.4.1: target peerIdentity
- Re: [webrtc-pc] Refine error reporting for identity assertion
- Re: [webrtc-pc] Handing SDP with more than one identity
- [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
Monday, 18 June 2018
Friday, 15 June 2018
- [webrtc-pc] Order of RTCRtpSendParameters.encodings is not described
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- [webrtc-pc] Pull Request: Unify stop transceiver steps.
- [webrtc-pc] pc.close() almost stops transceivers fully.
Thursday, 14 June 2018
- Re: [webrtc-pc] Have addTransceiver throw on closed peer connection.
- Re: [webrtc-pc] addTransceiver: check [[isClosed]]
- Re: [webrtc-pc] addTransceiver: check [[isClosed]]
- Re: [webrtc-pc] Have addTransceiver throw on closed peer connection.
- [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.
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by burnburn
- Re: [webrtc-pc] Stats & isolated streams
- [webrtc-stats] Pull Request: Added list of forbidden stats for isolated streams.
- [webrtc-pc] new commits pushed by alvestrand
- Re: [webrtc-pc] Fire signalingstatechange later at end of SLD/SRD algorithm like other events
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- Re: [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
- [webrtc-pc] Legacy getRemoteStreams() in Unified Plan
Wednesday, 13 June 2018
Tuesday, 12 June 2018
- Re: [webrtc-pc] Fire signalingstatechange later at end of SLD/SRD algorithm like other events
- [webrtc-pc] Pull Request: Update web-platform-tests URLs
Monday, 11 June 2018
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- Re: [webrtc-pc] RTCPriorityType is not documented at all
- [webrtc-pc] RTCPriorityType is not documented at all
Sunday, 10 June 2018
Thursday, 7 June 2018
- Re: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?
- Closed: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Data channel closing procedure
- [webrtc-pc] new commits pushed by taylor-b
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-stats] Fixing some descriptions of ID references between stats objects.
- Re: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?
- [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
- Closed: [webrtc-pc] Section 12: Missing sdpCauseCode in RTCError
- Closed: [webrtc-pc] legacy error handling
Tuesday, 5 June 2018
- Re: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?
- Re: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?
- [webrtc-pc] Firing signalingstatechange early and synchronously invites trouble
- Re: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?
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?
Friday, 1 June 2018
- Re: [webrtc-stats] add a graph showing the relationship of stats to the spec
- Re: [webrtc-pc] Allow to import existing certificate
- Closed: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Update mandatory to implement stats
- Closed: [webrtc-pc] What should receiver.getParameters().encodings[] return?
- Closed: [webrtc-pc] RTCRtpDecodingParameters
- Re: [webrtc-pc] RTCDataChannelInit unknown member handling
- Closed: [webrtc-pc] RTCDataChannelInit unknown member handling
- Re: [webrtc-pc] RTCDataChannelInit unknown member handling