Re: comments on ...isakmp-mode-cfg-02
Tero Kivinen <kivinen@ssh.fi> Mon, 23 March 1998 21:37 UTC
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id QAA26195 for ipsec-outgoing; Mon, 23 Mar 1998 16:37:18 -0500 (EST)
Date: Mon, 23 Mar 1998 23:50:38 +0200
Message-Id: <199803232150.XAA05431@pilari.ssh.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: Tero Kivinen <kivinen@ssh.fi>
To: "Scott G. Kelly" <skelly@redcreek.com>
Cc: "Michael C. Richardson" <mcr@sandelman.ottawa.on.ca>, ipsec@tis.com
Subject: Re: comments on ...isakmp-mode-cfg-02
In-Reply-To: <3510073F.E92CCB2C@redcreek.com>
References: <199803180036.TAA03135@istari.sandelman.ottawa.on.ca> <3510073F.E92CCB2C@redcreek.com>
X-Mailer: VM 6.34 under Emacs 19.34.2
Organization: SSH Communications Security Oy
X-Edit-Time: 1 min
Sender: owner-ipsec@ex.tis.com
Precedence: bulk
Scott G. Kelly writes: > > o Minor Version (4 bits) - indicates the minor version of the ISAKMP > > protocol in use. Implementations based on this version of the ISAKMP > > Internet-Draft MUST set the Minor Version to 0. Implementations > > *** > > based on previous versions of ISAKMP Internet-Drafts MUST set the > > Minor Version to 1. Implementations SHOULD never accept packets with > > *** > > a minor version number larger than its own, given the major version > > numbers are identical. > > > > Isn't the 0/1 minor numbers reversed? Previous == 1, current = 0?] > I think so - I sent email to Doug Maughan asking about this just before > v09 was released to the list, but figured either I was missing > something, or that he didn't get the email in time. No, they are not reversed. The old version number was 0.1 (major.minor) and now it is 1.0. So the major version number also changes and of course we then reset the minor version number back to zero: ---------------------------------------------------------------------- o Major Version (4 bits) - indicates the major version of the ISAKMP protocol in use. Implementations based on this version of the ISAKMP Internet-Draft MUST set the Major Version to 1. Implementations based on previous versions of ISAKMP Internet-Drafts MUST set the Major Version to 0. Implementations SHOULD never accept packets with a major version number larger than its own. o Minor Version (4 bits) - indicates the minor version of the ISAKMP protocol in use. Implementations based on this version of the ISAKMP Internet-Draft MUST set the Minor Version to 0. Implementations based on previous versions of ISAKMP Internet-Drafts MUST set the Minor Version to 1. Implementations SHOULD never accept packets with a minor version number larger than its own, given the major version numbers are identical. -- kivinen@iki.fi Work : +358-9-4354 3207 Magnus Enckellin kuja 9 K 19, 02610, Espoo Home : +358-9-502 1573
- 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