Re: [Emu] Adoption call for EAP-EDHOC
peter@akayla.com Thu, 14 December 2023 22:38 UTC
Return-Path: <peter@akayla.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AFCCC14CEF9 for <emu@ietfa.amsl.com>; Thu, 14 Dec 2023 14:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 FQA1wuVimw0g for <emu@ietfa.amsl.com>; Thu, 14 Dec 2023 14:38:20 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 715F1C14F748 for <emu@ietf.org>; Thu, 14 Dec 2023 14:38:20 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 5CEDAF60FF for <emu@ietf.org>; Thu, 14 Dec 2023 17:38:19 -0500 (EST)
Received: from NewSpectre (server.houseofyee.com [173.8.184.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 17137F6793 for <emu@ietf.org>; Thu, 14 Dec 2023 17:38:19 -0500 (EST)
From: peter@akayla.com
To: emu@ietf.org
References: <60F5E1EB-AFD8-4673-A93E-39260B74B74E@akayla.com> <1D419D51-4BF8-40A3-8D9C-E8A1E3F78936@akayla.com>
In-Reply-To: <1D419D51-4BF8-40A3-8D9C-E8A1E3F78936@akayla.com>
Date: Thu, 14 Dec 2023 14:38:19 -0800
Message-ID: <005b01da2ede$3d214960$b763dc20$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGesCdtcuoBaeKlFlhmTsDj+fSsMQKdLv3usQtxpRA=
Content-Language: en-us
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/OerUmgvYqARo_yjdZBqLgJQmFR8>
Subject: Re: [Emu] Adoption call for EAP-EDHOC
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2023 22:38:24 -0000
Based on the feedback seen during the adoption call, I believe we can safely say that the consensus is overwhelmingly in favor of adopting EAP-EDHOC. Thank you to everyone who expressed an opinion during the adoption call. Once the new EMU charter is finalized and approved, we will formally request a WG version of the EAP-EDHOC draft. Of course, discussion about and refinement of the personal can continue before that. -Joe and Peter -----Original Message----- From: Peter Yee <peter@akayla.com> Sent: Wednesday, November 29, 2023 10:37 AM To: emu@ietf.org Subject: Re: Adoption call for EAP-EDHOC Off-by-one-bug. That deadline is December 13th! -Peter On 11/29/23, 9:13 AM, "Peter Yee" <peter@akayla.com <mailto:peter@akayla.com>> wrote: This is an adoption call for EAP-EDHOC (draft-ingles-eap-edhoc) [1]. This draft was originally briefed in Yokohama and while it didn't receive strong backing at that time, a short re-airing in Prague showed that there's distinct interest in taking on this work. While this work is not currently in scope for the EMU WG, it’s definitely something we could take on under a rechartering of the WG. So, if you've got interest in seeing the work adopted, please formalize that by responding to the EMU mailing list with your position. We are particularly interested in hearing from parties who are willing to review and/or contribute to the development of the specification. The deadline for feedback is November 13th. We hope to hear from lots of you. Joe and Peter 1) https://datatracker.ietf.org/doc/draft-ingles-eap-edhoc/ <https://datatracker.ietf.org/doc/draft-ingles-eap-edhoc/>
- Re: [Emu] Adoption call for EAP-EDHOC Peter Yee
- Re: [Emu] Adoption call for EAP-EDHOC Alexander PELOV
- Re: [Emu] Adoption call for EAP-EDHOC Laurent Toutain
- Re: [Emu] Adoption call for EAP-EDHOC GABRIEL LOPEZ MILLAN
- Re: [Emu] Adoption call for EAP-EDHOC Alan DeKok
- Re: [Emu] Adoption call for EAP-EDHOC Marco Tiloca
- Re: [Emu] Adoption call for EAP-EDHOC Jesus Sanchez
- Re: [Emu] Adoption call for EAP-EDHOC Ramon Llorca
- Re: [Emu] Adoption call for EAP-EDHOC peter
- [Emu] Adoption call for EAP-EDHOC Peter Yee
- Re: [Emu] Adoption call for EAP-EDHOC PEREÑIGUEZ GARCÍA, FERNANDO