[Lwip] Ben Campbell's Yes on draft-ietf-lwig-crypto-sensors-05: (with COMMENT)

Ben Campbell <ben@nostrum.com> Thu, 22 February 2018 03:30 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ben Campbell <ben@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lwig-crypto-sensors@ietf.org, Zhen Cao <zhencao.ietf@gmail.com>, lwig-chairs@ietf.org, zhencao.ietf@gmail.com, lwip@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151927022640.21177.6294444000115439888.idtracker@ietfa.amsl.com>
Date: Wed, 21 Feb 2018 19:30:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/jRR-3XZmLHkzdDvMYI9DTvTD8-4>
Subject: [Lwip] Ben Campbell's Yes on draft-ietf-lwig-crypto-sensors-05: (with COMMENT)

Ben Campbell has entered the following ballot position for
draft-ietf-lwig-crypto-sensors-05: Yes

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-lwig-crypto-sensors/



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

I'm balloting "yes", because I think this is interesting and useful material.
But, as others have mentioned, it's confusing that this appears to be a working
group document, but it seems to be about the authors' personal design and
experimentations.

Otherwise, I just have a few editorial comments:

§2, first paragraph, third sentence: Missing article before "CoAP base
specification".

§4.1, paragraph 4: "Once both peers...": What peers? Does this use the term
"peer" for the server?

§4.1, last _word_: missing article before Igrp.

§4.2: "While this is not impossible in data object security
   solutions either, it is not the typical arrangement either."
I suspect the first "either" was not intended.

§5: "It is written in nesC programming language..." missing article before
"nesC".

[Lwip] Ben Campbell's Yes on draft-ietf-lwig-cryp… Ben Campbell