Wednesday, 31 May 2017
- [webrtc-pc] Pull Request: Move Section 4.4 State Definitions before 4.3 RTCPeerConnection
 - [webrtc-pc] Section 4.4: State Definitions
 - [webrtc-pc] Pull Request: Section 4.2.6: remove informative sentences
 - [webrtc-pc] Pull Request: intertone gap maximum
 - [webrtc-pc] Pull Request: WEBRTC-LOGINDONE
 - [webrtc-pc] Section 11.6: Diagram
 - [webrtc-pc] Section 11: Examples
 - [webrtc-pc] Section 10.4.1: target peerIdentity
 - [webrtc-pc] Section 4.2.3 (createOffer)
 - [webrtc-pc] Section 4.3.1
 - [webrtc-pc] Section 4.2.6
 - [webrtc-pc] pc.removeTrack(receiver) should throw an error.
 - [webrtc-pc] Section 4.2.2
 - [webrtc-pc] Events not bubbling
 - [webrtc-pc] Inconsistencies in Asynchronous Task Queueing
 - [webrtc-pc] Pull Request: [respec-updater] New ReSpec release
 - [webrtc-pc] Missing steps on handling direction argument in addTransceiver
 - Re: Review of WebRC PC Spec
 
Tuesday, 30 May 2017
- Review of WebRC PC Spec
 - Weekly github digest (WebRTC WG specifications)
 - [webrtc-pc] Pull Request: Remove "at-risk" marking from Identity
 
Monday, 29 May 2017
- [webrtc-pc] Spec has reference to WEBIDL-1 and WEBIDL
 - [webrtc-pc] Need to resolve if we reference STUn or STUnbis
 - [webrtc-pc] Failure of transmission of isolated stream
 - [webrtc-pc] Clarity in section 9.7 example 11
 - [webrtc-pc] Lifetime of pc.PeerIdentity
 - [webrtc-pc] DTFM payout algorithm does not specify comma handling
 - [webrtc-pc] Does insertDTMF append to or replace the current tone buffer
 - [webrtc-pc] How to find what keyGenAlgorithm values the browser supports?
 - [webrtc-pc] MTI specification of crypto for certs
 - [webrtc-pc] Section 4.4.4 closed state
 - [webrtc-pc] Error for when peer identity is wrong
 - [webrtc-pc] lastOffer on the PC
 - [webrtc-pc] invalid SDP for the state
 - [webrtc-pc] Pull Request: clean up logic to support removal of RTCP mux "negotiated" value
 - [webrtc-pc] Pull Request: remove note about identity is at risk
 
Sunday, 28 May 2017
Friday, 26 May 2017
Thursday, 25 May 2017
- [webrtc-pc] RTCDtlsTransport: why is there no getLocalCertificates?
 - [webrtc-pc] maximum bandwidth: TIAS or AS?
 - [webrtc-pc] setParameters woes
 - [webrtc-pc] Pull Request: RTP/RTCP mux -> RTCP mux
 - [webrtc-pc] processing remote MediaStreamTracks -- stopping the transceiver to reject them
 - [webrtc-pc] empty attribute descriptions in ice description
 - [webrtc-pc] `parameters` not defined in `setParameters` algotrithm
 
Wednesday, 24 May 2017
- [webrtc-pc] editorial: move video cropping algorithm from rtpsender interface section
 - Announcing date and time for June VI
 - [webrtc-pc] rtcsessiondescription: attributes are not mutable
 - [webrtc-pc] rtp media api: when is a receiver created
 - [webrtc-pc] editorial: media api introduction
 - [webrtc-pc] Pull Request: RTCIceConnectionEventInit: url is nullable
 - [webrtc-pc] which ice-tcp types will a browser emit?
 - [webrtc-pc] [[associated MediaStreams]] and [[send encodings]] internal slots for RTCRtpSender are not used
 - [webrtc-pc] legacy error handling
 - [webrtc-pc] setRemoteDescription error when rtcpMuxPolicy=negotiate is not implemented
 
Tuesday, 23 May 2017
- Re: "pranswer" status (or get rid of it)
 - [webrtc-pc] API to access certificate of remote side
 - Weekly github digest (WebRTC WG specifications)
 
