[rtcweb] WG last call comments on use-case and requirement document, “multiple resolutions”

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Mon, 29 April 2013 14:05 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 C2AFA21F9DD8 for <rtcweb@ietfa.amsl.com>; Mon, 29 Apr 2013 07:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level:
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HtQ9ANSoTl72 for <rtcweb@ietfa.amsl.com>; Mon, 29 Apr 2013 07:05:49 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2036421F9DC8 for <rtcweb@ietf.org>; Mon, 29 Apr 2013 07:05:47 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f316d0000028db-f7-517e7e3b60d9
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 1A.98.10459.B3E7E715; Mon, 29 Apr 2013 16:05:47 +0200 (CEST)
Received: from [150.132.141.119] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.279.1; Mon, 29 Apr 2013 16:05:47 +0200
Message-ID: <517E7E3A.3090300@ericsson.com>
Date: Mon, 29 Apr 2013 16:05:46 +0200
From: =?windows-1252?Q?Stefan_H=E5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCJMWRmVeSWpSXmKPExsUyM+Jvra51XV2gwYFDghZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoErY82jtWwFh3kqNh2/ytTAOJ2ri5GTQ0LARGLpu9lsELaYxIV7 64FsLg4hgVOMEhf+vWMESQgJrGWUOL3YBMTmFdCWeHhzKROIzSKgKrFwezNQAwcHm0CwxIwp RiBhUYEoiX9vdzNClAtKnJz5hAXEFhFQl7j88AI7yHxhgQWMEqtftoP1MgvYSzzYWgZSwywg L7H97RxmiLW6Eu9e32OdwMg3C8moWQgds5B0LGBkXsXInpuYmZNebriJERgyB7f81t3BeOqc yCFGaQ4WJXHe6VKVgUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYp14+PIVfb+fNuNcWgjuC FizsneBbJVPW/Mk9/HFPeVrbtPti7OWZX05PsFu+4bNVf5lgIbv+N3GfwmtN89rdDY65nXU+ 8rrrgHxNuB3vt8dndszeJtso5t4bvvXB/OYEnbnHzjXvTFR0lZ78oubwfK/fE6qdgg75Jl02 Yt275M2OFdPmShjtVGIpzkg01GIuKk4EANr8OtvnAQAA
Subject: [rtcweb] =?windows-1252?q?WG_last_call_comments_on_use-case_and_r?= =?windows-1252?q?equirement_document=2C_=93multiple_resolutions=94?=
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: Mon, 29 Apr 2013 14:05:49 -0000

This relates to the comments to the WG last call of the use-cases and 
requirements document [1].

There is a use-case (4.3.3) detailing the use of multiple resolutions of 
the data from one single source, with three options on how to meet that 
mentioned (scalable codec, simulcast and transcoding).

There has been a request ([2]) to clarify which method(s) that should be 
mandatory, but no conclusion yet.

To recap, the use case is about a multiparty video (and audio of course) 
communication session using a central node. At the screen of each 
endpoint/user, one video is displayed on a large surface, with other 
videos are shown as (live) thumbnails.

Which video to show at the large display surface is depending on speech 
activity; the video from the endpoint with currently talking user(s) is 
shown on the large surface - and this will usually change frequently 
during the session. This selection is handled by the central node which 
has access to all video and audio streams.

I think this is a quite common model, used by many services.
The current draft list three ways to support this use-case (use scalable 
video codecs, transcode in the central node, or use simulcast), but 
there are no requirements that back this up. We should pick at least one 
solution that must be supported, and then derive the corresponding 
requirements.

I am a proponent for simulcast as solution for this use-case.

Stefan

[1] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06136.html

[2] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06157.html