Re: [AVTCORE] AD Evaluation of draft-ietf-avtext-lrr-05
Ben Campbell <ben@nostrum.com> Tue, 06 June 2017 21:15 UTC
Return-Path: <ben@nostrum.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2E81294E2; Tue, 6 Jun 2017 14:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 Xc-eMPwgJ0R2; Tue, 6 Jun 2017 14:15:27 -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 6F25A128BB6; Tue, 6 Jun 2017 14:15:26 -0700 (PDT)
Received: from [10.0.2.78] (ip-5-232-239-173.texas.us.northamericancoax.com [173.239.232.5]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v56LEnkT079638 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 6 Jun 2017 16:14:50 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-5-232-239-173.texas.us.northamericancoax.com [173.239.232.5] claimed to be [10.0.2.78]
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (14F89)
In-Reply-To: <192000CE-8D82-4856-8282-9A0B0C7AFFE8@vidyo.com>
Date: Tue, 06 Jun 2017 17:14:48 -0400
Cc: "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, IETF AVTCore WG <avt@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC1AC8B7-6EDB-4714-A996-B657A1DCBD20@nostrum.com>
References: <D54F2BC9-8823-403A-B6A8-38C7282925EB@nostrum.com> <192000CE-8D82-4856-8282-9A0B0C7AFFE8@vidyo.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/24EF7A3dbEXgGNBAd5bxwa8EZqY>
Subject: Re: [AVTCORE] AD Evaluation of draft-ietf-avtext-lrr-05
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 06 Jun 2017 21:15:28 -0000
All sounds good, thanks! > On Jun 6, 2017, at 5:00 PM, Jonathan Lennox <jonathan@vidyo.com> wrote: > > >> On May 25, 2017, at 6:47 PM, Ben Campbell <ben@nostrum.com> wrote: >> >> Hi, >> >> This is my AD Evaluation of draft-ietf-avtext-lrr-05. I only have a couple of editorial comments, which can be handled along with any IETF Last Call comments. I will request IETF Last Call shortly. >> >> Thanks! >> >> Ben. > > Thanks for your comments! > > >> -3.2, last paragraph: the “MAY” seems like a statement of fact, rather than normative permission. Please consider lower case. > > Fixed, along with a general paragraph rewording in response to Fred Baker’s ops-dir review. > >> -4.3, 2nd paragraph: " >> Figure 8 shows the format of the layer index field for H.265 streams. The "RES" fields MUST be set to 0 on transmission and ignored on reception.” >> >> Is that MUST a new normative requirement, or a reference to one in RFC 7798? If the later, please use descriptive (i.e. non-2119) language. > > It’s a new normative requirement; this is defining the codec-specific fields for this document. > > However, this does reveal to me that this section still uses the old term “layer index” not the new terms “TTID” and “TLID”, which was probably the source of the confusion, so I’ll fix that.
- [AVTCORE] AD Evaluation of draft-ietf-avtext-lrr-… Ben Campbell
- Re: [AVTCORE] AD Evaluation of draft-ietf-avtext-… Jonathan Lennox
- Re: [AVTCORE] AD Evaluation of draft-ietf-avtext-… Ben Campbell