Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-vc1-00.txt
Thomas Kernen <tkernen@deckpoint.ch> Wed, 21 September 2005 14:53 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EI5yE-0004WB-Bf; Wed, 21 Sep 2005 10:53:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EI5yB-0004W2-PF for avt@megatron.ietf.org; Wed, 21 Sep 2005 10:53:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25660 for <avt@ietf.org>; Wed, 21 Sep 2005 10:53:09 -0400 (EDT)
Received: from mail0.noc.ip-man.net ([217.169.140.13] helo=mail0.gva254.dmz.ip-man.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EI646-0004H3-GO for avt@ietf.org; Wed, 21 Sep 2005 10:59:27 -0400
Received: from localhost (localhost [127.0.0.1]) by mail0.gva254.dmz.ip-man.net (Postfix) with ESMTP id C8AF1264F8; Wed, 21 Sep 2005 16:52:36 +0200 (CEST)
Received: from mail0.gva254.dmz.ip-man.net ([127.0.0.1]) by localhost (mail0.gva254.dmz.ip-man.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66166-01; Wed, 21 Sep 2005 16:52:28 +0200 (CEST)
Received: from [10.16.53.154] (unknown [217.169.129.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail0.gva254.dmz.ip-man.net (Postfix) with ESMTP id BC1CF264E8; Wed, 21 Sep 2005 16:52:28 +0200 (CEST)
Message-ID: <433173AA.5090207@deckpoint.ch>
Date: Wed, 21 Sep 2005 16:52:26 +0200
From: Thomas Kernen <tkernen@deckpoint.ch>
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: anderskl@microsoft.com
Subject: Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-vc1-00.txt
References: <E1E8Njd-0007XE-GB@newodin.ietf.org>
In-Reply-To: <E1E8Njd-0007XE-GB@newodin.ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at ip-man.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Audio/Video Transport Working Group of the IETF. > > Title : RTP Payload Format for Video Codec 1 (VC-1) > Author(s) : A. Klemets > Filename : draft-ietf-avt-rtp-vc1-00.txt > Pages : 21 > Date : 2005-8-25 > > This memo specifies an RTP payload format for encapsulating Video > Codec 1 (VC-1) compressed bit streams, as defined by the proposed > Society of Motion Picture and Television Engineers (SMPTE) standard, > SMPTE 421M. SMPTE is the main standardizing body in the motion > imaging industry and the proposed SMPTE 421M standard defines a > compressed video bit stream format and decoding process for > television. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-vc1-00.txt > Here are my comments with regards to the draft. These are minor points related to wording clarification. - In section 3, the Advanced profile is referred to as "... making it suitable for nearly lossless encoding of HDTV signals". This is subject to interpretation and therefore is there a purpose to specify this matter? In n years from now the meaning of the term HDTV may not be the same as today, therefore this comment may be incorrect. Shouldn't the document be more factual? - In section 3.1, BI-picture is referred to but is not defined in section 2. Please could you either define in section 2 or change the wording of "These terms are defined in section 2 of this document and in section 4.12 of SMPTE 421M [1]". I was expecting to find a reference to BI-picture in the section 2 considering it's one liner in 4.12 of SMPTE 421M. - In section 4.3, "Knowing if the stream will contain B-pictures helps the decoder allocate resources more efficiently, as the encoder will not reorder any frames." Should not this be the other way around? "Knowing if the stream will NOT contain B-pictures..." - Across sections 6.1, 6.2 & 8, VC1 is referred to in lowercase and uppercase, is this related to the definition of VC1 as an (un)approved MIME subtype or simply an overlooked inconsistency in the draft? HTH Thomas _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] I-D ACTION:draft-ietf-avt-rtp-vc1-00.txt Internet-Drafts
- Re: [AVT] I-D ACTION:draft-ietf-avt-rtp-vc1-00.txt Thomas Kernen