[webrtc-pc] RTCDataChannelInit unknown member handling
[webrtc-pc] Pull Request: Correction for feature at risk
[webrtc-pc] new commits pushed by stefhak
Closed: [webrtc-pc] Editorial: Does throwing an error imply aborting the steps?
[webrtc-pc] new commits pushed by alvestrand
Closed: [webrtc-pc] Initial data channel state is inconsistent
[webrtc-pc] new commits pushed by burnburn
[webrtc-pc] Pull Request: Specify that "throw" aborts processing
Re: [webrtc-pc] Update structured cloning for recent changes to HTML
Re: [webrtc-stats] Add stat for RTTs between client and STUN/TURN server
Closed: [webrtc-stats] Add per layer stats for SVC
[webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- Re: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- Re: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- Re: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- Re: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- Re: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- Re: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
- Re: [webrtc-pc] Possible to lose data with a reliable, pre-negotiated data channel?
Re: [webrtc-pc] Data channel closing procedure
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: Fix Respec link error
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Recycling an m= section may not remove the old transceiver's remote track from its stream
[webrtc-pc] new commits pushed by aboba
Re: [webrtc-pc] Handling of invalid values in RTCRtpSender.setParameters()
[webrtc-pc] Pull Request: Add internal slots for descriptions.
[webrtc-pc] Pull Request: Mark simulcast reception as a feature at risk
[webrtc-pc] Pull Request: receiver.getParameters clarification
Re: [webrtc-pc] RTCRtpDecodingParameters
Re: [webrtc-pc] Add support for WebRTC Data Channel in Workers
Re: [webrtc-pc] What should receiver.getParameters() return?
Re: [webrtc-pc] What should sender.getParameters().codecs return before negotiation?
Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
- Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
- Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
- Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
- Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
- Re: [webrtc-pc] What happens when an answerer stops a transceiver that others are "bundled" on?
[webrtc-pc] RTCSctpTransportState "new" never used
[webrtc-stats] new commits pushed by vr000m
[webrtc-stats] Pull Request: Fixing some descriptions of ID references between stats objects.
[webrtc-stats] Identifier ambiguity in stat objects
- Re: [webrtc-stats] Identifier ambiguity in stat objects
- Closed: [webrtc-stats] Identifier ambiguity in stat objects
[webrtc-pc] Pull Request: Make RTCSctpTransport.maxChannels nullable & line breaks
Re: [webrtc-pc] Data channel minimum amount of streams supported
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] No way to add track with stream associations to a given transceiver
Closed: [webrtc-pc] Simulcast makes no sense for audio.
Closed: [webrtc-pc] replaceTrack algorithm lost some important text
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Data channel receive procedure missing?
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Data channel minimum amount of streams supported
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Not possible to tell how old `RTCRtpContributingSource.timestamp` is
Closed: [webrtc-pc] RTCRtpContributingSource.timestamp needs a clearer definition
[webrtc-pc] new commits pushed by taylor-b
Closed: [webrtc-pc] Should a signalingstatechange event be fired when closing a RTCPeerConnection?
Re: [webrtc-pc] Should a signalingstatechange event be fired when closing a RTCPeerConnection?
Re: [webrtc-pc] Codify refusing to generate an empty Offer
Closed: [webrtc-stats] Unable to distinguish "sender" stats if multiple senders are sending the same track
Re: [webrtc-stats] Clarify stats hierarchies
Re: [webrtc-stats] Work through implications of simulcast on the receiver side
[webrtc-stats] new commits pushed by alvestrand
Closed: [webrtc-stats] Lifetime of RTPStreamStats
Closed: [webrtc-stats] Consider the Reporting API as a stats export mechanism
Re: [webrtc-stats] Consider the Reporting API as a stats export mechanism
Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
[webrtc-stats] Pull Request: Define creation time for RTP objects
[webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities
- Re: [webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities
- Re: [webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities
- Re: [webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities
- Re: [webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities
- Closed: [webrtc-pc] sendEncodings in "create an RTPSender" should reflect platform capabilities
[webrtc-pc] localDescription, remoteDescription et al. need internal slots
- Re: [webrtc-pc] localDescription, remoteDescription et al. need internal slots
- Closed: [webrtc-pc] localDescription, remoteDescription et al. need internal slots
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
[webrtc-stats] add a graph showing the relationship of stats to the spec
- Re: [webrtc-stats] add a graph showing the relationship of stats to the spec
- Re: [webrtc-stats] add a graph showing the relationship of stats to the spec
- Re: [webrtc-stats] add a graph showing the relationship of stats to the spec
[webrtc-pc] Pull Request: Make RTCCertificate unusable by other origins
Re: [webrtc-pc] Editorial: Does throwing an error imply aborting the steps?
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] should RTCRtpSender.setParameters invalidate LastReturnedParameters?
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] new commits pushed by alvestrand
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
Re: [webrtc-pc] In-band negotiated channel should be open when dispatching
- Re: [webrtc-pc] In-band negotiated channel should be open when dispatching
- Re: [webrtc-pc] In-band negotiated channel should be open when dispatching
- Re: [webrtc-pc] In-band negotiated channel should be open when dispatching
Re: [webrtc-pc] Initial data channel state is inconsistent
[webrtc-pc] Pull Request: editorial: remove getParameters/setParameters ()
[webrtc-pc] Pull Request: Invalidate [[LastReturnedParameters]] in RTCRtpSender.setParameters
Re: [webrtc-stats] Write a "how to add more stats" guideline document
- Re: [webrtc-stats] Write a "how to add more stats" guideline document
- Re: [webrtc-stats] Write a "how to add more stats" guideline document
- Re: [webrtc-stats] Write a "how to add more stats" guideline document
[webrtc-stats] Should WebRTC be [SecureContext]
- Re: [webrtc-stats] Should WebRTC be [SecureContext]
- Re: [webrtc-stats] Should WebRTC be [SecureContext]
- Re: [webrtc-stats] Should WebRTC be [SecureContext]
- Closed: [webrtc-stats] Should WebRTC be [SecureContext]
- Re: [webrtc-stats] Should WebRTC be [SecureContext]
Re: [webrtc-stats] Add per layer stats for SVC
- Re: [webrtc-stats] Add per layer stats for SVC
- Re: [webrtc-stats] Add per layer stats for SVC
- Re: [webrtc-stats] Add per layer stats for SVC
[webrtc-stats] Add a "panel test" to track implementation status
- Re: [webrtc-stats] Add a "panel test" to track implementation status
- Re: [webrtc-stats] Add a "panel test" to track implementation status
[webrtc-pc] Pull Request: Fire events in SLD(answer) in direction rejection edge-case.
- Re: [webrtc-pc] Fire events in SLD(answer) in direction rejection edge-case.
- Re: [webrtc-pc] Fire events in SLD(answer) in direction rejection edge-case.
[webrtc-pc] Pull Request: Fix simulcast example
- Re: [webrtc-pc] Fix simulcast example
- Re: [webrtc-pc] Fix simulcast example
- Re: [webrtc-pc] Fix simulcast example
[webrtc-pc] Pull Request: Legacy methods do not throw exceptions.
[webrtc-pc] Pull Request: Fix typo s/sdpCauseCode/sctpCauseCode/
Closed: [webrtc-pc] Should a signalingstatechange event be fired when closing a RTCPeerConnection?
Closed: [webrtc-pc] Does RTCStatsReport need a toJSON method?
Re: [webrtc-pc] Does RTCStatsReport need a toJSON method?
[webrtc-pc] Pull Request: Improve replaceTrack prose; restores lost pre-negotiation behavior.
[webrtc-pc] Pull Request: Trim [[SendEncodings]] down to what user agent supports.
[webrtc-pc] Pull Request: Require some codec dictionary members
Re: [webrtc-pc] Treat rejected m= sections (port of 0) as having "inactive" direction.
Re: [webrtc-pc] Does direction matter for rejected m= sections?
Re: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
Closed: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate
- Re: [webrtc-pc] Allow to import existing certificate