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

Joseph A Holsten <joseph@josephholsten.com> Sat, 05 September 2009 07:56 UTC

Return-Path: <josephholsten@gmail.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E5B43A67A7; Sat, 5 Sep 2009 00:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 ygEmsO2QystC; Sat, 5 Sep 2009 00:56:37 -0700 (PDT)
Received: from mail-yx0-f190.google.com (mail-yx0-f190.google.com [209.85.210.190]) by core3.amsl.com (Postfix) with ESMTP id 205D63A6875; Sat, 5 Sep 2009 00:56:37 -0700 (PDT)
Received: by yxe28 with SMTP id 28so1619439yxe.19 for <multiple recipients>; Sat, 05 Sep 2009 00:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=U2ll29pg0TNFz26SLX/T6xUiW3zBGa3fPrJOLjohzFI=; b=qvkMu0JKbYT6k+VhhrMrjbBR7DPvlGYM1NzFKkBZnRZPfyE1fnQgf1jL6txuQDyFG9 fZ/aoGmC5oxdeH0jwUkCWQrM8qgTNv08t4t1ZR6ccV5n8SK4BjJg4rknQSaN8mY6FDBc jg9FeOYNR+/Zeh9tCq0MMnF0e4f9LHQrpscC4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=ZqK/g+Sze3qZD/vtWrVoLhe5d0QFnxRGb0frC08SuWmDWjbzGcBE0H9Lq9gx/lxylF zXziCtJ1iOSpwbckDJWFS3vYoH7XZ4/kaFYtWL2prid7rfoCROH67TT4ncBjzgBh98D2 nnhOgBSimwpxSvoboB13Y++eTsJpKXGB3ZA+M=
Received: by 10.101.90.20 with SMTP id s20mr13471144anl.61.1252137416019; Sat, 05 Sep 2009 00:56:56 -0700 (PDT)
Received: from ?192.168.1.137? (ip70-189-74-20.ok.ok.cox.net [70.189.74.20]) by mx.google.com with ESMTPS id b32sm1604105ana.0.2009.09.05.00.56.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 05 Sep 2009 00:56:55 -0700 (PDT)
Sender: Joseph Holsten <josephholsten@gmail.com>
Message-Id: <92531F42-BD89-4B2B-82E7-957BA99D6BEC@josephholsten.com>
From: Joseph A Holsten <joseph@josephholsten.com>
To: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <4AA2098B.9090900@gmx.de>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 05 Sep 2009 02:56:53 -0500
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> <27A077DD-42B6-4ABD-B633-12EB73AA4201@josephholsten.com> <4AA2098B.9090900@gmx.de>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Thu, 10 Sep 2009 18:54:56 -0700
Cc: URI <uri@w3.org>, "hybi@ietf.org" <hybi@ietf.org>, "uri-review@ietf.org" <uri-review@ietf.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Subject: Re: [hybi] [Uri-review] ws: and wss: schemes
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Sep 2009 07:56:38 -0000

Julian Reschke supposedly wrote:
> Joseph A Holsten wrote:
>> ...
>> The only scheme I can think of that was defined as an IRI was XMPP  
>> [RFC4622]. It actually makes more sense when you start with IRIs.  
>> If that's what you need, please just do that.
>> ...
>
> Actually, that RFC *registers* a URI scheme; see <http://tools.ietf.org/html/rfc4622#section-3 
> >.

It does, and so should websocket. But every other scheme RFC defines  
the URI first and foremost, then describes how to map IRIs. If  
websocket will be an IRI scheme first and foremost, defining it in  
terms of ihier-part and iquery makes sense. Then just adapt the text  
from RFC4622 sections 2 and 3.

The first sentence from <http://tools.ietf.org/html/rfc4622#section-2.8.1 
 > seems quite similar to Ian's preference with websocket:
"If a processing application is presented with an XMPP URI and not  
with an XMPP IRI, it MUST first convert the URI into an IRI by  
following the procedure specified in Section 3.2 of [IRI]."
--
Joseph Holsten