Re: [IPsec] IKEv2 Diffie-Hellman Elliptic curve mess (RFC4753, RFC5114, RFC4869, and draft-solinas-rfc4753bis-01)

"Dan Harkins" <dharkins@lounge.org> Sat, 23 January 2010 08:13 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C75EA3A67B3 for <ipsec@core3.amsl.com>; Sat, 23 Jan 2010 00:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level:
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YPG3Bbx-lXNv for <ipsec@core3.amsl.com>; Sat, 23 Jan 2010 00:13:15 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by core3.amsl.com (Postfix) with ESMTP id 237203A659C for <ipsec@ietf.org>; Sat, 23 Jan 2010 00:13:15 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 8CFA01022404A; Sat, 23 Jan 2010 00:13:10 -0800 (PST)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Sat, 23 Jan 2010 00:13:10 -0800 (PST)
Message-ID: <48e61fa1cc7322f35f4ddf99d4faedb0.squirrel@www.trepanning.net>
In-Reply-To: <4B59F2F1.9030107@orion.ncsc.mil>
References: <19243.32427.247190.77844@fireball.kivinen.iki.fi> <p06240800c756c4a8ed30@[10.20.30.249]> <4B59F2F1.9030107@orion.ncsc.mil>
Date: Sat, 23 Jan 2010 00:13:10 -0800
From: Dan Harkins <dharkins@lounge.org>
To: "Jerome A. Solinas" <jasolin@orion.ncsc.mil>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: ipsec@ietf.org
Subject: Re: [IPsec] IKEv2 Diffie-Hellman Elliptic curve mess (RFC4753, RFC5114, RFC4869, and draft-solinas-rfc4753bis-01)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 23 Jan 2010 08:13:18 -0000

  I agree with Jerome's opinion. Let's leave 19, 20, and 21 the way
they are. If there is confusion between the 2 RFCs than let's fix it
in a -bis favoring the former of the two.

  Dan.

On Fri, January 22, 2010 10:48 am, Jerome A. Solinas wrote:
> Paul Hoffman wrote:
>> First off, thank you for bringing the topic to the WG. As the Designated
>> Expert, you are certainly allowed to make decisions without asking, so
>> it is extra nice that you ask on decisions that might be controversial.
>>
>> On this particular topic, I would note that RFC 4753 is Informational
>> RFC, not a standards-track document. Thus, I would think that desires of
>> the authors of the RFC should have a heavier influence than the rest of
>> us, although our input might be important inputs to them (and maybe to
>> the Designated Expert). Maybe we should put the issue aside until we
>> hear from them, which could be after the holiday.
>>
>> --Paul Hoffman, Director
>>
> We would recommend keeping the same numbers (19, 20, 21) since it
> appears that all existing implementations have made the correction.
> Also, we would prefer to keep RFC4753 and RFC5114 distinct since we'd
> like to keep a separate document as a Suite B reference.  If the
> inclusion of the three ECP groups in two different standards is causing
> confusion, it might be worth thinking about removing them from the
> upcoming RFC5114 update.
>
> -- Jerome A. Solinas, RFC4753 coauthor
>
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>