Re: [OAUTH-WG] Authentication Method Reference Values spec incorporating adoption feedback

Thomas Broyer <t.broyer@gmail.com> Fri, 12 February 2016 08:32 UTC

Return-Path: <t.broyer@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F6A1B41C4 for <oauth@ietfa.amsl.com>; Fri, 12 Feb 2016 00:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 dJlwbxaNscmi for <oauth@ietfa.amsl.com>; Fri, 12 Feb 2016 00:32:02 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CB331B41C5 for <oauth@ietf.org>; Fri, 12 Feb 2016 00:32:02 -0800 (PST)
Received: by mail-lb0-x22f.google.com with SMTP id tk3so29015378lbb.3 for <oauth@ietf.org>; Fri, 12 Feb 2016 00:32:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=THnmucfvt2W5w2mgwq5LiqhpUTEq4J/jCBsDu8PZI5k=; b=Uz/52cAXjIdo0IgXwHtC3C5exm5oFmSPbfKM9sCkVL4mYbel0VHK5Z0wnHQ951JNIs 3N6KVm41uNq1EGXOwnfgpKEzgW6DnX9W3D08sz4D481+uhBHaBXu1qtAsMxGi5/FIqa5 O+v9+mvQ8iHfk6riBL+esNLJrjfvIOgRb/50X031IeAQvAzAEY0bN3GT1TnAgfiTK5xp 6VrIB2ADtm5CWRfhKCnQgOYFyLkDI4iO20M0FdHERryjGk02789NBTEGxvNc/HJMd7d8 vyvr2syJAII/Jjw4dmWrcoPUOQykqErZQuMCcFBIA7WdVz8Rkcsw1JSIRFqG7KooWXAT x62w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=THnmucfvt2W5w2mgwq5LiqhpUTEq4J/jCBsDu8PZI5k=; b=i7AKaicv3WzphBdVNzkxzqK/taCtFImvrBBhfj9qQj1zbhfmwKA9RTz66aeCswclwn y/Rj0WEnMbm2ngSA6fekepx+DinBU43I2O4qpK1DUq2KbVf2IUcAWcCu8zvDbu+nFUJM N8D6VpWx+e29sDFSG/Mm9edOBaueA/ntnxkYJVhcFchXUSdaPbXvx9mKhOb1y+liQWxN PJB/teiGwfYzCx+JGBSgn61vjlSeP6YGAT6VO/p7JRz5ueWQ1+H1GxZ+tvWXCmkrdfVy jtz/IEua8XSGQTlRqHRFTofrMaCymCGixYsvsw0wbymNYHCbVqn+cJMiAqWaMg6opKK8 /JtA==
X-Gm-Message-State: AG10YOSGrf1on0z9L0uuOI6tUnY2WZ2zN3xIskOyHf1zSzBei7PrZ0vRglfCWiEkeOCe2BLgnIOIFheUiriahA==
X-Received: by 10.112.64.5 with SMTP id k5mr107789lbs.133.1455265920354; Fri, 12 Feb 2016 00:32:00 -0800 (PST)
MIME-Version: 1.0
References: <BY2PR03MB442A9083066AB2DD7EA8547F5A90@BY2PR03MB442.namprd03.prod.outlook.com>
In-Reply-To: <BY2PR03MB442A9083066AB2DD7EA8547F5A90@BY2PR03MB442.namprd03.prod.outlook.com>
From: Thomas Broyer <t.broyer@gmail.com>
Date: Fri, 12 Feb 2016 08:31:50 +0000
Message-ID: <CAEayHEO5FPywk27u401bvLi3vEb3EpgVG+oPp3Y2SwBP=Uf6eA@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3eeb63c8f06052b8e8023
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/6DttraiiIMXnjGfpupjgEWtmW20>
Subject: Re: [OAUTH-WG] Authentication Method Reference Values spec incorporating adoption feedback
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 08:32:04 -0000

So, you just removed every relationship to OAuth (and the note about OAuth
and authentication seems a bit out of context), and I thus wonder why the
OAuth WG would adopt this draft; that'd rather be a JOSE thing.

Le ven. 12 févr. 2016 07:03, Mike Jones <Michael.Jones@microsoft.com> a
écrit :

> This draft of the Authentication Method Reference Values specification
> incorporates OAuth working group feedback from the call for adoption.  The
> primary change was to remove the “amr_values” request parameter, so that “
> amr” values can still be returned as part of an authentication result,
> but cannot be explicitly requested.  Also, noted that OAuth 2.0 is
> inadequate for authentication without employing appropriate extensions and
> changed the IANA registration procedure to no longer require a
> specification.
>
>
>
> The specification is available at:
>
> ·       http://tools.ietf.org/html/draft-jones-oauth-amr-values-05
>
>
>
> An HTML-formatted version is also available at:
>
> ·       http://self-issued.info/docs/draft-jones-oauth-amr-values-05.html
>
>
>
>                                                           -- Mike
>
>
>
> P.S.  This announcement was also posted at http://self-issued.info/?p=1539
> and as @selfissued <https://twitter.com/selfissued>.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>