[AVTCORE] maximum receive video resolution -open issue

"Roni Even" <ron.even.tlv@gmail.com> Tue, 27 May 2014 08:13 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7A151A03E3; Tue, 27 May 2014 01:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ud1k4hU1Y4Sf; Tue, 27 May 2014 01:13:09 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B85CF1A03DE; Tue, 27 May 2014 01:13:07 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id u56so8998745wes.37 for <multiple recipients>; Tue, 27 May 2014 01:13:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=1/3AyyPcL3RXRiF3K0lM9oLSN/7vfhmhFL8i3CjlHsc=; b=BOiuZAs9QwKHUBfplv4gAGiBeDF8HBtYkCAIAN9ZXKHs9xYMtuNiDnsP6kuj9DLGsv MF40bhsr2OkOmrlixZQBn+Xaz4Bl6DzWGf+1lbwaGGH2ElOS2/tsBAz+sgVKIa+v/Fcq hnzOLgpLSXbPAStk9YjGOuUn2jdtGZldx6CTzQ+9OmHpHEPbFGyPNV7EBAlalZF2zHN7 HP3QnH6f9+gp0tI3QctHPCpcPJ56D6jnu9RBTPayp3U2V1aUXAcqQM+PTlQpqqLPK4pm 04R6l/lXacBxale6E53CRBpPHNEA0PfJrQHAPvEWo+q90IG3mw8W2gBfxU3TiustrnbA Wfzg==
X-Received: by 10.180.72.136 with SMTP id d8mr34813539wiv.36.1401178383336; Tue, 27 May 2014 01:13:03 -0700 (PDT)
Received: from RoniE ([109.67.104.144]) by mx.google.com with ESMTPSA id f6sm6307365wiy.19.2014.05.27.01.13.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 May 2014 01:13:02 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: payload@ietf.org
Date: Tue, 27 May 2014 11:12:56 +0300
Message-ID: <033b01cf7983$78f591f0$6ae0b5d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_033C_01CF799C.9E436630"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac95g3Q7dDyBSvZrRoWjbmxkG++FEQ==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/bk74z-RfEgL1trOHsD9NGaUlcrw
Cc: avt@ietf.org
Subject: [AVTCORE] maximum receive video resolution -open issue
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 27 May 2014 08:13:11 -0000

Hi,

We need to get feedback on this topic ( posting also to AVTcore to get
larger exposure)

At the IETF 89 meeting the chairs summarized the topic as follows:

 

Payload specific parameters for specifying video resolution in SDP in
http://tools.ietf.org/id/draft-nandakumar-payload-sdp-max-video-resolution-0
0.txt was presented by Suhas Nandakumar. 

 

The slides are is
https://tools.ietf.org/agenda/89/slides/slides-89-payload-5.pdf . 

 

The proposal is to provide a codec agnostic way for a receiver to signal
maximum receive video resolution. 

 

The feeling is that there is a need for this but need use cases. There was
disagreement whether to use codec agnostics or codec specifics. 

 

Action: There is a need for a document that will specify the need to signal
maximum receive video resolution. (Can be in RTP how to or a separate
document). 

 

 

Need to discuss on the list if the solution should be codec specific or not.


 

 

Since there were no comments to far and we want to progress the VP8 RTP
payload specification  we may start a WGLC on the VP8 RTP payload and have
this topic as one of the issues to conclude.

 

Roni Even

Payload co-chair