Re: [Lake] I-D Action: draft-ietf-lake-edhoc-21.txt

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

Hi Stephen, and all,

The authors think they have now addressed all IESG comments and there are no DISCUSSes left. Please note that there are some small updates in the github master branch didn’t make it into -21, including final comment on section 3.4 from Zahed Sarker, change log for -21, and acknowledgments.

We plan to submit -22 today, unless there is reason to wait.

Göran

From: Lake <[e-mail]> on behalf of Stephen Farrell <[e-mail]>
Date: Thursday, 24 August 2023 at 20:41
To: [e-mail] <[e-mail]>
Subject: Re: [Lake] I-D Action: draft-ietf-lake-edhoc-21.txt

Hi all,

As you'll have seen, a bunch of comments were (as usual:-)
received during IESG review of edhoc and the editors have
worked really quickly to handle those. (@editors: do you
think we've addressed all of those?)

I had a look over the diffs and I don't see any changes that
would require the WG to pause and think again about anything
so don't at this stage plan to do that. But if I missed some
substantive change, please do yell and we can take a look.

All going well, that'd mean the IESG will clear their DISCUSS
positions and then the draft will be sent to the RFC editor
queue. (Or, there may be a little more back-and-forth with
IESG members, we'll see.)

Cheers,
S.

On 24/08/2023 18:59, [e-mail] wrote:
> Internet-Draft draft-ietf-lake-edhoc-21.txt is now available. It is a work
> item of the Lightweight Authenticated Key Exchange (LAKE) WG of the IETF.
>
>     Title:   Ephemeral Diffie-Hellman Over COSE (EDHOC)
>     Authors: Göran Selander
>              John Preuß Mattsson
>              Francesca Palombini
>     Name:    draft-ietf-lake-edhoc-21.txt
>     Pages:   111
>     Dates:   2023-08-24
>
> Abstract:
>
>     This document specifies Ephemeral Diffie-Hellman Over COSE (EDHOC), a
>     very compact and lightweight authenticated Diffie-Hellman key
>     exchange with ephemeral keys.  EDHOC provides mutual authentication,
>     forward secrecy, and identity protection.  EDHOC is intended for
>     usage in constrained scenarios and a main use case is to establish an
>     OSCORE security context.  By reusing COSE for cryptography, CBOR for
>     encoding, and CoAP for transport, the additional code size can be
>     kept very low.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lake-edhoc/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-lake-edhoc-21.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lake-edhoc-21
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>