IETF Logo Mail Archive

Re: [kitten] sasl-oauth "user" as a kvpair or in the gs2 header?

Sam Hartman <hartmans@mit.edu> Mon, 03 March 2014 18:44 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414191A0342 for <kitten@ietfa.amsl.com>; Mon, 3 Mar 2014 10:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZxmTA_ux-kN for <kitten@ietfa.amsl.com>; Mon, 3 Mar 2014 10:44:50 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 659431A034D for <kitten@ietf.org>; Mon, 3 Mar 2014 10:44:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id CB937206A2; Mon, 3 Mar 2014 13:40:23 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3O5tBJeGnCPO; Mon, 3 Mar 2014 13:40:23 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [130.129.155.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 3 Mar 2014 13:40:23 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8373F83EF2; Mon, 3 Mar 2014 13:44:45 -0500 (EST)
From: Sam Hartman <hartmans@mit.edu>
To: Bill Mills <wmills@yahoo-inc.com>
References: <1393869321.174.YahooMailNeo@web125602.mail.ne1.yahoo.com>
Date: Mon, 03 Mar 2014 13:44:45 -0500
In-Reply-To: <1393869321.174.YahooMailNeo@web125602.mail.ne1.yahoo.com> (Bill Mills's message of "Mon, 3 Mar 2014 09:55:21 -0800")
Message-ID: <tslr46j2kbm.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/mO6jm3kUDc_UrmyWyF4i4Pp05Kc
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] sasl-oauth "user" as a kvpair or in the gs2 header?
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 03 Mar 2014 18:44:51 -0000

When we talked about removing the GS2 support, I assumed we were
maintaining the GS2 header, just dropping the descriptions of the
GSS-API mechanism and   reference to GS2.

Speaking as an individual, I'd prefer to maximize alignment with GS2
even if we do not specify as a GSS-API mechanism at this time.

v2.30.2 | Report a Bug | By Email | System Status