[Emu] Support of NIST P-256 in EAP-NOOB
Eduardo Inglés UM <eduardo.ingles@um.es> Thu, 20 June 2019 10:23 UTC
Return-Path: <eduardo.ingles@um.es>
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 2CFA412002F for <emu@ietfa.amsl.com>; Thu, 20 Jun 2019 03:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 YinV4ickO6lG for <emu@ietfa.amsl.com>; Thu, 20 Jun 2019 03:23:11 -0700 (PDT)
Received: from xenon41.um.es (xenon41.um.es [IPv6:2001:720:1710:601::41]) by ietfa.amsl.com (Postfix) with ESMTP id 3E84B12009C for <emu@ietf.org>; Thu, 20 Jun 2019 03:23:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by xenon41.um.es (Postfix) with ESMTP id 995CB264FA for <emu@ietf.org>; Thu, 20 Jun 2019 12:23:10 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon41.um.es
Received: from xenon41.um.es ([127.0.0.1]) by localhost (xenon41.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uZNuA7LLBHJy for <emu@ietf.org>; Thu, 20 Jun 2019 12:23:10 +0200 (CEST)
Received: from [130.233.193.143] (unknown [130.233.193.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: eduardo.ingles) by xenon41.um.es (Postfix) with ESMTPSA id 5BDC423B56 for <emu@ietf.org>; Thu, 20 Jun 2019 12:23:10 +0200 (CEST)
To: "emu@ietf.org" <emu@ietf.org>
From: Eduardo Inglés UM <eduardo.ingles@um.es>
Message-ID: <e578fc8c-8c90-8648-315e-7174e7a07c00@um.es>
Date: Thu, 20 Jun 2019 13:23:09 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: es-ES
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Y49lRPyeQAfWq4CHmFWRST63xiE>
Subject: [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: Thu, 20 Jun 2019 10:23:13 -0000
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] Support of NIST P-256 in EAP-NOOB Eduardo Inglés UM
- Re: [Emu] Support of NIST P-256 in EAP-NOOB Aura Tuomas