[Admin] ISAKMP Inline Keying document editor
Ran Atkinson <rja@cisco.com> Fri, 01 November 1996 14:16 UTC
Received: from cnri by ietf.org id aa03100; 1 Nov 96 9:16 EST
Received: from neptune.hq.tis.com by CNRI.Reston.VA.US id aa10131; 1 Nov 96 9:16 EST
Received: from neptune.tis.com by neptune.TIS.COM id aa01718; 1 Nov 96 8:29 EST
Message-Id: <199611010057.QAA19310@cornpuffs.cisco.com>
From: Ran Atkinson <rja@cisco.com>
Date: Thu, 31 Oct 1996 16:57:00 -0800
In-Reply-To: rja@cisco.com (Ran Atkinson) "ISAKMP support for inline keying" (Oct 16, 4:05pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: ipsec@tis.com
Subject: [Admin] ISAKMP Inline Keying document editor
Sender: ipsec-approval@neptune.tis.com
Precedence: bulk
All, The IPsec WG co-chairs would like to announce the appointment of Bill Sommerfeld <sommerfeld@apollo.hp.com> as IPsec Document Editor for adding inline-keying support within the ISAKMP framework. This action is taken in conformance with the guidance provided by the Security AD in his September public statement. Bill is specifically asked to prepare an I-D (and corresponding presentation for the San Jose IETF) on placing inline-keying mechanisms within the ISAKMP Framework. This work is to be based on in part on SKIP as defined in <draft-ietf-ipsec-skip-07.txt> and the other SKIP documents, and also based in part on inputs from other members of the working group. One goal of this specification is to devise a protocol that could share code with an ISAKMP implementation wherever that might be practical. It is intended that the resulting document will follow the normal IETF standards track ultimately resulting in a protocol specification that is ELECTIVE standard. Change control for the resulting specification will rest solely with the IETF. Ran rja@cisco.com --
- [Admin] ISAKMP Inline Keying document editor Ran Atkinson