Re: question on "code preserving" section in Paul's draft

Dan Harkins <dharkins@tibernian.com> Wed, 15 May 2002 21:23 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g4FLNZL11939; Wed, 15 May 2002 14:23:35 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id QAA05249 Wed, 15 May 2002 16:44:45 -0400 (EDT)
Message-Id: <200205152056.g4FKuUk09579@trpz.com>
To: Michael Thomas <mat@cisco.com>
cc: ipsec@lists.tislabs.com
Subject: Re: question on "code preserving" section in Paul's draft
In-Reply-To: Your message of "Wed, 15 May 2002 11:33:31 PDT." <15586.43515.644098.353766@thomasm-u1.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <684.1021495619.1@tibernian.com>
Date: Wed, 15 May 2002 13:46:59 -0700
From: Dan Harkins <dharkins@tibernian.com>
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

  It is not our intention to say "MUST implement" IKEv1. If you have
already implemented IKEv1 then there will be things, like the payload
parsing code, that can be reused when writing IKEv2. If you have not
implemented IKEv1 then "code preservingness" is a non-issue. We're
not forcing people to write IKEv1 so they can reuse code when implemen-
ting IKEv2. Definitely not.

  I didn't get that impression from the draft but if you did then
most likely more people did too. What's the particular text that gave
you that impression so it can be re-whacked?

  Dan.

On Wed, 15 May 2002 11:33:31 PDT you wrote
> 
> Paul's SOI draft seems to imply that an IKEv2
> implementation must also implement IKEv1 as well.
> 
> Is that the intention of the IKEv2 authors? If
> so, there's more to this issue, not the least of
> which is an even *heavier* burden placed on small
> memory footprint widgets.
> 
> 		 Mike