Thursday, 31 August 2017
- [webrtc-pc] Ordering of SRD promise resolving vs. track "mute" event
- Closed: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] addIceCandidate end of candidates woes
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Session description attribute not specified for some steps in check if negotiation is needed
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Is contents validation based on exact string matching or fingerprint list matching when verifying identity assertion?
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] close all DtlsTransports in pc.close() (including sctp.transport)
- Re: [webrtc-pc] Adding `remoteTrackId` attribute to represent SDP-signaled track ID.
- Re: [webrtc-pc] [[associated MediaStreams]] internal slot for RTCRtpSender is not used
- Re: [webrtc-pc] Adding `remoteTrackId` attribute to represent SDP-signaled track ID.
- [webrtc-pc] new commits pushed by adam-be
- Re: [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
Wednesday, 30 August 2017
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-stats] RTCMediaStreamTrackStats.keyFramesReceived
- Re: [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
- Re: [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
- Re: [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
- Re: [webrtc-stats] Need DSCP information for outgoing RTP streams
- Re: [webrtc-stats] Dated getStats example.
- Closed: [webrtc-stats] Dated getStats example.
- Re: [webrtc-pc] Harmonize and update our references to other specifications
- Re: [webrtc-pc] Section 5.2: centering, scaling, cropping
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] close all DtlsTransports in pc.close() (including sctp.transport)
- Re: [webrtc-pc] RTCPeerConnection.close: release transceiver before ICE transport
- Re: [webrtc-pc] Harmonize and update our references to other specifications
- Closed: [webrtc-pc] What happens if RTCDataChannelInit.negotiated is true, but id is absent?
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- [webrtc-pc] Pull Request: Adding `remoteTrackId` attribute to represent SDP-signaled track ID.
- Re: [webrtc-pc] Add a section summarizing different ICE candidate events.
- [webrtc-pc] Pull Request: Add a section summarizing different ICE candidate events.
Tuesday, 29 August 2017
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Race condition between createOffer and setIdentityProvider
- Re: [webrtc-pc] Formalize how createOffer interacts with identity providers.
- Re: [webrtc-pc] Clarify whether RTCRtpContributingSource members are live.
- [webrtc-stats] Do the "audio level" stats include MediaStreamTrack volume settings?
- Re: [webrtc-pc] Section 5.2: centering, scaling, cropping
- Re: [webrtc-pc] Section 5.2: centering, scaling, cropping
- Re: [webrtc-pc] Ambiguities with BUNDLE and ICE
- Re: [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Handling encoding parameter errors
- Re: [webrtc-pc] Handling of encoder/decoder errors
- Closed: [webrtc-pc] Handling of encoder/decoder errors
- [webrtc-pc] Pull Request: close all DtlsTransports in pc.close() (including sctp.transport)
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- [webrtc-pc] Deciding on resolutions with scaleResolutionDownBy
- Re: [webrtc-pc] Ambiguities with BUNDLE and ICE
- [webrtc-pc] Ambiguities with BUNDLE and ICE
Monday, 28 August 2017
- [webrtc-pc] How to handle removing and re-adding remote streams/tracks - possible ID collisions?
- [webrtc-stats] Add stat to reflect the redundancy of FEC/RED data
Friday, 25 August 2017
- Re: [webrtc-pc] Fields in RTCStats dictionary should be required
- Re: [webrtc-pc] Required fields in RTCRtpParameters returned from getParameters
- Re: [webrtc-pc] Required fields in RTCRtpParameters returned from getParameters
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- Re: [webrtc-pc] Meta: auto-publish changes to the spec
- [webrtc-pc] Pull Request: Clarify which session description to check for if negotiation is needed
- Closed: [webrtc-pc] Result returned from receiver.getParameters() when no session description is set
Thursday, 24 August 2017
- Closed: [webrtc-pc] Invalid JSON in examples
- Re: [webrtc-pc] Invalid JSON in examples
- Closed: [webrtc-pc] Performing rollback via the other set*Description
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] getCapabilities should throw TypeError if invalid kind is provided
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] When is the dtmf attribute in RTCRtpSender set?
- Closed: [webrtc-pc] Type checking for selectorArg in getStats is unnecessary
- [webrtc-pc] new commits pushed by aboba
- Re: [webrtc-pc] replace "a RTCsomething" with "an RTCsomething"
- Re: [webrtc-pc] replace "a RTCsomething" with "an RTCsomething"
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] rtp media api: when is a receiver created
- [webrtc-pc] new commits pushed by burnburn
- Re: [webrtc-pc] When dtmf attribute is set
- Closed: [webrtc-pc] Validation for binaryType setter in RTCDataChannel
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Confusion on currentRemoteDescription.sdp need not match remoteDescription.sdp
- Re: [webrtc-pc] replace "a RTCsomething" with "an RTCsomething"
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Requesting Identity Assertions incorrectly mention steps of validating assertion
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Some Mandatory To Implement Stats fields are out of sync with webrtc-stats
- Re: [webrtc-pc] Reference rtcweb-data-channel for RTCPriorityType enum.
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Fields in RTCStats dictionary should be required
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] RTCPriorityType should reference rtcweb-data-channel
- Re: [webrtc-pc] Reference rtcweb-data-channel for RTCPriorityType enum.
- Re: [webrtc-pc] replace "a RTCsomething" with "an RTCsomething"
- Re: [webrtc-pc] Allow createAnswer to be called only in valid signaling state
- Re: [webrtc-pc] s/outboundrtp/outbound-rtp
- Re: [webrtc-pc] Type checking for selectorArg in getStats is unnecessary
- Re: [webrtc-pc] getCapabilities behavior with an unsupported value of kind
- Re: [webrtc-pc] Check for invalid rollback
- [webrtc-pc] Pull Request: setParameters: Do argument checks in sync section
- Re: [webrtc-pc] rtciceserver: fix represents a turn server
- [webrtc-pc] Pull Request: Reference rtcweb-data-channel for RTCPriorityType enum.
- Re: [webrtc-pc] What happens if RTCDataChannelInit.negotiated is true, but id is absent?
- [webrtc-pc] Pull Request: Throw if a DataChannel, negotiated by the script, lacks id
- [webrtc-pc] Pull Request: Make fields in RTCStats required
- Re: [webrtc-pc] setParameters does input validation in parallel, and doesn't actually apply parameters?
- Re: [webrtc-pc] SLD/SRD: Check if transceiver is stopped before setting currentDirection
- Re: [webrtc-pc] SLD/SRD: Check if transceiver is stopped before setting currentDirection
- Re: [webrtc-pc] Clarify the meaning of session description sdp need not match
- Re: [webrtc-pc] Allow createAnswer to be called only in valid signaling state
- [webrtc-pc] Pull Request: Update mandatory to implement stats fields to sync with webrtc-stats
- [webrtc-pc] Pull Request: Fix reference to validating assertion result in requesting assertions
Wednesday, 23 August 2017
- Re: [webrtc-pc] createAnswer does not guard against invalid remoteDescription or signaling state
- Re: [webrtc-pc] update current*Description and pending*Description
- [webrtc-pc] Pull Request: replace "a RTCsomething" with "an RTCsomething"
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] Pull Request: What algorithms the browser supports
- Re: [webrtc-pc] Section 5.2: centering, scaling, cropping
- [webrtc-pc] Pull Request: Harmonize and update our references to other specifications
- [webrtc-pc] Pull Request: Clarify the meaning of session description sdp need not match
- [webrtc-pc] Pull Request: Validate binaryType value when setting it in RTCDataChannel
- [webrtc-pc] Pull Request: Allow createAnswer to be called only in valid signaling state
- Closed: [webrtc-pc] Clarify addIceCandidate behavior when adding candidate after end of candidate
- Re: [webrtc-pc] Clarify addIceCandidate behavior when adding candidate after end of candidate
- Re: [webrtc-pc] Result returned from receiver.getParameters() when no session description is set
- [webrtc-pc] Pull Request: Add note that IdP must treat contents as opaque
- [webrtc-pc] Pull Request: Wait for certificate to be generated before identity assertion process
Tuesday, 22 August 2017
- Closed: [webrtc-pc] Normative language in upper case
- Re: [webrtc-pc] Normative language in upper case
- Closed: [webrtc-pc] insertDTMF when transceiver.currentDirection is null
- Re: [webrtc-pc] insertDTMF when transceiver.currentDirection is null
- [webrtc-pc] Use automatically generated default toJSON() method (when available)
- [webrtc-pc] new commits pushed by adam-be
- Closed: [webrtc-pc] Deterministic behavior for transactionId validation
- Re: [webrtc-pc] Clarify offerToReceiveAudio and offerToReceiveVideo in renegotiation
- Re: [webrtc-pc] protocol can only contain characters legal in a URI
Monday, 21 August 2017
- Re: [webrtc-pc] protocol can only contain legal characters
- Re: [webrtc-pc] Section 9.6: protocol type
- Re: [webrtc-pc] Normative language in upper case
- Re: [webrtc-pc] Invalid JSON in examples
- Re: [webrtc-pc] Revert JSON changes
- Re: [webrtc-pc] Invalid JSON in examples
- [webrtc-pc] Pull Request: Revert JSON changes
- Re: [webrtc-pc] Invalid JSON in examples
- Re: [webrtc-pc] Clarify offerToReceiveAudio and offerToReceiveVideo in renegotiation
- Re: [webrtc-pc] Invalid JSON in examples
- Re: [webrtc-pc] s/outboundrtp/outbound-rtp
Saturday, 19 August 2017
- Re: [webrtc-pc] s/outboundrtp/outbound-rtp
- [webrtc-stats] Dated getStats example.
- Re: [webrtc-pc] s/outboundrtp/outbound-rtp
- [webrtc-pc] Pull Request: s/outboundrtp/outbound-rtp
- [webrtc-pc] Invalid JSON in examples
Friday, 18 August 2017
- [webrtc-pc] Pull Request: duration, interToneGap and canInsertDTMF internal slots of RTCDTMFSender
- Closed: [webrtc-pc] webidl for replaceTrack doesn't allow withTrack to be nullable
- Re: [webrtc-pc] webidl for replaceTrack doesn't allow withTrack to be nullable
- Re: [webrtc-pc] protocol can only contain ASCII
Thursday, 17 August 2017
- [webrtc-pc] Pull Request: getCapabilities behavior with an unsupported value of kind
- [webrtc-pc] Pull Request: Type checking for selectorArg in getStats is unnecessary
- Closed: [webrtc-pc] Section 4.4.4 closed state
- Closed: [webrtc-pc] Section 11.6: Diagram
- Re: [webrtc-pc] Section 11.6: Diagram
- [webrtc-pc] Pull Request: protocol can only contain ASCII
- Re: [webrtc-pc] Section 9.6: protocol type
- Closed: [webrtc-pc] Support for RRID and FEC/RTX RIDs?
- [webrtc-pc] Normative language in lower case
- Re: [webrtc-pc] toJSON Dfn needed
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Make 4.3.1. referenceable
- [webrtc-pc] Pull Request: When DTMF can be sent
- Closed: [webrtc-pc] ResourceInUse exception is not defined
- Re: [webrtc-pc] Should refer to enums in a consistent way
- Closed: [webrtc-pc] Should refer to enums in a consistent way
- Closed: [webrtc-pc] No <dfn> for toJSON in RTCSessionDescription
- Re: [webrtc-pc] Make 4.3.1. referenceable
- Re: [webrtc-pc] Make 4.3.1. referenceable
- Re: [webrtc-pc] At risk text in wrong location
- Re: [webrtc-pc] What happens if RTCDataChannelInit.negotiated is true, but id is absent?
- Re: [webrtc-pc] setParameters does input validation in parallel, and doesn't actually apply parameters?
- Re: [webrtc-pc] rtciceserver: fix represents a turn server
- Re: [webrtc-pc] Have createOffer call addTransceiver() on offerToReceive.
- Re: [webrtc-pc] update current*Description and pending*Description
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] new commits pushed by aboba
- [webrtc-pc] No <dfn> for toJSON in RTCSessionDescription
- Re: [webrtc-stats] RTCMediaStreamTrackStats.concealedAudibleSamples
Wednesday, 16 August 2017
- Re: [webrtc-pc] At risk text in wrong location
- Closed: [webrtc-pc] Editorial: Use consistent syntax for enum values and strings
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-pc] Make 4.3.1. referenceable
- Re: [webrtc-pc] Editorial: Use consistent syntax for enum values and strings
- Re: [webrtc-stats] Is keeping stats around a memory problem?
- [webrtc-pc] Pull Request: Change ResourceInUse to OperationError
- Re: [webrtc-pc] At risk text in wrong location
- Re: [webrtc-pc] Should refer to enums in a consistent way
- Closed: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- [webrtc-stats] Is keeping stats around a memory problem?
Tuesday, 15 August 2017
- Re: [webrtc-pc] What happens if RTCDataChannelInit.negotiated is true, but id is absent?
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-stats] RTCMediaStreamTrackStats.keyFramesReceived
- [webrtc-stats] RTCMediaStreamTrackStats.keyFramesReceived
- Re: [webrtc-pc] Remove event.receiver.
Saturday, 12 August 2017
Friday, 11 August 2017
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- Re: [webrtc-pc] Ensure that "track" events fire before the SRD promise resolves.
- Re: [webrtc-pc] Remove event.receiver.
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
Thursday, 10 August 2017
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- [webrtc-pc] Pull Request: Remove event.receiver.
- Re: [webrtc-pc] Update paragraph that introduces senders/receivers/transceivers.
- Re: [webrtc-pc] Remove duplicate info on method parameters
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] What should happen if a DataChannel "OPEN" message uses priority other than one of the recommended values?
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] removeTrack: does not always cause createOffer to mark media description
- Closed: [webrtc-pc] setDirection needs an internal slot and an algorithm.
- Re: [webrtc-pc] Update paragraph that introduces senders/receivers/transceivers.
- Re: [webrtc-pc] Formalize how createOffer interacts with identity providers.
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Need to define what an "associated" transceiver is.
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Ambiguous connection state when list of transports are empty
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is false (in-band negotiation)?
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] Default values for RTCRtpEncodingParameters
- [webrtc-pc] new commits pushed by aboba
- Closed: [webrtc-pc] We shouldn't rely on the public API to access objects in the specification
- Closed: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
- Re: [webrtc-pc] Ambiguous definition for IdP errors
- Re: [webrtc-pc] Formalize how createOffer interacts with identity providers.
Wednesday, 9 August 2017
- [webrtc-pc] Pull Request: Remove SSRCs from RTCRtpEncodingParameters.
- Re: [webrtc-pc] We shouldn't rely on the public API to access objects in the specification
- Re: [webrtc-pc] Adding defaults for RTCRtpEncodingParameters.active and priority
- [webrtc-pc] Pull Request: Adding defaults for RTCRtpEncodingParameters.active and priority
- [webrtc-pc] Pull Request: Ignore RTCDataChannelInit.id if "negotiated" is false.
- Re: [webrtc-pc] When ICE restarts results in connection to a new endpoint
- [webrtc-pc] Pull Request: Define what an "associated" transceiver is.
- [webrtc-pc] Pull Request: Clarify that ICE states should be "new" if there are no transports.
- [webrtc-pc] Pull Request: Reference [[Direction]] internal slot from addTrack/removeTrack.
- Re: [webrtc-pc] setDirection needs an internal slot and an algorithm.
- Re: [webrtc-pc] setDirection needs an internal slot and an algorithm.
- Closed: [webrtc-pc] setDirection needs an internal slot and an algorithm.
- Re: [webrtc-pc] RTP Media API section should describe how tracks for senders/receivers relate to each other.
- [webrtc-pc] Pull Request: Specify how data channel priority enum is initialized from priority integer
- [webrtc-pc] Pull Request: Formalize how createOffer interacts with identity providers.
- [webrtc-pc] Pull Request: Making getParameters/setParameters matching logic more deterministic.
- Re: [webrtc-pc] Deterministic behavior for transactionId validation
- [webrtc-pc] setParameters does input validation in parallel, and doesn't actually apply parameters?
- [webrtc-pc] Pull Request: Ensure that "track" events fire before the SRD promise resolves.
Tuesday, 8 August 2017
- [webrtc-pc] new commits pushed by dontcallmedom
- Re: [webrtc-stats] Privacy & Security self review
- Re: [webrtc-stats] Privacy & Security self review
- Re: [webrtc-stats] Privacy & Security self review
Monday, 7 August 2017
Saturday, 5 August 2017
- Closed: [webrtc-stats] pliCount typo
- [webrtc-stats] new commits pushed by vr000m
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
Friday, 4 August 2017
- [webrtc-stats] Pull Request: s/Packet Loss Indication/Picture Loss Indication/
- [webrtc-stats] pliCount typo
Thursday, 3 August 2017
- Re: [webrtc-pc] Default identity provider
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-pc] Limiting number of RTCRtpTransceivers
- Re: [webrtc-pc] insertDTMF when transceiver.currentDirection is null
- Re: [webrtc-pc] insertDTMF when transceiver.currentDirection is null
Wednesday, 2 August 2017
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
- Re: [webrtc-pc] Processing Remote MediaStreamTracks should pass on receiver when constructing track event
Tuesday, 1 August 2017
- [webrtc-pc] Constructor for RTCDTMFToneChangeEvent does not validate format of tone
- Re: [webrtc-pc] DTMF tonechange event timing when toneBuffer is modified in between
- Closed: [webrtc-pc] DTMF tonechange event timing when toneBuffer is modified in between
- Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?