RE: request
"Scott Davidson" <scott.davidson@iprg.nokia.com> Fri, 15 October 1999 17:45 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 KAA02225; Fri, 15 Oct 1999 10:45:35 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id LAA04912 Fri, 15 Oct 1999 11:50:02 -0400 (EDT)
Reply-To: scott.davidson@iprg.nokia.com
From: Scott Davidson <scott.davidson@iprg.nokia.com>
To: "Derrell D. Piper" <ddp@network-alchemy.com>
Cc: ipsec@lists.tislabs.com
Subject: RE: request
Date: Fri, 15 Oct 1999 10:51:52 -0500
MIME-Version: 1.0
Message-ID: <NCBBIIIDALGGCGKAECNGIEFFCCAA.scott.davidson@iprg.nokia.com>
Content-Type: multipart/signed; micalg="SHA1"; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_000C_01BF16FA.718A7E40"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-reply-To: <199910150402.VAA01414@gallium.network-alchemy.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
That is what I meant to say, exactly. Thanks for the clarification. Scott Davidson Central US Systems Engineer NOKIA IPRG US Sales - Dallas 214.632.6191 scott.davidson@iprg.nokia.com www.nokia.com support.iprg.nokia.com -----Original Message----- From: owner-ipsec@lists.tislabs.com [mailto:owner-ipsec@lists.tislabs.com]On Behalf Of Derrell D. Piper Sent: Thursday, October 14, 1999 11:03 PM To: scott.davidson@iprg.nokia.com Cc: jerome@psti.com; ipsec@lists.tislabs.com Subject: Re: request 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