[lamps] Spencer Dawkins' No Objection on charter-ietf-lamps-01-00: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Wed, 07 February 2018 18:14 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: lamps-chairs@ietf.org, spasm@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151802724697.4759.5326501296981118086.idtracker@ietfa.amsl.com>
Date: Wed, 07 Feb 2018 10:14:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/5M-w0gnNkxU6HV10t9dOHxOw5ZI>
Subject: [lamps] Spencer Dawkins' No Objection on charter-ietf-lamps-01-00: (with COMMENT)

Spencer Dawkins has entered the following ballot position for
charter-ietf-lamps-01-00: 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.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-lamps/



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

Nice work on this one.

This is very nit-picky, but perhaps placing the explanation of each topic
immediately following the list item naming the topic would be clearer?

Like, so:

Having completed the S/MIME 4.0 specifications and updates to support
i18n email addresses in PKIX certificates, the LAMPS WG is now tackling
these topics:

1. Specify a discovery mechanism for CAA records to replace the one
   described in RFC 6844.

RFC 6844 describes the mechanism by which CAA records relating to a
domain are discovered.  Implementation experience has demonstrated an
ambiguity in the current processing of CNAME and DNAME records during
discovery.  Subsequent discussion has suggested that a different
discovery approach would resolve limitations inherent in the current
approach.

2. Specify the use of SHAKE128/256 and SHAKE256/512 for PKIX and
S/MIME.

Unlike the previous hashing standards, the SHA-3 family of functions are
the outcome of an open competition.  They have a clear design rationale
and have received a lot of public analysis, which gives great confidence
that the SHA-3 family of functions are secure.  Also, since SHA-3 uses a
very different construction from SHA-2, the SHA-3 family of functions
offers an excellent alternative.  In particular, SHAKE128/256 and
SHAKE256/512 offer security and performance benefits.

[lamps] Spencer Dawkins' No Objection on charter-… Spencer Dawkins