[Cbor] Robert Wilton's No Objection on draft-ietf-cbor-cddl-control-06: (with COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Thu, 21 October 2021 14:19 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: cbor@ietf.org
Delivered-To: cbor@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B00D33A174F; Thu, 21 Oct 2021 07:19:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-cbor-cddl-control@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, christian@amsuess.com, christian@amsuess.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <163482596094.17691.12740221348124236410@ietfa.amsl.com>
Date: Thu, 21 Oct 2021 07:19:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/jttUzPCHCIvVyWSvLGdW44o5gkM>
Subject: [Cbor] Robert Wilton's No Objection on draft-ietf-cbor-cddl-control-06: (with COMMENT)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2021 14:19:31 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-cbor-cddl-control-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:



Thanks for this.  I have to confess that I'm not particularly familiar with

It does feel that adding support for ABNF increases the size/complexity of the
CDDL language a fair bit.  Is the expectation that all CDDL implementations
will add support for these new control codes?  I guess you have to add support
if you want to parse CDDL text that uses the new control codes.  Would it be
helpful to have any text in the introduction about conformance/implementation? 
Finally, would it be helpful for this document to "update" the base CDDL spec,
so that readers looking for the base CDDL spec would also find this RFC, or
perhaps that is achieved via the IANA registration.

One minor nit:

Regarding dedenting, I suggest changing "in all" => "present in all"

   1.  determining the smallest amount of left-most blank space (number
       of leading space characters) in all the non-blank lines, and

Just a suggestion, but it might be helpful to include a short example where
some lines are not fully dedented.  I.e., so something doesn't think that each
line is processed independently.