[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: where is draft-ietf-ipsec-oakley-02.
Actually, the OAKLEY draft (draft-ietf-ipsec-oakley-01.txt) expired on
August 24th. Does anyone know if or when it will be revised?
----------
From: Lewis McCarthy[SMTP:lmccarth@cs.umass.edu]
Sent: Tuesday, September 17, 1996 3:10 AM
To: ipsec
Subject: where is draft-ietf-ipsec-oakley-02.txt
The ISAKMP/Oakley resolution draft
(draft-ietf-ipsec-isakmp-oakley-00.txt) refers to a
draft-ietf-ipsec-oakley-02.txt. All I've been able to find in the
usual ID directories is -01.txt. Is the -02 a typo or is the new
version just remarkably hard to locate ?
--
Lewis http://www.cs.umass.edu/~lmccarth/lmkey.asc
"He said, `You are as constant as a northern star,' and I said,
`Constantly in the darkness ? Where's that at ?'" -- Joni Mitchell
Date: Tue, 17 Sep 1996 12:55:09 -0400
From: Hilarie Orman <ho@earth.hpc.org>
Message-Id: <199609171655.MAA18700@earth.hpc.org>
To: danmcd@pacific-86.eng.sun.com
Cc: ipsec@TIS.COM
In-Reply-To: Yourmessage <199609171541.IAA25888@kebe.eng.sun.com>
Subject: Re: Using SKIP as inspiration, not a
Sender: ipsec-approval@neptune.tis.com
Precedence: bulk
> REQURING more than one thing splits us vendors (especially those of us in
> politically hairy environments where I don't see eye-to-eye with others in a
> different part of said environment) into camps, and LOWERS interoperability
> and SLOWS deployment.
How much extra effort is required to add SKIP non-PFS support to an
IPSEC+some_kind_of_DH_key_mgmt_interface base? I'd think it should be
fairly trivial, under 100 lines of code (blithely said by someone who
hasn't written a line in some months). How can this be a serious
impediment?
Date: Tue, 17 Sep 1996 13:45:38 -0400
From: Hilarie Orman <ho@earth.hpc.org>
Message-Id: <199609171745.NAA20113@earth.hpc.org>
To: rpereira@timestep.com
Cc: ipsec@TIS.COM
In-Reply-To: Yourmessage <199609171717.KAA17319@baskerville.CS.Arizona.EDU>
Subject: Re: "RE: where is draft-ietf-ipsec-oakley-02."
Sender: ipsec-approval@neptune.tis.com
Precedence: bulk
There is an Oakley 02 draft in progress but languishing; I'd like the
next draft to be completely coordinated with related drafts, so I've
viewed my procrastination as a useful artifact. Plans for OAKLEY are
to add DH certificates to the list of OAKLEY authentication
mechanisms, clarify the use of signatures, standardize the use of
ISAKMP formats, and add the last elliptic curve group definition (EC
group available separately on request).
There are issues with respect to naming the transforms for the
required encryption and keyed hash mechanisms that remain open, and
I'm not sure they can be resolved by December. The details of how an
algorithm key is derived from an OAKLEY raw key are also open; this
should be part of the encryption and keyed hash transform interface
specifications.