[Lake] Lars Eggert's No Objection on charter-ietf-lake-01-00: (with COMMENT)

Lars Eggert via Datatracker <noreply@ietf.org> Mon, 24 April 2023 14:59 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lars Eggert via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: lake-chairs@ietf.org, lake@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Lars Eggert <lars@eggert.org>
Message-ID: <168234837817.35300.14112116345361892940@ietfa.amsl.com>
Date: Mon, 24 Apr 2023 07:59:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/9fuL38KRjGt_35xhcMBkp-BqnEE>
Subject: [Lake] Lars Eggert's No Objection on charter-ietf-lake-01-00: (with COMMENT)

Lars Eggert has entered the following ballot position for
charter-ietf-lake-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-lake/



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

# GEN AD review of charter-ietf-lake-01-00

CC @larseggert

## Comments

### "IOTOPS", paragraph 1
```
  EDHOC (draft-ietf-lake-edhoc), an output of the LAKE working group, defines a
  lightweight authenticated key exchange protocol between two peers. EDHOC
  provides forward secrecy, mutual peer authentication, identity protection of
  the protocol initiator, and crypto agility. EDHOC was formally studied in
  different security models: its design reflects the academic community feedback
  that analyzed its security properties. EDHOC is intended to be used in
  constrained network environments such as NB-IoT, 6TiSCH and LoRaWAN.

  The primary purpose of EDHOC is to key the Object Security for Constrained
  RESTful Environments protocol (OSCORE, RFC 8613). EDHOC is based on Concise
  Binary Object Representation (CBOR, RFC 8949) and CBOR Object Signing and
  Encryption (COSE, RFC 9052 and RFC 9053) to minimize the message sizes and the
  memory footprint when used with other CBOR-based protocols.
  Draft-ietf-lake-edhoc is a dependency of documents in the CoRE, ACE, EMU and
  IOTOPS working groups.

  By publishing EDHOC, the base protocol specification, the LAKE working group
  has completed its initial goal. The working group will continue to work on
  draft-ietf-lake-traces, a draft gathering protocol traces in different EDHOC
  execution modes, and aims to maintain and extend the base protocol
  specification as appropriate.
```
This is *very* long. I think all you need as an intro is the first sentence of
the first paragraph, or maybe the entire first paragraph.

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments
[IRT]: https://github.com/larseggert/ietf-reviewtool

[Lake] Lars Eggert's No Objection on charter-ietf… Lars Eggert via Datatracker