IETF Logo Mail Archive

Re: [Uri-review] [hybi] ws: and wss: schemes

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 08 September 2009 10:16 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 633FE3A6890 for <uri-review@core3.amsl.com>; Tue, 8 Sep 2009 03:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.658
X-Spam-Level:
X-Spam-Status: No, score=0.658 tagged_above=-999 required=5 tests=[AWL=0.448, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3]
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 aPUMHTpxKMvP for <uri-review@core3.amsl.com>; Tue, 8 Sep 2009 03:16:41 -0700 (PDT)
Received: from scmailgw02.scop.aoyama.ac.jp (scmailgw02.scop.aoyama.ac.jp [133.2.251.42]) by core3.amsl.com (Postfix) with ESMTP id BE5243A697B for <uri-review@ietf.org>; Tue, 8 Sep 2009 03:16:39 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp (scmse01.scbb.aoyama.ac.jp [133.2.253.158]) by scmailgw02.scop.aoyama.ac.jp (secret/secret) with SMTP id n88AGweM019652 for <uri-review@ietf.org>; Tue, 8 Sep 2009 19:16:58 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 6817_bdd8587a_9c60_11de_9736_001d096c566a; Tue, 08 Sep 2009 19:16:58 +0900
Received: from [IPv6:::1] ([133.2.210.1]:33929) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S11E703C> for <uri-review@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 8 Sep 2009 19:13:52 +0900
Message-ID: <4AA62F07.70402@it.aoyama.ac.jp>
Date: Tue, 08 Sep 2009 19:16:39 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090108 Eudora/3.0b1pre
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <OF22CD1320.96C55266-ON85257610.004AB599-85257610.004BC9CA@lotus.com> <C9931C12-E123-437D-8E7D-F8C680C62397@mnot.net> <4A8CAA72.3000209@berkeley.edu> <Pine.LNX.4.62.0909040147300.6775@hixie.dreamhostps.com> <4AA14792.4020009@gmx.de> <4D25F22093241741BC1D0EEBC2DBB1DA01AD6282C2@EX-SEA5-D.ant.amazon.com> <Pine.LNX.4.62.0909041947250.26930@hixie.dreamhostps.com> <4AA17310.1090108@gmx.de> <Pine.LNX.4.62.0909042013300.26930@hixie.dreamhostps.com> <4AA20894.9040704@gmx.de>
In-Reply-To: <4AA20894.9040704@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: URI <uri@w3.org>, "hybi@ietf.org" <hybi@ietf.org>, Ian Hickson <ian@hixie.ch>, "uri-review@ietf.org" <uri-review@ietf.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Subject: Re: [Uri-review] [hybi] ws: and wss: schemes
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: Tue, 08 Sep 2009 10:16:42 -0000

On 2009/09/05 15:43, Julian Reschke wrote:
> Ian Hickson wrote:

>> I've read this, but as far as I can tell, "Always UTF-8" and "See IRI"
>> are both complete and accurate ways of addressing this.

Ian, you are famous for pointing out your low trust in implementors. 
Given that, I'd tend to spend a few more words on this, to help them 
along a bit better.

>> Since apparently neither of these options satisfies you, could you
>> state exactly what literal text would satisfy you?
>> ...
>
> I already pointed you to RFC 5092 as relatively recent example, see
> <http://tools.ietf.org/html/rfc5092#section-8>.

A newer example (the RFC numbers are confusing, because RFC 5092 goes 
back to RFC 2192) would be the XMPP IRI/URI spec, see 
http://tools.ietf.org/html/rfc4622.


Also, please note that there may be nothing like an "IRI only" scheme. 
There is always the chance that in some strange context, a conversion to 
ASCII (i.e. to URIs) happens.

Regards,   Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

v2.23.0 | Report a Bug | By Email