IETF Logo Mail Archive

Re: KITTEN: IETF 75 - 76

Nicolas Williams <Nicolas.Williams@sun.com> Wed, 19 August 2009 22:25 UTC

Return-Path: <Nicolas.Williams@sun.com>
X-Original-To: kitten@core3.amsl.com
Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28D3B3A69DE for <kitten@core3.amsl.com>; Wed, 19 Aug 2009 15:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.903
X-Spam-Level:
X-Spam-Status: No, score=-5.903 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKIWgt6ntdk9 for <kitten@core3.amsl.com>; Wed, 19 Aug 2009 15:25:31 -0700 (PDT)
Received: from sca-ea-mail-2.sun.com (sca-ea-mail-2.Sun.COM [192.18.43.25]) by core3.amsl.com (Postfix) with ESMTP id E85E03A6C93 for <kitten@ietf.org>; Wed, 19 Aug 2009 15:25:24 -0700 (PDT)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n7JMPSbB001821 for <kitten@ietf.org>; Wed, 19 Aug 2009 22:25:28 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id n7JMPRDL054744 for <kitten@ietf.org>; Wed, 19 Aug 2009 16:25:27 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n7JMEjZS004568; Wed, 19 Aug 2009 17:14:45 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n7JMEf5j004567; Wed, 19 Aug 2009 17:14:41 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 19 Aug 2009 17:14:41 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Martin Rex <Martin.Rex@sap.com>
Subject: Re: KITTEN: IETF 75 - 76
Message-ID: <20090819221441.GR1043@Sun.COM>
References: <20090819203055.GJ1043@Sun.COM> <200908192211.n7JMB5d3007759@fs4113.wdf.sap.corp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200908192211.n7JMB5d3007759@fs4113.wdf.sap.corp>
User-Agent: Mutt/1.5.7i
Cc: kitten@ietf.org, Shawn.Emery@sun.com
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2009 22:25:32 -0000

On Thu, Aug 20, 2009 at 12:11:05AM +0200, Martin Rex wrote:
> IMHO -- if the functionality is needed, it can be, and should be
> built at the application level entirely -- and it will work
> just fine with all existing gssapi mechanisms.

I agree.  No one is actually proposing to add re-keying to the GSS-API,
so let's not bother.

One might argue that with sundry extensions the GSS-API would be a
useful API for using TLS, much as with the SSPI, therefore we should add
support for re-keying and other TLS-isms.  No one is proposing that
either, but if some one did propose it and intended to implement, then
I'd probably support such a proposal.

v2.23.0 | Report a Bug | By Email