[webrtc-pc] Is an RTCIceServer with no urls useful?
[webrtc-pc] Pull Request: Made maxFramerate and scaleResolutionDownBy unsigned long (were: doub…
Re: [webrtc-pc] Provide changelog for the spec in new editors draft workflow
Re: [webrtc-pc] Events not bubbling
Closed: [webrtc-pc] Sort out unmute and BYE
Closed: [webrtc-pc] Refine error reporting for identity assertion
Closed: [webrtc-pc] Multiple SRDs may leave streams and tracks in unexpected state.
Re: [webrtc-pc] Multiple SRDs may leave streams and tracks in unexpected state.
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Partial removal of a track?
Re: [webrtc-pc] Handling of invalid values in RTCRtpSender.setParameters()
Re: [webrtc-pc] Failure of transmission of isolated stream
- Re: [webrtc-pc] Failure of transmission of isolated stream
- Re: [webrtc-pc] Failure of transmission of isolated stream
Closed: [webrtc-pc] No normative definition for "Determine if negotiation is needed to transmit withTrack in place of the sender's existing track" in replaceTrack
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: Fire track event in response to remote sender.setStreams() changes.
[webrtc-pc] Pull Request: Add warning to RTCRtpTransceiver.stop(). Stop rejected transceivers at SLD().
[webrtc-pc] Mandating [SecureContext]
Closed: [webrtc-pc] Unable to figure out which receivers are "active".
Re: [webrtc-pc] RTCRtpReceiver.getStreams() and RTCRtpSender.getStreams()
[webrtc-pc] Pull Request: RTCRtpReceiver.streams
- Re: [webrtc-pc] RTCRtpReceiver.streams
- Re: [webrtc-pc] RTCRtpReceiver.streams
- Re: [webrtc-pc] RTCRtpReceiver.streams
[webrtc-pc] Pull Request: RTCRtpSender.streamIds
- Re: [webrtc-pc] RTCRtpSender.streamIds
- Re: [webrtc-pc] RTCRtpSender.streamIds
- Re: [webrtc-pc] RTCRtpSender.streamIds
[webrtc-pc] Pull Request: throw NotSupportedError when mux policy does not match
[webrtc-pc] new commits pushed by alvestrand
Re: [webrtc-pc] Adding note about potential consequences of stopping a transceiver.
Closed: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
Closed: [webrtc-pc] Firing signalingstatechange early and synchronously invites trouble
[webrtc-pc] Pull Request: Clarify stats lifetimes and statsended event.
Re: [webrtc-pc] reducing audio packet rate while track is disabled
[webrtc-pc] Direction can get out of sync, blocking updates.
- Re: [webrtc-pc] Direction can get out of sync, blocking updates.
- Re: [webrtc-pc] Direction can get out of sync, blocking updates.
- Re: [webrtc-pc] Direction can get out of sync, blocking updates.
Re: [webrtc-pc] Should rollback fire addtrack/removetrack events?
Re: [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy is "require" and SDP is missing "a=rtcp-mux"
- Re: [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy is "require" and SDP is missing "a=rtcp-mux"
- Re: [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy is "require" and SDP is missing "a=rtcp-mux"
- Re: [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy is "require" and SDP is missing "a=rtcp-mux"
Closed: [webrtc-pc] Make promise rejection/enqueing consistent
[webrtc-pc] Pull Request: Reject promise at replaceTrack if TRX is stopped.
- Re: [webrtc-pc] Reject promise at replaceTrack if TRX is stopped.
- Re: [webrtc-pc] Reject promise at replaceTrack if TRX is stopped.
- Re: [webrtc-pc] Reject promise at replaceTrack if TRX is stopped.
- Re: [webrtc-pc] Reject promise at replaceTrack if TRX is stopped.
- Re: [webrtc-pc] Reject promise at replaceTrack if TRX is stopped.
[webrtc-pc] Promise should be rejected if transceiver is stopped
- Re: [webrtc-pc] Promise should be rejected if transceiver is stopped
- Re: [webrtc-pc] Promise should be rejected if transceiver is stopped
- Re: [webrtc-pc] Promise should be rejected if transceiver is stopped
- Closed: [webrtc-pc] Promise should be rejected if transceiver is stopped
- Re: [webrtc-pc] Promise should be rejected if transceiver is stopped
Re: [webrtc-pc] No normative definition for "Determine if negotiation is needed to transmit withTrack in place of the sender's existing track" in replaceTrack
[webrtc-pc] Cannot update associated remote streams for a track once added
- Re: [webrtc-pc] Cannot update associated remote streams for a track once added
- Re: [webrtc-pc] Cannot update associated remote streams for a track once added
- Re: [webrtc-pc] Cannot update associated remote streams for a track once added
- Re: [webrtc-pc] Cannot update associated remote streams for a track once added
- Re: [webrtc-pc] Cannot update associated remote streams for a track once added
- Re: [webrtc-pc] Cannot update associated remote streams for a track once added
- Closed: [webrtc-pc] Cannot update associated remote streams for a track once added
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] Identity needs to refer to track not stream
[webrtc-pc] Pull Request: Move isolated streams to identity spec
[webrtc-pc] RTCError suberrors for identity should move to identity spec
[webrtc-pc] Should / does the order of replaceTrack and direction matter?
- Re: [webrtc-pc] Should / does the order of replaceTrack and direction matter?
- Closed: [webrtc-pc] Should / does the order of replaceTrack and direction matter?
- Re: [webrtc-pc] Should / does the order of replaceTrack and direction matter?
- Re: [webrtc-pc] Should / does the order of replaceTrack and direction matter?
Closed: [webrtc-pc] Checks for negotiation-needed are underspecified when currentLocalDescription/currentRemoteDescription are not set
[webrtc-pc] Pull Request: Fix RTCRtpSender/Receiver.getCapabilities() return type
[webrtc-pc] Move [[WEBRTC-IDENTITY]] to its own repo
Closed: [webrtc-pc] RTCSctpTransportState "new" never used
Closed: [webrtc-pc] SctpTransportState transitions
[webrtc-pc] new commits pushed by alvestrand
Closed: [webrtc-pc] What should sender.getParameters().codecs return before negotiation?
[webrtc-pc] new commits pushed by alvestrand
Closed: [webrtc-pc] either full check certs or explain why it's not necessary (4.4.1.1 Constructor)
[webrtc-pc] new commits pushed by alvestrand
Re: [webrtc-pc] Update a receiver's set of remote streams when "a=msid" lines change.
- Re: [webrtc-pc] Update a receiver's set of remote streams when "a=msid" lines change.
- Re: [webrtc-pc] Update a receiver's set of remote streams when "a=msid" lines change.
- Re: [webrtc-pc] Update a receiver's set of remote streams when "a=msid" lines change.
[webrtc-pc] new commits pushed by alvestrand
Re: [webrtc-pc] It's not that hard to run tidy
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Split Identity into its own specification
[webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
- Re: [webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
- Re: [webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
- Re: [webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
- Re: [webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
- Re: [webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
- Re: [webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
- Re: [webrtc-pc] Rename sender.transport.transport to sender.transport.iceTransport?
Re: [webrtc-pc] What should sender.getParameters().codecs return before negotiation?
Re: [webrtc-pc] Splits Identity into its own specification.
[webrtc-pc] Move Isolated Streams from [[WEBRTC]] to [[WEBRTC-IDENTITY]]
- Re: [webrtc-pc] Move Isolated Streams from [[WEBRTC]] to [[WEBRTC-IDENTITY]]
- Closed: [webrtc-pc] Move Isolated Streams from [[WEBRTC]] to [[WEBRTC-IDENTITY]]
[webrtc-pc] Pull Request: RTCSctpTransportState cleanup
[webrtc-pc] Pull Request: What sender.getParameters().codecs returns before negotiation
Re: [webrtc-pc] pc.addTrack/removeTrack can be described in terms of Transceivers. This may be good for understanding them.
- Re: [webrtc-pc] pc.addTrack/removeTrack can be described in terms of Transceivers. This may be good for understanding them.
- Re: [webrtc-pc] pc.addTrack/removeTrack can be described in terms of Transceivers. This may be good for understanding them.
[webrtc-pc] Pull Request: Delete Example 14
- Re: [webrtc-pc] Delete Example 14
- Re: [webrtc-pc] Delete Example 14
- Re: [webrtc-pc] Delete Example 14
Re: [webrtc-pc] example 14: render before verifying the remote fingerprint?
[webrtc-pc] Pull Request: Explain why additional certificate checks are unnecessary
[webrtc-pc] Pull Request: "direction" and rtcrtpheaderextensionparameters
Re: [webrtc-pc] RTCIceTransport.component is at the wrong abstraction layer
Re: [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
[webrtc-stats] References to "objectDeleted" can be removed
[webrtc-stats] RTCIceCandidateStats.deleted can be removed
Re: [webrtc-pc] Section 4.3.1: operations queue and setDescription
Closed: [webrtc-pc] Section 5.2: transactionId restrictions
Re: [webrtc-pc] Make promise rejection/enqueing consistent
Closed: [webrtc-pc] Origin value for data channel message event
[webrtc-pc] new commits pushed by aboba
Re: [webrtc-pc] Do "process removal of remote track" steps when stopping a transceiver.
- Re: [webrtc-pc] Do "process removal of remote track" steps when stopping a transceiver.
- Re: [webrtc-pc] Do "process removal of remote track" steps when stopping a transceiver.
- Re: [webrtc-pc] Do "process removal of remote track" steps when stopping a transceiver.
Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
[webrtc-pc] Pull Request: RTCRtpReceiver.isActive added.
Re: [webrtc-pc] Section 5.2: transactionId restrictions
Re: [webrtc-pc] Checks for negotiation-needed are underspecified when currentLocalDescription/currentRemoteDescription are not set
- Re: [webrtc-pc] Checks for negotiation-needed are underspecified when currentLocalDescription/currentRemoteDescription are not set
- Re: [webrtc-pc] Checks for negotiation-needed are underspecified when currentLocalDescription/currentRemoteDescription are not set
Re: [webrtc-pc] Investigate stopping SRD and createAnswer
- Re: [webrtc-pc] Investigate stopping SRD and createAnswer
- Re: [webrtc-pc] Investigate stopping SRD and createAnswer
- Re: [webrtc-pc] Investigate stopping SRD and createAnswer
- Re: [webrtc-pc] Investigate stopping SRD and createAnswer
- Re: [webrtc-pc] Investigate stopping SRD and createAnswer
- Re: [webrtc-pc] Investigate stopping SRD and createAnswer
- Re: [webrtc-pc] Investigate stopping SRD and createAnswer
Re: [webrtc-pc] Origin value for data channel message event
- Re: [webrtc-pc] Origin value for data channel message event
- Re: [webrtc-pc] Origin value for data channel message event
Re: [webrtc-pc] either full check certs or explain why it's not necessary (4.4.1.1 Constructor)
Re: [webrtc-pc] Sort out unmute and BYE
Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
- Re: [webrtc-pc] does rtcrtpheaderextensionparameters need a direction?
Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
- Re: [webrtc-pc] Unable to figure out which receivers are "active".
Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface
- Re: [webrtc-pc] RTCPeerConnection incorrectly adds operation overload via a partial interface