Monday, 22 May 2017
- Re: "pranswer" status (or get rid of it)
 - RE: "pranswer" status (or get rid of it)
 - [webrtc-pc] Pull Request: move "set a configuration" algorithm
 - "pranswer" status (or get rid of it)
 - [webrtc-pc] RTCPeerConnectionIceEvent constructor validation
 
Sunday, 21 May 2017
Saturday, 20 May 2017
Friday, 19 May 2017
- [webrtc-pc] Pull Request: Add detailed steps for constructing RTCIceCandidate
 - [webrtc-pc] Confusion on currentRemoteDescription.sdp need not match remoteDescription.sdp
 - [webrtc-pc] addIceCandidate may add ice candidate to the wrong remote description
 - [webrtc-pc] Pull Request: Removing WebIDL defaults for various RTP parameters.
 
Thursday, 18 May 2017
Wednesday, 17 May 2017
- [webrtc-pc] Invalid value for maxBitrate
 - [webrtc-pc] Pull Request: operation: add subsections
 - [webrtc-pc] Pull Request: intro: increase scope to general p2p
 - [webrtc-pc] Pull Request: reorder createOffer/createAnswer paragraphs
 - [webrtc-pc] Default ufrag for addIceCandidate when there are different ufrags in SDP
 - [webrtc-pc] Race condition in enqueue an operation
 - [webrtc-pc] Missing References to JSEP spec
 - [webrtc-pc] Clarify addIceCandidate behavior when adding candidate after end of candidate
 - RE: Review of webrtc-pc (deadline: May 31st)
 
Tuesday, 16 May 2017
Monday, 15 May 2017
- [webrtc-pc] Define the unit used for framerates and maxframerates
 - New webrtc-pc Editor's draft (v20170515)
 
Sunday, 14 May 2017
- [webrtc-pc] addIceCandidate end of candidates woes
 - [webrtc-pc] Can we directly link to WebRTC-Stats for RTCStatsType?
 
Saturday, 13 May 2017
Friday, 12 May 2017
- [webrtc-pc] ufrag vs usernameFragment
 - Doodle for June WebRTC Virtual Interim
 - CR Exit criteria again (was Re: Notes from May 2nd VI)
 - [webrtc-stats] Audio/Video sync follow-up
 - [webrtc-pc] Pull Request: Throw error if data channel's buffer is filled, rather than closing.
 - [webrtc-pc] Pull Request: Add bufferSize attribute to RTCDataChannel.
 
Thursday, 11 May 2017
- [webrtc-pc] Setting a remote description may cause discontinuity due to codec switching.
 - [webrtc-pc] transceiver.direction isn't initialized.
 - [webrtc-pc] Sending data channel messages > maxMessageSize
 - [webrtc-stats] Pull Request: Adding audio level stat that can be used to compute averages.
 - [webrtc-stats] Need some way of getting an averaged audio level stat
 - [webrtc-pc] setDirection needs an internal slot and an algorithm.
 - [webrtc-pc] Need to identify if changes affect JSEP or MSID specs
 - [webrtc-pc] editorial: move "set a configuration" to operation section
 
Wednesday, 10 May 2017
- [webrtc-pc] RTCPeerConnectionIceEvent parameter: RTCPeerConnectionIceEventInit eventInitDict is optional
 - [webrtc-pc] RTCIceServer "represents a TURN server"
 - [webrtc-pc] Stream IDs MUST be generated according to mediacapture-main, but webrtc-pc contradicts this
 - [webrtc-pc] iceCandidatePoolSize type mismatch (minor spec bug)
 - [webrtc-stats] Issues raised in TAG review
 - [webrtc-stats] Pull Request: jitter buffer delay added to media stream tracks
 - [webrtc-stats] Pull Request: Issue 132/mediastreamtrack priority
 - [webrtc-stats] Pull Request: timestamps need for #61
 - [webrtc-stats] Pull Request: Add paragraph about timestamp and reference DOMHighResTimeStamp
 - [webrtc-stats] Pull Request: definition for 'framesPerSecond'
 - [webrtc-stats] Pull Request: RTCMediaStreamTrackStats.voiceActivityFlag added.
 - [webrtc-stats] Pull Request: RTCMediaStreamTrackStats.audioLevel: Reference RTCRtpSynchronizationSource
 - [webrtc-stats] Pull Request: packetsRetransmitted and bytesRetransmitted to RTCSentRTPStreamStats
 - [webrtc-stats] Pull Request: Issue 178/packets discarded on send
 - [webrtc-pc] editorial: currentLocalDescription getting updates with candidates
 
