Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-cases-and-requirements-10

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Fri, 25 January 2013 13:11 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 E879421F866D for <rtcweb@ietfa.amsl.com>; Fri, 25 Jan 2013 05:11:13 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6X0gC4MjL+51 for <rtcweb@ietfa.amsl.com>; Fri, 25 Jan 2013 05:11:13 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id F294321F844F for <rtcweb@ietf.org>; Fri, 25 Jan 2013 05:11:12 -0800 (PST)
X-AuditID: c1b4fb25-b7f366d000004d10-67-5102846f656d
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 1F.F1.19728.F6482015; Fri, 25 Jan 2013 14:11:11 +0100 (CET)
Received: from [150.132.141.90] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Fri, 25 Jan 2013 14:11:11 +0100
Message-ID: <5102846E.7070805@ericsson.com>
Date: Fri, 25 Jan 2013 14:11:10 +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/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <50F97303.4070906@ericsson.com>
In-Reply-To: <50F97303.4070906@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHJMWRmVeSWpSXmKPExsUyM+JvrW5+C1OgwaE96hZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoErY+aF3cwFZwUqth7qYm9g3MPbxcjJISFgIvH1ziN2CFtM4sK9 9WxdjFwcQgInGSXuL7rABOGsYZR41bsDrIpXQFvidO9RZhCbRUBV4svT1UwgNptAoMT1/7/A bFGBKIn3V5uYIeoFJU7OfMICYosICEtsfdULViMsECyxcuIXRhBbCGjmpO33gWwODk4BHYmj V0NBwswCthIX5lxngbDlJZq3zmaGKNeVePf6HusERoFZSDbMQtIyC0nLAkbmVYzsuYmZOenl RpsYgWF2cMtv1R2Md86JHGKU5mBREucNd70QICSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoGR 2ZVtzsRFq3ax7LihpaSSJ+7LKxp+PHmaZolZ6U6XoP+NPv5O13++rZ5/O+BxRt+r0LRZMh+k zROvsmvcUV0XLl+xl9VXxNVPz6nzbeINLq1S63WS+TtPdMg9X3dLZ88TiUOXxWJfzDw6/2mc 0OMJj1deVTOZeitA5pFTn1Cw+srfF6yPs2QosRRnJBpqMRcVJwIAgoiTKwECAAA=
Subject: Re: [rtcweb] WG Last Call: draft-ietf-rtcweb-use-cases-and-requirements-10
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: Fri, 25 Jan 2013 13:11:14 -0000

On 2013-01-18 17:06, Magnus Westerlund wrote:
> WG,
>
> I would here by like to announce a two week WG last call that ends on
> the 1st of February.
>
> Document is available here:
>
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/

As discussed in an earlier thread, I think that it should be clarified 
how the streams for the small/big video displays in use-case 4.3.3 are 
generated.

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 form 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 one solution that must be supported, and then derive the 
corresponding requirements.

As said before, I am a proponent for simulcast as solution to this use-case.

Stefan
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>