- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Mon, 27 Feb 2023 14:13:20 +0100
- To: "public-webrtc@w3.org" <public-webrtc@w3.org>
The minutes of Feb 21st are available at
https://www.w3.org/2023/02/21-webrtc-minutes.html - thanks Youenn for
scribing.
Dom
WebRTC Feb 2023 Meeting
Attendees
Present
@@@, Bernard, Harald, Jan-Ivar, TimP, Varun, Youenn
Regrets
Dom
Chair
Bernard, HTA, Jan-Ivar
Scribe
youenn
Contents
1. [2]CfC Summary
2. [3]WebRTC Stats
1. [4]issue #2819
2. [5]Issue #730
3. [6]WebRTC Extensions
1. [7]Issue #141
4. [8]WebRTC-SVC
1. [9]Issue #73
5. [10]MediaCapture Extensions
1. [11]Issue #927
2. [12]Issue #928
6. [13]ICE controller
7. [14]Face Detection CfC
8. [15]Video Conference Features
9. [16]onConfigurationChange
10. [17]auto mute in the case of getDisplayMedia
Meeting minutes
Recording: [18]https://www.youtube.com/watch?v=LiLi_YZRYSw
[18] https://www.youtube.com/watch?v=LiLi_YZRYSw
IFRAME:
[19]https://www.youtube.com/embed/LiLi_YZRYSw?enablejsapi=1&rel
=0&modestbranding=1
[19]
https://www.youtube.com/embed/LiLi_YZRYSw?enablejsapi=1&rel=0&modestbranding=1
Slideset: [20]https://lists.w3.org/Archives/Public/www-archive/
2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf
[20]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf
CfC Summary [21]🎞︎
[21] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=180
[22][Slide 9]
[22]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=9
[23]WebRTC Stats [24]🎞︎
[23] https://github.com/w3c/webrtc-stats
[24] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=240
issue [25]#2819 [26]🎞︎
[25] https://github.com/w3c/webrtc-stats/issues/2819
[26] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=240
[27][Slide 12]
[27]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=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 [28]#730 [29]🎞︎
[28] https://github.com/w3c/webrtc-stats/issues/730
[29] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=1140
[30][Slide 13]
[30]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=13
[31][Slide 14]
[31]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=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
[32]WebRTC Extensions [33]🎞︎
[32] https://github.com/w3c/webrtc-extensions
[33] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=2100
Issue [34]#141 [35]🎞︎
[34] https://github.com/w3c/webrtc-extensions/issues/141
[35] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=2100
[36][Slide 16]
[36]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=16
[37][Slide 17]
[37]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=17
[38][Slide 18]
[38]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=18
Agreement for proposal
… API proposal.
Not enough time for error case discussions. Continue discussion
on GitHub.
Marking issue as Ready for PR
[39]WebRTC-SVC [40]🎞︎
[39] https://github.com/w3c/webrtc-svc
[40] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=2400
Issue [41]#73 [42]🎞︎
[41] https://github.com/w3c/webrtc-svc/issues/73
[42] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=2400
[43][Slide 22]
[43]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=22
[44][Slide 23]
[44]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=23
[45][Slide 24]
[45]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=24
[46][Slide 25]
[46]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=25
Proposal: take the PR as is. If further loosening is useful, we
can discuss this as a follow-up
[47]MediaCapture Extensions [48]🎞︎
[47] https://github.com/w3c/mediacapture-extensions
[48] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=2400
Issue [49]#927 [50]🎞︎
[49] https://github.com/w3c/mediacapture-extensions/issues/927
[50] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=2940
[51][Slide 26]
[51]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=26
Proposal: Mark issue as Ready for PR.
Issue [52]#928 [53]🎞︎
[52] https://github.com/w3c/mediacapture-extensions/issues/928
[53] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=3420
[54][Slide 27]
[54]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=27
[55][Slide 28]
[55]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=28
No consensus.
Proposal: continue discussion on GitHub.
ICE controller [56]🎞︎
[56] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=3780
[57][Slide 33]
[57]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=33
[58][Slide 34]
[58]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=34
[59][Slide 35]
[59]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=35
[60][Slide 36]
[60]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=36
[61][Slide 37]
[61]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=37
[62][Slide 38]
[62]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=38
[63][Slide 39]
[63]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=39
[64][Slide 40]
[64]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=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 [65]🎞︎
[65] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=4800
[66][Slide 43]
[66]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=43
[67][Slide 44]
[67]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=44
[68][Slide 45]
[68]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=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 [69]🎞︎
[69] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=5640
[70][Slide 46]
[70]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=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.
[71]onConfigurationChange [72]🎞︎
[71] https://github.com/w3c/mediacapture-extensions/pull/83
[72] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=6180
[73][Slide 47]
[73]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=47
Proposal: Continue discussions on [GitHub]([74]https://
github.com/w3c/mediacapture-extensions/pull/83)
[74] https://github.com/w3c/mediacapture-extensions/pull/83)
auto mute in the case of getDisplayMedia [75]🎞︎
[75] https://www.youtube.com/watch?v=LiLi_YZRYSw#t=6240
[76][Slide 50]
[76]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=50
[77][Slide 51]
[77]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=51
[78][Slide 52]
[78]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=52
[79][Slide 53]
[79]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=53
[80][Slide 54]
[80]
https://lists.w3.org/Archives/Public/www-archive/2023Feb/att-0002/WEBRTCWG-2023-02-21.pdf#page=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.
Received on Monday, 27 February 2023 13:13:24 UTC