AW: Reasons to include ECC to our charter

"Dominikus Scherkl" <Dominikus.Scherkl@biodata.com> Wed, 05 September 2001 10:03 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22351 for <openpgp-archive@odin.ietf.org>; Wed, 5 Sep 2001 06:03:08 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id f859mVC04554 for ietf-openpgp-bks; Wed, 5 Sep 2001 02:48:31 -0700 (PDT)
Received: from mail1.biodata.com ([62.159.113.2]) by above.proper.com (8.11.6/8.11.3) with ESMTP id f859mUD04548 for <ietf-openpgp@imc.org>; Wed, 5 Sep 2001 02:48:30 -0700 (PDT)
Received: from fra1d001.biodata.org ([10.10.1.51]) by mail1.biodata.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 5 Sep 2001 11:48:15 +0200
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: AW: Reasons to include ECC to our charter
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Date: Wed, 5 Sep 2001 11:48:15 +0200
Message-ID: <100722F3C53A484B8CF1F14B4F062E93157072@fra1d001.biodata.org>
Thread-Topic: Reasons to include ECC to our charter
Thread-Index: AcE1lP1DGB9nBwWCQHCasLZSMIppWwAVlJSQ
From: "Dominikus Scherkl" <Dominikus.Scherkl@biodata.com>
To: "openPGP e-Mail (E-Mail)" <ietf-openpgp@imc.org>
X-OriginalArrivalTime: 05 Sep 2001 09:48:15.0817 (UTC) FILETIME=[E2984390:01C135EF]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id f859mVD04550
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>
Content-Transfer-Encoding: 8bit

Hello.

> > > That's precisely the issue - how do we make sure it
> > > doesn't assume a patented technology if we don't know
> > > what the patents are?
I think we agree now that there exists patents, so ECC will
not be mandatory part of the standard. But if it's optional
it is not essential to know what is patented and what not -
it would only be nice to know.

> > If someone comes up with a layout that supports ECC
> > generically, I'd say go with it.
May I remember that it's exactly what I ask for?
To go with what I submitted?

> > if someone else does the work and convinces us that it's
> > generic, I say go for it.
What do you dislike in my proposal? What is not generic enough?
Till mow I've not read any content-specific critics.

> > That's also why I said to do an informational RFC,
Ok, I can submit my draft also as an informational RFC.
Is it that what you want me to do?

> > make a sample implementation, let someone hack up GPG to
> > work with it, and we'll see.

To experiment wit elliptic curves LiDIA (Library for
computational number theory - from the Technische Universitaet
Darmstadt) has all you need. Also P1363 is a good point
to get implementations of most the algorithms needed for
ECC and ECDSA.

I think there are already diverse implementations of ECC
waiting for a standard to interoperate.

> 
> What will we see? Clearly its possible to do - so what's
> interesting about doing it before we can be sure we can use it?
We indeed _can_ be sure that we can use it - anyone can use it
unless she want to sell it (which may require licencing).

Sorry if my words sound too hard. I don't mind.
I don't worry about the discussion. Quite the opposit, it's
worthwhile. But I would enjoy it very much to have an ECC
standard at last.

Best regards.
-- 
Dominikus Scherkl
Biodata Application Security AG
mail: Dominikus.Scherkl@Biodata.com