Wednesday, 31 May 2017
- [webrtc-pc] Pull Request: Move Section 4.4 State Definitions before 4.3 RTCPeerConnection
- [webrtc-pc] Section 4.4: State Definitions
- [webrtc-pc] Pull Request: Section 4.2.6: remove informative sentences
- Re: [webrtc-pc] Section 6.4: Datachannel Garbage Collection
- [webrtc-pc] Pull Request: intertone gap maximum
- Re: [webrtc-pc] Section 7.2: infinite intertone gap
- Re: [webrtc-pc] Section 6.4: Datachannel Garbage Collection
- [webrtc-pc] Pull Request: WEBRTC-LOGINDONE
- Re: [webrtc-pc] Section 9.4: peerIdentity mismatches
- Re: [webrtc-pc] Section 10.4.1: target peerIdentity
- [webrtc-pc] Section 11.6: Diagram
- [webrtc-pc] Section 11: Examples
- [webrtc-pc] Section 10.4.1: target peerIdentity
- [webrtc-pc] Section 4.2.3 (createOffer)
- [webrtc-pc] Section 4.3.1
- [webrtc-pc] Section 4.2.6
- [webrtc-pc] pc.removeTrack(receiver) should throw an error.
- [webrtc-pc] Section 4.2.2
- [webrtc-pc] Events not bubbling
- [webrtc-pc] Inconsistencies in Asynchronous Task Queueing
- Re: [webrtc-pc] [respec-updater] New ReSpec release
- [webrtc-pc] Pull Request: [respec-updater] New ReSpec release
- Re: [webrtc-pc] ufrag vs usernameFragment
- [webrtc-pc] Missing steps on handling direction argument in addTransceiver
- Re: [webrtc-pc] Failure of transmission of isolated stream
- Re: [webrtc-stats] Need some way of getting an averaged audio level stat
Tuesday, 30 May 2017
- Re: [webrtc-pc] Need to resolve if we reference ICE or ICEbis
- [webrtc-pc] Pull Request: Remove "at-risk" marking from Identity
- Closed: [webrtc-pc] Need to resolve if we reference ICE or ICEbis
- Re: [webrtc-pc] Need to resolve if we reference STUn or STUnbis
- Re: [webrtc-pc] Spec has reference to WEBIDL-1 and WEBIDL
Monday, 29 May 2017
- Re: [webrtc-pc] Spec has reference to WEBIDL-1 and WEBIDL
- Re: [webrtc-pc] Spec has reference to WEBIDL-1 and WEBIDL
- [webrtc-pc] Spec has reference to WEBIDL-1 and WEBIDL
- [webrtc-pc] Need to resolve if we reference STUn or STUnbis
- [webrtc-pc] Failure of transmission of isolated stream
- [webrtc-pc] Clarity in section 9.7 example 11
- [webrtc-pc] Lifetime of pc.PeerIdentity
- [webrtc-pc] DTFM payout algorithm does not specify comma handling
- [webrtc-pc] Does insertDTMF append to or replace the current tone buffer
- [webrtc-pc] How to find what keyGenAlgorithm values the browser supports?
- [webrtc-pc] MTI specification of crypto for certs
- [webrtc-pc] Section 4.4.4 closed state
- [webrtc-pc] Error for when peer identity is wrong
- [webrtc-pc] lastOffer on the PC
- [webrtc-pc] invalid SDP for the state
- Re: [webrtc-pc] move "set a configuration" algorithm
- [webrtc-pc] Pull Request: clean up logic to support removal of RTCP mux "negotiated" value
- Re: [webrtc-pc] Need to identify if changes affect JSEP or MSID specs
- Re: [webrtc-pc] Rollback: a feature "at risk"?
- Re: [webrtc-pc] Race condition between createOffer and setIdentityProvider
- Re: [webrtc-pc] maximum bandwidth: TIAS or AS?
- Re: [webrtc-pc] move "set a configuration" algorithm
- [webrtc-pc] Pull Request: remove note about identity is at risk
- Re: [webrtc-pc] Add detailed steps for constructing RTCIceCandidate
Sunday, 28 May 2017
Friday, 26 May 2017
- Re: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
- Re: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
Thursday, 25 May 2017
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy is "require" and SDP is missing "a=rtcp-mux"
- Re: [webrtc-pc] RTP/RTCP mux -> RTCP mux
- Re: [webrtc-pc] RTP/RTCP mux -> RTCP mux
- Re: [webrtc-pc] maximum bandwidth: TIAS or AS?
- Re: [webrtc-pc] setParameters woes
- Re: [webrtc-pc] RTP/RTCP mux -> RTCP mux
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Can we directly link to WebRTC-Stats for RTCStatsType?
- Closed: [webrtc-pc] degradationPreference shouldn't have a default at the WebIDL level
- [webrtc-pc] new commits pushed by burnburn
- [webrtc-pc] new commits pushed by burnburn
- Closed: [webrtc-pc] RTCIceCandidate: component attribute missing?
- [webrtc-pc] new commits pushed by burnburn
- [webrtc-pc] new commits pushed by burnburn
- Closed: [webrtc-pc] Need to specify which members of the encodings in "sendEncodings" are actually used
- Re: [webrtc-pc] Removing WebIDL defaults for various RTP parameters.
- [webrtc-pc] RTCDtlsTransport: why is there no getLocalCertificates?
- [webrtc-pc] maximum bandwidth: TIAS or AS?
- Re: [webrtc-pc] setParameters woes
- [webrtc-pc] setParameters woes
- [webrtc-pc] Pull Request: RTP/RTCP mux -> RTCP mux
- [webrtc-pc] processing remote MediaStreamTracks -- stopping the transceiver to reject them
- [webrtc-pc] empty attribute descriptions in ice description
- Re: [webrtc-pc] RTCIceConnectionEventInit: url is nullable
- Re: [webrtc-pc] RTCIceConnectionEventInit: url is nullable
- Re: [webrtc-pc] Use data-cite for RTCStatsType
- [webrtc-pc] `parameters` not defined in `setParameters` algotrithm
- Re: [webrtc-pc] Removing WebIDL defaults for various RTP parameters.
- Re: [webrtc-stats] Need some way of getting an averaged audio level stat
- Re: [webrtc-stats] Need some way of getting an averaged audio level stat
- Re: [webrtc-stats] Need some way of getting an averaged audio level stat
- Re: [webrtc-stats] Need some way of getting an averaged audio level stat
- [webrtc-stats] new commits pushed by vr000m
Wednesday, 24 May 2017
- Re: [webrtc-pc] editorial: media api introduction
- Re: [webrtc-pc] which ice-tcp types will a browser emit?
- Re: [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy=negotiate is not implemented
- [webrtc-pc] editorial: move video cropping algorithm from rtpsender interface section
- [webrtc-pc] rtcsessiondescription: attributes are not mutable
- [webrtc-pc] rtp media api: when is a receiver created
- [webrtc-pc] editorial: media api introduction
- Re: [webrtc-pc] API to access certificate of remote side
- [webrtc-pc] Pull Request: RTCIceConnectionEventInit: url is nullable
- [webrtc-pc] which ice-tcp types will a browser emit?
- [webrtc-pc] [[associated MediaStreams]] and [[send encodings]] internal slots for RTCRtpSender are not used
- [webrtc-pc] legacy error handling
- Re: [webrtc-pc] API to access certificate of remote side
- [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy=negotiate is not implemented
- Re: [webrtc-pc] API to access certificate of remote side
- Closed: [webrtc-pc] API to access certificate of remote side
Tuesday, 23 May 2017
- Re: [webrtc-pc] API to access certificate of remote side
- [webrtc-pc] API to access certificate of remote side
- Re: [webrtc-stats] Adding audio level stat that can be used to compute averages.
- [webrtc-pc] new commits pushed by vivienlacourba
- Re: [webrtc-pc] Issue 1: Key shortening
Monday, 22 May 2017
- Re: [webrtc-pc] Issue 1: Key shortening
- [webrtc-pc] Pull Request: move "set a configuration" algorithm
- Re: [webrtc-pc] editorial: move "set a configuration" to operation section
- Re: [webrtc-pc] addIceCandidate may add ice candidate to the wrong remote description
- Re: [webrtc-pc] Add detailed steps for constructing RTCIceCandidate
- Re: [webrtc-pc] Issue 1: Key shortening
- [webrtc-pc] RTCPeerConnectionIceEvent constructor validation
Sunday, 21 May 2017
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- [webrtc-pc] legacy methods: when are they called?
- Re: [webrtc-pc] Removing WebIDL defaults for various RTP parameters.
Saturday, 20 May 2017
- Re: [webrtc-pc] Use data-cite for RTCStatsType
- [webrtc-pc] Pull Request: Use data-cite for RTCStatsType
Friday, 19 May 2017
- Re: [webrtc-pc] Issue 1: Key shortening
- Re: [webrtc-pc] addIceCandidate may add ice candidate to the wrong remote description
- Re: [webrtc-pc] Issue 1: Key shortening
- [webrtc-pc] Pull Request: Add detailed steps for constructing RTCIceCandidate
- Re: [webrtc-pc] Update for structured cloning changes in HTML
- Re: [webrtc-pc] Can we directly link to WebRTC-Stats for RTCStatsType?
- [webrtc-pc] Confusion on currentRemoteDescription.sdp need not match remoteDescription.sdp
- Re: [webrtc-pc] addIceCandidate may add ice candidate to the wrong remote description
- [webrtc-pc] addIceCandidate may add ice candidate to the wrong remote description
- Re: [webrtc-pc] Some JSEP "applying a description" steps can't occur in parallel.
- [webrtc-pc] Pull Request: Removing WebIDL defaults for various RTP parameters.
Thursday, 18 May 2017
- Re: [webrtc-pc] Issue 1: Key shortening
- [webrtc-pc] Pull Request: Units for maxFramerate
- Re: [webrtc-pc] RTCIceCandidate: how is extensibility handled?
- Re: [webrtc-pc] RTCIceCandidate: how is extensibility handled?
- Re: [webrtc-pc] Fix optional indicator for RTCPeerConnectionIceEventInit argument
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] editorial: add subsubsubsections to operation description?
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] editorial: p2p data transfer is a facet of video conferencing
- Re: [webrtc-pc] Throw error if data channel's buffer is filled, rather than closing.
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Fix optional indicator for RTCPeerConnectionIceEventInit argument
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Fix optional indicator for RTCPeerConnectionIceEventInit argument
- Re: [webrtc-pc] operation: add subsections
- Re: [webrtc-pc] intro: increase scope to general p2p
- Re: [webrtc-pc] intro: increase scope to general p2p
- Re: [webrtc-pc] Throw error if data channel's buffer is filled, rather than closing.
- Re: [webrtc-pc] Add bufferSize attribute to RTCDataChannel.
- Re: [webrtc-pc] Invalid RTCRtpTransceiverDirection already throws TypeError.
- Re: [webrtc-pc] RTCIceCandidate: add component
- Re: [webrtc-pc] Add more detail about how getParameters and setParameters work.
- Re: [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
- Re: [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
- Re: [webrtc-pc] Invalid value for maxBitrate
- Closed: [webrtc-pc] Invalid value for maxBitrate
Wednesday, 17 May 2017
- Re: [webrtc-pc] Invalid value for maxBitrate
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
- Re: [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- [webrtc-pc] Invalid value for maxBitrate
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- [webrtc-pc] Pull Request: operation: add subsections
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- [webrtc-pc] Pull Request: intro: increase scope to general p2p
- [webrtc-pc] Pull Request: reorder createOffer/createAnswer paragraphs
- [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
- [webrtc-pc] Race condition in enqueue an operation
- [webrtc-pc] Missing References to JSEP spec
- [webrtc-pc] Clarify addIceCandidate behavior when adding candidate after end of candidate
- Re: [webrtc-pc] addIceCandidate end of candidates woes
- Re: [webrtc-pc] editorial: createOffer description
- Re: [webrtc-pc] editorial: currentLocalDescription getting updates with candidates
- Re: [webrtc-pc] editorial: update the ice gathering state: firing icecandidate with null is a legacy hack
- Re: [webrtc-pc] editorial: add subsubsubsections to operation description?
Tuesday, 16 May 2017
- Re: [webrtc-pc] editorial: 4.3.1 Operation "settled" is not defined
- Re: [webrtc-pc] editorial: p2p data transfer is a facet of video conferencing
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Do we need getAlgorithm() at all?
- Re: [webrtc-pc] Do we need getAlgorithm() at all?
- Re: [webrtc-pc] addIceCandidate end of candidates woes
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
Monday, 15 May 2017
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- [webrtc-pc] Define the unit used for framerates and maxframerates
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- [webrtc-pc] new commits pushed by adam-be
- [webrtc-pc] new commits pushed by adam-be
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] addIceCandidate end of candidates woes
Sunday, 14 May 2017
- [webrtc-pc] addIceCandidate end of candidates woes
- [webrtc-pc] Can we directly link to WebRTC-Stats for RTCStatsType?
Saturday, 13 May 2017
Friday, 12 May 2017
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] Need to describe when ICE and DTLS transport objects are created/changed
- Re: [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- Re: [webrtc-pc] Update structured cloning for recent changes to HTML
- Re: [webrtc-stats] Audio/Video sync follow-up
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- [webrtc-pc] ufrag vs usernameFragment
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] Need to describe when ICE and DTLS transport objects are created/changed
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-stats] Audio/Video sync follow-up
- [webrtc-stats] Audio/Video sync follow-up
- [webrtc-pc] Pull Request: Throw error if data channel's buffer is filled, rather than closing.
- [webrtc-pc] Pull Request: Add bufferSize attribute to RTCDataChannel.
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
Thursday, 11 May 2017
- [webrtc-pc] Setting a remote description may cause discontinuity due to codec switching.
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- [webrtc-pc] transceiver.direction isn't initialized.
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- [webrtc-pc] Sending data channel messages > maxMessageSize
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- [webrtc-stats] Pull Request: Adding audio level stat that can be used to compute averages.
- Re: [webrtc-pc] audioLevel of tracks, both send and receive?
- [webrtc-stats] Need some way of getting an averaged audio level stat
- Re: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- [webrtc-pc] setDirection needs an internal slot and an algorithm.
- [webrtc-pc] Need to identify if changes affect JSEP or MSID specs
- Re: [webrtc-pc] Some JSEP "applying a description" steps can't occur in parallel.
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- Closed: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] Remove getAlgorithm()
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Related attributes should be updated at the same time (in the same microtask checkpoint?)
- Re: [webrtc-stats] adding total consent interval
- Re: [webrtc-stats] RTCIceCandidatePairStats.last[Request/Response]Timestamp added
- Re: [webrtc-stats] RTCMediaStreamTrackStats.concealedAudibleSamples added.
- Re: [webrtc-stats] adding total consent interval
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Closed: [webrtc-pc] what is the component for a icetransport of a datachannel?
- Re: [webrtc-stats] adding total consent interval
- Re: [webrtc-pc] Fix the type of iceCandidatePoolSize in description
- Re: [webrtc-pc] maxFramerate type double
- Re: [webrtc-pc] Expanding RTCPeerConnection introduction.
- Re: [webrtc-pc] Adding more detail to RTCIceTransportPolicy enum descriptions.
- [webrtc-stats] new commits pushed by henbos
- Closed: [webrtc-stats] Add stat to RTCTransportStats for ICE role (controlling or controlled)
- Re: [webrtc-stats] Stats to keep track of sync between audio and video
- Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
- Re: [webrtc-stats] Adds RTCTransportStats.iceRole
- [webrtc-pc] editorial: move "set a configuration" to operation section
- Re: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
- [webrtc-stats] new commits pushed by vr000m
- Closed: [webrtc-stats] Stats report for RTCRtpContributingSource objects
- Re: [webrtc-stats] Need DSCP information for outgoing RTP streams
- Re: [webrtc-stats] Adding RTCRTPContributingSourceStats stats report object.
- Re: [webrtc-pc] Update RTCCertificate ref to get serializer from WebIDL
- Re: [webrtc-pc] Update structured cloning for recent changes to HTML
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
Wednesday, 10 May 2017
- Re: [webrtc-pc] Stream IDs MUST be generated according to mediacapture-main, but webrtc-pc contradicts this
- Re: [webrtc-pc] Race condition between createOffer and setIdentityProvider
- [webrtc-pc] RTCPeerConnectionIceEvent parameter: RTCPeerConnectionIceEventInit eventInitDict is optional
- Re: [webrtc-pc] Stream IDs MUST be generated according to mediacapture-main, but webrtc-pc contradicts this
- Re: [webrtc-pc] RTCIceServer "represents a TURN server"
- [webrtc-pc] RTCIceServer "represents a TURN server"
- Re: [webrtc-pc] Stream IDs MUST be generated according to mediacapture-main, but webrtc-pc contradicts this
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- [webrtc-pc] Stream IDs MUST be generated according to mediacapture-main, but webrtc-pc contradicts this
- [webrtc-pc] iceCandidatePoolSize type mismatch (minor spec bug)
- Closed: [webrtc-stats] Should document what RTCRTPStreamStats metrics are valid when `isRemote` is true.
- Re: [webrtc-stats] Should document what RTCRTPStreamStats metrics are valid when `isRemote` is true.
- Re: [webrtc-pc] Race condition between createOffer and setIdentityProvider
- [webrtc-stats] Issues raised in TAG review
- Closed: [webrtc-stats] Reuse of "inbound-rtp" and "outbound-rtp" for RTCP is confusing.
- Re: [webrtc-stats] jitter buffer delay added to media stream tracks
- Re: [webrtc-stats] jitter buffer delay added to media stream tracks
- Re: [webrtc-stats] adding total consent interval
- Re: [webrtc-stats] RTCIceCandidatePairStats.last[Request/Response]Timestamp added
- Closed: [webrtc-stats] Need priority information for MediaStreamTracks
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
- Re: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
- [webrtc-stats] Pull Request: jitter buffer delay added to media stream tracks
- [webrtc-stats] Pull Request: Issue 132/mediastreamtrack priority
- [webrtc-stats] Pull Request: timestamps need for #61
- [webrtc-stats] Pull Request: Add paragraph about timestamp and reference DOMHighResTimeStamp
- Re: [webrtc-stats] Need DSCP information for outgoing RTP streams
- Re: [webrtc-stats] Need DSCP information for outgoing RTP streams
- [webrtc-stats] Pull Request: definition for 'framesPerSecond'
- [webrtc-stats] Pull Request: RTCMediaStreamTrackStats.voiceActivityFlag added.
- [webrtc-stats] Pull Request: RTCMediaStreamTrackStats.audioLevel: Reference RTCRtpSynchronizationSource
- [webrtc-stats] Pull Request: packetsRetransmitted and bytesRetransmitted to RTCSentRTPStreamStats
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- [webrtc-stats] Pull Request: Issue 178/packets discarded on send
- [webrtc-stats] new commits pushed by henbos
- Closed: [webrtc-stats] Stat for how many audio stream packets are expanded when packets are lost (and lost and the user is speaking)
- Re: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
- [webrtc-stats] new commits pushed by vr000m
- Closed: [webrtc-stats] RTCCodecStats needs `transportId` and `isRemote` to give it context
- Re: [webrtc-stats] Adding RTCRTPContributingSourceStats stats report object.
- Re: [webrtc-stats] Should document what RTCRTPStreamStats metrics are valid when `isRemote` is true.
- Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
- Re: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
- Re: [webrtc-pc] editorial: createOffer description
- [webrtc-pc] editorial: currentLocalDescription getting updates with candidates
- Re: [webrtc-pc] Race condition between createOffer and setIdentityProvider
Tuesday, 9 May 2017
- [webrtc-pc] update the ice gathering state: firing icecandidate with null is a legacy hack
- [webrtc-pc] editorial: add subsubsubsections to operation description?
- [webrtc-pc] editorial: 4.3.1 Operation "settled" is not defined
- [webrtc-pc] Pull Request: editorial: introduction: explain signaling process
- Re: [webrtc-pc] createAnswer: disambiguate blob
- [webrtc-pc] Pull Request: createAnswer: disambiguate blob
- [webrtc-pc] editorial: terminology of Blob and "blob of SDP"
- [webrtc-pc] editorial: p2p data transfer is a facet of video conferencing
- [webrtc-pc] Race condition between createOffer and setIdentityProvider
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
Monday, 8 May 2017
- Re: [webrtc-pc] RTCIceCandidate: component attribute missing?
- Re: [webrtc-pc] degradationPreference shouldn't have a default at the WebIDL level
- [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] RTCIceCandidate: component attribute missing?
- Re: [webrtc-pc] RTCIceCandidate: component attribute missing?
- Re: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Re: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Re: [webrtc-pc] degradationPreference shouldn't have a default at the WebIDL level
- Closed: [webrtc-pc] Are camelCase codec parameters useful at all?
- Re: [webrtc-pc] Are camelCase codec parameters useful at all?
- Re: [webrtc-pc] Need to describe when ICE and DTLS transport objects are created/changed
- Re: [webrtc-pc] Are camelCase codec parameters useful at all?
- [webrtc-pc] Pull Request: maxFramerate type double
- [webrtc-pc] new commits pushed by adam-be
- [webrtc-pc] new commits pushed by adam-be
- [webrtc-pc] new commits pushed by adam-be
- [webrtc-pc] Are camelCase codec parameters useful at all?
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
- [webrtc-pc] Need to describe when ICE and DTLS transport objects are created/changed
- [webrtc-pc] Some JSEP "applying a description" steps can't occur in parallel.
- Re: [webrtc-pc] Adding note about legacy `createAnswer` not supporting options dict.
- [webrtc-pc] new commits pushed by taylor-b
- [webrtc-pc] Pull Request: Adding more detail to RTCIceCandidatePolicy enum descriptions.
- [webrtc-pc] Pull Request: Expanding RTCPeerConnection introduction.
- [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
Sunday, 7 May 2017
- [webrtc-pc] degradationPreference shouldn't have a default at the WebIDL level
- Re: [webrtc-pc] Add paragraph about RtpContributingSources being updated simultaneously.
- [webrtc-pc] Pull Request: Adding note about legacy `createAnswer` not supporting options dict.
Saturday, 6 May 2017
Friday, 5 May 2017
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] RTCIceCandidate: component attribute missing?
- [webrtc-pc] RTP Media API section should describe how tracks for senders/receivers relate to each other.
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- [webrtc-pc] Pull Request: Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] RTCIceCandidate: component attribute missing?
- [webrtc-pc] RTCIceCandidate: component attribute missing?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
Thursday, 4 May 2017
- [webrtc-pc] Pull Request: Update RTCCertificate ref to get serializer from WebIDL
- [webrtc-pc] type of maxFramerate
- Re: [webrtc-pc] Add paragraph about RtpContributingSources being updated simultaneously.
- Re: [webrtc-pc] Do we need getAlgorithm() at all?
- Re: [webrtc-pc] Add paragraph about RtpContributingSources being updated simultaneously.
- [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need getAlgorithm() at all?
- [webrtc-pc] Pull Request: Remove getAlgorithm()
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] DTLS failures
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] RTCRtpContributingSource naming
- Re: [webrtc-pc] Do we need getAlgorithm() at all?
- [webrtc-pc] Do we need getAlgorithm() at all?
- Re: [webrtc-pc] DTLS failures
- [webrtc-pc] Section 12: Missing WebIDL in RTCError
- Re: [webrtc-pc] DTLS failures
- Re: [webrtc-pc] How do applications know a DataChannel's buffer capacity, so they can avoid filling it?
- Re: [webrtc-pc] Add link to iceRestart.
- Re: [webrtc-pc] DTLS failures
- Re: [webrtc-pc] Split getContributingSources into two methods, for CSRCs and SSRCs.
- Re: [webrtc-pc] FrozenArray, sequence and SameObject
- Re: [webrtc-pc] Handling encoding parameter errors
- Re: [webrtc-pc] Prepare status of the document for CR publication
- Re: [webrtc-pc] Fix optional indicator for RTCPeerConnectionIceEventInit argument
- Re: [webrtc-pc] Move Issue 1 text to a note
Wednesday, 3 May 2017
- [webrtc-pc] Pull Request: Move Issue 1 text to a note
- [webrtc-pc] Issue 1: Key shortening
- Re: [webrtc-pc] The "set an RTCSessionDescription" algorithm is unreferenced
- [webrtc-pc] The "set an RTCSessionDescription" algorithm is unreferenced
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-stats] RTCMediaStreamTrackStats.concealedAudioSamples
- Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
- Re: [webrtc-pc] Fix optional indicator for RTCPeerConnectionIceEventInit argument
Tuesday, 2 May 2017
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] Handling encoding parameter errors
- Re: [webrtc-pc] legacy createAnswer: support for answerOptions?
- [webrtc-pc] legacy createAnswer: support for answerOptions?
- Re: [webrtc-pc] Add more detail about how getParameters and setParameters work.
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] Specify an AllowUnverifiedMedia RTCConfiguration property
- Closed: [webrtc-pc] Specify an AllowUnverifiedMedia RTCConfiguration property
Monday, 1 May 2017
- Re: [webrtc-pc] Add more detail about how getParameters and setParameters work.
- [webrtc-pc] Pull Request: Handling encoding parameter errors
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- [webrtc-pc] Pull Request: Add paragraph about RtpContributingSources being updated simultaneously.
- Re: [webrtc-pc] Add more detail about how getParameters and setParameters work.