Re: comments on ...isakmp-mode-cfg-02
"Scott G. Kelly" <skelly@redcreek.com> Tue, 17 March 1998 00:36 UTC
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id TAA10856 for ipsec-outgoing; Mon, 16 Mar 1998 19:36:38 -0500 (EST)
Message-ID: <350DC8D4.F23C2A7@redcreek.com>
Date: Mon, 16 Mar 1998 16:50:28 -0800
From: "Scott G. Kelly" <skelly@redcreek.com>
Organization: RedCreek Communications
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: Roy Pereira <rpereira@TimeStep.com>
CC: "'ipsec@tis.com'" <ipsec@tis.com>
Subject: Re: comments on ...isakmp-mode-cfg-02
References: <c=US%a=_%p=TimeStep_Corpora%l=TSNTSRV2-980316162927Z-308@tsntsrv2.timestep.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ipsec@ex.tis.com
Precedence: bulk
Roy Pereira wrote: > This same converstaion has gone on for a couple of weeks off the mailing > list as well, so I'd like to propose the following: > > 1) A separate Config payload is defined. > 2) Support for ISAKMP-Cfg is denoted by a ISAKMP version of 1.1 or > higher. Support does not mean you actually use it, just that it does > not break your implementation. > > Comments? This makes more sense. Since the draft is relatively new, it will (probably) be hashed out in IPSECond. That being the case, it makes sense to properly integrate the functionality into the protocol.
- comments on ...isakmp-mode-cfg-02 Scott G. Kelly
- RE: comments on ...isakmp-mode-cfg-02 Roy Pereira
- RE: comments on ...isakmp-mode-cfg-02 Shawn Mamros
- Re: comments on ...isakmp-mode-cfg-02 Scott G. Kelly
- Re: comments on ...isakmp-mode-cfg-02 Michael C. Richardson
- RE: comments on ...isakmp-mode-cfg-02 Roy Pereira
- Re: comments on ...isakmp-mode-cfg-02 Scott G. Kelly
- Re: comments on ...isakmp-mode-cfg-02 Tero Kivinen