Re: [Lake] Call for adoption of draft-selander-lake-traces

["Hristozov, Stefan" <[e-mail]>]

Hi,

I support the adoption of the document as well, since I found it useful for updating our implementation.

I will suggest adding traces for suites 2 and/or 3, which are of interest for us as well.

Br,
Stefan

On Thu, 2021-10-21 at 15:37 +0200, Marco Tiloca wrote:

Hi all,


I support adoption of this document, that I have personally found useful

through the implementation/testing process.


I believe that publication as RFC is appropriate too. This would be

analogous to RFC8448.


The current level of details in the traces looks actually good to me. I

think additional traces should include cipher suite 2 (both with

authentication method 0 and 3). This would make the document useful also

for implementations supporting only cipher suite 2, which is admitted

for constrained endpoints.


Best,

/Marco


On 2021-10-18 12:52, Mališa Vučinić wrote:

Dear all,


As discussed during the IETF-111 meeting and the last interim, this email triggers a 2-week call for adoption of draft-selander-lake-traces-01. The draft contains the EDHOC test vectors, previously part of draft-ietf-lake-edhoc.


We are seeking the working group input on the following points:

- Whether draft-selander-lake-traces should be adopted as a working group item, and if yes:

- Whether this draft should be published as an RFC

- What should be the scope of the document? The current version of the draft covers authentication methods 0 (signature - signature) and 3 (static DH - static DH). Should the draft cover additional methods and / or additional intermediary values? Anything else deemed useful from the implementers point of view?


Please provide your comments by November 1st, 2021.


Mališa and Stephen


--

Stefan Hristozov
Department Hardware Security
Fraunhofer Institute for Applied and Integrated Security AISEC
Lichtenbergstraße 11, 85748 Garching near Munich, Germany
Tel. [phone]
[e-mail]<mailto:[e-mail]>
https://www.aisec.fraunhofer.de/