[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Last Call for IPSEC

To: "Scott G. Kelly" <skelly@redcreek.com>, Lewis McCarthy <lmccarth@cs.umass.edu>
Subject: Re: Last Call for IPSEC
From: Robert Moskowitz <rgm-sec@htt-consult.com>
Date: Wed, 15 Apr 1998 00:25:10 -0400
Cc: Peter Ford <peterf@microsoft.com>, iesg@ietf.org, ipsec@tis.com
In-Reply-To: <352D2FF9.C3530302@redcreek.com>
References: <8D8EF175E72CD111805800805F3198EE03925D67@red-msg-46.dns.microsoft.com><352D1160.446B@cs.umass.edu>
Sender: owner-ipsec@ex.tis.com

At 01:30 PM 4/9/98 -0700, Scott G. Kelly wrote:
>
>ISAKMP is designed to accept key-exchange plug-ins. This makes ISAKMP a
>well-designed protocol, in that if we find flaws with the key-exchange
>component, it may be replaced without designing an entirely new
>protocol. This seems quite reasonable to anticipate, given the relative
>dearth of practical operating experience in this frontier.

Note that ISAKMP is standards track.  That was in recognistion of its
nature.  Will there be another 'IKE'?  Field experience will tell.  Also it
is up to other wgs to see how they will embrace ISAKMP.  Will they use IKE
with their own DOI?  Or develop 'Casidy' or 'Carson', or....

Robert Moskowitz
ICSA
Security Interest EMail: rgm-sec@htt-consult.com

References:

Last Call for IPSEC

From: Peter Ford <peterf@microsoft.com>

Re: Last Call for IPSEC

From: Lewis McCarthy <lmccarth@cs.umass.edu>

Re: Last Call for IPSEC

From: "Scott G. Kelly" <skelly@redcreek.com>

Prev by Date: Re: byte order
Next by Date: Re: Last Call: Security Architecture for the Internet Protocol to Proposed Standard
Prev by thread: Re: Last Call for IPSEC
Next by thread: RE: Last Call for IPSEC
Index(es):
- Main
- Thread