AW: Reasons to include ECC to our charter
"Dominikus Scherkl" <Dominikus.Scherkl@biodata.com> Thu, 09 August 2001 14:59 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 KAA26102 for <openpgp-archive@odin.ietf.org>; Thu, 9 Aug 2001 10:59:41 -0400 (EDT)
Received: by above.proper.com (8.11.3/8.11.3) id f79Eo2b18879 for ietf-openpgp-bks; Thu, 9 Aug 2001 07:50:02 -0700 (PDT)
Received: from mail1.biodata.com ([62.159.113.2]) by above.proper.com (8.11.3/8.11.3) with ESMTP id f79Eo0N18867 for <ietf-openpgp@imc.org>; Thu, 9 Aug 2001 07:50:00 -0700 (PDT)
Received: from fra1d001.biodata.org ([10.10.1.51]) by mail1.biodata.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 9 Aug 2001 16:49:49 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
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
Date: Thu, 09 Aug 2001 16:49:49 +0200
Message-ID: <100722F3C53A484B8CF1F14B4F062E93157061@fra1d001.biodata.org>
Thread-Topic: Reasons to include ECC to our charter
Thread-Index: AcEg4WalieDgznX9R+O3lfinU+xmXAAAGDzw
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: 09 Aug 2001 14:49:49.0825 (UTC) FILETIME=[8A4F8710:01C120E2]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id f79Eo1N18873
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
> You can't add [ECC] to the _standard_ because of restrictive licensing. ?!? The openPGP standard is exactly this - "open". So of course we can add ECC (it is still reserved). Or do you mean patents on ECC? That is also no Problem, because patents only apply to the applications that implement the standard - they need to licence the algorithms. If not licenced, the application may not support ECC (but is still conform to the standard - same as for elgamal). -- Dominikus Scherkl Biodata Application Security AG mail: Dominikus.Scherkl@Biodata.com
- AW: Reasons to include ECC to our charter Dominikus Scherkl
- Re: Reasons to include ECC to our charter Thomas Roessler
- AW: Reasons to include ECC to our charter Dominikus Scherkl
- Re: AW: Reasons to include ECC to our charter John W Noerenberg II
- AW: Reasons to include ECC to our charter Dominikus Scherkl
- Re: AW: Reasons to include ECC to our charter Bodo Moeller
- AW: Reasons to include ECC to our charter Dominikus Scherkl
- AW: Reasons to include ECC to our charter Dominikus Scherkl
- Re: AW: Reasons to include ECC to our charter Ben Laurie
- AW: Reasons to include ECC to our charter Dominikus Scherkl
- Re: AW: Reasons to include ECC to our charter Ben Laurie
- Re: AW: Reasons to include ECC to our charter Shawn C. Masters