Re: [Gen-art] Gen-ART Review of draft-ietf-rtcweb-video-05

Adam Roach <adam@nostrum.com> Tue, 09 June 2015 21:01 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0D21A1A98; Tue, 9 Jun 2015 14:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 FAw71vx6pytV; Tue, 9 Jun 2015 14:01:37 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F59F1A00FA; Tue, 9 Jun 2015 14:01:34 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t59L1XsY059880 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 9 Jun 2015 16:01:33 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
Message-ID: <5577542C.1050100@nostrum.com>
Date: Tue, 09 Jun 2015 16:01:32 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>, draft-ietf-rtcweb-video.all@ietf.org
References: <E485CE00-5D68-421C-96F3-72AB7CEE2B83@vigilsec.com>
In-Reply-To: <E485CE00-5D68-421C-96F3-72AB7CEE2B83@vigilsec.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/5mt3sJunz51b3EgUwAlECK4GlK4>
Cc: IETF Gen-ART <gen-art@ietf.org>, IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-rtcweb-video-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2015 21:01:38 -0000

On 5/15/15 10:14, Russ Housley wrote:
> In section 3, the first sentence says: "This section provides guidance
> on pre- or post-processing of video streams."  s/pre- or/pre- and/

Thanks, agreed.

> Maybe the intended audience will understand "Y'CbCr 4:2:0", but a
> reference would have helped me.

Yes, I do believe that the intended audience will be familiar with this 
as a term of art. I suspect that casual readers will be as adroit with 
web search engines as you are. I would be very hesitant to cite 
something as fluid as a wiki for a definition.

> The indented text in Section 5 should begin with "NOTE: ".

Thanks, agreed.

> In section 6, I assume that "320x240" is measured in pixels.  Please
> make the text clear.

Thanks, agreed.

> Section 6.2 says: "Unless otherwise signaled, implementations that use
> H.264 MUST encode and decode pixels with a implied 1:1 (square) aspect
> ratio."  Isn't this true for VP8 as well?

Yes, it would make sense to have this in the VP8 section.

> Other Comments:
>
> There are references to several outdated I-Ds.  Some of the references
> point to particular section numbers.  I did not check whether the
> updates had an impact on these sections, but someone should do so:

Good catch. This is the result of unexpected caching behavior in 
xml2rfc. Easy to fix.

>    - draft-ietf-rtcweb-security-arch-09: -11) exists
>    - draft-ietf-rtcweb-security-06: -08 exists

These are the only documents with specific sections cited. I have 
verified that the references are correct with regard to the most recent 
version.

/a