IETF Logo Mail Archive

[Emu] Adoption call for EAP-EDHOC

Peter Yee <peter@akayla.com> Wed, 29 November 2023 17:13 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 4DCFEC15107E for <emu@ietfa.amsl.com>; Wed, 29 Nov 2023 09:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 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_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 vZ6mT0q39Jcy for <emu@ietfa.amsl.com>; Wed, 29 Nov 2023 09:13:33 -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 7681EC151070 for <emu@ietf.org>; Wed, 29 Nov 2023 09:13:33 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 350717F40D for <emu@ietf.org>; Wed, 29 Nov 2023 12:13:32 -0500 (EST)
Received: from [172.27.177.117] (unknown [98.97.124.237]) (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 C6B3D7F488 for <emu@ietf.org>; Wed, 29 Nov 2023 12:13:31 -0500 (EST)
User-Agent: Microsoft-MacOutlook/16.79.23111718
Date: Wed, 29 Nov 2023 09:13:26 -0800
From: Peter Yee <peter@akayla.com>
To: "emu@ietf.org" <emu@ietf.org>
Message-ID: <85C7362D-5FF0-4777-82ED-CC933115848E@akayla.com>
Thread-Topic: Adoption call for EAP-EDHOC
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/PznxFeOR6mdkqmQfooW-f3sSeqE>
Subject: [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: Wed, 29 Nov 2023 17:13:37 -0000

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/

v2.23.0 | Report a Bug | By Email