Re: request

"Derrell D. Piper" <ddp@network-alchemy.com> Fri, 15 October 1999 05:33 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by mail.imc.org (8.9.3/8.9.3) with ESMTP id WAA15433; Thu, 14 Oct 1999 22:33:30 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id AAA02255 Fri, 15 Oct 1999 00:01:42 -0400 (EDT)
Message-Id: <199910150402.VAA01414@gallium.network-alchemy.com>
To: scott.davidson@iprg.nokia.com
cc: jerome@psti.com, ipsec@lists.tislabs.com
Subject: Re: request
In-reply-to: Your message of "Thu, 14 Oct 1999 21:29:56 CDT." <NCBBIIIDALGGCGKAECNGOEFCCCAA.scott.davidson@iprg.nokia.com>
Date: Thu, 14 Oct 1999 21:02:54 -0700
From: "Derrell D. Piper" <ddp@network-alchemy.com>
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

Scott,

>The standard known as ISAKMP/Oakley is now known as IKE

Correct.

>The standard known as IKE does not specifically exactly conform to the
>standard known as ISAKMP/Oakley
>Manufacturers have adopted IKE in order to satisfy customer needs rather
>than try to comply with the full ISAKMP/Oakley standard
>IKE and ISAKMP/Oakley are not the same standard as viewed from the RFC,
>IKE is a subset of the original standard that for all intents and
>purposes is the same thing in practical applications.

These statements are partially incorrect and misleading.  What you may have
meant is that IKE does not implement all of ISAKMP or all of Oakley.  That's
certainly true.  However, IKE is ISAKMP/Oakley and is _the_ key exchange
mechanism that the IETF adopted.  All we did was shorten its name to make it
more pronouncable.  We published the Oakley draft as an RFC because it
provides important background and justification for the security of the IKE
key exchange protocol.

>You will hear IKE and ISAKMP/Oakley used interchangeably

Actually, few people speak of ISAKMP/Oakley anymore.

Derrell

request CHIU,JAY C F
RE: request Scott Davidson
Re: request jerome
RE: request Scott Davidson
Re: request Derrell D. Piper
RE: request Scott Davidson