IETF Logo Mail Archive

Re: [OAUTH-WG] Possible alternative resolution to issue 26

Julian Reschke <julian.reschke@gmx.de> Wed, 05 October 2011 07:22 UTC

Return-Path: <julian.reschke@gmx.de>
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 E76A521F8513 for <oauth@ietfa.amsl.com>; Wed, 5 Oct 2011 00:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.993
X-Spam-Level:
X-Spam-Status: No, score=-102.993 tagged_above=-999 required=5 tests=[AWL=-0.394, BAYES_00=-2.599, 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 JcvP9n-eVl-Q for <oauth@ietfa.amsl.com>; Wed, 5 Oct 2011 00:22:39 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 05AA821F84FB for <oauth@ietf.org>; Wed, 5 Oct 2011 00:22:38 -0700 (PDT)
Received: (qmail invoked by alias); 05 Oct 2011 07:25:42 -0000
Received: from p5DCC39D6.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.57.214] by mail.gmx.net (mp062) with SMTP; 05 Oct 2011 09:25:42 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19hZKcNTWFhLD54v/ivjGtiRNIfmM8ezZP6cbUgfS wQoC7XavQWdQuG
Message-ID: <4E8C066A.2030504@gmx.de>
Date: Wed, 05 Oct 2011 09:25:30 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: William Mills <wmills@yahoo-inc.com>
References: <4E1F6AAD24975D4BA5B16804296739435C21DD2C@TK5EX14MBXC284.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E1129015546C@WSMSG3153V.srv.dir.telstra.com> <1317621663.4810.YahooMailNeo@web31813.mail.mud.yahoo.com> <4E1F6AAD24975D4BA5B16804296739435C226298@TK5EX14MBXC284.redmond.corp.microsoft.com> <1317704315.93442.YahooMailNeo@web31811.mail.mud.yahoo.com> <4E8B2DE1.2090706@mtcc.com> <C2C10679-2611-415B-80B7-8526937C1E82@oracle.com> <1317747487.89926.YahooMailNeo@web31809.mail.mud.yahoo.com> <6B898133-E7D0-45B1-9E3B-3B6DAFCDF671@oracle.com> <CAGdjJpJ+XkyPAJXEJa-3p3tNTxKzMpZXSHmH3H-m-7T9v=4x0Q@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739435C2276BD@TK5EX14MBXC284.redmond.corp.microsoft.com> <27AFD040F6F8AA4193E0614E2E3AF9C910D2F0CAAA@SISPE7MB1.commscope.com> <1317772567.49150.YahooMailNeo@web31811.mail.mud.yahoo.com>
In-Reply-To: <1317772567.49150.YahooMailNeo@web31811.mail.mud.yahoo.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Possible alternative resolution to issue 26
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, 05 Oct 2011 07:22:40 -0000

On 2011-10-05 01:56, William Mills wrote:
> Allowing URI requires allowing % encoding, which is workable. As far as
> the protocol goes URI is a form of space separated string and the
> protocol doesn't care. URI doesn't include quote or qhitespace in the
> allowed characters so there's no problem there.
>
> I agree that we'd have to write it such that it's clear you don't have
> to use a URI. Drawing from
> http://labs.apache.org/webarch/uri/rev-2002/rfc2396bis.html#path perhaps
> the allowed charset becomes
> ...

Note that RFC 2396 has been obsoleted by RFC 3986 a long time ago. Don't 
use it as base syntax.

Best regards, Julian

v2.23.0 | Report a Bug | By Email