Re: [Lake] EDHOC state machine (Was: edhoc end game: detailed plan)
supjps-ietf@jpshallow.com Tue, 10 January 2023 10:57 UTC
Return-Path: <jon.shallow@jpshallow.com>
X-Original-To: lake@ietfa.amsl.com
Delivered-To: lake@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA93C1595FC for <lake@ietfa.amsl.com>; Tue, 10 Jan 2023 02:57:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EirWrSgzaZHF for <lake@ietfa.amsl.com>; Tue, 10 Jan 2023 02:57:00 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [31.22.13.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7244DC1595E5 for <lake@ietf.org>; Tue, 10 Jan 2023 02:56:59 -0800 (PST)
Received: from [192.168.0.78] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1pFBtp-0000p2-CZ; Tue, 10 Jan 2023 10:30:33 +0000
From: supjps-ietf@jpshallow.com
To: 'Göran Selander' <goran.selander=40ericsson.com@dmarc.ietf.org>, 'John Mattsson' <john.mattsson=40ericsson.com@dmarc.ietf.org>, 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>, lake@ietf.org
References: <f390f969-fbfa-405e-7f60-5a7f5d401bcf@cs.tcd.ie> <PAXPR07MB88447DBA170213F733D4BEA9F4E59@PAXPR07MB8844.eurprd07.prod.outlook.com> <HE1PR0701MB305034556CBC4EEE67FAE27089F59@HE1PR0701MB3050.eurprd07.prod.outlook.com> <PAXPR07MB8844DE96BC26DCFB63C389BCF4FE9@PAXPR07MB8844.eurprd07.prod.outlook.com>
In-Reply-To: <PAXPR07MB8844DE96BC26DCFB63C389BCF4FE9@PAXPR07MB8844.eurprd07.prod.outlook.com>
Date: Tue, 10 Jan 2023 10:30:30 -0000
Message-ID: <082201d924de$9067c640$b13752c0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0823_01D924DE.9067C640"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLBc9oUbiUMHH049C+ASwS7QAUbpAH0Q5vlAbeNr8YCjb/GEqyVB3AQ
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/g3ExrrDOW89sa1RzaIIGmQkBGTI>
Subject: Re: [Lake] EDHOC state machine (Was: edhoc end game: detailed plan)
X-BeenThere: lake@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Lightweight Authenticated Key Exchange <lake.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lake>, <mailto:lake-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lake/>
List-Post: <mailto:lake@ietf.org>
List-Help: <mailto:lake-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lake>, <mailto:lake-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2023 10:57:05 -0000
Hi all, I find having the state machine very useful. I confess to have only partially implemented EDHOC (up to all Message_2 exchanges as per the sig/dh traces), but completion has been down to a lack of spare time. Regards Jon From: Göran Selander [mailto: goran.selander=40ericsson.com@dmarc.ietf.org] Sent: 09 January 2023 13:31 To: John Mattsson; Stephen Farrell; lake@ietf.org Subject: Re: [Lake] EDHOC state machine (Was: edhoc end game: detailed plan) >Three different developers has expressed (I think publically on GitHub but it might have been offline) that they think this is very useful. All comments on the PR have been supportive, see https://github.com/lake-wg/edhoc/pull/373 This includes all people that expressed concerns during IETF 115. So there are at the moment 5 voices in favor, none known or suspected against. More input is requested, supportive or not. Göran From: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org> Date: Wednesday, 4 January 2023 at 11:31 To: Göran Selander <goran.selander@ericsson.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, lake@ietf.org <lake@ietf.org> Subject: Re: [Lake] EDHOC state machine (Was: edhoc end game: detailed plan) Stephen wrote: Ah. At this point, now that we've hit publication requested, I think a change like this needs positive backing, given that people expressed concerns about the possibility that state machine text could lead to delays. So I think the default position needs to remain that the state machine text be omitted until we see sufficient indication that the WG would like to include that. I was one of the persons expressed concerns about the possibility that state machine text could lead to delays. After reading the current suggestion I dont have these concerns anymore. The state machine seems quite simple and it is just an informative example. Three different developers has expressed (I think publically on GitHub but it might have been offline) that they think this is very useful. Given this I am personally positive to include it. Cheers, John
- [Lake] edhoc end game: detailed plan Stephen Farrell
- Re: [Lake] edhoc end game: detailed plan Sean Turner
- Re: [Lake] edhoc end game: detailed plan Stephen Farrell
- Re: [Lake] edhoc end game: detailed plan Stephen Farrell
- [Lake] EDHOC state machine (Was: edhoc end game: … Göran Selander
- Re: [Lake] EDHOC state machine (Was: edhoc end ga… Stephen Farrell
- Re: [Lake] EDHOC state machine (Was: edhoc end ga… John Mattsson
- Re: [Lake] EDHOC state machine (Was: edhoc end ga… Göran Selander
- Re: [Lake] EDHOC state machine (Was: edhoc end ga… supjps-ietf