WG Last Call

Robert Moskowitz <rgm3@chrysler.com> Tue, 30 September 1997 19:25 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id PAA25730 for ipsec-outgoing; Tue, 30 Sep 1997 15:25:43 -0400 (EDT)
Message-Id: <>
Reply-To: rgm3@chrysler.com
X-Sender: rgm3@dilbert.is.chrysler.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 30 Sep 1997 14:10:53 -0400
To: ipsec@tis.com
From: Robert Moskowitz <rgm3@chrysler.com>
Subject: WG Last Call
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

Ted and I will start work group last call on the following documents
effective Oct 6, 1997:


The last call will end on Oct 17, 1997.  Documents without substantive
comments will go directly to the IESG.  Common practices on cleaning up
wording may result in new drafts going directly to the IESG.  Those
documents that the workgroup finds broken in some respect will cycle a
draft version within the workgroup.

draft-ietf-ipsec-isakmp-oakley-05.txt will start its last call shortly
after Dan publishes it.  The wait period will be determined by the extent
of the diff file from Dan and the resolution of the issue brought up by Hugo.

draft-ietf-ipsec-arch-sec-01.txt will not go into last call until a sense
of working group consensus surfaces.  There is no assurance that arch-01
will go into last call.

Note all of these drafts represent a unified specification, and the IESG is
expecting to review them as a set.  Thus it behooves all of us to review
them and get this done!

ipsec-oakley-02.txt and perhaps ipsec-doc-roadmap-01.txt will most likely
be informational, all the rest are standards track.

We need everyone to review these and comment on their readiness.  PLEASE
include the draft name in the subject for everyone's benefit.

Those that receive no major comments by 9/26/97 will start wg last call on
the 9/29/97.  We need to get ALL of these through wg last call before
sending on to the IESG!  The 3 drafts with notes attached are already not
considered ready for last call by the chairs.  We request the editors of
these documents to submit updated versions, based on wg concensus in the
next week.


The following documents are still considered wg documents, but will follow
the above group to the IESG.  We do not want to overload them with reading
and slow down approval on the core documents.  Note that since the working
group consensus was explicit IVs only, this list does not include any
proposals that use derived, or 'implicit' IVs.  If I did not get this list
right in this regard, let me know!

draft-ietf-ipsec-ciph-arcfour-00.txt		(author reports new ver soon)

Somehow, it seems that we need to develop applicablity statements for all
of these algorithms, suggestions anyone?

The following drafts, for various reasons are dead:

draft-ietf-ipsec-vpn-00.txt				old vpn, watch for wg BOF
draft-ietf-ipsec-revised-enc-mode-01.txt		roll into isakmp-oakley-05
draft-ietf-ipsec-new-esp-00.txt			old esp	drop
draft-ietf-ipsec-ah-hmac-sha-04.txt		old ah		drop
draft-ietf-ipsec-ah-hmac-sha-1-96-00.txt		old ah		drop
draft-ietf-ipsec-ah-hmac-md5-96-00.txt		old ah		drop

The following draft will be moved to IPsecond:


The following drafts are released to their authors for independent
Informational RFC publication AFTER the main IPsec drafts are issued as
RFCs.  The justification for this is either there was no wg concensus on
their value to the IPsec specification, or they use protocol designs (for
example, derived IV) rejected by wg concensus.


Thank you all.

Theodore T'so and Robert Moskowitz

Robert Moskowitz
Chrysler Corporation
(810) 758-8212

Robert Moskowitz
Chrysler Corporation
(810) 758-8212