IETF Logo Mail Archive

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed Resolutions

John Bradley <ve7jtb@ve7jtb.com> Mon, 17 October 2011 00:11 UTC

Return-Path: <ve7jtb@ve7jtb.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 739E321F84F5 for <oauth@ietfa.amsl.com>; Sun, 16 Oct 2011 17:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 cVnJIfAxx74w for <oauth@ietfa.amsl.com>; Sun, 16 Oct 2011 17:11:59 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id D7FE321F84D5 for <oauth@ietf.org>; Sun, 16 Oct 2011 17:11:58 -0700 (PDT)
Received: by gyh20 with SMTP id 20so3040589gyh.31 for <oauth@ietf.org>; Sun, 16 Oct 2011 17:11:58 -0700 (PDT)
Received: by 10.151.122.4 with SMTP id z4mr15630502ybm.76.1318810318136; Sun, 16 Oct 2011 17:11:58 -0700 (PDT)
Received: from [10.10.1.58] ([209.118.182.66]) by mx.google.com with ESMTPS id l8sm7827255anb.1.2011.10.16.17.11.56 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Oct 2011 17:11:57 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="us-ascii"
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723452604B908A@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Sun, 16 Oct 2011 17:11:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E5660BC-C797-454B-B2AF-48AB3E886AC7@ve7jtb.com>
References: <4E1F6AAD24975D4BA5B16804296739435C23C5A6@TK5EX14MBXC284.redmond.corp.microsoft.com><7A22B287-CC99-4FD7-84DF-8FF5DA871FC6@gmx.net><4E1F6AAD24975D4BA5B16804296739435C23CAFE@TK5EX14MBXC284.redmond.corp.microsoft.com><89BE3D9D-AB1D-44B2-BA7D-0C0D74BCA885@gmx.net> <4E1F6AAD24975D4BA5B16804296739435C23CC9D@TK5EX14MBXC284.redmond.corp.microsoft.com> <999913AB42CC9341B05A99BBF358718DAABC44@FIESEXC035.nsn-intra.net> <4E1F6AAD24975D4BA5B16804296739435C23EA6A@TK5EX14MBXC284.redmond.corp.microsoft.com> <4E9AB561.5060904@gmx.de> <4E1F6AAD24975D4BA5B16804296739435C23F5B6@TK5EX14MBXC284.redmond.corp.microsoft.com> <4E9B1BA6.2060704@gmx.de> <90C41DD21FB7C64BB94121FBBC2E723452604B908A@P3PW5EX1MB01.EX1.SECURESERVER.NET>
To: Eran Hammer-Lahav <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues & Proposed Resolutions
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: Mon, 17 Oct 2011 00:11:59 -0000

Restricting it now in the core spec is going to save a lot of headaches later.

John B.
On 2011-10-16, at 3:54 PM, Eran Hammer-Lahav wrote:

> It's an open question for the list.
> 
> EHL
> 
>> -----Original Message-----
>> From: Julian Reschke [mailto:julian.reschke@gmx.de]
>> Sent: Sunday, October 16, 2011 11:00 AM
>> To: Mike Jones
>> Cc: Tschofenig, Hannes (NSN - FI/Espoo); Hannes Tschofenig; OAuth WG;
>> Eran Hammer-Lahav
>> Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-09: Open Issues &
>> Proposed Resolutions
>> 
>> On 2011-10-16 18:44, Mike Jones wrote:
>>> As Eran wrote on 9/30, "The fact that the v2 spec allows a wide range of
>> characters in scope was unintentional. The design was limited to allow simple
>> ASCII strings and URIs."
>>> ...
>> 
>> I see. Thanks.
>> 
>> Is this going to be clarified in -23?
>> 
>> Best regards, Julian
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email