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

Sam Hartman <hartmans-ietf@mit.edu> Fri, 08 April 2011 16: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 95AC23A694F for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 09:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.848
X-Spam-Level:
X-Spam-Status: No, score=-102.848 tagged_above=-999 required=5 tests=[AWL=-0.583, 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 W0W4KWPEI+f8 for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 09:34:21 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 1F5FA3A6889 for <kitten@ietf.org>; Fri, 8 Apr 2011 09:34:21 -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 E2E8820384; Fri, 8 Apr 2011 12:32:48 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 56035446E; Fri, 8 Apr 2011 12:36:01 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Simon Josefsson <simon@josefsson.org>
References: <20110408070506.12ECB3A6A4C@core3.amsl.com> <416848.75882.qm__16525.0710481361$1302247955$gmane$org@web32314.mail.mud.yahoo.com> <87hba9b13i.fsf@latte.josefsson.org>
Date: Fri, 08 Apr 2011 12:36:01 -0400
In-Reply-To: <87hba9b13i.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 08 Apr 2011 10:26:25 +0200")
Message-ID: <tsl4o684s5q.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>, Tim Showalter <timshow@yahoo-inc.com>
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 16:34:21 -0000

I'm confused.
Why does the oauth sasl mechanism want to restrict what channel binding
types are permitted?
Also, why the desire to require tls-unique instead of
tls-server-endpoint?
The tls-server-endpoint channel binding type is easier to implement.