Re: Why ECC?
"Michael Young" <firstname.lastname@example.org> Tue, 24 September 2002 16:25 UTC
Received: from above.proper.com (mail.proper.com [188.8.131.52])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04538
for <email@example.com>; Tue, 24 Sep 2002 12:25:47 -0400 (EDT)
Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id g8OGBBl26133 for ietf-openpgp-bks; Tue, 24 Sep 2002 09:11:11 -0700 (PDT)
Received: from xfw.transarc.ibm.com (xfw.transarc.ibm.com [184.108.40.206]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g8OGB9v26125 for <firstname.lastname@example.org>; Tue, 24 Sep 2002 09:11:09 -0700 (PDT)
Received: from mailhost.transarc.ibm.com (mailhost.transarc.ibm.com [220.127.116.11]) by xfw.transarc.ibm.com (AIX4.3/UCB 8.7/8.7) with ESMTP id LAA14936 for <email@example.com>; Tue, 24 Sep 2002 11:57:43 -0400 (EDT)
Received: from mwyoung (dhcp-193-40.transarc.ibm.com [18.104.22.168]) by mailhost.transarc.ibm.com (8.8.0/8.8.0) with SMTP id MAA21897 for <firstname.lastname@example.org>; Tue, 24 Sep 2002 12:11:05 -0400 (EDT)
From: "Michael Young" <email@example.com>
Subject: Re: Why ECC?
Date: Tue, 24 Sep 2002 12:09:20 -0400
Content-Type: text/plain; charset="iso-8859-1"
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > At 03:18 AM 9/25/2002 +1200, Peter Gutmann wrote: > >Because it already contains every algorithm anyone could think of anyway, > >and a > >few more for implementors to ignore wouldn't matter? I took Peter's comment as a joke, a jab at the load of things already there. From: "Rodney Thayer" <firstname.lastname@example.org> > -- we alread have DSA for that. (Well if we want to claim RSA and DSA are > structurally related we don't but that's not the question at hand) If we're going to fantasize about future breakthroughs, we could also speculate that ECC and the integer DLP problems will be structurally related. > The second thing we're doing is violating the "it should be implementable" > principle. These RFC's are supposed to be buildable by normal mortals. I agree with this sentiment. Interoperability for the masses is important. It's also fine to have a place for experimenters to play, but there shouldn't be much pressure to get such things into the specification. > So, I come back to my question -- why do we want ECC? If there isn't > a requirement it fulfills it shouldn't be in the standard -- it just > takes up space and causes problems. At least in the last proposal I read, it takes up a LOT of space. There were a dozen representation options. It seemed quite unlikely that anyone would implement more than a small subset. Good luck finding other interoperable implementations. I'd be very happy for this to remain a separate document. -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.3 iQA/AwUBPZCOLlMkvpTT8vCGEQKD7ACg1px3nQlElzbI/jzOjsdNvOIF9CoAoIg5 XgV8+vrU/RjspqiKWoZejBkp =kDhI -----END PGP SIGNATURE-----