Re: [Uri-review] about: scheme; Simplified Encoding Considerations

Julian Reschke <julian.reschke@gmx.de> Mon, 21 September 2009 07:26 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFF513A6849 for <uri-review@core3.amsl.com>; Mon, 21 Sep 2009 00:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.717
X-Spam-Level:
X-Spam-Status: No, score=-4.717 tagged_above=-999 required=5 tests=[AWL=-2.118, BAYES_00=-2.599]
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 Ey+UCFpvC6Nd for <uri-review@core3.amsl.com>; Mon, 21 Sep 2009 00:26:39 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 867E53A683B for <uri-review@ietf.org>; Mon, 21 Sep 2009 00:26:38 -0700 (PDT)
Received: (qmail invoked by alias); 21 Sep 2009 07:27:37 -0000
Received: from p508FD4E2.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.212.226] by mail.gmx.net (mp008) with SMTP; 21 Sep 2009 09:27:37 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/N+WgEnJrNcXWryc1M+VKny/EWzeGLyUjp9NKP4K KhwGVi4zeB2Yjm
Message-ID: <4AB72ACB.5060004@gmx.de>
Date: Mon, 21 Sep 2009 09:27:07 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Joseph A Holsten <joseph@josephholsten.com>
References: <9E1BA1C0-F936-4202-885C-CA26FA86DF60@josephholsten.com>
In-Reply-To: <9E1BA1C0-F936-4202-885C-CA26FA86DF60@josephholsten.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.6
Cc: uri-review@ietf.org
Subject: Re: [Uri-review] about: scheme; Simplified Encoding Considerations
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2009 07:26:39 -0000

Joseph A Holsten wrote:
> URI people:
> 
> I intend to replace the current about: scheme Encoding Considerations[1]:
> 
>    Because many characters are not permitted with this syntax, the
>    "segment" and "query" elements may contain characters from the
>    Unicode Character Set [UCS] as suggested by URI [RFC3986], by first
>    encoding those characters as octets to the UTF-8 character encoding
>    [RFC3629]; then only those octets that do not correspond to
>    characters in the unreserved set should be percent-encoded.
> 
>    By using UTF-8 encoding, there are no known compatibility issues with
>    mapping Internationlized Resource Identifiers to about URIs according
>    to [RFC3987].  Since about URIs do not use domain names, "ireg-name"
>    conversion is unnecessary.
> 
> with the following (adapted from hixie's ws: scheme[2]):
> 
>    Characters in the "segment" or "query" parts that are excluded by the
>    syntax defined above must be converted from Unicode to ASCII by first
>    encoding the characters as UTF-8 and then replacing the corresponding
>    bytes using their percent-encoded form as defined in the URI and IRI
>    specifications. [RFC3986] [RFC3987]
> 
> Any objections or issues?
> ...

I think the current text is clearer with respect to whether IDNA 
conversion is needed or not.

BR, Julian