Re: [IPsec] RFC4307 & ENCR_NULL & USGv6 profile & Roadmap document

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 21 October 2009 20:27 UTC

Return-Path: <paul.hoffman@vpnc.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 CC09428C14B for <ipsec@core3.amsl.com>; Wed, 21 Oct 2009 13:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.439
X-Spam-Level:
X-Spam-Status: No, score=-5.439 tagged_above=-999 required=5 tests=[AWL=0.607, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 i6YUsHXcIlaq for <ipsec@core3.amsl.com>; Wed, 21 Oct 2009 13:27:30 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 0C26328C141 for <ipsec@ietf.org>; Wed, 21 Oct 2009 13:27:30 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n9LKRaEE046123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Oct 2009 13:27:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240809c7051edfa378@[10.20.30.158]>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C4930789878B68@MBCLUSTER.xchange.nist.gov>
References: <19165.48619.530034.469960@fireball.kivinen.iki.fi> <D7A0423E5E193F40BE6E94126930C4930789878B5E@MBCLUSTER.xchange.nist.gov>, <p 06240807c70514f45089@[10.20.30.158]> <D7A0423E5E193F40BE6E94126930C4930789878B68@MBCLUSTER.xchange.nist.gov>
Date: Wed, 21 Oct 2009 13:27:35 -0700
To: "Frankel, Sheila E." <sheila.frankel@nist.gov>, Tero Kivinen <kivinen@iki.fi>, "ipsec@ietf.org" <ipsec@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [IPsec] RFC4307 & ENCR_NULL & USGv6 profile & Roadmap document
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: Wed, 21 Oct 2009 20:27:30 -0000

At 4:08 PM -0400 10/21/09, Frankel, Sheila E. wrote:
>If that's the case, we'll remove the offending statements in the roadmap.

Assuming others remember it as I do (well, after looking at the archive), that would be great.

>Just 2 more questions: even if this was a sloppy document, why is there a separate section for IKE Encrypted Payload algorithms, that contains a subset of the Transform Type 1 (encryption) algorithms?

Because the split happened late in the process when many of us were quite burned out; we didn't review carefully.

> Also, is sloppiness enough to account for both NULL encryption and AES-CTR being specified for IKEv2 - and noone from the WG noticing either?

I think so, unfortunately.

--Paul Hoffman, Director
--VPN Consortium