Re: dropping gss_name_to_any ?

Nicolas Williams <Nicolas.Williams@sun.com> Wed, 18 November 2009 00:09 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 0B1A73A6B2B for <kitten@core3.amsl.com>; Tue, 17 Nov 2009 16:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.269
X-Spam-Level:
X-Spam-Status: No, score=-5.269 tagged_above=-999 required=5 tests=[AWL=0.477, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, 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 1l5R2aU6V+p8 for <kitten@core3.amsl.com>; Tue, 17 Nov 2009 16:09:09 -0800 (PST)
Received: from sca-ea-mail-1.sun.com (sca-ea-mail-1.Sun.COM [192.18.43.24]) by core3.amsl.com (Postfix) with ESMTP id 07E1B3A6879 for <kitten@ietf.org>; Tue, 17 Nov 2009 16:09:08 -0800 (PST)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nAI093vf001373 for <kitten@ietf.org>; Wed, 18 Nov 2009 00:09:03 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 nAI092HG035619 for <kitten@ietf.org>; Tue, 17 Nov 2009 17:09:02 -0700 (MST)
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 nAHNvQYb001761; Tue, 17 Nov 2009 17:57:26 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id nAHNvP56001760; Tue, 17 Nov 2009 17:57:25 -0600 (CST)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Tue, 17 Nov 2009 17:57:25 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Love Hörnquist Åstrand <lha@kth.se>
Subject: Re: dropping gss_name_to_any ?
Message-ID: <20091117235725.GW773@Sun.COM>
References: <200909141004.39686.leifj@mnt.se> <4B02B173.5070003@mnt.se> <20091117164631.GM773@Sun.COM> <E9348CB0-4D26-4082-A129-2699C8B150CF@padl.com> <C332A731-CAC7-48BD-984E-A87961CD4B1A@kth.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C332A731-CAC7-48BD-984E-A87961CD4B1A@kth.se>
User-Agent: Mutt/1.5.7i
Cc: "kitten@ietf.org" <kitten@ietf.org>
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, 18 Nov 2009 00:09:10 -0000

On Tue, Nov 17, 2009 at 02:04:04PM -0800, Love Hörnquist Åstrand wrote:
> I think that when we get a real use for it we can add it all back.
> 
> Pushing out random objects is sane.

Insane, yes.  My original use had been for an OS-specific view of things
like the PAC.  But as long as there's few consumers or the parsing code
can live in a library, then there's no need for this.  I.e., there's no
need for this -- it was a mistake on my part to include it in the first
place.