Re: [AVT] SVC and multiscreen

Roni Even <Even.roni@huawei.com> Sun, 13 December 2009 21:10 UTC

Return-Path: <Even.roni@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 425CB3A6937 for <avt@core3.amsl.com>; Sun, 13 Dec 2009 13:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.435
X-Spam-Level:
X-Spam-Status: No, score=0.435 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rEa5TOVkZsGW for <avt@core3.amsl.com>; Sun, 13 Dec 2009 13:10:28 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 5212C3A6915 for <avt@ietf.org>; Sun, 13 Dec 2009 13:10:28 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KUM005TO04T3N@szxga02-in.huawei.com> for avt@ietf.org; Mon, 14 Dec 2009 05:10:05 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KUM00I7T04TV5@szxga02-in.huawei.com> for avt@ietf.org; Mon, 14 Dec 2009 05:10:05 +0800 (CST)
Received: from windows8d787f9 (bzq-82-81-138-101.red.bezeqint.net [82.81.138.101]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KUM00B0604M9O@szxml01-in.huawei.com>; Mon, 14 Dec 2009 05:10:05 +0800 (CST)
Date: Sun, 13 Dec 2009 23:06:54 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <BLU0-SMTP572C46234E25BC9F90BC30D88A0@phx.gbl>
To: 'Tom Taylor' <tom111.taylor@bell.net>, 'IETF AVT WG' <avt@ietf.org>
Message-id: <019b01ca7c38$36dc4ae0$a494e0a0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-us
Content-transfer-encoding: 7bit
Thread-index: Acp8E/f5pOZpjEfjTxWTmGe87kI10AAI53PA
References: <BLU0-SMTP572C46234E25BC9F90BC30D88A0@phx.gbl>
Subject: Re: [AVT] SVC and multiscreen
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Dec 2009 21:10:31 -0000

Hi,
The current text in the draft describe a possible use case for SVC and does
not add any value to the SVC draft.
I got some impression that the authors would like to describe such
application where the receiver will be able to request specific layers
compositions using some parameters which are not specified, this is not for
SVC but should be a separate draft that may expand the image attribute draft
in MMUSIC.

Roni Even as individual



> -----Original Message-----
> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
> Tom Taylor
> Sent: Sunday, December 13, 2009 6:47 PM
> To: IETF AVT WG
> Subject: [AVT] SVC and multiscreen
> 
> Given that SVC hasn't quite been put to bed, I would like to draw the
> WG's
> attention to draft-nanwang-avt-svc-multiscreen-00.txt.
> 
> The original intention of the author was that this text be added to the
> SVC
> draft. Could I ask for comment from the WG on whether that is sensible
> or
> whether it is better to develop a separate document? Further: how does
> this
> relate to draft-wang-avt-rtp-mvc, which was agreed to be a WG item at
> the Dublin
> meeting once the SVC work was done?
> 
> Tom Taylor
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt