IETF Logo Mail Archive

Re: [Curdle] AD review of draft-ietf-curdle-cms-chacha20-poly1305-03

Russ Housley <housley@vigilsec.com> Wed, 30 November 2016 22:43 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E27129BA9 for <curdle@ietfa.amsl.com>; Wed, 30 Nov 2016 14:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUHkcT09loMO for <curdle@ietfa.amsl.com>; Wed, 30 Nov 2016 14:43:22 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC7512957E for <curdle@ietf.org>; Wed, 30 Nov 2016 14:43:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 889683001A6 for <curdle@ietf.org>; Wed, 30 Nov 2016 17:33:05 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 35MLGodSZs48 for <curdle@ietf.org>; Wed, 30 Nov 2016 17:33:04 -0500 (EST)
Received: from [192.168.2.100] (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 863EF300086; Wed, 30 Nov 2016 17:33:04 -0500 (EST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <f04798d8-6d68-e909-7a82-b29320eb79e7@cs.tcd.ie>
Date: Wed, 30 Nov 2016 17:41:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C69CB138-4560-44C5-9E46-C19135D57B9D@vigilsec.com>
References: <b27e8b77-5025-23f0-e71f-9c10af0b2265@cs.tcd.ie> <6E89FD59-D2DA-4697-AF37-5041B09F2035@vigilsec.com> <f04798d8-6d68-e909-7a82-b29320eb79e7@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/LAF8UOPK3HbXgtoS1w0f_5qNuws>
Cc: "curdle@ietf.org" <curdle@ietf.org>
Subject: Re: [Curdle] AD review of draft-ietf-curdle-cms-chacha20-poly1305-03
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2016 22:43:24 -0000

Responding only to the comment where we still have a disconnect.

>>> (2) section 3: What does "content authenticated encryption" mean
>>> exactly? You use that phrase a lot, and I don't know what it means
>>> and it does not occur in [CMS]. Do we need a better term?
>>> (Apologies if I'm forgetting the WG discussing that.)
>> 
>> RFC 5083 uses the term "content-authenticated-encryption keys”.  I
>> can add the hyphens id that improves clarity.
> 
> Personally, I think that term lacks clarity and adds confusion.
> I don't see why it's better than just saying "key" when you
> mean that, and "key+nonce" when that's meant.

No, that is not what is meant.

This key is used to authenticate and encrypt the content.  That is why RFC 5083 calls it the "content-authenticated-encryption key”.

I have just re-read Section 3, and I am at a loss to see where this confusion is coming from.

Russ

v2.23.0 | Report a Bug | By Email