W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2016

Re: maxHeight and maxWidth

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Sun, 14 Feb 2016 02:14:41 +0000
To: Adam Roach <adam@nostrum.com>
CC: Adam Roach <abr@mozilla.com>, Peter Thatcher <pthatcher@google.com>, Randell Jesup <randell-ietf@jesup.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <D20943F2-6718-446D-8EEE-7A2116A316BD@microsoft.com>
On Feb 13, 2016, at 5:01 PM, Adam Roach <adam@nostrum.com<mailto:adam@nostrum.com>> wrote:

[BA] The major flaw of cloning is the potential for simulcast streams to converge.  That flaw was addressed in RTCRtpEncodingParameters by introducing resolutionScaleDownBy - to ensure the streams remain distinct.

  1.  Bad interaction with congestion control
  2.  Suboptimal browser performance, and
  3.  incompatibility with scalable coding.
  4.   "@@@" above

#1 and #4 (convergence) are symptoms of the same underlying problem - lack of a well defined response to congestion.

The important thing to understand is that these problems are *not* inherent properties of track cloning - they arise because cloning by itself doesn't provide browsers with the information needed to decide how to react to congestion.
Received on Sunday, 14 February 2016 02:15:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:13 UTC