Friday, 30 June 2017
- [webrtc-pc] RTCSctpTransport.maxMessageSize 0 case
- [webrtc-pc] Standard should provide some guidance for when an application should perform an ICE restart
- [webrtc-pc] Examples with dictionaries shouldn't use quotes around member names
- [webrtc-pc] Pull Request: SLD/SRD: Check if transceiver is stopped before setting currentDirection
- Re: [webrtc-pc] Editorial: Add 'Style Conventions' section to contributing guidelines
- [webrtc-pc] Pull Request: Editorial: Add 'Style Conventions' section to contributing guidelines
- Re: [webrtc-pc] update current*Description and pending*Description
- Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
- Re: [webrtc-pc] ResourceInUse exception is not defined
- Re: [webrtc-pc] editorial: currentLocalDescription getting updates with candidates
- [webrtc-pc] Pull Request: update current*Description and pending*Description
Thursday, 29 June 2017
- Re: [webrtc-pc] Handling of encoding/decoding errors
- Re: [webrtc-pc] move "set a configuration" algorithm
- Re: [webrtc-pc] move "set a configuration" algorithm
- Closed: [webrtc-pc] transceiver.currentDirection should be set to null when stopped
- [webrtc-pc] Pull Request: Set [[CurrentDirection]] for provisional answers.
- [webrtc-pc] new commits pushed by taylor-b
- Closed: [webrtc-pc] Clarify "cannot be applied at the media layer"
- Closed: [webrtc-pc] Editorial: negotiation-needed algorithm returns a string
- Closed: [webrtc-pc] when voiceActivityDetection is false, browser must send media even if it is silent
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Add RTCDataChannelPriority enum and step to initialize data channel priority
- [webrtc-pc] new commits pushed by adam-be
- [webrtc-pc] new commits pushed by adam-be
- Closed: [webrtc-pc] Section 8.2: Null selector properly handled by getStats?
- Closed: [webrtc-pc] rtcsessiondescription: attributes are not mutable
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] which ice-tcp types will a browser emit?
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Editorial: Assume default values for optional dictionaries in spec text
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-stats] Why no Jitter for RTCOutboundRTPAudioStream?
- Re: [webrtc-pc] Don't fire ONN on removeTrack() if sender.track is already null.
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] We shouldn't rely on the public API to access objects in the specification
- Re: [webrtc-pc] Standardize how internal slots are named and linked to.
- Re: [webrtc-pc] add type error for unknown ice server schema
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- Re: [webrtc-pc] We shouldn't rely on the public API to access objects in the specification
- Re: [webrtc-pc] Don't fire ONN on removeTrack() if sender.track is already null.
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- Re: [webrtc-pc] getstats: improve selector definiton
- Re: [webrtc-pc] getstats: improve selector definiton
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- [webrtc-pc] Handle transceiver stopped between creation and description set
- Re: [webrtc-pc] transceiver.currentDirection should be set to null when stopped
- [webrtc-pc] Pull Request: RTCRtpTransceiver: Set currentDirection to null when stopping
- [webrtc-pc] We shouldn't rely on the public API to access objects in the specification
- Re: [webrtc-pc] Missing definition for obtaining list of all RTCIceTransport and RTCDtlsTransport
- Re: [webrtc-pc] Don't fire ONN on removeTrack() if sender.track is already null.
Wednesday, 28 June 2017
- Re: [webrtc-pc] Clarify offerToReceiveAudio and offerToReceiveVideo in renegotiation
- [webrtc-pc] Pull Request: Don't fire ONN on removeTrack() if sender.track is already null.
- Re: [webrtc-pc] ResourceInUse exception is not defined
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] add type error for unknown ice server schema
- [webrtc-pc] Pull Request: add type error for unknown ice server schema
- Re: [webrtc-pc] Clarify offerToReceiveAudio and offerToReceiveVideo in renegotiation
- [webrtc-pc] new commits pushed by dontcallmedom
- [webrtc-pc] Pull Request: addTranscevier: Assume defalut dictionary
- [webrtc-pc] Pull Request: Use links on body of spec consistent with links in references
- [webrtc-pc] Pull Request: Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
Tuesday, 27 June 2017
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] rtciceserver: fix represents a turn server
- Re: [webrtc-pc] rtciceserver: fix represents a turn server
- Re: [webrtc-stats] Why no Jitter for RTCOutboundRTPAudioStream?
- Re: [webrtc-pc] rtcsessiondescription: attributes are not mutable
Monday, 26 June 2017
- [webrtc-pc] Pull Request: ice-tcp: add note about ice-tcp types a UA will gather
- Re: [webrtc-pc] RTCPeerConnection.close: release transceiver before ICE transport
- [webrtc-pc] Pull Request: getstats: improve selector definiton
- Re: [webrtc-pc] RTCIceServer "represents a TURN server"
- Re: [webrtc-pc] Handling of encoding/decoding errors
- Re: [webrtc-pc] transceiver.currentDirection should be set to null when stopped
- Re: [webrtc-pc] RTCRtpTransceiver setDirection() should throw InvalidStateError if transceiver is stopped
- [webrtc-pc] What happens if you set a remote description with two tracks with the same ID?
- Re: [webrtc-pc] Standardize how internal slots are named and linked to.
- Re: [webrtc-pc] Standardize how internal slots are named and linked to.
- Re: [webrtc-pc] Section 4.4.4 closed state
- Re: [webrtc-pc] RTCPeerConnection.close: release transceiver before ICE transport
- Re: [webrtc-pc] Add RTCDataChannelPriority enum and step to initialize data channel priority
- Re: [webrtc-pc] What should happen if a DataChannel "OPEN" message uses priority other than one of the recommended values?
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Standardize how internal slots are named and linked to.
Sunday, 25 June 2017
Friday, 23 June 2017
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Add RTCDataChannelPriority enum and step to initialize data channel priority
- [webrtc-pc] What should happen if a DataChannel "OPEN" message uses priority other than one of the recommended values?
- Re: [webrtc-pc] When is ICE gathering triggered?
- Re: [webrtc-pc] When is ICE gathering triggered?
- Re: [webrtc-pc] Race condition in enqueue an operation
- Closed: [webrtc-pc] Missing References to JSEP spec
- Re: [webrtc-pc] Missing References to JSEP spec
- Re: [webrtc-pc] Add reference to JSEP that setLocalDescription triggers ICE gathering
- [webrtc-pc] When is ICE gathering triggered?
- Re: [webrtc-pc] Queue enqueued operation as task if length of operations is 1
- [webrtc-pc] Pull Request: Clarify enqueue is acted on specific connection's operation queue
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is false (in-band negotiation)?
Thursday, 22 June 2017
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Editorial: consistent Internal slot names e.g. [[IsClosed]] vs [[isClosed]]?
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] Race condition in enqueue an operation
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is true?
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is true?
- Re: [webrtc-pc] move "set a configuration" algorithm
- Re: [webrtc-pc] Improve description for enqueing operations
- Re: [webrtc-pc] Standardize how internal slots are named and linked to.
- Re: [webrtc-pc] Improve description for enqueing operations
- Re: [webrtc-pc] Standardize how internal slots are named and linked to.
- Re: [webrtc-pc] move "set a configuration" algorithm
- Re: [webrtc-pc] When is the dtmf attribute in RTCRtpSender be set?
- [webrtc-pc] WebIDL serializer has been deprecated in favor of toJSON operation
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] Clarify offerToReceiveAudio and offerToReceiveVideo in renegotiation
- Re: [webrtc-pc] Setting a remote description may cause discontinuity due to codec switching.
- [webrtc-pc] RTCRtpTransceiver setDirection() should throw InvalidStateError error if transceiver is stopped
- [webrtc-pc] transceiver.currentDirection should be set to null when stopped
- Re: [webrtc-pc] RTCError should have WebIDL-friendly definition
- Closed: [webrtc-pc] RTCError should have WebIDL-friendly definition
- [webrtc-pc] RTCError should have WebIDL-friendly definition
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is true?
- [webrtc-pc] When is the dtmf attribute in RTCRtpSender be set?
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is true?
Wednesday, 21 June 2017
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is true?
- Re: [webrtc-pc] Editorial: consistent Internal slot names e.g. [[IsClosed]] vs [[isClosed]]?
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] RTCPeerConnection.close: release transceiver before ICE transport
- Re: [webrtc-pc] `addTransceiver(track)` doesn't mention checking the origin of track
- [webrtc-pc] Pull Request: RTCPeerConnection.close: release transceiver before ICE transport
- Re: [webrtc-pc] `addTransceiver(track)` doesn't mention checking the origin of track
- [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is true?
- [webrtc-pc] ResourceInUse exception is not defined
Tuesday, 20 June 2017
- [webrtc-stats] Why no Jitter for RTCOutboundRTPAudioStream?
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- Re: [webrtc-pc] move "set a configuration" algorithm
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Make promise rejection/enqueing consistent
- [webrtc-pc] Pull Request: Fix a link to RFC 7635.
- Re: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Re: [webrtc-pc] Section 5.2: transactionId restrictions
- Re: [webrtc-pc] [[associated MediaStreams]] internal slot for RTCRtpSender is not used
- Re: [webrtc-pc] Section 12: Missing WebIDL in RTCError
- [webrtc-pc] Pull Request: when voiceActivityDetection is false browser sends media
- Re: [webrtc-pc] when voiceActivityDetection is false, browser must send media even if it is silent
- Re: [webrtc-pc] Remove condition "If channel's underlying data transport is not established yet, then abort these steps" from send()
- Closed: [webrtc-pc] Setting session description section should have step to set transceiver currentDirection
- Re: [webrtc-pc] Setting session description section should have step to set transceiver currentDirection
- Re: [webrtc-pc] [[associated MediaStreams]] internal slot for RTCRtpSender is not used
Monday, 19 June 2017
- Re: [webrtc-pc] In data channel send(), remove the condition "If channel's underlying data transport is not established yet, then abort these steps"
- Re: [webrtc-pc] Remove condition "If channel's underlying data transport is not established yet, then abort these steps" from send()
- Re: [webrtc-pc] Remove condition "If channel's underlying data transport is not established yet, then abort these steps" from send()
- Re: [webrtc-pc] In data channel send(), remove unneeded conditions
- Re: [webrtc-pc] In data channel send(), remove the condition "If channel's underlying data transport is not established yet, then abort these steps"
- Re: [webrtc-pc] In data channel send(), remove the condition "If channel's underlying data transport is not established yet, then abort these steps"
- Re: [webrtc-pc] Section 12: Missing WebIDL in RTCError
- [webrtc-pc] Pull Request: Use true and false instead of "true" and "false".
- Re: [webrtc-pc] [[associated MediaStreams]] and [[send encodings]] internal slots for RTCRtpSender are not used
- [webrtc-pc] Pull Request: label/protocol length restriction
- Re: [webrtc-pc] Section 6.1: label length
- Re: [webrtc-pc] Setting a pranswer should change RTCRtpTransceiver's currentDirection
- Re: [webrtc-pc] removeTrack changes transceiver.direction based on on currentDirection not direction
- Re: [webrtc-pc] Setting session description section should have step to set transceiver currentDirection
- Closed: [webrtc-stats] RTCPeerConnectionStats: should they contain a link to transports?
- Re: [webrtc-stats] RTCPeerConnectionStats: should they contain a link to transports?
- Closed: [webrtc-stats] Stat for retransmitted bytes
- Re: [webrtc-stats] RTCPeerConnectionStats: should they contain a link to transports?
- Re: [webrtc-stats] RTCPeerConnectionStats: should they contain a link to transports?
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
Sunday, 18 June 2017
- Re: [webrtc-pc] Check crypto suites
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-stats] Fix markup issues
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- Re: [webrtc-pc] MTI specification of crypto for certs
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- Re: [webrtc-pc] Need to describe when ICE and DTLS transport objects are created/changed
- Re: [webrtc-pc] Missing initialization of priority attribute when firing datachannel event
- Re: [webrtc-pc] Missing initialization of priority attribute when firing datachannel event
- Re: [webrtc-pc] Origin value for data channel message event
- Re: [webrtc-pc] Inconsistent behaviors of addTrack compared to addTranseiver and sender.replaceTrack
- Closed: [webrtc-pc] Inconsistent behaviors of addTrack compared to addTranseiver and sender.replaceTrack
- [webrtc-pc] `addTransceiver(track)` doesn't mention checking the origin of track
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Closed: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] When ICE restarts results in connection a new endpoint
- [webrtc-pc] When ICE restarts results in connection a new endpoint
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] Check crypto suites
- Closed: [webrtc-pc] Check crypto suites
- [webrtc-pc] Pull Request: Remove "cannot be applied at the media layer"
- Re: [webrtc-pc] MTI specification of crypto for certs
- Re: [webrtc-pc] Check crypto suites
- [webrtc-pc] Pull Request: In data channel send(), remove unneeded conditions
Saturday, 17 June 2017
- Re: [webrtc-pc] Sending data channel messages > maxMessageSize
- [webrtc-pc] Editorial: negotiation-needed algorithm returns a string
Friday, 16 June 2017
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction.
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction.
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- [webrtc-pc] Pull Request: Add/remove remote tracks from msid streams based on direction (rebased)
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction.
- Re: [webrtc-pc] close sctp.transport in pc.close()
- [webrtc-pc] Pull Request: close sctp.transport in pc.close()
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-stats] RTCPeerConnectionStats: should they contain a link to transports?
- [webrtc-pc] Pull Request: Add RTCDataChannelPriority enum and step to initialize data channel priority
- [webrtc-stats] RTCPeerConnectionStats: should they contain a link to transports?
- [webrtc-pc] Pull Request: Add reference to JSEP that setLocalDescription triggers ICE gathering
- Re: [webrtc-pc] RTCIceCandidate and candidate string parsing requirements
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- [webrtc-pc] Pull Request: Improve description for enqueing operations
- Re: [webrtc-pc] In data channel send(), remove the condition "If channel's underlying data transport is not established yet, then abort these steps"
- Closed: [webrtc-pc] Improve description for semantics of updating bufferedAmount
- Re: [webrtc-pc] Improve description for semantics of updating bufferedAmount
- [webrtc-pc] In data channel send(), remove the condition "If channel's underlying data transport is not established yet, then abort these steps"
- Closed: [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- Re: [webrtc-pc] Lack of validation in RTCIceCandidate constructor
- Re: [webrtc-pc] Relating RTCDtlsTransportState to RTCIceTransportState and RTCIceGathererState
- Closed: [webrtc-pc] Relating RTCDtlsTransportState to RTCIceTransportState and RTCIceGathererState
Thursday, 15 June 2017
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- [webrtc-pc] Pull Request: Standardize how internal slots are named and linked to.
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Start integrating direction into 'create RTCRtpTransceiver' algorithm
- [webrtc-pc] Setting a pranswer should change RTCRtpTransceiver's currentDirection
- [webrtc-pc] Need to define what an "associated" transceiver is.
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Start integrating direction into 'create RTCRtpTransceiver' algorithm
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
- [webrtc-pc] Pull Request: Add reference to RFC 5245
- Closed: [webrtc-pc] Section 4.4: State Definitions
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] DTMF playout algorithm does not specify comma handling
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] DTLS failures
- Closed: [webrtc-pc] empty attribute descriptions in ice description
- Closed: [webrtc-pc] invalid SDP for the state
- Closed: [webrtc-pc] lastOffer on the PC
- Closed: [webrtc-pc] Check for state when "setting an RTCSessionDescription description"
- Closed: [webrtc-pc] Section 6.2: when data cannot be sent
- Closed: [webrtc-pc] createOffer(): Built-in certificate behavior
- Closed: [webrtc-pc] setLocalDescription algorithm for rejecting modification
- Closed: [webrtc-pc] Don't update state if setLocalD is called with bogus input
- Closed: [webrtc-pc] track event description is obsolete since transceivers
- Closed: [webrtc-pc] RTCDtlsTransport and RTCIceTransport should inherit from EventTarget
- Closed: [webrtc-pc] Public accessor for isClosed
- Closed: [webrtc-pc] RTCRtpSender replaceTrack should accept nullable argument in WebIDL definition
- [webrtc-pc] new commits pushed by burnburn
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by taylor-b
- Re: [webrtc-pc] clean up logic to support removal of RTCP mux "negotiated" value
- Re: [webrtc-pc] move "set a configuration" algorithm
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Setting session description section should have step to set transceiver currentDirection
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by burnburn
- 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
- Re: [webrtc-stats] Fix markup issues
- Re: [webrtc-stats] Fix markup issues
- [webrtc-stats] Pull Request: Fix markup issues
- 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] Handling encoding parameter errors
- Re: [webrtc-pc] Remove paragraph about removeTrack causing track to be ended remotely.
- Re: [webrtc-pc] Throw error if data channel's buffer is filled, rather than closing.
- Re: [webrtc-pc] Add detailed steps for constructing RTCIceCandidate
- Re: [webrtc-pc] Move Section 4.4 State Definitions before 4.3 RTCPeerConnection
- Re: [webrtc-pc] Start integrating direction into 'create RTCRtpTransceiver' algorithm
- Re: [webrtc-pc] Algorithm for rejecting modification
- Re: [webrtc-pc] Built-in certificate behavior
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] Clarification: insertDTMF replaces the current tone buffer
- Re: [webrtc-pc] empty attribute descriptions in ice description
- [webrtc-pc] Setting session description section should have step to set transceiver currentDirection
- Re: [webrtc-pc] RTCDataChannel: Use internal slots and specify default values at one location
- Re: [webrtc-pc] pc.close() sets pc.signalingState to "closed"
- Re: [webrtc-pc] Add reference to RFC 5245
- Re: [webrtc-pc] DTMF playout algorithm for comma
- Re: [webrtc-pc] RTCDtlsTransport and RTCIceTransport inherit from EventTarget
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] Throw error if data channel's buffer is filled, rather than closing.
- [webrtc-pc] removeTrack changes transceiver.direction based on on currentDirection not direction
- 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
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- [webrtc-pc] No normative definition for "Determine if negotiation is needed to transmit withTrack in place of the sender's existing track" in replaceTrack
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] Inconsistent behaviors of addTrack compared to addTranseiver and sender.replaceTrack
- Re: [webrtc-pc] Inconsistent behaviors of addTrack compared to addTranseiver and sender.replaceTrack
- [webrtc-pc] Pull Request: replaceTrack should accept nullable argument
- [webrtc-pc] RTCRtpSender replaceTrack should accept nullable argument in WebIDL definition
- [webrtc-pc] Inconsistent behaviors of addTrack compared to addTranseiver and sender.replaceTrack
- Re: [webrtc-pc] DTMF playout algorithm for comma
Wednesday, 14 June 2017
- Re: [webrtc-pc] Throw error if data channel's buffer is filled, rather than closing.
- Re: [webrtc-pc] DTMF playout algorithm for comma
- Closed: [webrtc-stats] Packets or frames discarded on send?
- [webrtc-stats] new commits pushed by vr000m
- [webrtc-stats] Pull Request: ready for releasing new version 201706
- [webrtc-stats] Pull Request: changelog updated for new release
- Closed: [webrtc-stats] Implementing the Circuit Breaker based on StatsAPI
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-pc] Review issues reported to last in September
- [webrtc-stats] new commits pushed by vr000m
- Closed: [webrtc-stats] Need some way of getting an averaged audio level stat
- Re: [webrtc-pc] Enqueue an operation vs queue a task
- Re: [webrtc-pc] Review issues reported to last in September
- Re: [webrtc-pc] Section 4.3.3: optional methods
- Re: [webrtc-pc] Section 9.4: peerIdentity mismatches
- Re: [webrtc-pc] Section 9.4: peerIdentity mismatches
- Re: [webrtc-pc] Clarify "cannot be applied at the media layer"
- Re: [webrtc-pc] Make promise rejection/enqueing consistent
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] Enqueue an operation vs queue a task
- [webrtc-pc] new commits pushed by adam-be
- Re: [webrtc-stats] Adding audio level stat that can be used to compute averages.
- Re: [webrtc-pc] iceGatheringState on connection with data channel only before setRemoteDescription(answer) is set
Tuesday, 13 June 2017
- [webrtc-pc] Pull Request: Update RTCTrackEvent text.
- Re: [webrtc-stats] Adding audio level stat that can be used to compute averages.
- Re: [webrtc-pc] Section 6.4: Datachannel Garbage Collection
- Re: [webrtc-pc] close() method should close sctp transport and data channels
- Re: [webrtc-pc] pc.close() sets pc.signalingState to "closed"
- Closed: [webrtc-pc] Section 4.2.3 (createOffer)
- Re: [webrtc-pc] Section 4.2.3 (createOffer)
- [webrtc-pc] Pull Request: RTCDtlsTransport and RTCIceTransport inherit from EventTarget
- Re: [webrtc-pc] iceGatheringState on connection with data channel only before setRemoteDescription(answer) is set
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] Origin value for data channel message event
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- Re: [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- [webrtc-pc] offerToReceive* legacy behaviour spec does not match the behaviour of legacy implementations
- [webrtc-pc] iceGatheringState on connection with data channel only before setRemoteDescription(answer) is set
- Re: [webrtc-pc] Section 4.3.3: optional methods
- Closed: [webrtc-pc] Connection states after signaling handshake when there is no transceiver and SCTP transport
- Re: [webrtc-pc] Connection states after signaling handshake when there is no transceiver and SCTP transport
- [webrtc-pc] close() method should close sctp transport
- [webrtc-pc] Connection states when there is no transceiver and SCTP transport
- [webrtc-pc] Validation for binaryType setter in RTCDataChannel
- [webrtc-pc] Origin value for data channel message event
- [webrtc-pc] Pull Request: Add/remove remote tracks from msid streams based on direction.
- [webrtc-pc] Improve description for semantics of updating bufferedAmount
Monday, 12 June 2017
- Re: [webrtc-pc] Section 8.2: Null selector properly handled by getStats?
- [webrtc-pc] Checks for negotiation-needed are underspecified when currentLocalDescription/currentRemoteDescription are not set
- Re: [webrtc-pc] Clarify offerToReceiveAudio and offerToReceiveVideo in renogtiation
- Re: [webrtc-pc] getStats text still talks about selectors
- [webrtc-pc] Section 8.2: Null selector properly handled by getStats?
- Re: [webrtc-pc] Missing initialization of priority attribute when firing datachannel event
- Re: [webrtc-pc] Public accessor for isClosed
- Re: [webrtc-pc] Throw error if data channel's buffer is filled, rather than closing.
- Re: [webrtc-pc] getStats text still talks about selectors
- Closed: [webrtc-pc] Copy/modify spec from WebSocket for RTCDataChannel's binaryType and onmessage
- Re: [webrtc-pc] Copy/modify spec from WebSocket for RTCDataChannel's binaryType and onmessage
- Re: [webrtc-pc] getStats text still talks about selectors
- Closed: [webrtc-pc] getStats text still talks about selectors
- Re: [webrtc-pc] getStats text still talks about selectors
- Re: [webrtc-pc] getStats text still talks about selectors
- Re: [webrtc-pc] getStats text still talks about selectors
Sunday, 11 June 2017
- [webrtc-pc] Pull Request: DTMF playout algorithm for comma
- Re: [webrtc-pc] Handling of encoding/decoding errors
- [webrtc-pc] Pull Request: Add reference to RFC 5245
- Re: [webrtc-pc] Don't update state if setLocalD is called with bogus input
Saturday, 10 June 2017
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] Don't update state if setLocalD is called with bogus input
Friday, 9 June 2017
- Re: [webrtc-pc] pc.close() sets pc.signalingState to "closed"
- Re: [webrtc-pc] pc.close() sets pc.signalingState to "closed"
- [webrtc-pc] Pull Request: pc.close() sets pc.signalingState to "closed"
- Re: [webrtc-pc] Public accessor for isClosed
- Re: [webrtc-pc] Public accessor for isClosed
- Re: [webrtc-pc] Editorial: Use consistent syntax for enum values and strings
- Re: [webrtc-pc] Editorial: Use consistent syntax for enum values and strings
- [webrtc-pc] Editorial: Use consistent syntax for enum values and strings
- [webrtc-pc] Editorial: Assume default values for optional dictionaries in spec text
- Re: [webrtc-pc] Enqueue an operation vs queue a task
- [webrtc-pc] Missing initialization of priority attribute when firing datachannel event
- [webrtc-pc] Public accessor for isClosed
- [webrtc-pc] editorial: inconsistent use of dfn in section names
- Re: [webrtc-pc] RTCDataChannel: Use internal slots and specify default values at one location
- Re: [webrtc-pc] getStats text still talks about selectors
- [webrtc-pc] getStats text still talks about selectors
- Re: [webrtc-pc] lastOffer on the PC
- Re: [webrtc-pc] Handling of encoding/decoding errors
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] Relating RTCDtlsTransportState to RTCIceTransportState and RTCIceGathererState
- [webrtc-pc] RTCDtlsTransport and RTCIceTransport should inherit from EventTarget
- [webrtc-pc] Relating RTCDtlsTransportState to RTCIceTransportState and RTCIceGathererState
- Re: [webrtc-pc] Enqueue an operation vs queue a task
- [webrtc-pc] Clarify offerToReceiveAudio and offerToReceiveVideo in renogtiation
Thursday, 8 June 2017
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Closed: [webrtc-pc] Rationale for use of USVString in RTCPeerConnection.prototype.createDataChannel
- Re: [webrtc-pc] Rationale for use of USVString in RTCPeerConnection.prototype.createDataChannel
- Re: [webrtc-pc] Misuse of SyntaxError
- Re: [webrtc-pc] Possibly incorrect language in "generateCertificate" description
- [webrtc-pc] new commits pushed by burnburn
- Closed: [webrtc-pc] Define "reasonably soon"
- Closed: [webrtc-pc] Section 11.7: DTMF Examples
- Closed: [webrtc-pc] Does insertDTMF append to or replace the current tone buffer
- [webrtc-pc] new commits pushed by taylor-b
- Closed: [webrtc-pc] Misuse of SyntaxError
- [webrtc-pc] new commits pushed by burnburn
- Closed: [webrtc-pc] Section 5.1: RID restrictions
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] capitalization of 2119 works
- [webrtc-pc] new commits pushed by burnburn
- Re: [webrtc-pc] Section 4.2.5/4.2.6: Enum Table Inconsistency
- Closed: [webrtc-pc] Extend privacy note to clarify regarding defaultIceServers
- [webrtc-pc] new commits pushed by burnburn
- [webrtc-pc] new commits pushed by burnburn
- Closed: [webrtc-pc] maximum bandwidth: TIAS or AS?
- Closed: [webrtc-pc] Section 5.5.1: RFC 8122 consistency
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by taylor-b
- Re: [webrtc-pc] Start integrating direction into 'create RTCRtpTransceiver' algorithm
- [webrtc-pc] new commits pushed by burnburn
- [webrtc-pc] new commits pushed by adam-be
- Re: [webrtc-pc] Add bufferSize attribute to RTCDataChannel.
- [webrtc-pc] new commits pushed by burnburn
- Closed: [webrtc-stats] RTCMediaStreamTrackStats.voiceActivityFlag?
- Closed: [webrtc-stats] Missing consent interval in RTCIceCandidatePairStats
- [webrtc-stats] new commits pushed by henbos
- Closed: [webrtc-stats] RTCIceCandidatePairStats.lastResponseTimestamp
- Re: [webrtc-pc] Consider using generic algorithm
- Re: [webrtc-pc] Enqueue an operation vs queue a task
- Re: [webrtc-pc] Don't update state if setLocalD is called with bogus input
- Re: [webrtc-pc] Make promise rejection/enqueing consistent
- [webrtc-pc] Pull Request: createOffer/Answer: Remove sentence with vauge 'reasonably soon'.
- Re: [webrtc-pc] Define "reasonably soon"
- Re: [webrtc-pc] Verbose description for RTCDataChannel default values
- [webrtc-pc] Pull Request: RTCDataChannel: Use internal slots and specify defalt values at one location
- [webrtc-pc] What happen to RTCDtlsTransport during ICE restart?
- Re: [webrtc-pc] Verbose description for RTCDataChannel default values
- Re: [webrtc-pc] Verbose description for RTCDataChannel default values
- Re: [webrtc-pc] Misuse of SyntaxError
- [webrtc-pc] Pull Request: createDataChannel: Use TypeError for bad reliability arguments
- Re: [webrtc-pc] Rationale for use of USVString in RTCPeerConnection.prototype.createDataChannel
- Re: [webrtc-pc] setDirection needs an internal slot and an algorithm.
Wednesday, 7 June 2017
- Closed: [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- Re: [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- [webrtc-pc] Misuse of SyntaxError
- [webrtc-pc] Rationale for use of USVString in RTCPeerConnection.prototype.createDataChannel
- Re: [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- Re: [webrtc-pc] Start integrating direction into 'create RTCRtpTransceiver' algorithm
- Re: [webrtc-pc] Terminology around "setting" attributes may be incorrect
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-stats] jitterBufferDelay vs playoutDelay
- [webrtc-stats] jitterBufferDelay vs playoutDelay
- [webrtc-pc] Verbose description for RTCDataChannel default values
- [webrtc-pc] Copy/modify spec from WebSocket for RTCDataChannel's binaryType and onmessage
- Re: [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- 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?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] Do we need a "trackremoved" event?
Tuesday, 6 June 2017
- Re: [webrtc-stats] Adding audio level stat that can be used to compute averages.
- Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
- [webrtc-pc] track event description is obsolete since transceivers
- Re: [webrtc-pc] What happens if ufrag differs between different SDPs applied
- Closed: [webrtc-pc] What happens if ufrag differs between different SDPs applied
- Re: [webrtc-pc] rtp media api: when is a receiver created
- Re: [webrtc-pc] Built-in certificate behavior
- [webrtc-pc] Pull Request: Remove meaningless case-sensitive qualification of RID characters
- [webrtc-pc] Pull Request: Show RFC2119 keywords in small-caps
- [webrtc-pc] Pull Request: Add a note on the absence of privacy impact of configured default ICE…
- Re: [webrtc-pc] Ignore unsupported url types in setConfiguration
- Re: [webrtc-pc] When [[isClosed]] slot turns true, queue a task to update the connection state
- Closed: [webrtc-pc] When [[isClosed]] slot turns true, queue a task to update the connection state
- [webrtc-pc] Enqueue an operation vs queue a task
- Re: [webrtc-pc] Section 4.2.3 (createOffer)
- [webrtc-pc] Ignore unsupported url types in setConfiguration
- [webrtc-pc] Make promise rejection/enqueing consistent
- [webrtc-pc] Consider using generic algorithm
- [webrtc-pc] When [[isClosed]] slot turns true, queue a task to update the connection state
- Re: [webrtc-pc] Section 4.3.3: optional methods
- Re: [webrtc-pc] What happens if ufrag differs between different SDPs applied
- Re: [webrtc-pc] Extend privacy note to clarify regarding defaultIceServers
- Re: [webrtc-pc] Built-in certificate behavior
- Re: [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- Closed: [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- Re: [webrtc-pc] Section 4.2.5/4.2.6: Enum Table Inconsistency
- Re: [webrtc-pc] Built-in certificate behavior
Monday, 5 June 2017
- [webrtc-pc] Pull Request: Section 4.2.5/4.2.6: Enum Table Inconsistency
- Re: [webrtc-pc] empty attribute descriptions in ice description
- [webrtc-pc] Pull Request: empty attribute descriptions in ice description
- Re: [webrtc-pc] DTLS failures
- [webrtc-pc] Pull Request: Section 11.7 Fix DTMF Examples
- [webrtc-pc] Section 11.7: DTMF Examples
- [webrtc-pc] Pull Request: DTMF: Misplaced ";" in playout steps
- Re: [webrtc-pc] Check for state when "setting an RTCSessionDescription description"
- [webrtc-pc] Pull Request: Built-in certificate behavior
- Re: [webrtc-pc] algorithm for rejecting modification
- Re: [webrtc-pc] setLocalDescription algorithm for rejecting modification
- Re: [webrtc-pc] algorithm for rejecting modification
- [webrtc-pc] Pull Request: algorithm for rejecting modification
- Re: [webrtc-pc] setLocalDescription algorithm for rejecting modification
- Re: [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- Re: [webrtc-pc] DTLS failures
- Re: [webrtc-pc] maximum bandwidth: TIAS or AS?
- Re: [webrtc-pc] Section 11.6: Diagram
- Re: [webrtc-pc] capitalization of 2119 works
- Re: [webrtc-pc] capitalization of 2119 works
- Re: [webrtc-stats] Consider making (aggregate) stats more accessible
- [webrtc-pc] new commits pushed by adam-be
- [webrtc-pc] Inconsistencies and race conditions in updating negotiation-needed flag
- [webrtc-pc] Session description attribute not specified for some steps in check if negotiation is needed
Sunday, 4 June 2017
- [webrtc-pc] setLocalDescription algorithm for rejecting modification
- Re: [webrtc-pc] maximum bandwidth: TIAS or AS?
- [webrtc-pc] Pull Request: update for maxBitrate definition
Saturday, 3 June 2017
- [webrtc-pc] capitalization of 2119 works
- Re: [webrtc-stats] Consider making (aggregate) stats more accessible
- Re: [webrtc-pc] Section 4.8.1: missing attributes
- Closed: [webrtc-pc] Missing steps on handling direction argument in addTransceiver
- Re: [webrtc-pc] maximum bandwidth: TIAS or AS?
- Closed: [webrtc-pc] Do we need to control what is in SNI and Certname of DTLS connections
- Re: [webrtc-pc] Do we need to control what is in SNI and Certname of DTLS connections
- Closed: [webrtc-pc] What happens if cert expires mid call ?
- Re: [webrtc-pc] What happens if cert expires mid call ?
Friday, 2 June 2017
- Re: [webrtc-pc] createOffer(): Built-in certificate behavior
- Re: [webrtc-pc] createOffer(): Built-in certificate behavior
- Re: [webrtc-pc] createOffer(): Built-in certificate behavior
- Re: [webrtc-pc] createOffer(): Built-in certificate behavior
- Re: [webrtc-pc] Remove trailing whitespace
- [webrtc-pc] Pull Request: Remove fingerprint matching
- [webrtc-pc] Pull Request: Remove trailing whitespace
- Re: [webrtc-pc] RTCConfiguration.iceServers with undefined?
- Re: [webrtc-pc] RTCConfiguration.iceServers with undefined?
- Closed: [webrtc-pc] RTCConfiguration.iceServers with undefined?
- Re: [webrtc-pc] createOffer(): Built-in certificate behavior
- Re: [webrtc-pc] RTCConfiguration.iceServers with undefined?
- Re: [webrtc-pc] Start integrating direction into 'create RTCRtpTransceiver' algorithm
- [webrtc-pc] new commits pushed by adam-be
- Re: [webrtc-pc] Missing definition for obtaining list of all RTCIceTransport and RTCDtlsTransport
- Re: [webrtc-pc] Missing definition for obtaining list of all RTCIceTransport and RTCDtlsTransport
- Re: [webrtc-pc] Missing steps on handling direction argument in addTransceiver
- Re: [webrtc-pc] Missing definition for obtaining list of all RTCIceTransport and RTCDtlsTransport
- Re: [webrtc-pc] Do we need to control what is in SNI and Certname of DTLS connections
- Re: [webrtc-pc] What happens if cert expires mid call ?
Thursday, 1 June 2017
- Re: [webrtc-pc] RTCConfiguration.iceServers with undefined?
- Closed: [webrtc-pc] pc.removeTrack(receiver) should throw an error.
- Re: [webrtc-pc] pc.removeTrack(receiver) should throw an error.
- Re: [webrtc-pc] Section 4.4.4 closed state
- [webrtc-pc] Pull Request: Language in "generateCertificate" description
- [webrtc-pc] Possibly incorrect language in "generateCertificate" description
- Re: [webrtc-pc] Section 4.8.1: missing attributes
- Re: [webrtc-pc] Ambiguous connection state when list of transports are empty
- Re: [webrtc-pc] Missing definition for obtaining list of all RTCIceTransport and RTCDtlsTransport
- Re: [webrtc-pc] Check for state when "setting an RTCSessionDescription description"
- Re: [webrtc-pc] MTI specification of crypto for certs
- Re: [webrtc-pc] Missing steps on handling direction argument in addTransceiver
- [webrtc-pc] Handling of encoding/decoding errors
- Closed: [webrtc-pc] Section 4.2.6: informative sentence
- Re: [webrtc-pc] Do we need to control what is in SNI and Certname of DTLS connections
- Re: [webrtc-pc] What happens if cert expires mid call ?
- Re: [webrtc-pc] Section 4.8.1: missing attributes
- Re: [webrtc-pc] Section 4.8.1: missing attributes
- Re: [webrtc-pc] Section 4.8.3: Buried treasure
- Re: [webrtc-pc] Check crypto suites
- Re: [webrtc-pc] Do we need to control what is in SNI and Certname of DTLS connections
- Re: [webrtc-pc] What happens if cert expires mid call ?
- Closed: [webrtc-pc] guideline of when to time out an IdP
- Re: [webrtc-pc] guideline of when to time out an IdP
- Re: [webrtc-pc] Start integrating direction into 'create RTCRtpTransceiver' algorithm
- [webrtc-pc] new commits pushed by adam-be
- Closed: [webrtc-pc] Clarify '"trusted" origins'
- [webrtc-pc] new commits pushed by stefhak
- Re: [webrtc-pc] RFC 8122 consistency
- Re: [webrtc-pc] RFC 8122 consistency
- [webrtc-pc] new commits pushed by taylor-b
- [webrtc-pc] Built-in certificate behavior
- Re: [webrtc-pc] Section 6.2: when data cannot be sent
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] editorial: createOffer description
- Re: [webrtc-pc] Section 4.2.6: remove informative sentences
- [webrtc-pc] Pull Request: Start integrating direction into 'create RTCRtpTransceiver' algorithm
- Re: [webrtc-pc] What happens if cert expires mid call ?
- Re: [webrtc-pc] guideline of when to time out an IdP
- Re: [webrtc-pc] What happens if cert expires mid call ?
- Re: [webrtc-pc] Extend privacy note to clarify regarding defaultIceServers
- [webrtc-pc] Pull Request: Clarify "trusted" origins as whitelisted
- Closed: [webrtc-pc] RTCPeerConnectionIceEvent parameter: RTCPeerConnectionIceEventInit eventInitDict is optional
- Re: [webrtc-pc] RTCPeerConnectionIceEvent parameter: RTCPeerConnectionIceEventInit eventInitDict is optional
- Re: [webrtc-pc] Review issues reported to last in September
- [webrtc-pc] guideline of when to time out an IdP
- [webrtc-pc] What happens if cert expires mid call ?
- [webrtc-pc] More granular data channel error reporting
- [webrtc-pc] Do we ned to control what is in SNI and Certname of DTLS connections
- [webrtc-pc] Check crypto suites
- [webrtc-pc] Refine error reporting for identity assertion
- [webrtc-pc] Extend privacy note to clarify regarding defaultIceServers
- Re: [webrtc-pc] legacy methods: when are they called?
- [webrtc-pc] Clarify '"trusted" origins'
- [webrtc-pc] What happens if ufrag differs between different SDPs applied
- [webrtc-pc] Make 4.3.1. referenceable
- [webrtc-pc] Check for state when "setting an RTCSessionDescription description"
- [webrtc-pc] when voiceActivityDetection is false, that browser must send media even if it silent
- [webrtc-pc] Clarify "cannot be applied at the media layer"
- [webrtc-pc] Missing definition for obtaining list of all RTCIceTransport and RTCDtlsTransport
- [webrtc-pc] Ambiguous connection state when list of transports are empty
- [webrtc-pc] Pull Request: Mark Bernard as former editor
- Re: [webrtc-pc] Section 4.2.5/4.2.6: Enum Table Inconsistency