[mile] Benjamin Kaduk's No Objection on draft-ietf-mile-jsoniodef-13: (with COMMENT)

Benjamin Kaduk via Datatracker <noreply@ietf.org> Wed, 26 February 2020 20:59 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 78D8A3A1423; Wed, 26 Feb 2020 12:59:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mile-jsoniodef@ietf.org, mile-chairs@ietf.org, mile@ietf.org, Nancy Cam-Winget <ncamwing@cisco.com>, ncamwing@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.118.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <158275077042.20979.9867224928197693313.idtracker@ietfa.amsl.com>
Date: Wed, 26 Feb 2020 12:59:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/8hE9pD6NWQZi5_BhB0QsvcHdkuo>
Subject: [mile] Benjamin Kaduk's No Objection on draft-ietf-mile-jsoniodef-13: (with COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 20:59:31 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-mile-jsoniodef-13: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

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


Thank you for the updates in the -13; they are a good improvement!

I did notice a couple things while reviewing the diff from -12 to -13 that
I'll mention here, in case there might be any further tweaks to make.

In Figure 7 it looks like the encoded text includes an embedded CR+LF.
I don't think this is forbidden by anything, but is perhaps superfluous.

Thanks for the table of CBOR map keys in Section 5.  I note that slightly
shorter encodings might be possible by using negative integers as well as positive
ones, with "steps" for the encoding size occurring at 24, 256, etc., and -25, -257, etc.

[I did not check the examples for correct use of the CBOR map key values, on the
assumption that they were mechanically generated.]

The definition of StructuredInfo underwent a change that was not quite mechanical:
"(RawData: [+ BYTE] // Reference:[+ Reference])" became
"(iodef-RawData => [+ BYTE], iodef-Reference => [+ Reference])" (dropping the grouping
choice operator "//").  I don't remember if there was a reason to make this change, so
I mention it in case it was not deliberate.