Re: ISAKMP Configuration Method

bradr@iname.com Tue, 30 November 1999 19:57 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA13489; Tue, 30 Nov 1999 11:57:43 -0800 (PST)
Received: by lists.tislabs.com (8.9.1/8.9.1) id NAA01403 Tue, 30 Nov 1999 13:21:41 -0500 (EST)
Date: Tue, 30 Nov 1999 09:19:36 -0800
From: bradr@iname.com
To: "Derrell D. Piper" <ddp@network-alchemy.com>
cc: ipsec@lists.tislabs.com
Subject: Re: ISAKMP Configuration Method
In-Reply-To: <199911301602.IAA15074@gallium.network-alchemy.com>
Message-ID: <Pine.LNX.4.21.9911300906400.17356-100000@spickard.inside.sealabs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

Thanks for the information, but I'm still a little confused. In section
3.2 of the draft-ietf-ipsec-isakmp-mode-cfg-05.txt document, a description
of a "new payload is defined to carry attributes as well as the type of
transaction message". This payload would have to be referenced from the
previous payload's `Next Payload' identifier field, right?

  -brad

On Tue, 30 Nov 1999, Derrell D. Piper wrote:

> 
> Brad,
> 
> > After reading through this particular draft as well as searching through
> > the DOI, ISAKMP, and other rfcs and drafts, I am unable to find any value
> > mentioned for the `Next Payload' identifier for the ATTRIBUTE_PAYLOAD of a
> > transaction exchange. Is this specified somewhere else, or did I just
> > overlook it?
> 
> The ISAKMP Attribute information is not encoded as a separate payload.
> Instead, it's basically appended to any of the defined payloads.  Its format
> is defined in Section 3.3 of RFC 2408.
> 
> Derrell
>

ISAKMP Configuration Method bradr
Re: ISAKMP Configuration Method Derrell D. Piper
Re: ISAKMP Configuration Method bradr
Re: ISAKMP Configuration Method Derrell D. Piper
Re: ISAKMP Configuration Method bradr