Re: Remove SHOULD for elliptic curve groups in IKEv2

Eric Rescorla <ekr@rtfm.com> Wed, 13 March 2002 00:35 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g2D0Z5401415; Tue, 12 Mar 2002 16:35:06 -0800 (PST)
Received: by lists.tislabs.com (8.9.1/8.9.1) id SAA19484 Tue, 12 Mar 2002 18:56:14 -0500 (EST)
To: "The Purple Streak (Hilarie Orman)" <ho@alum.mit.edu>
Cc: IP Security List <ipsec@lists.tislabs.com>
Subject: Re: Remove SHOULD for elliptic curve groups in IKEv2
References: <Pine.BSI.3.91.1020312131533.25973E-100000@spsystems.net> <3C8E5E1F.4030000@alum.mit.edu> <kjr8mpsaqg.fsf@romeo.rtfm.com> <3C8E91ED.3020104@alum.mit.edu>
Reply-to: EKR <ekr@rtfm.com>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset="US-ASCII"
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 12 Mar 2002 16:08:00 -0800
In-Reply-To: "The Purple Streak's message of "Tue, 12 Mar 2002 16:40:29 -0700"
Message-ID: <kjn0xds527.fsf@romeo.rtfm.com>
Lines: 29
X-Mailer: Gnus v5.6.45/XEmacs 20.4 - "Emerald"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

"The Purple Streak (Hilarie Orman)" <ho@alum.mit.edu> writes:
> Oakley and IKE and draft-orman-public-key-lengths-05 name the
> algorithms, the strengths, computational scaling,  etc. of
> ECC for Diffie-Hellman key agreement.  Mathematically,
> the algorithm is DH using point addition in elliptic curve groups over 
> GF[2^n].
> 
> Specific implementation techniques may be covered by patents, but
> see, for example, Fast Key Exchange with Elliptic Curve Systems,
> in Crypto '95, for details and pseudocode of a non-encumbered method.
What I had in mind here, was a draft that collect all of this
information in one place so that it could inform this sort of
dicussion.

The particular paper you refer to, while interesting, unfortunately,
is a little difficult to draw direct conclusions from:

	(1) It doesn't describe the technique you use for performing
	the DH key agremement you're comparing to. 
	(2) The timings you describe are on such outdated platforms
	(granted, they weren't outdated at the time) that it's very
	difficult to compare them with implementations on modern
	platforms.
	
-Ekr
	
-- 
[Eric Rescorla                                   ekr@rtfm.com]
                http://www.rtfm.com/