IETF Logo Mail Archive

RE: [Ipsec] draft-ietf-ipsec-ikev2-17.txt

Stephen Kent <kent@bbn.com> Mon, 04 October 2004 19:13 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04907 for <ipsec-archive@lists.ietf.org>; Mon, 4 Oct 2004 15:13:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEY9P-0004cD-Cl; Mon, 04 Oct 2004 15:05:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEY3q-0006ma-HQ for ipsec@megatron.ietf.org; Mon, 04 Oct 2004 14:59:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03059 for <ipsec@ietf.org>; Mon, 4 Oct 2004 14:59:48 -0400 (EDT)
Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEYCy-0003q0-C2 for ipsec@ietf.org; Mon, 04 Oct 2004 15:09:17 -0400
Received: from [128.89.89.75] (dhcp89-089-075.bbn.com [128.89.89.75]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id i94IxGjf023974; Mon, 4 Oct 2004 14:59:17 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po2.bbn.com
Message-Id: <p06110416bd874c0c89e0@[128.89.89.75]>
In-Reply-To: <F5F4EC6358916448A81370AF56F211A50404E495@RED-MSG-51.redmond.corp.microsof t.com>
References: <F5F4EC6358916448A81370AF56F211A50404E495@RED-MSG-51.redmond.corp.microsof t.com>
Date: Mon, 04 Oct 2004 14:53:04 -0400
To: Charlie Kaufman <charliek@microsoft.com>
From: Stephen Kent <kent@bbn.com>
Subject: RE: [Ipsec] draft-ietf-ipsec-ikev2-17.txt
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ipsec@ietf.org, housley@vigilsec.com
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Security <ipsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
Sender: ipsec-bounces@ietf.org
Errors-To: ipsec-bounces@ietf.org

At 11:30 AM -0700 10/4/04, Charlie Kaufman wrote:
>I couldn't find RFC2402bis and RFC2406bis in forms that could be
>referenced, so no. Are these part of the set that will be advanced
>together? If so, I assume there is some mechanism to get them to all
>reference one another as part of the advancement process.
>
>Pointers to how to make sure this happens would be appreciated.
>
>	--Charlie

Charlie,

yes, they cleared WG last call a long time ago, and have been waiting 
for 2401bis and IKEv2.  Russ tells me that they will be progressed 
together.

I'll ask Karen to send you the current references.

Steve

_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec

v2.23.0 | Report a Bug | By Email