IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Mon, 17 March 2014 22:29 UTC

Return-Path: <nico@cryptonector.com>
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 A52461A063F for <kitten@ietfa.amsl.com>; Mon, 17 Mar 2014 15:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334] 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 Ios4DmFzKrDo for <kitten@ietfa.amsl.com>; Mon, 17 Mar 2014 15:29:01 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (agjbgdcfdbfg.dreamhost.com [69.163.253.156]) by ietfa.amsl.com (Postfix) with ESMTP id BDF7A1A0324 for <kitten@ietf.org>; Mon, 17 Mar 2014 15:29:01 -0700 (PDT)
Received: from homiemail-a26.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTP id A0412B805C for <kitten@ietf.org>; Mon, 17 Mar 2014 15:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=QVk1M++smduP5TU9Dfaq tr2TMPw=; b=uBIPeHqd/YuHD14Kqqvkd/abq4t0KdJFwTjuNUpouCfJjlqfOMbU lmdNuNRdlUWDHjLv45VYlGSEllcAEoSTWeDOKRALxed3CoozEjzVFjs91YtUF6Mn m8echXKvH+WRK2vKZJtFE8plY/YoZRFhzZRxqEOGdjvrCvx3Eq6lXec=
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a26.g.dreamhost.com (Postfix) with ESMTPSA id 521B0B805B for <kitten@ietf.org>; Mon, 17 Mar 2014 15:28:53 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id hr14so2909273wib.3 for <kitten@ietf.org>; Mon, 17 Mar 2014 15:28:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ddiqbXxaBS6wakuGfZ4LHv79bgIGTOf+qQIUz2ScilY=; b=bEccdfb1DzcExsIxRnbi6clyr52wGcAvDVur+8dvOYBAcuTS5e9LTq9PkK+QIZrx0M vFLxcHgRnvfah4ujVbwr5jakLIXDvsDqS/dhhKWet/GT2wCjbH5Zcs1Ewl7HNn9sZ2pK laPBTwJcA/fF3h/ZP/oGtEEU53DDMfko8PivB9i9OtKcXFaBnthcEc5OgiyxxKQvFdAX F8sAUNL8H6OmhDfEtUBRdH+d0LQSHs8cSXN7WW01HXqdokEmZuOs0Sv+tqIN0cgqry/V ZKziiqs1KiULJZiUt4gZE2iMX+QdDY0Mf5L8foX/q2DilozP3uT5zaCrm2UGWGBvTn1b gm2w==
MIME-Version: 1.0
X-Received: by 10.180.36.8 with SMTP id m8mr11441755wij.42.1395095332005; Mon, 17 Mar 2014 15:28:52 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Mon, 17 Mar 2014 15:28:51 -0700 (PDT)
In-Reply-To: <1395093378.75479.YahooMailNeo@web142803.mail.bf1.yahoo.com>
References: <1393869321.174.YahooMailNeo@web125602.mail.ne1.yahoo.com> <tslr46j2kbm.fsf@mit.edu> <1393875779.29082.YahooMailNeo@web125604.mail.ne1.yahoo.com> <tsld2i21j7u.fsf@mit.edu> <1393926562.54403.YahooMailNeo@web125603.mail.ne1.yahoo.com> <1393948558.69282.YahooMailNeo@web125602.mail.ne1.yahoo.com> <CAPe4Cjoh7n-cQAuy17MWs66wigqTQvGBVVtEJ0_3zjaSg-5JmQ@mail.gmail.com> <1394650561.77489.YahooMailNeo@web142801.mail.bf1.yahoo.com> <1394833947.5753.YahooMailNeo@web142802.mail.bf1.yahoo.com> <CAK3OfOhr0ksktckcBK5UG7OYb4-Z=QP6DXCcyArk6A3qVWK3gA@mail.gmail.com> <53275BC1.50808@cisco.com> <1395090919.78935.YahooMailNeo@web142806.mail.bf1.yahoo.com> <CAK3OfOiQeZXs4iBP2C3WyZ4y69ejA3QG2fv8ne3C99PJNRySNQ@mail.gmail.com> <1395093378.75479.YahooMailNeo@web142803.mail.bf1.yahoo.com>
Date: Mon, 17 Mar 2014 17:28:51 -0500
Message-ID: <CAK3OfOhzLr8TckHB6FjMohskrEd_MBq+vL6HJC0y6_TwnY210g@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Bill Mills <wmills_92105@yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/kSVYJiS0d8dkvCF4KIz5etkFAek
Cc: "kitten@ietf.org" <kitten@ietf.org>, Bill Mills <wmills@yahoo-inc.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [kitten] Pending draft 15 Re: 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, 17 Mar 2014 22:29:02 -0000

On Mon, Mar 17, 2014 at 4:56 PM, Bill Mills <wmills_92105@yahoo.com> wrote:
> This feels like soft-selling what the implementer actually has to do.  It's
> like how HTTP evolved to be bug-compliant with major browser or server bugs.
> Never actually documented but are the de facto standard anyway.  Why leave a
> landmine like that unspecified?

Because the way it works in practice is that the app has something
like a dialog or panel where the user is invited to "set/create an
account" or something like that.  The user will be invited to specify
a server name, pick a mechanism, and for the mechnism selection
perhaps addition inputs, and finally they'll be invited to specify an
authzid.  Some of these account parameters are generic:

 - a local name for whatever this "account" is
 - the server name (and port)
 - the authzid
 - the name of the mechanism

everything else is mechanism-specific (e.g., "password", "keystore",
"principal name", ...).

The generic bits are generic.  And authzid has always been
application-specific.  Application protocols are allowed to require an
authzid.  Servers are allowed to require an authzid.  Mechanisms are
NOT allowed to require an authzid.

Nico
--

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