[rtcweb] Support of video with different resolutions

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 19 December 2012 15:55 UTC

Return-Path: <christer.holmberg@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 5BF2921F8583 for <rtcweb@ietfa.amsl.com>; Wed, 19 Dec 2012 07:55:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.217
X-Spam-Level:
X-Spam-Status: No, score=-6.217 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, 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 zhZ0q-SUhCBe for <rtcweb@ietfa.amsl.com>; Wed, 19 Dec 2012 07:55:04 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 4029F21F857D for <rtcweb@ietf.org>; Wed, 19 Dec 2012 07:55:04 -0800 (PST)
X-AuditID: c1b4fb25-b7fb26d000006129-37-50d1e357298a
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 7E.67.24873.753E1D05; Wed, 19 Dec 2012 16:55:03 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.43]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.02.0318.004; Wed, 19 Dec 2012 16:55:02 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Support of video with different resolutions
Thread-Index: Ac3eAPnQIvwgLiQDS2yGSHFqvIzF8g==
Date: Wed, 19 Dec 2012 15:55:01 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B06E211@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B06E211ESESSMB209ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+JvjW7444sBBt8mylis/dfO7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujMs/7rIXrLeumNR3kLGBcb5xFyMnh4SAicStT+/YIWwxiQv3 1rN1MXJxCAkcYpQ4O38aO4SzmFFi2ZaXzF2MHBxsAhYS3f+0QRpEBNQlLj+8wA4SFgYatPRy MUTYUuLkl9tMELaexOS3z9hAbBYBVYnJX46BTeEV8Ja4+CMSJMwItPb7qTVg5cwC4hK3nsxn gjhHQGLJnvPMELaoxMvH/1hBWiUEFCWW98tBlOdLbHo+DaycV0BQ4uTMJywTGIVmIZk0C0nZ LCRlEHEdiQW7P7FB2NoSyxa+Zoaxzxx4zIQsvoCRfRUje25iZk56udEmRmDAH9zyW3UH451z IocYpTlYlMR5w10vBAgJpCeWpGanphakFsUXleakFh9iZOLglGpgVNWuUuK5afb6rkTeXclD J6oiPz1P4MzTf9NmWif6PtK87sqc+eL1T5w4di848m7pSsn2LdY+iswpwf+EprndYjyo5xpR zHFu2ZUmw/brj88zf7kuxxkh1P0uUbV4ia6MQk+MaZfkT8sDL776vBefZiE2O32TOdcdnlAh Qcb/exZesfudOuGwEktxRqKhFnNRcSIA03IlJkYCAAA=
Subject: [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, 19 Dec 2012 15:55:06 -0000

Hi,

Section 4.3.3.1 (description of the 'Video conferencing system with
central server' use-case) of the use-case-and-requirements draft
contains a note, describing different mechanisms for providing
video streams with different resolution.

                "Note: This use-case adds requirements on support for fast stream switches F7, on encryption of media and on ability to
                traverse very restrictive FWs. There exist several solutions that enable the server to forward one high resolution and several low
                resolution video streams: a) each browser could send a high resolution, but scalable stream, and the server could send just the
                base layer for the low resolution streams, b) each browser could in a simulcast fashion send one high resolution and one low
                resolution stream, and the server just selects or c) each browser sends just a high resolution stream, the server transcodes into
low resolution streams as required."
If we want to support content sent in different resolutions, the question is whether we need to mandate the browser to support a specific
mechanism.

As shown in the note, there are basically 3 mechanism: SVC, simulcast and "local transcoding".

The "local transcoding" alternative doesn't put any requirements on
browsers. The SVC and simulcast alternatives would.


However, the "local transcoding" alternative will consume lots of resources,

and as far as I know none of the proposed MTI video codecs support SVC.



Some people have indicated support for simulcast in the past, but it would

be nice to get a wider view.

Opinions?

Regards,

Christer