Re: [Cfrg] KCipher-2

Jon Callas <jon@callas.org> Fri, 07 December 2012 19:00 UTC

Return-Path: <jon@callas.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80AD421F875E for <cfrg@ietfa.amsl.com>; Fri, 7 Dec 2012 11:00:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VilvpQr04NOa for <cfrg@ietfa.amsl.com>; Fri, 7 Dec 2012 11:00:38 -0800 (PST)
Received: from mail.merrymeet.com (merrymeet.com [173.164.244.100]) by ietfa.amsl.com (Postfix) with ESMTP id C7EDE21F86AA for <cfrg@irtf.org>; Fri, 7 Dec 2012 11:00:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.merrymeet.com (Postfix) with ESMTP id C7E10143D6E3 for <cfrg@irtf.org>; Fri, 7 Dec 2012 11:00:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at merrymeet.com
Received: from mail.merrymeet.com ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BlwExoGV7KUi for <cfrg@irtf.org>; Fri, 7 Dec 2012 11:00:37 -0800 (PST)
Received: from keys.merrymeet.com (keys.merrymeet.com [173.164.244.97]) by mail.merrymeet.com (Postfix) with ESMTPSA id 9486A143D6D8 for <cfrg@irtf.org>; Fri, 7 Dec 2012 11:00:37 -0800 (PST)
Received: from [192.168.4.75] ([70.102.71.225]) by keys.merrymeet.com (PGP Universal service); Fri, 07 Dec 2012 11:00:37 -0800
X-PGP-Universal: processed; by keys.merrymeet.com on Fri, 07 Dec 2012 11:00:37 -0800
Mime-Version: 1.0 (Apple Message framework v1283)
From: Jon Callas <jon@callas.org>
In-Reply-To: <015c01cdd43a$f18f3b60$d4adb220$@augustcellars.com>
Date: Fri, 7 Dec 2012 11:00:30 -0800
Message-Id: <612879CA-AB3A-46AE-AD66-808EF4B4C57F@callas.org>
References: <015c01cdd43a$f18f3b60$d4adb220$@augustcellars.com>
To: "Jim Schaad" <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.1283)
X-PGP-Encoding-Format: Partitioned
X-PGP-Encoding-Version: 2.0.2
X-Content-PGP-Universal-Saved-Content-Transfer-Encoding: quoted-printable
X-Content-PGP-Universal-Saved-Content-Type: text/plain; charset=us-ascii
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: cfrg@irtf.org, Jon Callas <jon@callas.org>
Subject: Re: [Cfrg] KCipher-2
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 19:00:39 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My answers:

No, and yes.

Publish the document. It's an *informational* RFC. In general, I think that an informational RFC should default against editorializing. For a cipher, yes, you don't want to document something that is bad. We all know and agree that. We all also know the dangers of too many options. But we also know the dangers of monoculture. Providing information is different than interpreting it. I think KCipher-2 meets a bar on that. 

Yes, put the table in. It's a long-standing frustration of mine that crypto documents seem to think that part of the fun is to guess about implementation until you finally get it right. A sort of gameification, I suppose, that makes a spec a choose-your-own adventure. This gets boring, fast. The vast majority of us implementors want to get it done, fast and accurate. Anything that helps that is a Good Thing.

	Jon


-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 3.2.0 (Build 1672)
Charset: us-ascii

wj8DBQFQwjzVsTedWZOD3gYRAiKsAJ9uwclJKU5IGDAfo1D0+oBR693xwACgqSXa
D5QBJprFkRvn2xOoAYqqibQ=
=bog0
-----END PGP SIGNATURE-----