[webrtc-pc] How do applications know a DataChannel's buffer capacity, so they can avoid filling it?
[webrtc-pc] Pull Request: Add link to iceRestart.
[webrtc-pc] new commits pushed by burnburn
[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
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
Re: [webrtc-stats] Privacy & Security self review
Closed: [webrtc-stats] What should `availableOutgoingBitrate`/`availableOutgoingBitrate` be for candidate pairs not in use?
Closed: [webrtc-stats] Design consideration for inactive SSRCs and inactive transports
Closed: [webrtc-stats] Remove availableIncomingBitrate?
[webrtc-stats] RTCMediaStreamTrackStats.concealedAudioSamples
[webrtc-stats] new commits pushed by vr000m
Closed: [webrtc-stats] RTCIceCandidatePairStats.writable/readable: redundant?
[webrtc-stats] RTCIceCandidatePairStats.lastResponseTimestamp
[webrtc-stats] Explain DomHighResTimestamp once in the introduction.
[webrtc-pc] Pull Request: Revert: pranswer as a "feature atrisk"
[webrtc-pc] Pull Request: FrozenArray, sequence and SameObject
- Re: [webrtc-pc] FrozenArray, sequence and SameObject
- Re: [webrtc-pc] FrozenArray, sequence and SameObject
- Re: [webrtc-pc] FrozenArray, sequence and SameObject
- Re: [webrtc-pc] FrozenArray, sequence and SameObject
- Re: [webrtc-pc] FrozenArray, sequence and SameObject
- Re: [webrtc-pc] FrozenArray, sequence and SameObject
[webrtc-pc] Pull Request: Remove space before commas
[webrtc-pc] Pull Request: move legacy callback definitions to legacy section
[webrtc-pc] "Callback definitions" section should go under "legacy interface extensions"
- Re: [webrtc-pc] "Callback definitions" section should go under "legacy interface extensions"
- Re: [webrtc-pc] "Callback definitions" section should go under "legacy interface extensions"
- Closed: [webrtc-pc] "Callback definitions" section should go under "legacy interface extensions"
[webrtc-pc] "Firing an RTCTrackEvent event named e" is never referenced
[webrtc-pc] Pull Request: Add a link to web-platform-tests to the top of the spec
- Re: [webrtc-pc] Add a link to web-platform-tests to the top of the spec
- Re: [webrtc-pc] Add a link to web-platform-tests to the top of the spec
[webrtc-pc] Pull Request: Call RTCDtlsFingerprint a dictionary, not an object
[webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
- Re: [webrtc-pc] Use [SameObject] for the FrozenArray<T> attributes that never change
[webrtc-pc] Pull Request: Adding more detail about RTCDataChannel.id's default value (null).
[webrtc-pc] Pull Request: Fire the "track" event from a queued task.
[webrtc-pc] "track" event fires while MediaStream has a partial list of tracks.
[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] Pull Request: Specify which encoding parameters can be set through sendEncodings.
Re: [webrtc-pc] Meta: auto-publish changes to the spec
[webrtc-pc] Pull Request: Split getContributingSources into two methods, for CSRCs and SSRCs.
- Re: [webrtc-pc] Split getContributingSources into two methods, for CSRCs and SSRCs.
- Re: [webrtc-pc] Split getContributingSources into two methods, for CSRCs and SSRCs.
Re: [webrtc-pc] Make RTCDataChannels Transferable
[webrtc-stats] new commits pushed by henbos
Closed: [webrtc-stats] RTCTransportStats packet counters
[webrtc-stats] new commits pushed by henbos
Closed: [webrtc-stats] RTCIceCandidatePairStats packet counters
[webrtc-stats] new commits pushed by henbos
Closed: [webrtc-stats] Stat for camera input framerate of local video tracks
[webrtc-pc] Define what the default RTCDataChannel id is
- Re: [webrtc-pc] Define what the default RTCDataChannel id is
- Re: [webrtc-pc] Define what the default RTCDataChannel id is
- Re: [webrtc-pc] Define what the default RTCDataChannel id is
- Re: [webrtc-pc] Define what the default RTCDataChannel id is
- Closed: [webrtc-pc] Define what the default RTCDataChannel id is
[webrtc-pc] Pull Request: Drop [TreatNullAs=EmptyString] for USVString
- Re: [webrtc-pc] Drop [TreatNullAs=EmptyString] for USVString
- Re: [webrtc-pc] Drop [TreatNullAs=EmptyString] for USVString
- Re: [webrtc-pc] Drop [TreatNullAs=EmptyString] for USVString
- Re: [webrtc-pc] Drop [TreatNullAs=EmptyString] for USVString
- Re: [webrtc-pc] Drop [TreatNullAs=EmptyString] for USVString
[webrtc-pc] Pull Request: Clarify that configuration.certificates remains undefined in the RTCPeerConnection constructor.
[webrtc-pc] Pull Request: examples: dont fiddle with srcObject if already set
- Re: [webrtc-pc] examples: dont fiddle with srcObject if already set
- Re: [webrtc-pc] examples: dont fiddle with srcObject if already set
- Re: [webrtc-pc] examples: dont fiddle with srcObject if already set
- Re: [webrtc-pc] examples: dont fiddle with srcObject if already set
[webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] example 13: getReceivers semantics
- Re: [webrtc-pc] 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)
- 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] Algorithm to mute/disable tracks is unclear
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Make legacy API optional to implement
Closed: [webrtc-pc] Section 12.2.4: Note
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: Section 12.2.4: Remove Note
[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] Should the spec describe addStream/onaddstream as legacy API?
- 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] Should the spec describe addStream/onaddstream as legacy API?
- 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] Should the spec describe addStream/onaddstream as legacy API?
- 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] Should the spec describe addStream/onaddstream as legacy API?
- 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] Should the spec describe addStream/onaddstream as legacy API?
- 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] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
Closed: [webrtc-pc] Mark Identity as feature at risk?
[webrtc-pc] Conformance section
[webrtc-pc] new commits pushed by stefhak
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Update for structured cloning changes in HTML
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] RTCRtpContributingSource.audioLevel not guaranteed to be in sync with audio playout
[webrtc-pc] Pull Request: RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() to return a compatible AlgorithmIdentifier.
Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
- Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
- Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
- Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
- Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
- Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
- Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats.
Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
- Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
- Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
- Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
- Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
- Re: [webrtc-stats] Added RTCInboundRTPStreamStats sample counters.
[webrtc-stats] Pull Request: RTCMediaStreamTrackStats: framesCaptured added.
[webrtc-stats] Pull Request: RTCIceCandidatePairStats: packetsSent/Received added.
[webrtc-stats] Pull Request: RTCTransportStats: packetsSent/Received added.
[webrtc-stats] Pull Request: RTCIceCandidatePairStats: Update writable, remove readable
[webrtc-pc] RTCCertificate.getAlgorithm() wording and serialization
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() wording and serialization
- Re: [webrtc-pc] RTCCertificate.getAlgorithm() wording and serialization
- Closed: [webrtc-pc] RTCCertificate.getAlgorithm() wording and serialization
[webrtc-pc] RTCCertificate.getAlgorithm for remote certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Re: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
- Closed: [webrtc-pc] RTCCertificate.getAlgorithm for implicitly generated local certificates
[webrtc-pc] Pull Request: Making legacy methods optional to implement.
- Re: [webrtc-pc] Making legacy methods optional to implement.
- Re: [webrtc-pc] Making legacy methods optional to implement.
[webrtc-pc] [TreatNullAs=EmptyString] is not allowed for USVString per Web IDL
- Re: [webrtc-pc] [TreatNullAs=EmptyString] is not allowed for USVString per Web IDL
- Re: [webrtc-pc] [TreatNullAs=EmptyString] is not allowed for USVString per Web IDL
- Re: [webrtc-pc] [TreatNullAs=EmptyString] is not allowed for USVString per Web IDL
- Closed: [webrtc-pc] [TreatNullAs=EmptyString] is not allowed for USVString per Web IDL
[webrtc-pc] RTCRtpContributingSource.getReceiver()
- Re: [webrtc-pc] RTCRtpContributingSource.getReceiver()
- Re: [webrtc-pc] RTCRtpContributingSource.getReceiver()
- Re: [webrtc-pc] RTCRtpContributingSource.getReceiver()
- Re: [webrtc-pc] RTCRtpContributingSource.getReceiver()
- Closed: [webrtc-pc] RTCRtpContributingSource.getReceiver()
[webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
- Re: [webrtc-pc] "getParameters" and "setParameters" need more thorough specification
Re: [webrtc-pc] Section 12.2.4: Note
[webrtc-pc] Pull Request: DTLS failures
[webrtc-pc] Pull Request: Mark Identity as a feature at risk
[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] Terminology around "setting" attributes may be incorrect
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] new commits pushed by aboba
Closed: [webrtc-pc] Diagram for RTCSignalingState includes "closed" state, which doesn't exist?
[webrtc-pc] new commits pushed by alvestrand
Re: [webrtc-pc] Make legacy API optional to implement
- Re: [webrtc-pc] Make legacy API optional to implement
- Re: [webrtc-pc] Make legacy API optional to implement
- Re: [webrtc-pc] Make legacy API optional to implement
Re: [webrtc-pc] Need to specify which members of the encodings in "sendEncodings" are actually used
- Re: [webrtc-pc] Need to specify which members of the encodings in "sendEncodings" are actually used
- Re: [webrtc-pc] Need to specify which members of the encodings in "sendEncodings" are actually used
Closed: [webrtc-pc] NetworkError event is not defined and might not be needed
[webrtc-pc] Describe update strategy on variables
- Re: [webrtc-pc] Describe update strategy on variables
- Re: [webrtc-pc] Describe update strategy on variables
- Re: [webrtc-pc] Describe update strategy on variables
[webrtc-pc] new commits pushed by alvestrand
Closed: [webrtc-pc] When exactly is an SSRC RTCRtpContributingSource object updated?
[webrtc-pc] new commits pushed by alvestrand
Closed: [webrtc-pc] get/setParameters does not have a parameter for packetization interval
[webrtc-pc] new commits pushed by alvestrand
Re: [webrtc-pc] RTCRtpContributingSource naming
- Re: [webrtc-pc] RTCRtpContributingSource naming
- Re: [webrtc-pc] RTCRtpContributingSource naming
- Re: [webrtc-pc] RTCRtpContributingSource naming
Re: [webrtc-pc] Handling of simulcast errors
- Re: [webrtc-pc] Handling of simulcast errors
- Re: [webrtc-pc] Handling of simulcast errors
- Re: [webrtc-pc] Handling of simulcast errors
[webrtc-pc] new commits pushed by aboba
[webrtc-stats] Pull Request: Adding RTCRTPContributingSourceStats stats report object.
Closed: [webrtc-stats] getStats example is outdated and redundant.
Closed: [webrtc-stats] example 8.2: calculating fraction lost vs fractionLost stat
[webrtc-stats] new commits pushed by vr000m
Re: [webrtc-pc] Eliminate NetworkError
Re: [webrtc-pc] DTLS failures
[webrtc-pc] Pull Request: Mark pranswer as a "feature atrisk"
- Re: [webrtc-pc] Mark pranswer as a "feature atrisk"
- Re: [webrtc-pc] Mark pranswer as a "feature atrisk"
- Re: [webrtc-pc] Mark pranswer as a "feature atrisk"
- Re: [webrtc-pc] Mark pranswer as a "feature atrisk"
- Re: [webrtc-pc] Mark pranswer as a "feature atrisk"
- Re: [webrtc-pc] Mark pranswer as a "feature atrisk"
[webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification
Re: [webrtc-pc] Attempt to update RTCRtpContributingSource objects at playout time.
- Re: [webrtc-pc] Attempt to update RTCRtpContributingSource objects at playout time.
- Re: [webrtc-pc] Attempt to update RTCRtpContributingSource objects at playout time.
- Re: [webrtc-pc] Attempt to update RTCRtpContributingSource objects at playout time.
- Re: [webrtc-pc] Attempt to update RTCRtpContributingSource objects at playout time.
- Re: [webrtc-pc] Attempt to update RTCRtpContributingSource objects at playout time.
[webrtc-pc] new commits pushed by aboba
[webrtc-pc] Pull Request: Adding configurable "ptime" member of RTCRtpEncodingParameters.
Re: [webrtc-stats] example 8.2: calculating fraction lost vs fractionLost stat
Closed: [webrtc-stats] Clarify if stat object's members can change after having been returned
Re: [webrtc-stats] getStats example is outdated and redundant.
Re: [webrtc-stats] RTCCodecStats needs `transportId` and `isRemote` to give it context
Closed: [webrtc-stats] mediaTrackId field missing a description
Re: [webrtc-stats] mediaTrackId field missing a description
Re: [webrtc-pc] Always update the RTCRtpContributingSource for SSRCs.
- Re: [webrtc-pc] Always update the RTCRtpContributingSource for SSRCs.
- Re: [webrtc-pc] Always update the RTCRtpContributingSource for SSRCs.
Re: [webrtc-pc] Add missing "closed" signaling state.
[webrtc-pc] Pull Request: Update structured cloning for recent changes to HTML
- Re: [webrtc-pc] Update structured cloning for recent changes to HTML
- Re: [webrtc-pc] Update structured cloning for recent changes to HTML
[webrtc-stats] Pull Request: Update example to match webrtc spec's + senders.getStats.
[webrtc-stats] Pull Request: New 'remote-inbound-rtp' + 'remote-outbound-rtp' (refactor out isRemote)
- Re: [webrtc-stats] New 'remote-inbound-rtp' + 'remote-outbound-rtp' (refactor out isRemote)
- Re: [webrtc-stats] New 'remote-inbound-rtp' + 'remote-outbound-rtp' (refactor out isRemote)
- Re: [webrtc-stats] Refactor out isRemote.
- Re: [webrtc-stats] Refactor out isRemote.
- Re: [webrtc-stats] Refactor out isRemote.
- Re: [webrtc-stats] Refactor out isRemote.
- Re: [webrtc-stats] Refactor out isRemote.
- Re: [webrtc-stats] Refactor out isRemote.
[webrtc-pc] Pull Request: Section 12.2.1.1: enum errorDetail definition
[webrtc-pc] Mark Provisional Answer as a feature at risk?
- Re: [webrtc-pc] Mark Provisional Answer as a feature at risk?
- Closed: [webrtc-pc] Mark Provisional Answer as a feature at risk?
Re: [webrtc-stats] Reuse of "inbound-rtp" and "outbound-rtp" for RTCP is confusing.
- Re: [webrtc-stats] Reuse of "inbound-rtp" and "outbound-rtp" for RTCP is confusing.
- Re: [webrtc-stats] Reuse of "inbound-rtp" and "outbound-rtp" for RTCP is confusing.
Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work
- Re: [webrtc-pc] strawman text to show how unverified media would work