Re: [IPsec] Early code point assignment (was: I-D Action: draft-ietf-ipsecme-chacha20-poly1305-00.txt)

Yoav Nir <ynir.ietf@gmail.com> Tue, 31 March 2015 14:16 UTC

Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E6031ACD5F for <ipsec@ietfa.amsl.com>; Tue, 31 Mar 2015 07:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 4YfuxD31aNWW for <ipsec@ietfa.amsl.com>; Tue, 31 Mar 2015 07:16:31 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16E501ACD6E for <ipsec@ietf.org>; Tue, 31 Mar 2015 07:16:31 -0700 (PDT)
Received: by wiaa2 with SMTP id a2so27953958wia.0 for <ipsec@ietf.org>; Tue, 31 Mar 2015 07:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HXncUfw6oEeUKU+pYhfATG/C4iuT08E3wSfXbb5baXc=; b=mPPNHpn+N4FVvxP+d86pZUGZmD0VK+2qstohp3b4EMj1IL+7pWtcdq8xeYfThYfTS5 93AmzTQJqn4Pn7yp72AvDU0IjrRGhdcLDpIYi/fhm4kvRjTD8bRuc76u+oziiZsrDIHp +VRrqD6r1woni/vTpDY1pllSmTq1sqAsTaJFFl0OomTE0uHE8vaKs7Neagka7krzcw9t 3ILvPzi4dGBsDN+7G0UPzFgjiYi4QX/Zu2XxvzjGY/vtkbc1h6oNEaiTVztuXGzehsu2 wun1vuUmKNWrouDocZvpDpyMVkaV5NuT5NXCXauJb5/Vz9TjLagJ36NZTHTzgqp4FhJ5 hv4w==
X-Received: by 10.194.133.199 with SMTP id pe7mr75481900wjb.120.1427811389716; Tue, 31 Mar 2015 07:16:29 -0700 (PDT)
Received: from [172.24.250.177] ([194.29.32.131]) by mx.google.com with ESMTPSA id bp1sm20554189wjb.31.2015.03.31.07.16.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 31 Mar 2015 07:16:28 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <alpine.LFD.2.10.1503311001100.1147@bofh.nohats.ca>
Date: Tue, 31 Mar 2015 17:16:24 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F071A62-C101-4683-AEBD-71BDD4D2BFBC@gmail.com>
References: <20150330133237.21486.80504.idtracker@ietfa.amsl.com> <D7430231-BDAB-4766-8637-D4609634F3D3@gmail.com> <09B9FFB9-3C87-45F6-96CD-BB02B08C83F1@gmail.com> <alpine.LFD.2.10.1503311001100.1147@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipsec/XxZt58iljcjZU_371aQBgs6ztY8>
Cc: IETF IPsec <ipsec@ietf.org>
Subject: Re: [IPsec] Early code point assignment (was: I-D Action: draft-ietf-ipsecme-chacha20-poly1305-00.txt)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 14:16:32 -0000

> On Mar 31, 2015, at 5:03 PM, Paul Wouters <paul@nohats.ca> wrote:
> 
> On Tue, 31 Mar 2015, Yoav Nir wrote:
> 
>> Seeing as none of the transform names begins with “ESP_” and that we’re specifying the algorithm for IKE as well as ESP, I’ve changed
>> the identifier to ENCR_ChaCha20_Poly1305.
>> Yoav
> 
> Can we make it ENCR_CHACHA20_POLY1305 ?
> 
> Currently IANA mostly has no CamelCase and it is kind of a C habbit to
> have defines in CAPS :)

I guess, although some of the names don’t quite work as identifiers: "AES-GCM with a 8 octet ICV” or "ENCR-AES-CCM_12”, which is surprisingly different in terms of dashes vs underscores than “ENCR_AES-CCM_8”.

Yoav