IETF Logo Mail Archive

Re: [kitten] Fw: New Version Notification for draft-mills-kitten-sasl-oauth-02

Sam Hartman <hartmans-ietf@mit.edu> Fri, 08 April 2011 17:34 UTC

Return-Path: <hartmans@mit.edu>
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 B04EF3A6987 for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 10:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.839
X-Spam-Level:
X-Spam-Status: No, score=-102.839 tagged_above=-999 required=5 tests=[AWL=-0.574, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 F+PgN8sqwv0c for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 10:34:37 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id E5A263A68D4 for <kitten@ietf.org>; Fri, 8 Apr 2011 10:34:36 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 7781620384; Fri, 8 Apr 2011 13:33:04 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 20737446E; Fri, 8 Apr 2011 13:36:16 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "William J. Mills" <wmills@yahoo-inc.com>
References: <20110408070506.12ECB3A6A4C@core3.amsl.com> <416848.75882.qm__16525.0710481361$1302247955$gmane$org@web32314.mail.mud.yahoo.com> <87hba9b13i.fsf@latte.josefsson.org> <tsl4o684s5q.fsf@mit.edu> <754979.46407.qm@web32303.mail.mud.yahoo.com>
Date: Fri, 08 Apr 2011 13:36:16 -0400
In-Reply-To: <754979.46407.qm@web32303.mail.mud.yahoo.com> (William J. Mills's message of "Fri, 8 Apr 2011 10:31:42 -0700 (PDT)")
Message-ID: <tslr59c3asv.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: "kitten@ietf.org" <kitten@ietf.org>, Simon Josefsson <simon@josefsson.org>, Tim Showalter <timshow@yahoo-inc.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [kitten] Fw: New Version Notification for draft-mills-kitten-sasl-oauth-02
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: Fri, 08 Apr 2011 17:34:37 -0000

>>>>> "William" == William J Mills <wmills@yahoo-inc.com> writes:

    William> At the moment I was going with simple.  If multiple types
    William> are supported then I have to be able to communicate what
    William> types of channel binding are accepted, which I suppose
    William> could go in the WWW-Authenticate header in the discovery
    William> information.  It's relatively easy to add a variable for
    William> the CB type.


I don't think this is true if you're a SASL mechanism.
I think that's the application's problem.
I think all you have to do is communicate  the channel binding type you
support.

Also, the abstract interface between the application and SASL assumes
that all SASL mechanisms supporting any CB types support all CB types.
This is even more true if you happen to be running through a GS2 bridge
which may not be applicable to your mechanism.

I promised Hannes at the meeting that near end of April I'd be happy to
get up to speed on this and work with the draft authors on all this.

I'm sorry I don't have time to do that this week or next but I'll get
there.

v2.23.0 | Report a Bug | By Email