Re: [OAUTH-WG] New Version Notification for draft-hunt-oauth-v2-user-a4c-00.txt

Nat Sakimura <sakimura@gmail.com> Tue, 30 July 2013 20:43 UTC

Return-Path: <sakimura@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24ABE11E823C for <oauth@ietfa.amsl.com>; Tue, 30 Jul 2013 13:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JFiHVEtt3zDQ for <oauth@ietfa.amsl.com>; Tue, 30 Jul 2013 13:43:21 -0700 (PDT)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 9F96511E823A for <oauth@ietf.org>; Tue, 30 Jul 2013 13:43:17 -0700 (PDT)
Received: by mail-lb0-f173.google.com with SMTP id 10so3414lbf.18 for <oauth@ietf.org>; Tue, 30 Jul 2013 13:43:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r08CipkWpXU5mTsI274cieq3vnHC/1o+SU0YksRtzR4=; b=vB6fWSy4TbNwZzQQfyx97MQ3rI0HG0JPxq2vDtdAhT+xUylILMARjpqxa/FYzkdUJB K92lLwGSTlYFsWnrfstIroOVEw1fkmG7oWY39ffyUqRWayVCfGpHb5iZ6ArmPPVJmeXc KCndOapa6gkKxOekGT3w1BlJP5DLA6rAr3SFaAoNuJaBvwOSq5Xdz41gBRw9PzTLpQ8l mvWynaO56WXSvJeUsUQHe1PYu7yfd9t7Us+I4DcN/deDJ/OCLLmTYYzWmpRymgGLuK7W M2bGM2472ZgqNVuKr3+/bvjs1IfIve8NdJlcICbf08oZNPhaAECiPY9124UK+rJirskP 0iVQ==
MIME-Version: 1.0
X-Received: by 10.112.11.136 with SMTP id q8mr4000736lbb.94.1375216991011; Tue, 30 Jul 2013 13:43:11 -0700 (PDT)
Received: by 10.112.134.38 with HTTP; Tue, 30 Jul 2013 13:43:10 -0700 (PDT)
In-Reply-To: <CC27EF1D-9640-4D4D-BA5E-C29EA3A59C1F@mitre.org>
References: <20130729074941.28839.7732.idtracker@ietfa.amsl.com> <E4ED649B-D9FE-4B38-B8B2-82A7FF600C07@oracle.com> <00230F32-D037-4A70-98E5-7D47A4BD2D1C@mitre.org> <CA+k3eCTHsBiHtnmrT+n3F6EuikwR5WMYgb=fkP6JGr4+F9CchQ@mail.gmail.com> <51F7F080.9040902@gmail.com> <CC27EF1D-9640-4D4D-BA5E-C29EA3A59C1F@mitre.org>
Date: Wed, 31 Jul 2013 05:43:10 +0900
Message-ID: <CABzCy2B=2b-+5Nop9TDw3e04zLk=B7gJFZH-dzhx6EMvP2s4Yg@mail.gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
To: "Richer, Justin P." <jricher@mitre.org>
Content-Type: multipart/alternative; boundary="001a11c3b61e3d07fc04e2c0a840"
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] New Version Notification for draft-hunt-oauth-v2-user-a4c-00.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 30 Jul 2013 20:43:22 -0000

Right. Anyone who agreed to IPR could have proposed the text in the work
group.

Re: Messages and Standard

Messages were supposed to be the collection of terminology and parameters
sets.
Standard was meant to be HTTP binding, which would effectively make it
OAuth 2.0 + authentication + identity.
As such, normative portion of the standard was to be made of the HTTP
protocol element, reference to the parameters sets in Messages, and the
documentation on how to serialize. It should be very concise. Non-normative
portions were supposed to have examples. In some sections, it is like that,
but in sections like 2.2.1.1, it is currently repeating much of what the
Messages have.
This, to me, is suboptimal but many people wanted to be this way so that
they do not have to refer to the Messages.

Maybe, for the final, we might reconsider it.






2013/7/31 Richer, Justin P. <jricher@mitre.org>

>  So it's not the protocol that's the problem, it's the documentation. For
> that I'm 100% with you all. However, I really don't think that the right
> response to that is "we'll just invent something new and incompatible with
> slightly different names" -- it's to document the protocol better.
>
>   -- Justin
>
>  On Jul 30, 2013, at 12:57 PM, Paul Madsen <paul.madsen@gmail.com>
>  wrote:
>
>  I always think I pretty much understand OIDC until I see the specs list
>
>  On 7/30/13 12:39 PM, Brian Campbell wrote:
>
> Yes, that.
>
> On Tue, Jul 30, 2013 at 4:46 PM, Richer, Justin P. <jricher@mitre.org>wrote:
>
>>
>> Yes, I agree that the giant stack of documents is intimidating and in my
>> opinion it's a bit of a mess with Messages and Standard split up (but I
>> lost that argument years ago).
>>
>
>
>
> _______________________________________________
> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>


-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en