AW: Reasons to include ECC to our charter

"Dominikus Scherkl" <Dominikus.Scherkl@biodata.com> Wed, 15 August 2001 13:54 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 JAA20880 for <openpgp-archive@odin.ietf.org>; Wed, 15 Aug 2001 09:54:48 -0400 (EDT)
Received: by above.proper.com (8.11.3/8.11.3) id f7FDYgb20188 for ietf-openpgp-bks; Wed, 15 Aug 2001 06:34:42 -0700 (PDT)
Received: from mail1.biodata.com ([62.159.113.2]) by above.proper.com (8.11.3/8.11.3) with ESMTP id f7FDYeN20184 for <ietf-openpgp@imc.org>; Wed, 15 Aug 2001 06:34:41 -0700 (PDT)
Received: from fra1d001.biodata.org ([10.10.1.51]) by mail1.biodata.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 15 Aug 2001 15:33:24 +0200
Subject: AW: Reasons to include ECC to our charter
Date: Wed, 15 Aug 2001 15:33:24 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <100722F3C53A484B8CF1F14B4F062E93157065@fra1d001.biodata.org>
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: Reasons to include ECC to our charter
Thread-Index: AcEhsbuvGZnJ9QwpSu2blA5ocaHvZQD2p2Bg
From: Dominikus Scherkl <Dominikus.Scherkl@biodata.com>
To: Ben Laurie <ben@algroup.co.uk>
Cc: "openPGP e-Mail (E-Mail)" <ietf-openpgp@imc.org>
X-OriginalArrivalTime: 15 Aug 2001 13:33:24.0396 (UTC) FILETIME=[DBA916C0:01C1258E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id f7FDYfN20185
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

Hi.

> > IIRC, not all ECC stuff is patented, only curves over GF(q), q even,
> > which can be implemented efficiently using two-valued logic.
> 
> As I read it, this I-D includes these.
But it also includes Curves over GF(q), q prime or a power of some
odd prime. I wouldn't appreciate it much to exclude some stuff,
now that we have a definition including simply every finite field.
But my suggestion doesn't require an application to use binary
fields, and other curves are also given (and own for which noone
could claim any rights could be generated), so licence problems are
easy to avoid.

As I already mentioned to some people, I think it is the main topic
for an internet standard to enhance interoperability. So im still
convinced it is a good idea to provide a common way to store data
for ECC algorithms even if a particular implementation decide not to
use ECC (or not all suggested curves) for licence reasons.

I see the point that we shouldn't do the work for those who claimed
rights that should not be granted to anyone (like patenting a number).

But 1. most of the work is done, 2. a patent won't last forever and
if a standard is available before it's most likely that future
applications will conform to it.
-- 
Dominikus Scherkl
Biodata Application Security AG
mail: Dominikus.Scherkl@Biodata.com