Re: [IPsec] Call for WG adoption: draft-nir-ipsecme-chacha20-poly1305

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 06 March 2015 16:01 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 5EFE91A005C for <ipsec@ietfa.amsl.com>; Fri, 6 Mar 2015 08:01:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] 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 vJT2E7A6HVjF for <ipsec@ietfa.amsl.com>; Fri, 6 Mar 2015 08:01:20 -0800 (PST)
Received: from proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22CD81A00B5 for <ipsec@ietf.org>; Fri, 6 Mar 2015 08:01:18 -0800 (PST)
Received: from [10.20.30.109] (142-254-17-245.dsl.dynamic.fusionbroadband.com [142.254.17.245]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t26G1HEr060703 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ipsec@ietf.org>; Fri, 6 Mar 2015 09:01:17 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 142-254-17-245.dsl.dynamic.fusionbroadband.com [142.254.17.245] claimed to be [10.20.30.109]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <86AC7585-93BD-456D-B75E-F85D2D2A2D7F@vpnc.org>
Date: Fri, 06 Mar 2015 08:01:19 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F74554C8-4FA0-485A-9B74-9DB0E70D68DD@vpnc.org>
References: <86AC7585-93BD-456D-B75E-F85D2D2A2D7F@vpnc.org>
To: IPsecME WG <ipsec@ietf.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipsec/8qmdCc6bbXndJJpcG2BZZNQO4qs>
Subject: Re: [IPsec] Call for WG adoption: draft-nir-ipsecme-chacha20-poly1305
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: Fri, 06 Mar 2015 16:01:22 -0000

On Feb 26, 2015, at 2:11 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> Greetings again. A few people have expressed interest in having https://tools.ietf.org/html/draft-nir-ipsecme-chacha20-poly1305 as a WG item for IPsecME. If you want this as a WG document, and you are willing to review drafts as they move through, please say so on this thread. If you are opposed to this being a WG document, please say so (and say why). Thanks in advance.

This got very little interest, which surprised me. Without a few more people who will commit to review the document and offer comments, we can't really call it a WG work item. Is there really so little interest in new algorithms that are being adopted in other protocols?

If you are an IPsec implementer, it would be very useful to know whether or not you would support adding this algorithm to your implementation, and why.

--Paul Hoffman