Re: [rtcweb] Support of video with different resolutions

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Wed, 02 January 2013 23:50 UTC

Return-Path: <stefan.lk.hakansson@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50F9A21F843F for <rtcweb@ietfa.amsl.com>; Wed, 2 Jan 2013 15:50:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qny8w1zSo+7Q for <rtcweb@ietfa.amsl.com>; Wed, 2 Jan 2013 15:50:11 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id D4D5B21F843E for <rtcweb@ietf.org>; Wed, 2 Jan 2013 15:50:10 -0800 (PST)
X-AuditID: c1b4fb30-b7f736d0000010de-df-50e4c7b1806a
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 69.F3.04318.1B7C4E05; Thu, 3 Jan 2013 00:50:09 +0100 (CET)
Received: from [153.88.49.5] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Thu, 3 Jan 2013 00:50:00 +0100
Message-ID: <50E4C7A7.4000400@ericsson.com>
Date: Thu, 03 Jan 2013 00:49:59 +0100
From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B06E211@ESESSMB209.ericsson.se> <BLU002-W15E73B3AAD5DBC4D12C5DC93360@phx.gbl> <50E46B45.6080100@ericsson.com> <CA+9kkMA1W=f4yZxd9Q4zcy7u4nxq9ZwDVRfGkQsQMBoCR-HZ8w@mail.gmail.com>
In-Reply-To: <CA+9kkMA1W=f4yZxd9Q4zcy7u4nxq9ZwDVRfGkQsQMBoCR-HZ8w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphluLIzCtJLcpLzFFi42KZGfG3Rnfj8ScBBq+Py1qs/dfObtE4186B yWPnrLvsHkuW/GQKYIrisklJzcksSy3St0vgyvj0uJGpoJ2/4k7jX7YGxv3cXYycHBICJhLv 1vxngbDFJC7cW8/WxcjFISRwklFib/9yJghnBaPExZvXgKo4OHgFtCXWTmMFaWARUJE4cHUn M4jNJhAocf3/LyYQW1QgROL690eMIDavgKDEyZlPwBaICChL7L2ygw3EZhYQlthwsQ0sLizg KPHn+gKoXfcYJWY++g5WxAk0tG/6CUaIBluJC3Ous0DY8hLNW2eDLRYS0JV49/oe6wRGwVlI 9s1C0jILScsCRuZVjOy5iZk56eXmmxiBIXlwy2+DHYyb7osdYpTmYFES5w13vRAgJJCeWJKa nZpakFoUX1Sak1p8iJGJg1OqgTG8U17wVMR1xW09et82sEzWj2bMPCUSLniq+uW5qauU9pXJ Kv240Lby0C39P5Vmy+aX2L1cOlXrWVXd61drVphqrjm9/ee34wdDgk/vMlqcJj3v5ufG53Ka B+Nf1T09YjbzYZxPmeBS62u5N3nKb7x42Dv1iVkv87HX5w2b/R5u+76V79mFv0LFSizFGYmG WsxFxYkAJtTR5RcCAAA=
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Support of video with different resolutions
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 23:50:12 -0000

On 2013-01-02 19:32, Ted Hardie wrote:
> On Wed, Jan 2, 2013 at 9:15 AM, Stefan Håkansson LK
> <stefan.lk.hakansson@ericsson.com
> <mailto:stefan.lk.hakansson@ericsson.com>> wrote:
>
>
>     Another way to look at this is that we already have the following
>     requirement:
>
>     "F11             The browser MUST be able to transmit streams and
>                         data to several peers concurrently.",
>
>     and presumably there would be independent rate control for these
>     streams (since they may experience different network conditions),
>
>     simulcast is in  sense just a special case (the two other peer's are
>     the same endpoint).
>
>
> While I agree that you could model it this way, I think it may be more
> appropriate to treat simulcast as its own case, rather than as a special
> case of the multiple peer.

I agree fully. I was just trying to say that we already have 
requirements covering a large part of what is needed for simulcast, so 
simulcast would not require much more in terms of implementation than 
what we already have agreement on.

But it should be its own case. Apart from the point you make about rate 
control, there is also a tighter requirement on synchronization between 
two versions of the same stream in a simulcast case than what would 
(likely) be needed in a multiple peer case.

>
> Consider this pair of scenarios:
>
> Case one:
> There is one endpoint, Zelda, which is sending media via Turn service to
> two hosts behind the same NAT (let's call them Scott and Edouard).
> There is independent rate control for the streams sending this media.
>
> Case two:
> There is an endpoint, Zelda, which is sending simulcast media to Scott,
> which is using a Turn service and is behind a NAT.
>
> Isn't managing fairness going to be potentially very different between
> case one and case two?
>
> regards,
>
> Ted