Re: [Cfrg] [IANA #809084] Conflict Review requested for draft-irtf-cfrg-chacha20-poly1305
Yoav Nir <ynir.ietf@gmail.com> Fri, 20 February 2015 21:53 UTC
Return-Path: <ynir.ietf@gmail.com>
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 B819F1A886B; Fri, 20 Feb 2015 13:53:42 -0800 (PST)
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 IUI2dDKJpvQg; Fri, 20 Feb 2015 13:53:35 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (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 1D2611A0222; Fri, 20 Feb 2015 13:53:35 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so5749236wid.5; Fri, 20 Feb 2015 13:53:33 -0800 (PST)
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=rQ1WgSziF1fc4n6rzU7t+97sy2VKLnfpQC3wqWtdCBI=; b=At4pr7Xh+rI8AtlLWQSE6NDxndrYz7iOs2qvkJZ34/IuSMfqcqk8tXCeWB36ceBugO eeKaUnlc1TOJre29gvQUA+pJjMPrWKkdOo0KDG6LZAzPmbCIpEQd6SiJuc5AfJlIZQAe ajJsn7gZrD+Tpn4EvCJJer6tZ84pPM8fjW69XIHvRNJCUbQ1aR+4nkv+O0VhYBlhuyV9 soK5U4ZTB67+uadz4Za4S+UdEttppTDyIo6XPE8yBqEec01H26mn2QzWrzXal11pD6ij lPxCMoM/VXBh5oDDUNj2yReFWm9DrWLfeK5Lnxb/0m5Chf8V1Lnh/QprXZimnk1Rgst3 Wr4w==
X-Received: by 10.194.48.12 with SMTP id h12mr23600869wjn.74.1424469213811; Fri, 20 Feb 2015 13:53:33 -0800 (PST)
Received: from [192.168.1.13] ([46.120.13.132]) by mx.google.com with ESMTPSA id l6sm43859105wjx.33.2015.02.20.13.53.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 13:53:33 -0800 (PST)
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: <rt-4.2.9-2332-1424190105-64.809084-7-0@icann.org>
Date: Fri, 20 Feb 2015 23:53:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5348465-5B06-4C6B-A4F9-F158F618F697@gmail.com>
References: <RT-Ticket-809084@icann.org> <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> <20150217075216.6259935f@chromobil.localdomain> <0B311C17-32B3-4E07-A085-91F6FA14BA4E@gmail.com> <rt-4.2.9-2332-1424190105-64.809084-7-0@icann.org>
To: drafts-eval@iana.org
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/cfrg/k-6weYUWim3VP9-vHakCpAU_jyY>
Cc: cfrg@ietf.org, irsg@irtf.org, cfrg-chairs@ietf.org, draft-irtf-cfrg-chacha20-poly1305.all@ietf.org
Subject: Re: [Cfrg] [IANA #809084] 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: Fri, 20 Feb 2015 21:53:42 -0000
Fixed in version -10. > On Feb 17, 2015, at 6:21 PM, Pearl Liang via RT <drafts-eval@iana.org> wrote: > > Thank you Stefan for pointing that out. > > Yoav, please update the next version of the draft to the new requested name to > 'AEAD_CHACHA20_POLY1305' with underscores. Regarding what characters > are allowed in RFC5116, you may check with David McGrew. > > I leave it as IANA Okay for the draft. > > Thanks, > ~pl > > On Tue Feb 17 09:40:17 2015, ynir.ietf@gmail.com wrote: >> On Feb 17, 2015, at 8:52 AM, Stefan Bühler <source@stbuehler.de> wrote: >>> >>> 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. >> >> I’m fine with that as well. > >