IETF Logo Mail Archive

Re: dropping gss_name_to_any ?

Leif Johansson <leifj@mnt.se> Wed, 18 November 2009 12:45 UTC

Return-Path: <leifj@mnt.se>
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 2E8E83A691D for <kitten@core3.amsl.com>; Wed, 18 Nov 2009 04:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 V97714dcPjtE for <kitten@core3.amsl.com>; Wed, 18 Nov 2009 04:45:40 -0800 (PST)
Received: from backup-server.nordu.net (backup-server.nordu.net [193.10.252.66]) by core3.amsl.com (Postfix) with ESMTP id 1A4763A689F for <kitten@ietf.org>; Wed, 18 Nov 2009 04:45:39 -0800 (PST)
Received: from [192.36.125.216] (dhcp-216.pilsnet.sunet.se [192.36.125.216] (may be forged)) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id nAICjYK9027695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Nov 2009 13:45:36 +0100 (CET)
Message-ID: <4B03EC70.3040602@mnt.se>
Date: Wed, 18 Nov 2009 13:45:36 +0100
From: Leif Johansson <leifj@mnt.se>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: dropping gss_name_to_any ?
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> <20091117235725.GW773@Sun.COM>
In-Reply-To: <20091117235725.GW773@Sun.COM>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
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 12:45:41 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nicolas Williams wrote:
> 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.

OK I'll venture to declare consensus on that point then. That just
leaves one item for me before I can get out 06: where to define
gss_buffer_set_t and related functions: separate document or inline?

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksD7HAACgkQ8Jx8FtbMZncNpACgtFt3R3TLZQKPZQ/eHK9IVh53
CAIAoLwP+B4JlHMfiKZ4nAH/LWcz0r5p
=Y1Qe
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email