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

Glen Zorn <gwz@net-zen.net> Mon, 21 March 2011 06:10 UTC

Return-Path: <gwz@net-zen.net>
X-Original-To: payload@core3.amsl.com
Delivered-To: payload@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38DB83A67B5 for <payload@core3.amsl.com>; Sun, 20 Mar 2011 23:10:01 -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 aQRIoah7XpNF for <payload@core3.amsl.com>; Sun, 20 Mar 2011 23:09:56 -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 2971E3A67B3 for <payload@ietf.org>; Sun, 20 Mar 2011 23:09:56 -0700 (PDT)
Received: (qmail 12301 invoked from network); 21 Mar 2011 06:11:28 -0000
Received: from unknown (124.122.150.171) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 21 Mar 2011 06:11:27 -0000
Message-ID: <4D86EC09.2020304@net-zen.net>
Date: Mon, 21 Mar 2011 13:11:21 +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: Roni Even <Even.roni@huawei.com>
References: <B99DECD58A94E143BA6F1508CC688351B417FB@dfweml504-mbx.china.huawei.com> <4D85C5FA.4010407@net-zen.net> <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com>
In-Reply-To: <000701cbe6f9$f44b1e80$dce15b80$%roni@huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 21 Mar 2011 05:20:45 -0700
Cc: payload@ietf.org, avt@ietf.org
Subject: Re: [payload] [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO payload drafts
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 06:10:01 -0000

On 3/20/2011 7:25 PM, Roni Even wrote:

> Hi Glen,
> The technical change is more in H.264/AVC specification. In the payload
> specifications (3984bis/ RCDO and SVC) the change is to specify the
> conversion between the old and new parameter and to explain the change in
> H.264.
> It can be looked as a technical and I will leave it to the AD to help here.
> 
> As for the quality of the change it was done by YK with the help of Steve
> Botzko (H.241 editor) and Gary Sullivan the Rapportuer of Q6 SG16 that does
> the video codec in a f2f meeting. It was also reviewed by me and by some
> other experts on video coding and I feel good about the solution,

I'm admittedly not an expert on H.264, so I can't quibble about the
quality of the proposed solution.  My comment is a procedural one: I
don't believe that technical changes are allowed after the completion of
IETF review, nor should they be.  My understanding is that the AUTH48
review is provided only as a last-minute opportunity to catch typos or
make small editorial changes, not to modify the technical content of a
document.  BTW, I'm in the same boat myself right now: one of my
co-authors has fairly significant technical changes (and has proposed
even bigger ones) to a draft now in AUTH48 & I'm saying the same thing
about that one.  I'm _not_ looking forward to restarting the whole
process, but OTOH my co-author (& for that matter, I) should have had
our act together before requesting publication.

> 
> This change involves also an update to H.241 that has the same issue and the
> objective is to approve the H.241 change this week at the ongoing ITU Study
> Group 16 meeting. The solution for the IETF draft and ITU draft should be
> the same to address interoperability.
> 
> Thanks
> Roni Even
> As individual.
> 
> 
>> -----Original Message-----
>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of
>> Glen Zorn
>> Sent: Sunday, March 20, 2011 11:17 AM
>> To: Ye-Kui Wang
>> Cc: avt@ietf.org; payload@ietf.org
>> Subject: Re: [AVTCORE] Some changes to rfc3984bis, SVC, and RCDO
>> payload drafts
>>
>> 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.
>>
>> ...
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
> 
>