IETF Logo Mail Archive

Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts

Glen Zorn <gwz@net-zen.net> Sun, 20 March 2011 09:15 UTC

Return-Path: <gwz@net-zen.net>
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 720E73A69D5 for <avt@core3.amsl.com>; Sun, 20 Mar 2011 02:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2Wtl08QFvvHM for <avt@core3.amsl.com>; Sun, 20 Mar 2011 02:15:18 -0700 (PDT)
Received: from smtpauth20.prod.mesa1.secureserver.net (smtpauth20.prod.mesa1.secureserver.net [64.202.165.36]) by core3.amsl.com (Postfix) with SMTP id 91C013A6A38 for <avt@ietf.org>; Sun, 20 Mar 2011 02:15:18 -0700 (PDT)
Received: (qmail 8186 invoked from network); 20 Mar 2011 09:16:49 -0000
Received: from unknown (124.120.73.139) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 20 Mar 2011 09:16:48 -0000
Message-ID: <4D85C5FA.4010407@net-zen.net>
Date: Sun, 20 Mar 2011 16:16:42 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: Ye-Kui Wang <yekui.wang@huawei.com>
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com>
In-Reply-To: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "avt@ietf.org" <avt@ietf.org>, "payload@ietf.org" <payload@ietf.org>
Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <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, 20 Mar 2011 09:15:19 -0000

On 3/20/2011 3:20 PM, Ye-Kui Wang wrote:
> Folks,
> 
>  
> 
> The three H.264/AVC related payload formats, namely,
> draft-ietf-avt-rtp-rfc3984bis-12, draft-ietf-avt-rtp-svc-27, and
> draft-ietf-avt-rtp-h264-rcdo-08, are all at the AUTH48 stage.
> 
>  
> 
> The RFC-Editor has found the following problem: In
> draft-ietf-avt-rtp-rfc3984bis-12, the definition of the max-dpb media
> parameter refers to the MaxDPB that was defined the first version of the
> H.264/AVC spec, but not any more in the latest version (the 2010
> version). The parameter in the latest H.264/AVC version corresponding to
> MaxDPB is MaxDpbMbs, and the unit of the new parameter (i.e.,
> macroblocks) is different from the original one (i.e. 1024 bytes).

...

> Since the drafts are at the AUTH48 stage, please provide comments by
> Monday, March 21, if any. Many thanks!

Just my opinion but these seem like technical changes that can't really
be dealt with in AUTH48.

...

v2.23.0 | Report a Bug | By Email