[lamps] Éric Vyncke's No Objection on draft-ietf-lamps-cms-shakes-15: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Mon, 05 August 2019 15:03 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 26D31120232; Mon, 5 Aug 2019 08:03:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Éric Vyncke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lamps-cms-shakes@ietf.org, Russ Housley <housley@vigilsec.com>, lamps-chairs@ietf.org, housley@vigilsec.com, spasm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.99.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Éric Vyncke <evyncke@cisco.com>
Message-ID: <156501738314.24515.1427171792378435809.idtracker@ietfa.amsl.com>
Date: Mon, 05 Aug 2019 08:03:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/iEqr--dO0TcP8bL3rVm-2jnnh8w>
Subject: [lamps] Éric Vyncke's No Objection on draft-ietf-lamps-cms-shakes-15: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2019 15:03:04 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-lamps-cms-shakes-15: 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:
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-shakes/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


Thank you for the work put into this document. I second Alexey's DISCUSS that
is easy to fix.

Regards,

-éric

== COMMENTS ==

-- Section 4.1 --

Can you check whether the begin and the end of this section are consistent ?
I.e. "id-shake128 and id-shake256 OIDs" vs. "output length of SHA256 or
SHAKE256" ? I must admit that my knowledge of crypto is not paramount but I
find this weird.

-- Section 4.2.1 --

Is there any reason why length are measured in bytes while in other sections it
is in bits? Readers can do the math of course but why making the text more
complex to parse?

== NITS ==

-- Section 3 --

Why are some object identifier are fully in lowercase and some are a mix of
lower and uppercase characters?