Tuesday, 30 August 2016
Monday, 29 August 2016
- [webrtc-pc] Pull Request: Fix WebIDL of RTCDTMFSender
- [webrtc-stats] Merged Pull Request: adding XRBLOCK metrics
- Closed: [webrtc-stats] Importing metrics from the XRBlock discussions / docs to webrtc-stats.
Friday, 26 August 2016
- [webrtc-pc] Pull Request: Issue 714 patch
- RE: Comments needed - procedures for defining stats
- [webrtc-stats] Merged Pull Request: Adding counters to debug ICE problems
- Comments needed - procedures for defining stats
- [webrtc-pc] Handling of invalid characters in the tone buffer is broken
- [webrtc-pc] The sentence "It MUST be at least 30 ms" in the definition of the insertDTMF method seems to be content-free
- [webrtc-pc] duration definition on RTCDTMFSender doesn't quite make sense
- [webrtc-pc] interToneGap definition doesn't quite make sense
- [webrtc-pc] Why does the interToneGap getter return long instead of unsigned long?
- [webrtc-pc] What are the units of interToneGap?
- [webrtc-pc] insertDTMF doesn't define what happens with characters that are not supported
- [webrtc-pc] insertDTMF should normalize input
- [webrtc-pc] RTCDTMFSender needs to inherit from EventTarget
- [webrtc-pc] Why [NoInterfaceObject] for RTCDTMFSender?
Thursday, 25 August 2016
- Re: Decisions reached at the Aug 23 virtual interim
- Re: Decisions reached at the Aug 23 virtual interim
- [webrtc-pc] Pull Request: Adding more detail to the definition of the ICE `disconnected` state.
- Re: Decisions reached at the Aug 23 virtual interim
- [webrtc-pc] Merged Pull Request: Add steps to createAnswer and explicitly specify what is queued
- [webrtc-pc] Merged Pull Request: RTCIdentityProviderGlobalScope needs Exposed attributes
- Closed: [webrtc-pc] Interface RTCIdentityProviderGlobalScope should be defined with [Global, Exposed]
- [webrtc-pc] Merged Pull Request: Remove closed check from addIceCandidate steps (covered by enqueue steps)
- [webrtc-pc] Merged Pull Request: Add steps to createOffer and explicitly specify what is queued
- Closed: [webrtc-pc] createOffer should have steps that explicitly states what is queued
- [webrtc-pc] Specify how an RTCRtpSender should treat an ended track
- [webrtc-pc] Merged Pull Request: replaceTrack with the previous one as ended
- [webrtc-pc] Closed Pull Request: STUN/TURN OAuth token auth parameter handover
- [webrtc-pc] Handling of simulcast errors
- [webrtc-pc] Merged Pull Request: Clarification on receipt of multiple RTP encodings
- [webrtc-pc] Pull Request: Remove closed check from addIceCandidate steps (covered by enqueue steps)
- [webrtc-pc] addIceCandidate checks for closed state twice (changes introduced by #744)
- Decisions reached at the Aug 23 virtual interim
Wednesday, 24 August 2016
- What happens when creating a data channel with an out-of-range stream ID? (Issue 746)
- [minutes] WebRTC Virtual Interim 23 August 2016
- [webrtc-pc] Closed Pull Request: Meaning of "Liveness checks have failed"
Tuesday, 23 August 2016
- [webrtc-pc] Figure out backward-compatible way to indicate ufrag+mid on end-of-candidates
- [webrtc-pc] Pull Request: Clarification on receipt of multiple RTP encodings
- [webrtc-pc] Pull Request: replaceTrack with the previous one as ended
- [webrtc-pc] Pull Request: Support ufrag in IceCandidate and end of IceCandidate indicator
- [webrtc-pc] Pull Request: Integrate queueing into the setLocal/RemoteDescription steps
- [webrtc-pc] setLocal/RemoteDescription should explicitly state which steps that are queued
- [webrtc-pc] Merged Pull Request: Update list of sections from JSEP
- Reminder: virtual interim meeting later today
Monday, 22 August 2016
- Re: Issue 714: STUN/TURN OAuth token auth parameter handover
- Closed: [webrtc-pc] What is the appropriate behavior when a new track is added using an previously used msid?
- [webrtc-pc] What is the appropriate behavior when a new track is added using and old trackid?
- [webrtc-pc] Pull Request: Update list of sections from JSEP
- [webrtc-pc] Pull Request: Add steps to createAnswer and explicitly specify what is queued
- [webrtc-pc] createAnswer should have steps that explicitly states what is queued
- [webrtc-pc] Pull Request: RTCIdentityProviderGlobalScope needs Exposed attributes
- Closed: [webrtc-pc] DTLS1.2 negotiation failure on webrtc using firefox5.0 version
Friday, 19 August 2016
- [webrtc-pc] DTLS1.2 negotiation failure on webrtc using firefox5.0 version
- [webrtc-pc] Interface RTCIdentityProviderGlobalScope should be defined with [Global, Exposed]
- Re: Issue 714: STUN/TURN OAuth token auth parameter handover
- [webrtc-pc] Merged Pull Request: Specify the synchronous and queued steps for addIceCandidate (ver 2) (issue #600)
Thursday, 18 August 2016
- Closed: [webrtc-pc] Need JSEP reference for general RTCPeerConnection description
- Re: Issue 714: STUN/TURN OAuth token auth parameter handover
- [webrtc-pc] Merged Pull Request: Fix for issue 654
- [webrtc-pc] Merged Pull Request: Reference to RTCRtpReceiver.stop()
- [webrtc-pc] Merged Pull Request: Fix target of links for addIceCandidate
- Closed: [webrtc-pc] addIceCandidate link in IDL links to legacy description
- [webrtc-pc] Merged Pull Request: issue 566: replace set of senders/receivers/transceivers with algorithms
- Closed: [webrtc-pc] Link addIceCandidate to JSEP for applying ICE candidate
- [webrtc-pc] Pull Request: Fix for issue 654
Wednesday, 17 August 2016
- [webrtc-pc] Need to specify what happens if `createDataChannel` is called with an invalid ID
- [webrtc-pc] Pull Request: Add steps to createOffer and explicitly specify what is queued
- [webrtc-pc] createOffer should have steps that explicitly states what is queued
Tuesday, 16 August 2016
- [webrtc-pc] Pull Request: Reference to RTCRtpReceiver.stop()
- August 23rd at 20:00 UTC slot picked for next WebRTC virtual interim (was Slot picked for next WebRTC virtual interim: August 28th at 20:00 UTC)
- [webrtc-pc] Pull Request: Fix target of links for addIceCandidate
- Slot picked for next WebRTC virtual interim: August 28th at 20:00 UTC
- [webrtc-pc] addIceCandidate link in IDL links to legacy description
- Re: [webrtc-pc] Merged Pull Request: Improve error handling for IdP proxy interactions
- Re: [webrtc-pc] Merged Pull Request: Improve error handling for IdP proxy interactions
Monday, 15 August 2016
- Re: Issue 685: Update JSEP reference for receipt of multiple RTP encodings
- Re: Issue 714: STUN/TURN OAuth token auth parameter handover
- Re: Issue 732: replaceTrack with the previous one as ended
- Reminder: register for TPAC
- [webrtc-pc] Pull Request: issue 714 patch
Friday, 12 August 2016
Thursday, 11 August 2016
- Closed: [webrtc-pc] Fob on RTCRtpEncodingParameters to turn on and off sending CN / DTX
- Closed: [webrtc-pc] RTX/RED/FEC handling
- [webrtc-pc] Merged Pull Request: Fix mistakes in examples.
- [webrtc-pc] Merged Pull Request: RTCRtpEncodingParameters attribute to turn on/off sending CN / DTX
- [webrtc-pc] Merged Pull Request: Clarification on RTX in Codec Capabilities/Parameters
- [webrtc-pc] Merged Pull Request: The IdP environment can be spoofed
- Closed: [webrtc-pc] Assurance that requests to IdP proxy originate from the user agent
- [webrtc-pc] Merged Pull Request: Improve error handling for IdP proxy interactions
- Closed: [webrtc-pc] What to do with an RTCIdentityProvider that returns rubbish
- [webrtc-pc] Pull Request: issue 566: replace set of senders/receivers/transceivers with algorithms
- Closed: [webrtc-pc] Automatically open data channel when connections are established
- Closed: [webrtc-pc] ICE Candidate should have accessors for protocol-relevant items
Wednesday, 10 August 2016
- [webrtc-pc] Pull Request: Getting the fingerprint of a RTCCertificate
- [webrtc-pc] Closed Pull Request: Fix mistakes in examples.
- [webrtc-pc] Closed Pull Request: Fix mistakes in examples.
- [webrtc-pc] Pull Request: Fix mistakes in examples.
- [webrtc-pc] Pull Request: Fix mistakes in examples.
Tuesday, 9 August 2016
Monday, 8 August 2016
Friday, 5 August 2016
- [webrtc-pc] Automatically open data channel when connections are established
- [webrtc-pc] Closed Pull Request: Tidy
- [webrtc-pc] Closed Pull Request: RTCRtpEncodingParameters attribute to turn on/off sending CN / DTX
- [webrtc-pc] Pull Request: RTCRtpEncodingParameters attribute to turn on/off sending CN / DTX
- [webrtc-pc] Closed Pull Request: Clarification on RTX in Codec Capabilities/Parameters
- [webrtc-pc] Pull Request: Clarification on RTX in Codec Capabilities/Parameters
Thursday, 4 August 2016
- [webrtc-pc] Merged Pull Request: Use https links
- [webrtc-pc] Merged Pull Request: Revised WebRTC 1.0 RTCIceTransportState transition diagram
- [webrtc-pc] Merged Pull Request: fingerpriting
- [webrtc-pc] Closed Pull Request: Add RTCRtpCodecRtxParameters dictionary (related to #548)
- [webrtc-pc] Merged Pull Request: Missing destruction sequence
- [webrtc-pc] replaceTrack with the previous one as ended
Wednesday, 3 August 2016
- [webrtc-stats] RTCCertificateStats doesn't have a RTCStatsType value
- [webrtc-pc] Pull Request: Use https links