– DRAFT –
WebRTC Feb 2023 Meeting

Recording: https://www.youtube.com/watch?v=LiLi_YZRYSw

Slideset: https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf

CfC Summary 🎞︎

[Slide 9]

WebRTC Stats 🎞︎

issue webrtc-pc#2819 🎞︎

[Slide 12]

Mozilla not much interested in implementing totalRoundTripTime.

Harald: totalRoundTripTime is per candidate, SCTP or RTP round trip time is different.

Varun: smooth RTT is on data channel so different. Would prefer to have both of them.

Tim panton: both RTTs are useful. Would be good to have them both MTI.
… More useful in a future where ICE API gets exposed.

Mozilla: agreeing with responsesReceived and totalRoundTripTime to have the same exposure

Proposal: let's continue discussion on GitHub

Issue #730 🎞︎

[Slide 13]

[Slide 14]

Poll: Proposal A: Define an algorithm in one spec that other specs can point to
… Proposal B: Can that place be MC's exposure of powerEfficient?

Proposal A has some consensus

Proposal B does not have consensus

Proposal: continue discussion, hoping to piggy back on webcodecs discussion

WebRTC Extensions 🎞︎

Issue #141 🎞︎

[Slide 16]

[Slide 17]

[Slide 18]

Agreement for proposal
… API proposal.

Not enough time for error case discussions. Continue discussion on GitHub.

Marking issue as Ready for PR

WebRTC-SVC 🎞︎

Issue #73 🎞︎

[Slide 22]

[Slide 23]

[Slide 24]

[Slide 25]

Proposal: take the PR as is. If further loosening is useful, we can discuss this as a follow-up

MediaCapture and Streams 🎞︎

Issue #927 🎞︎

[Slide 26]

Proposal: Mark issue as Ready for PR.

Issue #928 🎞︎

[Slide 27]

[Slide 28]

No consensus.

Proposal: continue discussion on GitHub.

ICE controller 🎞︎

[Slide 33]

[Slide 34]

[Slide 35]

[Slide 36]

[Slide 37]

[Slide 38]

[Slide 39]

[Slide 40]

Discussions about similarities/differences with FlexICE.

Consensus in the room to make progress in that area.

Add links to requirements and use cases.

Face Detection CfC 🎞︎

[Slide 43]

[Slide 44]

[Slide 45]

Proposal: Bernard to mark issue 1 and 3 as not blocking for the CfC success. Bernard to mark issue 2 as blocking the CfC to succeed. Riju et al to update the PR to resolve issue 2, at which point, it could land.

Video Conference Features 🎞︎

[Slide 46]

Proposal: Status is 'Ready for PR' for the 3 issues. Revive the PR and have a look at the APIs. Land the PR and we will do a CfC.

onConfigurationChange 🎞︎

[Slide 47]

Proposal: Continue discussions on [GitHub](https://github.com/w3c/mediacapture-extensions/pull/83)

auto mute in the case of getDisplayMedia 🎞︎

[Slide 50]

[Slide 51]

[Slide 52]

[Slide 53]

[Slide 54]

Consensus in the room that the use case is good. Some concerns about the API shape.

Proposal: focus discussion on track vs. source and other requirements (do we need to set auto pause dynamically). Then focus on API.