IETF Logo Mail Archive

Re: [OAUTH-WG] Meeting Minutes

Justin Richer <jricher@mit.edu> Fri, 14 November 2014 16:47 UTC

Return-Path: <jricher@mit.edu>
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 EDBCE1A1ADD for <oauth@ietfa.amsl.com>; Fri, 14 Nov 2014 08:47:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.794
X-Spam-Level:
X-Spam-Status: No, score=-4.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, 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 z19WzmMiMRYt for <oauth@ietfa.amsl.com>; Fri, 14 Nov 2014 08:47:13 -0800 (PST)
Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 486301A1AD7 for <oauth@ietf.org>; Fri, 14 Nov 2014 08:47:13 -0800 (PST)
X-AuditID: 1209190f-f79aa6d000005b45-8c-5466320f1270
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id DF.FD.23365.F0236645; Fri, 14 Nov 2014 11:47:11 -0500 (EST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id sAEGlAsK000837; Fri, 14 Nov 2014 11:47:11 -0500
Received: from [IPv6:2607:fb90:422:9736:0:2:16b5:8b01] ([172.56.38.194]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id sAEGl407028690 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 14 Nov 2014 11:47:08 -0500
Date: Fri, 14 Nov 2014 06:47:02 -1000
Message-ID: <fx01ttu90xsgt98441yoyqry.1415983622964@email.android.com>
Importance: normal
From: Justin Richer <jricher@mit.edu>
To: Brian Campbell <bcampbell@pingidentity.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_862564369347770"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPIsWRmVeSWpSXmKPExsUixG6nrstvlBZicOWYrsXq/zcZLZbuvMdq cfLtKzYHZo/Fm/azeSxZ8pPJ4+7RiywBzFFcNimpOZllqUX6dglcGUt29LAWzDaqWHktsIHx rkEXIyeHhICJxNzJe1khbDGJC/fWs3UxcnEICcxmkjjSv5MdwtnIKHGhZT6Us4tJ4v3NVWAt LAKqElsaZwK1cHAIC6hLNP3QAwnzCrhJtJ99BhbmFBCS6NolARJmA6qevqaFCcQWEciU+Ltr KyOIzQwU/7LgPRNEq6DEyZlPWCDiIRJfTu9mmsDINwtJahaSFIStLvFn3iVmCFtRYkr3Q/ZZ QJuZBdQklrUqIQsvYGRbxSibklulm5uYmVOcmqxbnJyYl5dapGuil5tZopeaUrqJERTOnJL8 Oxi/HVQ6xCjAwajEw7vCOTVEiDWxrLgy9xCjJAeTkigvp1haiBBfUn5KZUZicUZ8UWlOavEh RgkOZiUR3u/Pgcp5UxIrq1KL8mFS0hwsSuK8m37whQgJpCeWpGanphakFsFkZTg4lCR4H+gC DRUsSk1PrUjLzClBSDNxcIIM5wEavgKkhre4IDG3ODMdIn+KUVFKnPeLDlBCACSRUZoH1wtL N68YxYFeEea9A9LOA0xVcN2vgAYzAQ1mPAZydXFJIkJKqoGxMrGk78LFS43NP0NmPRTcWlD+ JDWsJKKUvWZ15wNeC//zs0PfT5j/NOdUlvGxvpX3t0/NPpjiuPqY0MoXv2prJpYsnc10eW1/ kHijZt2xyI3rhb4sX2xV2XNg24NlDw9MXNs69+95wwOnv6u8m8dTqx/Ofsa/607L5o+fVfIO 2qT6++Sv1/jNq8RSnJFoqMVcVJwIAGLeVDQSAwAA
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/UGRHQZidHLP42QKeyX_KfnSSiFU
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Meeting Minutes
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: <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: Fri, 14 Nov 2014 16:47:16 -0000

Brian is right, it's still a MUST NOT. We could relax that to a SHOULD NOT to allow for the (still largely theoretical) structured client_id construct to change over time. The reason it's how it is right now is that most systems use the client_id value as a key into things and funny expect it to change, as was discussed at several meetings and on the list already. Current implementations of this spec don't use structured client_id values. 

But as this is now tagged as experimental, we could also just publish it as is and see if anybody actually tried to deploy those two options together.

-- Justin

/ Sent from my phone /


-------- Original message --------
From: Brian Campbell <bcampbell@pingidentity.com> 
Date:11/14/2014  4:26 AM  (GMT-10:00) 
To: Hannes Tschofenig <hannes.tschofenig@gmx.net> 
Cc: oauth@ietf.org 
Subject: Re: [OAUTH-WG] Meeting Minutes 

My question was not really about the status of draft-bradley-oauth-stateless-client-id but rather about draft-ietf-oauth-dyn-reg-management allowing for the kind of stateless client id that Bradley described in his draft.

And draft-ietf-oauth-dyn-reg-management still has text that says, 'The value of the "client_id" MUST NOT change from the initial registration response.' which makes it incompatible with the concepts described in draft-bradley-oauth-stateless-client-id.

On Thu, Nov 13, 2014 at 8:05 PM, Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
Hi all,

here is a draft version of the meeting minutes:
http://www.ietf.org/proceedings/91/minutes/minutes-91-oauth

Thanks to Brian Rosen for taking notes.

Comments are welcome!

Ciao
Hannes & Derek


_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email