internationalization of URIs
Thomas Narten <narten@us.ibm.com> Mon, 15 October 2007 19:39 UTC
Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhVms-00072x-QD; Mon, 15 Oct 2007 15:39:38 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IhVmq-000723-VI for discuss-confirm+ok@megatron.ietf.org; Mon, 15 Oct 2007 15:39:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhVmq-00071S-0b for discuss@apps.ietf.org; Mon, 15 Oct 2007 15:39:36 -0400
Received: from e36.co.us.ibm.com ([32.97.110.154]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IhVmj-0000xP-Pe for discuss@apps.ietf.org; Mon, 15 Oct 2007 15:39:35 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e36.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l9FJdRk9020559 for <discuss@apps.ietf.org>; Mon, 15 Oct 2007 15:39:27 -0400
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id l9FJdQj5495384 for <discuss@apps.ietf.org>; Mon, 15 Oct 2007 13:39:27 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l9FJdQKN012786 for <discuss@apps.ietf.org>; Mon, 15 Oct 2007 13:39:26 -0600
Received: from localhost.localdomain (wecm-9-67-133-126.wecm.ibm.com [9.67.133.126]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l9FJdO1I012621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <discuss@apps.ietf.org>; Mon, 15 Oct 2007 13:39:26 -0600
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.14.1/8.12.5) with ESMTP id l9FJdIkM003350 for <discuss@apps.ietf.org>; Mon, 15 Oct 2007 15:39:19 -0400
Message-Id: <200710151939.l9FJdIkM003350@localhost.localdomain>
To: discuss@apps.ietf.org
Subject: internationalization of URIs
Date: Mon, 15 Oct 2007 15:39:18 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org
As some of you may know, as part of testing the readiness of IDNs, ICANN has inserted a set of internationalized versions of ".test" into the root zone of the DNS. See http://www.icann.org/announcements/announcement-15oct07.htm for details. One of the questions that this has prompted (again) is what about that pesky "http:", that still needs to typed in ascii. And what about the rest of the URL for that matter. I know this is not a new issue, but could someone summarize the landscape here on what "needs to be done" to internationalize the rest of the URI (other than the DNS name)? Is this considered to be completely an application issue? (I note that URIs are ascii, but there are escaping mechanisms to handle other characters.) Is there additional IETF work that needs to be done here? Or does this all fall under application-specific enablement? Or is even worse, in that this largely falls outside of applications and more into what is typically done by OS libraries and on the type of internationalization support the OS provides indirectly? Thomas
- Re: internationalization of URIs Martin Duerst
- Re: internationalization of URIs Ted Hardie
- internationalization of URIs Thomas Narten
- Re: internationalization of URIs Martin Duerst
- Re: internationalization of URIs Ted Hardie