Monday, 31 July 2017
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-pc] Don't proceed w/removeTrack() if sender.track is already null.
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-pc] Don't proceed w/removeTrack() if sender.track is already null.
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-pc] Don't fire ONN on removeTrack() if sender.track is already null.
- [webrtc-pc] DTMF tonechange event timing when toneBuffer is modified in between
- Re: [webrtc-pc] The same connection.peerIdentity promise can be resolved multiple times
Friday, 28 July 2017
- Re: [webrtc-pc] Check for invalid rollback
- Re: [webrtc-pc] Performing rollback via the other set*Description
- Re: [webrtc-pc] Performing rollback via the other set*Description
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-pc] The same connection.peerIdentity promise can be resolved multiple times
- [webrtc-pc] duration and interToneGap should be stored as internal slots of RTCDTMFSender
- [webrtc-pc] insertDTMF when transceiver.currentDirection is null
- Closed: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Closed: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] The same connection.peerIdentity promise can be resolved multiple times
Thursday, 27 July 2017
- Re: [webrtc-pc] The same connection.peerIdentity promise can be resolved multiple times
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] editorial: inconsistent use of dfn in section names
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by taylor-b
- Closed: [webrtc-pc] ufrag vs usernameFragment
- Re: [webrtc-pc] rtciceserver: fix represents a turn server
- Closed: [webrtc-pc] setConfiguration throwing InvalidModificationError with default values
- Closed: [webrtc-pc] setLocalDescription() with null sdp is not applicable
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] RTCRtpTransceiver setDirection() should throw InvalidStateError if transceiver is stopped
- Closed: [webrtc-pc] Direction of newly created transceiver in setRemoteDescription
- Closed: [webrtc-pc] scaleResolutionDownBy parameter is not validated in addTransceiver
- Re: [webrtc-pc] Result returned from receiver.getParameters() when no session description is set
- Re: [webrtc-pc] addTrack can reuse a sender whose transceiver is stopped
- Re: [webrtc-pc] getCapabilities should throw TypeError if invalid kind is provided
- Re: [webrtc-pc] Type checking for selectorArg in getStats is unnecessary
- Closed: [webrtc-pc] legacy methods: when are they called?
- Re: [webrtc-pc] Deterministic behavior for transactionId validation
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Don't fire ONN on removeTrack() if sender.track is already null.
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by taylor-b
- [webrtc-pc] new commits pushed by taylor-b
- [webrtc-pc] new commits pushed by taylor-b
- [webrtc-pc] new commits pushed by taylor-b
- Re: [webrtc-pc] setDirection(): throw InvalidStateError if transceiver is stopped or…
- Re: [webrtc-pc] Consistency in enum usage
- Re: [webrtc-pc] Validating scaleResolutionDownBy parameter in addTransceiver
- Re: [webrtc-pc] setLocalDescription() with null sdp is not applicable
- Re: [webrtc-pc] Direction of newly created transceiver in setRemoteDescription
- Re: [webrtc-pc] Update mandatory stats to reflect rtp refactor in webrtc-stats.
- Re: [webrtc-pc] rename ufrag to usernameFragment
- Re: [webrtc-pc] Don't fire ONN on removeTrack() if sender.track is already null.
- Re: [webrtc-pc] setRemoteDescription should fail if target peer identity is set but no a=identity in SDP
- Re: [webrtc-pc] setRemoteDescription should fail if target peer identity is set but no a=identity in SDP
- [webrtc-pc] The same connection.peerIdentity promise can be resolved multiple times
- [webrtc-pc] setRemoteDescription should fail if target peer identity is set but no a=identity in SDP
- Re: [webrtc-pc] rtciceserver: fix represents a turn server
- 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] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] How to find what keyGenAlgorithm values the browser supports?
- Re: [webrtc-pc] When is the dtmf attribute in RTCRtpSender set?
Wednesday, 26 July 2017
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- [webrtc-pc] Ambiguous definition for IdP errors
- Re: [webrtc-pc] Default identity provider
- [webrtc-pc] Requesting Identity Assertions incorrectly mention steps of validating assertion
- Re: [webrtc-pc] Support for RRID?
- [webrtc-pc] Default identity provider
Tuesday, 25 July 2017
- Re: [webrtc-pc] Support for RRID?
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-stats] Issues raised in TAG review
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-pc] Support for RRID?
- Re: [webrtc-pc] Support for RRID?
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-pc] Result returned from receiver.getParameters() when no session description is set
- Re: [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- Re: [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- Re: [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- Re: [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- Re: [webrtc-pc] Specifying third party IdP for validating assertion
- Re: [webrtc-pc] How is port number specified when verifying peer identity's assertion?
- Re: [webrtc-pc] Format of provider string for setIdentityProvider and validation
- Re: [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- Re: [webrtc-pc] setIdentityProvider should throw error if protocol contains invalid characters
- Re: [webrtc-pc] How is port number specified when verifying peer identity's assertion?
- Re: [webrtc-pc] Identity assertion process should wait for certificate to be generated
- Re: [webrtc-pc] setIdentityProvider should throw error if protocol contains invalid characters
- Re: [webrtc-pc] Format of provider string for setIdentityProvider and validation
- Re: [webrtc-pc] How is port number specified when verifying peer identity's assertion?
- Re: [webrtc-pc] Identity assertion process should wait for certificate to be generated
- Re: [webrtc-pc] Origin value for IdP proxy script
- Re: [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- Re: [webrtc-pc] Specifying third party IdP for validating assertion
Monday, 24 July 2017
- [webrtc-pc] Limiting number of RTCRtpTransceivers
- [webrtc-pc] Specifying third party IdP for validating assertion
- [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- [webrtc-pc] Origin value for IdP proxy script
Friday, 21 July 2017
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- [webrtc-pc] Identity assertion process should wait for certificate to be generated
- [webrtc-pc] How is port number specified when verifying peer identity's assertion?
- [webrtc-pc] Format of provider string for setIdentityProvider and validation
- [webrtc-pc] setIdentityProvider should throw error if protocol contains invalid characters
Thursday, 20 July 2017
Wednesday, 19 July 2017
- Re: [webrtc-pc] Validation of reordered readonly parameters in setParameters
- [webrtc-pc] getCapabilities should throw TypeError if invalid kind is provided
- Re: [webrtc-pc] Clarify addIceCandidate behavior when adding candidate after end of candidate
- Re: [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
- Re: [webrtc-pc] Confusion on currentRemoteDescription.sdp need not match remoteDescription.sdp
Tuesday, 18 July 2017
- [webrtc-pc] addTrack can reuse a sender whose transceiver is stopped
- Re: [webrtc-pc] Validation of reordered readonly parameters in setParameters
- Re: [webrtc-pc] toJSON Dfn needed
- Re: [webrtc-pc] Required fields in RTCRtpParameters returned from getParameters
- Re: [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
- Re: [webrtc-pc] Confusion on currentRemoteDescription.sdp need not match remoteDescription.sdp
- Re: [webrtc-pc] Validation of reordered readonly parameters in setParameters
- Re: [webrtc-pc] Required fields in RTCRtpParameters returned from getParameters
- Re: [webrtc-pc] Result returned from receiver.getParameters() when no session description is set
Monday, 17 July 2017
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- [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-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- [webrtc-pc] Required fields in RTCRtpParameters returned from getParameters
- [webrtc-pc] Validation of reordered readonly parameters in setParameters
- Closed: [webrtc-pc] Undefined setParameters behavior of handling parameters fields other than transactionId and encodings
- Re: [webrtc-pc] Undefined setParameters behavior of handling parameters fields other than transactionId and encodings
- [webrtc-pc] Default values for RTCRtpEncodingParameters
- Re: [webrtc-pc] transactionId validation for get/set parameters should have more consistent definition
- [webrtc-pc] Result returned from receiver.getParameters() when no session description is set
- [webrtc-pc] Undefined setParameters behavior of handling parameters fields other than transactionId and encodings
- [webrtc-pc] transactionId validation for get/set parameters should have more consistent definition
Sunday, 16 July 2017
Saturday, 15 July 2017
- [webrtc-pc] Pull Request: Check for invalid rollback
- Re: [webrtc-pc] editorial: inconsistent use of dfn in section names
- [webrtc-pc] Pull Request: setDirection(): throw InvalidStateError if transceiver is stopped or…
- [webrtc-pc] Pull Request: Consistency in enum usage
- [webrtc-pc] toJSON Dfn needed
- Re: [webrtc-pc] Fields in RTCStats dictionary should be required
- Re: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
Friday, 14 July 2017
- Closed: [webrtc-pc] Examples with dictionaries shouldn't use quotes around member names
- [webrtc-pc] Pull Request: Validating scaleResolutionDownBy parameter in addTransceiver
- [webrtc-pc] Pull Request: setLocalDescription() with null sdp is not applicable
- [webrtc-pc] Pull Request: Direction of newly created transceiver in setRemoteDescription
- Re: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Re: [webrtc-pc] Fields in RTCStats dictionary should be required
- Re: [webrtc-pc] Fields in RTCStats dictionary should be required
- Re: [webrtc-pc] Update mandatory stats to reflect rtp refactor in webrtc-stats.
- [webrtc-pc] Pull Request: Update mandatory stats to reflect rtp refactor in webrtc-stats.
- Re: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Re: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Re: [webrtc-pc] Replace serializers by toJSON definitions
- [webrtc-pc] Pull Request: rename ufrag to usernameFragment
- [webrtc-pc] scaleResolutionDownBy parameter is not validated in addTransceiver
- Re: [webrtc-pc] Fields in RTCStats dictionary should be required
- Re: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Re: [webrtc-pc] Fields in RTCStats dictionary should be required
- Closed: [webrtc-pc] We forgot about {offerToReceiveAudio: false, offerToReceiveVideo: false}
- Re: [webrtc-pc] We forgot about {offerToReceiveAudio: false, offerToReceiveVideo: false}
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
Thursday, 13 July 2017
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- [webrtc-pc] Minor inconsistencies around RTCSessionDescription vs. RTCSessionDescriptionInit
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] Add legacy note about addStream.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Add legacy note about addStream.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Fields in RTCStats dictionary should be required
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- [webrtc-pc] new commits pushed by taylor-b
- [webrtc-pc] new commits pushed by taylor-b
- Closed: [webrtc-pc] RTCIceServer "represents a TURN server"
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] WebIDL serializer has been deprecated in favor of toJSON operation
- Re: [webrtc-pc] Add legacy note about addStream.
- [webrtc-pc] Fields in RTCStats dictionary should be required
- Re: [webrtc-pc] Direction of newly created transceiver in setRemoteDescription
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Re: [webrtc-pc] Add legacy note about addStream.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Add legacy note about addStream.
Wednesday, 12 July 2017
- Re: [webrtc-pc] Add legacy note about addStream.
- Re: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Closed: [webrtc-pc] Section 4.8.3: Buried treasure
- Re: [webrtc-pc] Section 4.8.3: Buried treasure
- Re: [webrtc-pc] Highlighting errorCode 701
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Add legacy note about addStream.
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- Closed: [webrtc-pc] Data Channel ID assignment after SCTP renegotiation
- Re: [webrtc-pc] Data Channel ID assignment after SCTP renegotiation
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] Data Channel ID assignment after SCTP renegotiation
- Re: [webrtc-pc] Data Channel ID assignment after SCTP renegotiation
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-stats] We need "sender" and "receiver" stats, not "track" stats
- 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)
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] Direction of newly created transceiver in setRemoteDescription
- [webrtc-pc] Data Channel ID assignment after SCTP renegotiation
- Re: [webrtc-stats] We need "sender" and "receiver" stats, not "track" stats
- Re: [webrtc-stats] We need "sender" and "receiver" stats, not "track" stats
- Re: [webrtc-stats] We need "sender" and "receiver" stats, not "track" stats
- [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Closed: [webrtc-stats] Why no Jitter for RTCOutboundRTPAudioStream?
- Re: [webrtc-stats] Why no Jitter for RTCOutboundRTPAudioStream?
- Re: [webrtc-stats] Audio/Video sync follow-up
- Re: [webrtc-stats] Audio/Video sync follow-up
- Re: [webrtc-stats] Audio/Video sync follow-up
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] Direction of newly created transceiver in setRemoteDescription
- Re: [webrtc-pc] Direction of newly created transceiver in setRemoteDescription
Tuesday, 11 July 2017
- Re: [webrtc-pc] rtciceserver: fix represents a turn server
- [webrtc-pc] Direction of newly created transceiver in setRemoteDescription
- [webrtc-stats] We need "sender" and "receiver" stats, not "track" stats
Monday, 10 July 2017
- [webrtc-stats] RTCMediaStreamTrackStats is four dictionaries in one
- Re: [webrtc-pc] Transceiver kind definition is circular.
- Re: [webrtc-pc] Transceiver kind definition is circular.
- Closed: [webrtc-pc] Transceiver kind definition is circular.
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is false (in-band negotiation)?
- Re: [webrtc-pc] Transceiver kind definition is circular.
- Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is false (in-band negotiation)?
- [webrtc-pc] Transceiver kind definition is circular.
- [webrtc-pc] Calrify that rollback in stable state should throw InvalidStateError
- [webrtc-pc] Performing rollback via the other set*Description
- [webrtc-pc] Rollback with non-empty SDP string
- Re: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- Re: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
Saturday, 8 July 2017
- Re: [webrtc-pc] RTCTrackEvent's type parameter
- [webrtc-pc] Pull Request: move rescale paragraph
- Re: [webrtc-pc] Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Using setConfiguration() to add application certificates to an RTCPeerConnection post-construction?
Friday, 7 July 2017
- 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] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- Re: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- Re: [webrtc-pc] Using setConfiguration() to add application certificates to an RTCPeerConnection post-construction?
- [webrtc-pc] RTCTrackEvent's type parameter
- Re: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- [webrtc-pc] Pull Request: Cover legacy sendonly using {offerToReceiveAudio/Video: false}.
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-stats] Interframe delay stat for video receive stream.
- Re: [webrtc-stats] Interframe delay stat for video receive stream.
- [webrtc-stats] Interframe delay stat for video receive stream.
- [webrtc-pc] setLocalDescription() with null sdp is not applicable
- Re: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- Re: [webrtc-pc] setLocalDescription() with empty string sdp is allowed to pass without calling createOffer/createAnswer
- Re: [webrtc-pc] setLocalDescription() with empty string sdp is allowed to pass without calling createOffer/createAnswer
- [webrtc-pc] Pull Request: setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- [webrtc-pc] setLocalDescription() with empty string sdp is allowed to pass without calling createOffer/createAnswer
- [webrtc-pc] Pull Request: Examples with dictionaries shouldn't use quotes around member names
- Re: [webrtc-pc] Missing detail on obtaining lastOffer/lastAnswer in setLocalDescription
- Re: [webrtc-pc] Spec-compliant way to get remote streams and tracks?
- [webrtc-pc] We forgot about {offerToReceiveAudio: false, offerToReceiveVideo: false}
- Re: [webrtc-pc] setConfiguration can "unset" some configurations
- Re: [webrtc-pc] setConfiguration can "unset" some configurations
- Closed: [webrtc-pc] No way to associate streams using addTransceiver()
- Re: [webrtc-pc] No way to associate streams using addTransceiver()
Thursday, 6 July 2017
- [webrtc-pc] Pull Request: Remove "is set" text
- [webrtc-pc] Pull Request: Remove "is set" text
- [webrtc-pc] Pull Request: Highlighting errorCode 701
- Re: [webrtc-pc] RTCSctpTransport.maxMessageSize 0 case
- Re: [webrtc-pc] removeTrack: does not always cause createOffer to mark media description
- Closed: [webrtc-pc] setConfiguration can "unset" some configurations
- Re: [webrtc-pc] RTCPeerConnectionIceEvent constructor validation
- Closed: [webrtc-pc] RTCPeerConnectionIceEvent constructor validation
- Re: [webrtc-pc] iceGatheringState on connection with data channel only before setRemoteDescription(answer) is set
- Closed: [webrtc-pc] iceGatheringState on connection with data channel only before setRemoteDescription(answer) is set
- Re: [webrtc-pc] run ice server configuration validation steps for each url
- [webrtc-pc] Pull Request: run ice server configuration validation steps for each url
- Re: [webrtc-pc] RTCSctpTransport.maxMessageSize 0 case
- Closed: [webrtc-pc] Section 6.1: label length
- Re: [webrtc-pc] RTCSctpTransport.maxMessageSize 0 case
- Re: [webrtc-pc] setConfiguration throwing InvalidModificationError with default values
- Re: [webrtc-pc] setConfiguration can "unset" some configurations
- Re: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] editorial: move "set a configuration" to operation section
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] Remove duplicate info on method parameters
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Issue 1: Key shortening
- [webrtc-pc] new commits pushed by burnburn
- Re: [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- Re: [webrtc-pc] setConfiguration can "unset" some configurations
- [webrtc-pc] setConfiguration({ peerIdentity }) when there is no initial peerIdentity
- Re: [webrtc-pc] setConfiguration throwing InvalidModificationError with default values
- Re: [webrtc-pc] setConfiguration can "unset" some configurations
- Re: [webrtc-pc] Removing text talking about key shortening that was incorrect.
- [webrtc-pc] Pull Request: label/protocol length restriction
- Re: [webrtc-pc] setConfiguration can "unset" some configurations
- Re: [webrtc-pc] setConfiguration can "unset" some configurations
- [webrtc-pc] setConfiguration can "unset" some configurations
Wednesday, 5 July 2017
- Re: [webrtc-pc] Issue 1: Key shortening
- [webrtc-pc] Pull Request: Removing text talking about key shortening that was incorrect.
- Re: [webrtc-pc] No way to associate streams using addTransceiver()
- Re: [webrtc-pc] setConfiguration throwing InvalidModificationError with default values
- Re: [webrtc-pc] Add legacy note about addStream.
- Re: [webrtc-pc] how is addTrack without a stream signalled in the sdp?
- Closed: [webrtc-pc] how is addTrack without a stream signalled in the sdp?
- [webrtc-pc] No way to associate streams using addTransceiver()
- Re: [webrtc-pc] setConfiguration throwing InvalidModificationError with default values
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- Re: [webrtc-pc] [[associated MediaStreams]] internal slot for RTCRtpSender is not used
- Re: [webrtc-pc] [[associated MediaStreams]] internal slot for RTCRtpSender is not used
- Re: [webrtc-pc] Section 12: Missing WebIDL in RTCError
- Re: [webrtc-pc] Add legacy note about addStream.
- [webrtc-pc] Pull Request: Add legacy note about addStream.
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- [webrtc-pc] Pull Request: Remove duplicate info on method parameters
- Re: [webrtc-pc] how is addTrack without a stream signalled in the sdp?
- [webrtc-pc] Pull Request: Replace serializers by toJSON definitions
- Re: [webrtc-pc] how is addTrack without a stream signalled in the sdp?
- [webrtc-pc] how is addTrack without a stream signalled in the sdp
- Re: [webrtc-pc] Add/remove remote tracks from msid streams based on direction (rebased)
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- [webrtc-pc] setConfiguration throwing InvalidModificationError with default values
- Re: [webrtc-pc] Do we need a "trackremoved" event?
- Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
Tuesday, 4 July 2017
- Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?
- Re: [webrtc-pc] Add reference to JSEP that setLocalDescription triggers ICE gathering
- Re: [webrtc-pc] When is ICE gathering triggered?
- Closed: [webrtc-pc] When is ICE gathering triggered?
- Re: [webrtc-pc] Issue 1: Key shortening
- Re: [webrtc-pc] Section 4.2.2: Keying material
- Re: [webrtc-pc] Queue enqueued operation as task if length of operations is 1
- Re: [webrtc-pc] Race condition in enqueue an operation
- Closed: [webrtc-pc] Race condition in enqueue an operation