Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCUSS questions
Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 04 September 2014 07:48 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E5A1A6F27; Thu, 4 Sep 2014 00:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level:
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668] 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 URck3ROWV4Vz; Thu, 4 Sep 2014 00:48:22 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id E8E8C1A6F26; Thu, 4 Sep 2014 00:48:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A2866BF17; Thu, 4 Sep 2014 08:48:20 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iV9jP6vdHtTU; Thu, 4 Sep 2014 08:48:19 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.42.16.156]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 82875BEBE; Thu, 4 Sep 2014 08:48:19 +0100 (IST)
Message-ID: <54081943.3040107@cs.tcd.ie>
Date: Thu, 04 Sep 2014 08:48:19 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: Tom Henderson <tomh@tomh.org>, Tobias.Heer@Belden.com
References: <OFE663CEC5.35AA808D-ONC1257D47.005B2906-C1257D47.005F754B@belden.com> <5407F111.3050802@tomh.org>
In-Reply-To: <5407F111.3050802@tomh.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/hipsec/ai-XB5Fl9WUlhT8lp6hkjZ6Uoi0
Cc: hipsec@ietf.org, IESG <iesg@ietf.org>
Subject: Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCUSS questions
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 07:48:24 -0000
Hiya, On 04/09/14 05:56, Tom Henderson wrote: >> > > How could we move this issue forward? Stephen, would you advocate > putting in 2048-bit and 4096-bit groups (perhaps with values 11 and 12 > respectively)? I would advocate putting in the 2048 bit group yes. I figure you probably don't need the 4096 one on the basis that before one would go there you'd want to switch to some form of ECC. So I'd not argue to define a codepoint for the 4096 bit group for now myself, but equally, I'd not argue against doing so. > Or is there not enough support for this proposal? I'm fine that that's a WG chair call. And now that we've discussed the topic, I've cleared that point in any case, moving to a no-objection overall. Thanks for the discussion. Cheers, S.
- [Hipsec] RFC5201-bis: Stephen Farrell's DISCUSS q… Tom Henderson
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Rene Hummen
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Tom Henderson
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Miika Komu
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Stephen Farrell
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Tobias.Heer
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Tom Henderson
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Stephen Farrell
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Tom Henderson
- Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCU… Rene Hummen