Re: [OAUTH-WG] Fw: Breaking change in OAuth 2.0 rev. 23

Barry Leiba <barryleiba@computer.org> Wed, 14 March 2012 20:19 UTC

Return-Path: <barryleiba.mailing.lists@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 BE1BF21F8744 for <oauth@ietfa.amsl.com>; Wed, 14 Mar 2012 13:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.984
X-Spam-Level:
X-Spam-Status: No, score=-102.984 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ihDRlk0e8Mvg for <oauth@ietfa.amsl.com>; Wed, 14 Mar 2012 13:19:39 -0700 (PDT)
Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3790921F8733 for <oauth@ietf.org>; Wed, 14 Mar 2012 13:19:39 -0700 (PDT)
Received: by yhgm50 with SMTP id m50so3381237yhg.27 for <oauth@ietf.org>; Wed, 14 Mar 2012 13:19:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=iifEKnuZW494cYdyMXCfJesFUAWRCFXcSrh/4RVWEAk=; b=OzQQmq9I6c9Jnd/raxQsHLL7US9eIFZMOf/XPndSeoNuf1Qs8a+3vbDi44OVc9Tu50 MlMg6lwMu3gCjqRttF+VIwE/38/cLU63ELUqf9r0e7DvvwE9MnY6+fLKMNN5phIBRNqP gNrkBQ2HlpXOkDIqytBa4dteA6hEPult+RLTUh2ii+R1UHfy9o3Vd7BGSNnv0oL5yEC+ b0Oc+uuxJhMGNE4qf7wRwCo/fYFFXWt+dSywpQ4J1hgRpWt4aRGPivYfG6+yXz3StPoe DJZMBsbHf4rwk/BKT2VCT9OFGHR37FSatyEkBA0zeJ4fgJ9dYHgNWhrWvWqm5+bAUO2m oPvQ==
MIME-Version: 1.0
Received: by 10.236.181.66 with SMTP id k42mr2234530yhm.55.1331756378837; Wed, 14 Mar 2012 13:19:38 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Wed, 14 Mar 2012 13:19:38 -0700 (PDT)
In-Reply-To: <CAAJ++qG+jdej64rjWM8V4MU_uxEc-2WoT4MKqhD_9ef0jBYwgg@mail.gmail.com>
References: <CAGdjJpLBCyvg21zuGi1jWK58hkDL4Ff7-xdJ0dy0WZpvNPPrKA@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723453AFF08903@P3PW5EX1MB01.EX1.SECURESERVER.NET> <CAAJ++qE3KcFgJey7xXzW8dkTPzvtcu_ke7abkOEMS4hwi93yEg@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723453AFF08919@P3PW5EX1MB01.EX1.SECURESERVER.NET> <CAGdjJpK6dMzSyoxEb_2rQcB-anXzvWaW-PLdYTZW_jECieBSMg@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723453AFF08932@P3PW5EX1MB01.EX1.SECURESERVER.NET> <4E1F6AAD24975D4BA5B16804296739436641D4E3@TK5EX14MBXC284.redmond.corp.microsoft.com> <90C41DD21FB7C64BB94121FBBC2E723453AFF08949@P3PW5EX1MB01.EX1.SECURESERVER.NET> <CAAJ++qG+jdej64rjWM8V4MU_uxEc-2WoT4MKqhD_9ef0jBYwgg@mail.gmail.com>
Date: Wed, 14 Mar 2012 16:19:38 -0400
X-Google-Sender-Auth: 9XnlVjHo2xQD7ooqgdkFCyVTU3I
Message-ID: <CAC4RtVBzDdeJViT_zOJ4QQQoo4Soy0iJJL_EK5zGd+94J1h7RQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: OAuth WG <oauth@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [OAUTH-WG] Fw: Breaking change in OAuth 2.0 rev. 23
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: Wed, 14 Mar 2012 20:19:39 -0000

> I am sorry, but with this language this is a different spec with
> different compliance profiles and without supplying enough guidance
> for creating interoperable server implementations for common
> deployment models.

As I read this thread, I see two things come out clearly:

1. Eran didn't intend to make the change that some read into this, and

2. enough people interpret this as a change that Eran didn't intend
that it's worth fixing.

Everyone agrees on how it should be -- right?  So let's not worry
about whether the text is or isn't confusing, and instead focus on a
small change to the text that will keep the meaning that's intended
and that takes the confusion away from those who think something
drastic has changed.  That should be easy to do, and quick and
non-controversial to wrap up.

Barry