[Emu] FW: New Version Notification for draft-yan-emu-eap-multiple-psk-00.txt
"Yanlei(Ray)" <ray.yanlei@huawei.com> Tue, 05 March 2024 08:04 UTC
Return-Path: <ray.yanlei@huawei.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 7020AC14F685 for <emu@ietfa.amsl.com>; Tue, 5 Mar 2024 00:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.204
X-Spam-Level:
X-Spam-Status: No, score=-4.204 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 ZQb2INUS8lhp for <emu@ietfa.amsl.com>; Tue, 5 Mar 2024 00:04:24 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41433C14F60D for <emu@ietf.org>; Tue, 5 Mar 2024 00:04:24 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Tpnyy4dwXz6H6pg for <emu@ietf.org>; Tue, 5 Mar 2024 15:59:38 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (unknown [7.191.160.241]) by mail.maildlp.com (Postfix) with ESMTPS id 6A2D71400CB for <emu@ietf.org>; Tue, 5 Mar 2024 16:04:21 +0800 (CST)
Received: from kwepemm000020.china.huawei.com (7.193.23.93) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Tue, 5 Mar 2024 08:04:20 +0000
Received: from kwepemm600017.china.huawei.com (7.193.23.234) by kwepemm000020.china.huawei.com (7.193.23.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Tue, 5 Mar 2024 16:04:19 +0800
Received: from kwepemm600017.china.huawei.com ([7.193.23.234]) by kwepemm600017.china.huawei.com ([7.193.23.234]) with mapi id 15.01.2507.035; Tue, 5 Mar 2024 16:04:19 +0800
From: "Yanlei(Ray)" <ray.yanlei@huawei.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: New Version Notification for draft-yan-emu-eap-multiple-psk-00.txt
Thread-Index: AQHabja5jr+nO7s5Vk6ddXhV8nWKvLEoenyg
Date: Tue, 05 Mar 2024 08:04:18 +0000
Message-ID: <13f64874903a455690eb7cb66d140724@huawei.com>
References: <170955841049.41661.830381732512866525@ietfa.amsl.com>
In-Reply-To: <170955841049.41661.830381732512866525@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.39.228]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/n_EsELkCwryGd8S1VjuGBi9YfHU>
Subject: [Emu] FW: New Version Notification for draft-yan-emu-eap-multiple-psk-00.txt
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 08:04:26 -0000
Hi all, I'd like to bring your attention to the following individual IETF draft. Your comments are warmly welcome! The high level summary is as follows: The existing PSK-based EAP methods, such as EAP-GPSK [RFC5433] and EAP-PSK [RFC4764], assumed that only one PSK had been configured on a pair of EAP peer and server. Using only one PSK will bring several security issues [RFC5433]. One solution is to use multiple PSKs between the EAP peer and server. This document modifies the EAP-GPSK to support the negotiation of a PSK among multiple PSKs. Regards, Lei YAN -----Original Message----- From: internet-drafts@ietf.org <internet-drafts@ietf.org> Sent: Monday, March 4, 2024 9:20 PM To: Yanlei(Ray) <ray.yanlei@huawei.com> Subject: New Version Notification for draft-yan-emu-eap-multiple-psk-00.txt A new version of Internet-Draft draft-yan-emu-eap-multiple-psk-00.txt has been successfully submitted by Lei YAN and posted to the IETF repository. Name: draft-yan-emu-eap-multiple-psk Revision: 00 Title: EAP Multiple Pre-Shared Keys (EAP-MPSK) Method Date: 2024-03-04 Group: Individual Submission Pages: 4 URL: https://www.ietf.org/archive/id/draft-yan-emu-eap-multiple-psk-00.txt Status: https://datatracker.ietf.org/doc/draft-yan-emu-eap-multiple-psk/ HTML: https://www.ietf.org/archive/id/draft-yan-emu-eap-multiple-psk-00.html HTMLized: https://datatracker.ietf.org/doc/html/draft-yan-emu-eap-multiple-psk Abstract: This document defines an Extensible Authentication Protocol (EAP) method for supporting the negotiation of a PSK among multiple PSKs. The IETF Secretariat