IETF Logo Mail Archive

Re: [SPKM] Re: FW: I-D ACTION:draft-zhu-pku2u-01.txt

Nicolas Williams <Nicolas.Williams@sun.com> Thu, 19 April 2007 16:09 UTC

Return-path: <spkm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeZC3-0004Wu-P5; Thu, 19 Apr 2007 12:09:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeZC3-0004UR-BE for spkm@ietf.org; Thu, 19 Apr 2007 12:09:11 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeZC1-0003P4-WC for spkm@ietf.org; Thu, 19 Apr 2007 12:09:11 -0400
Received: from centralmail4brm.central.Sun.COM ([129.147.62.198]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l3JG95fQ010807 for <spkm@ietf.org>; Thu, 19 Apr 2007 16:09:09 GMT
Received: from binky.central.sun.com (binky.Central.Sun.COM [129.153.128.104]) by centralmail4brm.central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL, v2.2) with ESMTP id l3JG95aI012922 for <spkm@ietf.org>; Thu, 19 Apr 2007 10:09:05 -0600 (MDT)
Received: from binky.central.sun.com (localhost [127.0.0.1]) by binky.central.sun.com (8.13.8+Sun/8.13.6) with ESMTP id l3JG86nn011408; Thu, 19 Apr 2007 11:08:06 -0500 (CDT)
Received: (from nw141292@localhost) by binky.central.sun.com (8.13.8+Sun/8.13.8/Submit) id l3JG86YF011407; Thu, 19 Apr 2007 11:08:06 -0500 (CDT)
X-Authentication-Warning: binky.central.sun.com: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Thu, 19 Apr 2007 11:08:05 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Martin Rex <Martin.Rex@sap.com>
Subject: Re: [SPKM] Re: FW: I-D ACTION:draft-zhu-pku2u-01.txt
Message-ID: <20070419160805.GO4375@Sun.COM>
Mail-Followup-To: Martin Rex <Martin.Rex@sap.com>, spkm@ietf.org, kitten@lists.ietf.org
References: <20070419145614.GJ4375@Sun.COM> <200704191552.l3JFqNWE008872@fs4113.wdf.sap.corp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200704191552.l3JFqNWE008872@fs4113.wdf.sap.corp>
User-Agent: Mutt/1.5.7i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: kitten@lists.ietf.org, spkm@ietf.org
X-BeenThere: spkm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Low Infrastructure Public Key GSS mechanism <spkm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/spkm>
List-Post: <mailto:spkm@ietf.org>
List-Help: <mailto:spkm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=subscribe>
Errors-To: spkm-bounces@ietf.org

On Thu, Apr 19, 2007 at 05:52:23PM +0200, Martin Rex wrote:
> When a feature of a revised spec is significantly clarified over the
> previous version of the spec, a backwards interoperability warning
> should be added.  This is missing in rfc-4178 4.2.

It is certainly not missing from where it belongs -- see RFC 4178,
Appendix C:

   ...
   The working group was not aware of any RFC 2478 implementations
   deployed on the Internet.  Even if there are such implementations, it
   is unlikely that they will inter-operate because of a critical flaw
   in the description of the encoding of the mechanism list in RFC 2478.

   With the approach taken in this specification, security is ensured
   between new implementations all the time while maintaining
   interoperability with the implementations deployed within the IETF
   community.  The working group believes that this justifies breaking
   compatibility with a correct implementation of RFC 2478.
   ...

Nico
-- 

_______________________________________________
SPKM mailing list
SPKM@ietf.org
https://www1.ietf.org/mailman/listinfo/spkm

v2.23.0 | Report a Bug | By Email