IETF Logo Mail Archive

Re: [Emu] Support of NIST P-256 in EAP-NOOB

Aura Tuomas <tuomas.aura@aalto.fi> Tue, 02 July 2019 10:47 UTC

Return-Path: <tuomas.aura@aalto.fi>
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 75FF112006D for <emu@ietfa.amsl.com>; Tue, 2 Jul 2019 03:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aalto.fi
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBjD7rNR6Ggm for <emu@ietfa.amsl.com>; Tue, 2 Jul 2019 03:47:05 -0700 (PDT)
Received: from smtp-out-01.aalto.fi (smtp-out-01.aalto.fi [130.233.228.120]) (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 6BDF0120052 for <emu@ietf.org>; Tue, 2 Jul 2019 03:47:05 -0700 (PDT)
Received: from smtp-out-01.aalto.fi (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id D1D2711573F_D1B34B0B; Tue, 2 Jul 2019 10:40:48 +0000 (GMT)
Received: from exng4.org.aalto.fi (exng4.org.aalto.fi [130.233.223.23]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client CN "exng4.org.aalto.fi", Issuer "org.aalto.fi RootCA" (not verified)) by smtp-out-01.aalto.fi (Sophos Email Appliance) with ESMTPS id 8115411569F_D1B34B0F; Tue, 2 Jul 2019 10:40:48 +0000 (GMT)
Received: from exng8.org.aalto.fi (130.233.223.27) by exng4.org.aalto.fi (130.233.223.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Tue, 2 Jul 2019 13:47:00 +0300
Received: from exng8.org.aalto.fi ([fe80::edd7:7397:1f7f:cd7]) by exng8.org.aalto.fi ([fe80::edd7:7397:1f7f:cd7%17]) with mapi id 15.01.1713.007; Tue, 2 Jul 2019 13:46:59 +0300
From: Aura Tuomas <tuomas.aura@aalto.fi>
To: Eduardo Inglés UM <eduardo.ingles@um.es>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] Support of NIST P-256 in EAP-NOOB
Thread-Index: AQHVJ1Iv6Aa3WNDeikWiRvQx3x+5haa3NZJw
Date: Tue, 02 Jul 2019 10:46:59 +0000
Message-ID: <e5e9feb7088f4fe993602dc3f9a3ffd4@aalto.fi>
References: <15187_1561026201_5D0B5E98_15187_876_1_e578fc8c-8c90-8648-315e-7174e7a07c00@um.es>
In-Reply-To: <15187_1561026201_5D0B5E98_15187_876_1_e578fc8c-8c90-8648-315e-7174e7a07c00@um.es>
Accept-Language: fi-FI, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.233.0.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-SASI-RCODE: 200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aalto.fi; h=from:to:subject:date:message-id:references:in-reply-to:content-type:content-transfer-encoding:mime-version; s=its18; bh=UF6UHKaVxqyBfllwuiDdwgc5TxIQiDUDzCti4Pr5CVA=; b=RUZBteyyJlbKwGNAFMor4ofxxwWhDWsTMK1dn2fI6X3kFgyQIMDPjqPfHI2fiHdGlLqIVZS6sDO8lUCKQ1wShk2URKjJDr5ec3dqeDYAUcxAmch9zcMyCrHkYJhLxLYnUuLzttySGrYVYj0zgUTjUGKCRoTc5Md/+3Sv64wmmXcyOzQW3L7aRcxgpOowh3U4VsHd0zyFWXh+vQn5qCSgsfOVDQzQKFl1CTbBYgLq1T6ULylLEPAxvtjvVUNDOAtiQOgiEVx6S7O9l80N7LASwrS7/IH9Z1IkyicBBpUIS4hB463QD/90jMM/XAisn4UTFQnJ19jxhbIifH+XSg45Yw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/ZipWmffvWJpkbZf1C1uIsNdl4BU>
Subject: Re: [Emu] Support of NIST P-256 in EAP-NOOB
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Jul 2019 10:47:09 -0000

Thank you for bringing up this issue. If there is broader demand for NIST P-256, we certainly can consider adding it to the draft. In any case, it would make sense to have two different curves in the specification to facilitate interoperability testing of the cryptosuite negotiation. At this point, maybe we can work on the interoperability first and then decide on the specific curves. The selection of curves will probably require broader community input, for example from SAAG.

Tuomas

 

-----Original Message-----
From: Emu <emu-bounces@ietf.org> On Behalf Of Eduardo Inglés UM
Sent: Thursday, June 20, 2019 1:23 PM
To: emu@ietf.org
Subject: [Emu] Support of NIST P-256 in EAP-NOOB
Importance: High

Hi again,

I am currently implementing EAP-NOOB on Zolertia Firefly boards (https://zolertia.io/product/firefly/). The board provides hardware acceleration for ECC operations. However, currently the API only supports ECDHE with NIST P-256 and EAP-NOOB draft only mentions the cryptosuite x25519 in Section 4.1.

I know that IETF likes the curve x25519, which has been specified through the CFRG process. Besides that, I see that many other platforms only support NIST P-256 in hardware. Thus, I wonder if it would be possible to support NIST P-256 to the draft?

In this draft
(https://tools.ietf.org/html/draft-ietf-lwig-curve-representations-06) I see that perhaps it is possible to use the code NIST P-256 for doing x25519. However, I have no coding expertise in cryptographic encoding to do that. Hence authors, do you want to support another curve?


Regards,
Eduardo Inglés.

_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu

v2.23.0 | Report a Bug | By Email