W3C

Web Real-Time Communications Working Group Teleconference

22 May 2018

Agenda
Slides

Attendees

Present
Bernard_Aboba, Alexandre_Gouaillard, Youenn_Fablet, Adam_Bergkvist, Angelina_Gambo, Daniel_Burnett, Harald_Alvestrand, Jan-Ivar_Bruaroey, Jianjun_Zhu, Karthik_Budigere_Ramakrishna, Lennart_Grahl, Peter_Thatcher, Sergio_Garcia_Murillo, Taylor_Brandstetter, Varun_Singh, Vivien_Lacourba
Regrets
Stefan
Chair
Harald, Bernard
Scribe
DrAlex

Contents


Slides

[recording in progress]

KITE Update (Dr. Alex)

<vivien> Slides "KITE for webrtc testing 04-2018 Update"

<vivien> KITE project on GitHub

<vivien> DrAlex++ for giving a great presentation and super work on KITE

WebRTC-PC - Issue 1834: Handling of invalid values in sender.setParameters (AdamBe)Topic: WebRTC

<vivien> Issue 1834

decision: we should throw if unsigned

shall we check boundaries?

it s difficult to think about all the possible use case.....

WebRTC-PC - Issue 1839: What should sender.getParameters().codecs return prior to negotiation? (Taylor)

<vivien> Issue 1839

the proposed resolution

seems amenable to the group

a PR should be developed based on that.

WebRTC-PC - Issue 1840: What should receiver.getParameters() return? (Bernard)

<vivien> Issue 1840

proposed solution is accepted, with removal of the red text.

WebRTC-PC - Issue 1852: RTCRtpDecodingParameters (Bernard)

<vivien> Issue 1852

apart from testing, there does not seem to be a lot of use case for receiving simulcast.

The question is then, do we really need 5.1 at all?

mozilla: we don t have interest in receiving simulcast

WebRTC-PC - Issue 1858: What happens when an answerer stops a transceiver that others are “bundled” on? (Taylor)

<vivien> Issue 1858

Since Bundle spec states that you get them all or reject them all. we should respect that (hta)

<hta> Bundle spec text: If the criterium above is fulfilled the answerer can not reject the "m=" section in the answer. The answerer can either reject the whole offer, reject each bundled "m=" section within the BUNDLE group, or keep the "m=" section within the BUNDLE group in the answer and later create an offer where the "m=" section is disabled within the BUNDLE group [Section 7.5.3].

RESOLUTION: we reject both audio and video. PR to come from Harald and Taylor

WebRTC-PC - Issue 1872: sendEncodings in “create an RtpSender” should reflect platform capabilities (Harald)

<vivien> Issue 1872

consensus reached.

<vivien> [meeting adjourned, next meeting on June 19-20 F2F in Stockholm]

Summary of Action Items

Summary of Resolutions

  1. we reject both audio and video. PR to come from Harald and Taylor
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/05/23 09:33:11 $