IETF Logo Mail Archive

Re: [OAUTH-WG] 'Scope' parameter proposal

Brian Eaton <beaton@google.com> Thu, 22 April 2010 20:50 UTC

Return-Path: <beaton@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D827C3A695D for <oauth@core3.amsl.com>; Thu, 22 Apr 2010 13:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.903
X-Spam-Level:
X-Spam-Status: No, score=-105.903 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96TO82jNMwM8 for <oauth@core3.amsl.com>; Thu, 22 Apr 2010 13:50:41 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id A71D63A693A for <oauth@ietf.org>; Thu, 22 Apr 2010 13:50:39 -0700 (PDT)
Received: from hpaq3.eem.corp.google.com (hpaq3.eem.corp.google.com [10.3.21.3]) by smtp-out.google.com with ESMTP id o3MKoPgk007937 for <oauth@ietf.org>; Thu, 22 Apr 2010 13:50:27 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1271969427; bh=2nH81pOXBzTnzZkLp5SmzASApoQ=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=LoWKSzZeufJZzs7CupCLeCqqSBg8B/Njo7VRK/oqM44b8kiI74+FaKS0H1nL1KoK0 Yx1X76IiawZh0+x8rX27Q==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=QxLur+nGNN1kszZyLP/KdYl3E90C4e4tYOwdsArrX9V5aecHpPDrUyGZqhCJLkcSn 0v/Oh9Sx7lEelfagSooAg==
Received: from pvg3 (pvg3.prod.google.com [10.241.210.131]) by hpaq3.eem.corp.google.com with ESMTP id o3MKoNqO007279 for <oauth@ietf.org>; Thu, 22 Apr 2010 22:50:24 +0200
Received: by pvg3 with SMTP id 3so1328096pvg.40 for <oauth@ietf.org>; Thu, 22 Apr 2010 13:50:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.202.10 with HTTP; Thu, 22 Apr 2010 13:50:22 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723438E5C7FD4A@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <C7F1D1FC.32809%eran@hueniverse.com> <0D5497F5-75A7-4A42-9A5E-9C2310162B18@jkemp.net> <90C41DD21FB7C64BB94121FBBC2E723438E5C7F30A@P3PW5EX1MB01.EX1.SECURESERVER.NET> <g2mdaf5b9571004221036j5d6837f6z4d7959d69a3cbb2b@mail.gmail.com> <BB02FD4F-071E-4FF5-B3D0-F8D3FA22FEEE@jkemp.net> <90C41DD21FB7C64BB94121FBBC2E723438E5C7FD26@P3PW5EX1MB01.EX1.SECURESERVER.NET> <h2ldaf5b9571004221235tb844eb6ah623955979526c1b6@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723438E5C7FD4A@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Thu, 22 Apr 2010 13:50:22 -0700
Received: by 10.142.74.9 with SMTP id w9mr4915278wfa.305.1271969423017; Thu, 22 Apr 2010 13:50:23 -0700 (PDT)
Message-ID: <l2idaf5b9571004221350oa0dbeb11ndeb4cb9147407ba9@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] 'Scope' parameter proposal
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 22 Apr 2010 20:50:43 -0000

On Thu, Apr 22, 2010 at 12:41 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> Drop the 'scope' parameter as well and we're on the same page.

So we have a choice between

a) not documenting something that a bunch of providers have already
implemented and found useful
   or
b) documenting something that no one has built yet, and that might not
actually work

Bummer. =)

v2.23.0 | Report a Bug | By Email