W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2019

Re: [webrtc-pc] `ssrc` in `RTCRtpEncodingParameters` is inconsistent with ORTC (#1174)

From: Iñaki Baz Castillo via GitHub <sysbot+gh@w3.org>
Date: Tue, 05 Mar 2019 11:39:56 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-469648951-1551785995-sysbot+gh@w3.org>
> I have to disagree here, you will have to add headers (transportwide-cc,abs-send-time) and remove header extensions (client-to-mixer-audio-level/rids) negotiated between SFU and peers anyway, or change the ids (from 1 byte to 2 byte headers). If you expect to do a zero copy of the in buffer to the output buffer I think you are doing it wrong IMHO.

Well, of course I'll do. But the point here is that people is complaining because the "new" MID/RID mechanism breaks their working SFU logic (that depend on signaled `a=ssrc` values) even if Firefox implements it for long. Forcing them to also implement RTP header extension rewriting/addition/removal do not seem a comfortable solution. First of all, because they may not need it if they don't implement `transport-cc` and happily assume 1-byte heder extensions.

Also, removing client-to-mixer-audio-level/rids header extensions is not needed. It's easier to just not negotiate them at SDP level with the receivers.

GitHub Notification of comment by ibc
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1174#issuecomment-469648951 using your GitHub account
Received on Tuesday, 5 March 2019 11:39:58 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC