Re: [Cfrg] [IANA #807002] Conflict Review requested for draft-irtf-cfrg-chacha20-poly1305
Stefan Bühler <source@stbuehler.de> Tue, 17 February 2015 06:52 UTC
Return-Path: <source@stbuehler.de>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB2A11A872B; Mon, 16 Feb 2015 22:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.361
X-Spam-Level:
X-Spam-Status: No, score=-1.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 DHAfDp4e8tTY; Mon, 16 Feb 2015 22:52:21 -0800 (PST)
Received: from mail.stbuehler.de (stbuehler.de [IPv6:2a01:4f8:150:5244::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF0841A8727; Mon, 16 Feb 2015 22:52:20 -0800 (PST)
Received: from chromobil.localdomain (unknown [IPv6:2a02:8070:a18c:be00:baca:3aff:fed7:a10a]) by mail.stbuehler.de (Postfix) with ESMTPSA id B5B005E1DAE; Tue, 17 Feb 2015 06:52:17 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=stbuehler.de; s=stbuehler1; t=1424155937; bh=1vPfDQPwEPTNlpsMVKs0hQvcgWDgHzaAkTRDqF98eyQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=EfWoPhbOFFVwcVYQ1eUpX9Be5jzUK2ZUK4K7sdixGODIsK4mmDC6NMnsRaWtLkTZ9 kDlmGG3opw42fH/VXeJxay64U6j323HIEmR+Yh2Jkb+WH3nappUGmL0JsLt9OY+mDa l9HxCVwlqF59tI+7wBBUXp1JHBz/v/F5V2h44V3s=
Date: Tue, 17 Feb 2015 07:52:16 +0100
From: Stefan Bühler <source@stbuehler.de>
To: Yoav Nir <ynir.ietf@gmail.com>
Message-ID: <20150217075216.6259935f@chromobil.localdomain>
In-Reply-To: <AC8A31A6-03C3-4B5E-86E3-E5C80C6DD21E@gmail.com>
References: <RT-Ticket-807002@icann.org> <20150203100029.14793.43971.idtracker@ietfa.amsl.com> <rt-4.2.9-17455-1424124917-809.807002-7-0@icann.org> <AC8A31A6-03C3-4B5E-86E3-E5C80C6DD21E@gmail.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/cfrg/xeS58ithzYL_QGcdtJPcsOu9HJ0>
Cc: drafts-eval@iana.org, cfrg-chairs@ietf.org, cfrg@ietf.org, draft-irtf-cfrg-chacha20-poly1305.all@ietf.org, irsg@irtf.org
Subject: Re: [Cfrg] [IANA #807002] Conflict Review requested for draft-irtf-cfrg-chacha20-poly1305
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Feb 2015 06:52:22 -0000
Hi, On Tue, 17 Feb 2015 00:28:22 +0200 Yoav Nir <ynir.ietf@gmail.com> wrote: > Hi. > > RFC 5116 makes no statement about what characters are allowed for > names in this registry. The only requirement is for names to begin > with “AEAD_”. Additionally, these names are not used in any protocol, > so the risk of having parsers making assumptions is very low. > > The reason this name contains a hyphen is to distinguish parameters > and modes of operation that are separated by underscored (such as > AEAD_AES_128_GCM, where 128 is the key length and GCM is the mode of > operation), from combinations of algorithms that we separated by a > hyphen. That same algorithms might have been named AEAD_AES_128-GHASH > instead. Since there is no mode of operation associated with > Poly1305, we instead used the hyphen notation. > > I don’t believe this makes much of a difference either way, so if > others believe it should be replaced with an underscore, that’s fine > with me. I think many implementations will try to use the name as identifier, and most languages won't allow hyphens as part of that - so I'd replace it with an underscore to have consistent names. Stefan