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

Re: [webrtc-pc] Control surface for header extensions (#2243)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Wed, 31 Jul 2019 08:15:49 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-516747051-1564560948-sysbot+gh@w3.org>
Example: Chrome and Firefox support [abs-send-time](https://webrtc.org/experiments/rtp-hdrext/abs-send-time/) which allow receive-side congestion control by looking at the send-side timestamp. Chrome also supports [transport-wide-cc-extensions-01](https://tools.ietf.org/html/draft-holmer-rmcat-transport-wide-cc-extensions-01) which allows for send-side congestion control when used together with RTCP feedback mechanisms.

Related questions:
- How to control what is negotiated?
- Once negotiated, how to control which header extension-specific features are enabled?

In the case of congestion control, we might want to negotiate both for compatibility, but depending on application we may want to turn one of the congestion controls on or off if both are successfully negotiated.

In today's implementation, if both extensions are negotiated, it will use transport-wide-cc-extensions-01 and not abs-send-time. There may be use cases where we want to use both, and in other cases it would be superfluous to use both at the same time.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2243#issuecomment-516747051 using your GitHub account
Received on Wednesday, 31 July 2019 08:15:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:26 UTC