[Emu] Updated EMU charter
Peter Yee <peter@akayla.com> Tue, 05 March 2024 23:47 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 2A9A9C14F709 for <emu@ietfa.amsl.com>; Tue, 5 Mar 2024 15:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akayla.com
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 8KVF39uX33EP for <emu@ietfa.amsl.com>; Tue, 5 Mar 2024 15:47:25 -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 11D2DC14F618 for <emu@ietf.org>; Tue, 5 Mar 2024 15:47:24 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 06231106F6C for <emu@ietf.org>; Tue, 5 Mar 2024 18:47:24 -0500 (EST)
Received: from [192.168.168.205] (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 A9F2C107E64 for <emu@ietf.org>; Tue, 5 Mar 2024 18:47:23 -0500 (EST)
User-Agent: Microsoft-MacOutlook/16.82.24021813
Date: Tue, 05 Mar 2024 15:47:21 -0800
From: Peter Yee <peter@akayla.com>
To: "emu@ietf.org" <emu@ietf.org>
Message-ID: <C83485F3-87CB-42AC-AAA2-7A90C047BB2E@akayla.com>
Thread-Topic: Updated EMU charter
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akayla.com; h=date:subject:from:to:message-id:mime-version:content-type:content-transfer-encoding; s=pair-202402141610; bh=hRWtQ9pedhTvswMpxH/ywLbTKgfd2wVeVQHR1oYQLpE=; b=wgAZxl78qYyhNXj6iPaiMAOCnKgu92i9pWSHoLvDI2h7+U61ALDSZDWBX2dCwGk3FZiXWdYcLM9L/IO15ov+1oex/ZCvKbBbwANswOwO5ZoyWOYTnyRQ05T6HRH/Su4aXA33tC5p5KEUrLmVI+N/M0jx7hi697q8rbVul5aZPxYVYSRNa5XCPyPm/zBFfVY+Ofg9cEJsAgMZzshGYBGTE3qIoqrp5i+GnYaQRvuG3GEdnSMJmACb4ivtJTgoA3BFCBqGyQt1DfpqPhr1OIzkDaosNQvfRcdsK6qhYdO4u/1ZiEQRWeB0dhdAZkn2J6JCEbsCnWAJHiadXY06B84iuw==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/uuu1VfFvPEuKo7MdRPzXsHYB-Ks>
Subject: [Emu] Updated EMU charter
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: Tue, 05 Mar 2024 23:47:29 -0000
I've drafted an update to the EMU charter to give us room to work on EAP-EDHOC and EAP-FIDO (or whatever we end up calling it). I'd appreciate the WG looking over the updated charter (https://github.com/emu-wg/charter/blob/master/emu-charter.md) and replying to the list with any thoughts you might have on it. I propose to stop taking input on the charter one week from today unless there's active discussion taking place on the list. That way I can get the revised charter over to Paul Wouters (as the relevant Security AD) soon as the next step to getting it approved. Questions and input most welcome! -Peter
- [Emu] Updated EMU charter Peter Yee
- Re: [Emu] Updated EMU charter Alan DeKok