Re: [Lake] Roman Danyliw's No Objection on draft-ietf-lake-traces-07: (with COMMENT)

[Göran Selander <[e-mail]>]

Hi Roman,

Thanks for your review. Your comment is tracked in #448<https://github.com/lake-wg/edhoc/issues/448> and addressed in 340e442<https://github.com/lake-wg/edhoc/commit/340e442>.
(Latest version on the github is here<https://lake-wg.github.io/edhoc/draft-ietf-lake-traces.html>.)

Göran

From: Roman Danyliw via Datatracker <[e-mail]>
Date: Friday, 15 September 2023 at 21:42
To: The IESG <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: Roman Danyliw's No Objection on draft-ietf-lake-traces-07: (with COMMENT)
Roman Danyliw has entered the following ballot position for
draft-ietf-lake-traces-07: 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/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


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



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

Thank you for writing this document.  I am confident that it will help future
implementers.

I did not personally verify the encodings.

** Section 1.1
   The traces in this draft are valid for version -22 of
   [I-D.ietf-lake-edhoc].  The traces has been verified by two
   independent implementations.

I appreciate the precision of this statement.  In the long term, shouldn’t
these traces be valid for whatever RFC this EDHOC becomes.  Recommend providing
instructions to the RFC Editor to replace [I-D.ietf-lake-edhoc] with the
yet-to-be-assigned RFC number.