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

Re: ISAKMP Draft: NotifyCodes, alignment

To: John Burke <jburke@cylink.com>
Subject: Re: ISAKMP Draft: NotifyCodes, alignment
From: Daniel Harkins <dharkins@cisco.com>
Date: Thu, 19 Feb 1998 15:18:51 -0800
Cc: wdm@epoch.ncsc.mil, ipsec@tis.com
In-Reply-To: Your message of "Thu, 19 Feb 1998 13:48:03 PST." <3.0.32.19980219134802.009d9790@192.43.161.2>
Sender: owner-ipsec@ex.tis.com

  John,

> Notification Codes
> 
> 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.  

Section 3.14.1 of the ISAKMP draft specifically says:

   Values in the Private Use range are expected to be DOI-specific values.

so there is no violation of the draft.

  Dan.

References:

ISAKMP Draft: NotifyCodes, alignment

From: John Burke <jburke@cylink.com>

Prev by Date: ISAKMP Draft: NotifyCodes, alignment
Next by Date: Re: ISAKMP Draft: NotifyCodes, alignment
Prev by thread: ISAKMP Draft: NotifyCodes, alignment
Next by thread: Re: ISAKMP Draft: NotifyCodes, alignment
Index(es):
- Main
- Thread