Re: ISAKMP Draft: NotifyCodes, alignment

"Derrell D. Piper" <ddp@network-alchemy.com> Thu, 19 February 1998 23:39 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id SAA12264 for ipsec-outgoing; Thu, 19 Feb 1998 18:39:49 -0500 (EST)
Message-Id: <199802192353.SAA12215@relay.rv.tis.com>
To: John Burke <jburke@cylink.com>
cc: wdm@epoch.ncsc.mil, ipsec@tis.com
Subject: Re: ISAKMP Draft: NotifyCodes, alignment
In-reply-to: Your message of "Thu, 19 Feb 1998 13:48:03 PST." <3.0.32.19980219134802.009d9790@192.43.161.2>
Date: Thu, 19 Feb 1998 15:52:29 -0800
From: "Derrell D. Piper" <ddp@network-alchemy.com>
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

John,

>The IP DOI (v-06 and earlier) actually violated the ISAKMP draft by using
>codes in the Private range as Status codes (the DOI is a standard, not
>Private, right?).  Since people are presumably implementing these codes
>already, perhaps it would be better for the ISAKMP draft to change to make
>the present DOI valid.  Also the draft should spec the full range of the
>16-bit number.  How about this:

>From the current ISAKMP draft (note last sentence):

  3.14.1 Notify Message Types
  
  
  Notification information can be error messages specifying why an SA could
  not be established.  It can also be status data that a process managing
  an SA database wishes to communicate with a peer process.  For example,
  a secure front end or security gateway may use the Notify message to syn-
  chronize SA communication.  The table below lists the Nofitication mes-
  sages and their corresponding values.  Values in the Private Use range are
  expected to be DOI-specific values.

Derrell