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

Re: ISAKMP Configuration Method

To: bradr@iname.com
Subject: Re: ISAKMP Configuration Method
From: "Derrell D. Piper" <ddp@network-alchemy.com>
Date: Tue, 30 Nov 1999 08:02:32 -0800
cc: ipsec@lists.tislabs.com
In-reply-to: Your message of "Mon, 29 Nov 1999 15:45:26 PST." <Pine.LNX.4.21.9911291538200.16636-100000@spickard.inside.sealabs.com>
Sender: owner-ipsec@lists.tislabs.com

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

Follow-Ups:

Re: ISAKMP Configuration Method

From: bradr@iname.com

References:

ISAKMP Configuration Method

From: bradr@iname.com

Prev by Date: General discussion
Next by Date: IPSec SA DELETE in "dangling" implementation
Prev by thread: ISAKMP Configuration Method
Next by thread: Re: ISAKMP Configuration Method
Index(es):
- Main
- Thread