Tuesday, 9 May 2017
- [webrtc-pc] update the ice gathering state: firing icecandidate with null is a legacy hack
 - [webrtc-pc] editorial: add subsubsubsections to operation description?
 - [webrtc-pc] editorial: 4.3.1 Operation "settled" is not defined
 - [webrtc-pc] Pull Request: editorial: introduction: explain signaling process
 - [webrtc-pc] Pull Request: createAnswer: disambiguate blob
 - [webrtc-pc] editorial: terminology of Blob and "blob of SDP"
 - [webrtc-pc] editorial: p2p data transfer is a facet of video conferencing
 - [webrtc-pc] Race condition between createOffer and setIdentityProvider
 - Weekly github digest (WebRTC WG specifications)
 
Monday, 8 May 2017
- [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead
 - [webrtc-pc] Pull Request: maxFramerate type double
 - New webrtc-pc Editor's draft (v20170508)
 - [webrtc-pc] Are camelCase codec parameters useful at all?
 - [webrtc-pc] Need to describe when ICE and DTLS transport objects are created/changed
 - [webrtc-pc] Some JSEP "applying a description" steps can't occur in parallel.
 - [webrtc-pc] Pull Request: Adding more detail to RTCIceCandidatePolicy enum descriptions.
 - [webrtc-pc] Pull Request: Expanding RTCPeerConnection introduction.
 - [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC
 
Sunday, 7 May 2017
- [webrtc-pc] degradationPreference shouldn't have a default at the WebIDL level
 - [webrtc-pc] Pull Request: Adding note about legacy `createAnswer` not supporting options dict.
 
Saturday, 6 May 2017
- Re: Notes from May 2nd VI
 - Re: Notes from May 2nd VI
 - [webrtc-pc] Pull Request: revert PR#1108
 - [webrtc-pc] Pull Request: RTCIceCandidate: add component
 
Friday, 5 May 2017
- [webrtc-pc] RTP Media API section should describe how tracks for senders/receivers relate to each other.
 - [webrtc-pc] Pull Request: Remove paragraph about removeTrack causing track to be ended remotely.
 - Re: On the way to CR for webrtc-pc
 - [webrtc-pc] RTCIceCandidate: component attribute missing?
 - [webrtc-pc] RTCIceCandidate constructor should not require sdpMid/sdpMLineIndex
 - [webrtc-pc] Lack of validation in RTCIceCandidate constructor
 
Thursday, 4 May 2017
- [webrtc-pc] Pull Request: Update RTCCertificate ref to get serializer from WebIDL
 - [webrtc-pc] type of maxFramerate
 - [webrtc-pc] Do we need a "trackremoved" event?
 - [webrtc-pc] Pull Request: Remove getAlgorithm()
 - [webrtc-pc] Do we need getAlgorithm() at all?
 - [webrtc-pc] Section 12: Missing WebIDL in RTCError
 - Re: Notes from May 2nd VI
 - Re: Process for "feature at risk" designation
 - RE: Requirements review notes
 - Re: Process for "feature at risk" designation
 - Re: Process for "feature at risk" designation
 - Process for "feature at risk" designation
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Re: Requirements review notes
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 
Wednesday, 3 May 2017
- Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - [webrtc-pc] Pull Request: Move Issue 1 text to a note
 - [webrtc-pc] Issue 1: Key shortening
 - Requirements review notes
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - [webrtc-pc] The "set an RTCSessionDescription" algorithm is unreferenced
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Notes from May 2nd VI
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 
Tuesday, 2 May 2017
- Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property
 - Weekly github digest (WebRTC WG specifications)
 - [webrtc-pc] legacy createAnswer: support for answerOptions?
 - Reminder: Virtual Interim on May 2, 2017 at 15:00 UTC