Re: NIST publishes new DSA draft

Jon Callas <jon@callas.org> Sun, 19 March 2006 20:22 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL4QL-00034q-H4 for openpgp-archive@lists.ietf.org; Sun, 19 Mar 2006 15:22:49 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FL4QL-0000Y9-1E for openpgp-archive@lists.ietf.org; Sun, 19 Mar 2006 15:22:49 -0500
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k2JK2HP5073179; Sun, 19 Mar 2006 13:02:17 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id k2JK2HIC073178; Sun, 19 Mar 2006 13:02:17 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from merrymeet.com (merrymeet.com [63.73.97.162]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k2JK2GMt073171 for <ietf-openpgp@imc.org>; Sun, 19 Mar 2006 13:02:16 -0700 (MST) (envelope-from jon@callas.org)
Received: from keys.merrymeet.com (63.73.97.166) by merrymeet.com with ESMTP (Eudora Internet Mail Server X 3.2.7) for <ietf-openpgp@imc.org>; Sun, 19 Mar 2006 12:02:13 -0800
Received: from [130.129.130.213] ([130.129.130.213]) by keys.merrymeet.com (PGP Universal service); Sun, 19 Mar 2006 12:02:13 -0800
X-PGP-Universal: processed; by keys.merrymeet.com on Sun, 19 Mar 2006 12:02:13 -0800
Mime-Version: 1.0 (Apple Message framework v746.3)
In-Reply-To: <200603151914.k2FJE45H081897@mailserver2.hushmail.com>
References: <200603151914.k2FJE45H081897@mailserver2.hushmail.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <5BA6C174-0734-48CA-8D66-325081E5AEFF@callas.org>
Content-Transfer-Encoding: 7bit
From: Jon Callas <jon@callas.org>
Subject: Re: NIST publishes new DSA draft
Date: Sun, 19 Mar 2006 12:02:11 -0800
To: OpenPGP <ietf-openpgp@imc.org>
X-Mailer: Apple Mail (2.746.3)
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

> note that 3-DES is now referred to as TDEA
> should this perhaps be included in rfc 2440 when 3-DES is
> mentioned?
> i.e.
> when 3-DES is first mentioned,
> it should be referred to as 3-DES(also known as TDEA)

They're not the same. There is DES and DEA, just as there is DSA and  
DSS. In each pair, there is an Algorithm and a Standard. The standard  
is the algorithm plus other stuff. In the case of DES, it specifies  
that the low bit of each byte (excuse me, octet) of the key is a  
parity bit (and possibly other stuff I don't remember). Everyone uses  
DES, not DEA. What we use is 3DES, not TDEA. In the case of DSS, we  
*do* mean DSA because there were people who wanted (for example) to  
use RIPE-MD/160 with DSA, not SHA-1, as DSS.

I suppose we could call it "TDES," but it's been called "3DES" or  
"Triple-DES" for ages. If all of a sudden we start calling it TDES,  
there will be many people who will rightly mutter, "TDES? What the % 
$@! is TDES? Oh, *3DES*, why didn't you say so?"

	Jon