Re: [Uri-review] XMPP jabber: URI scheme not registered?

Peter Saint-Andre <stpeter@stpeter.im> Thu, 29 November 2012 04:21 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C9D721F89B7; Wed, 28 Nov 2012 20:21:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[AWL=-0.204, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eTvQqIYjsxJp; Wed, 28 Nov 2012 20:21:14 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C2AEB21F89B6; Wed, 28 Nov 2012 20:21:14 -0800 (PST)
Received: from [192.168.1.9] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D399740062; Wed, 28 Nov 2012 21:26:12 -0700 (MST)
Message-ID: <50B6E2BD.9030101@stpeter.im>
Date: Wed, 28 Nov 2012 21:21:17 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
References: <A723FC6ECC552A4D8C8249D9E07425A70F75EE78@xmb-rcd-x10.cisco.com> <50B4F2F0.3050406@stpeter.im> <50B652A7.2030502@ninebynine.org> <50B65E7D.9050005@stpeter.im> <C68CB012D9182D408CED7B884F441D4D1E371700C3@nambxv01a.corp.adobe.com> <50B68BBA.1000302@stpeter.im> <50B69BF5.2040808@stpeter.im> <50B6E130.4030003@it.aoyama.ac.jp>
In-Reply-To: <50B6E130.4030003@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: "uri-review@ietf.org" <uri-review@ietf.org>, Graham Klyne <GK@ninebynine.org>, "xmpp@ietf.org" <xmpp@ietf.org>
Subject: Re: [Uri-review] XMPP jabber: URI scheme not registered?
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 29 Nov 2012 04:21:15 -0000

On 11/28/12 9:14 PM, "Martin J. Dürst" wrote:
> Hello Peter,
> 
> On 2012/11/29 8:19, Peter Saint-Andre wrote:
> So here is the registration...
> 
> ###
> 
>     URI scheme name.
>        jabber
> 
>     Status.
>        permanent
> 
>     URI scheme syntax.
>        The only allowable strings are:
>        - jabber:client
>> ..
>     URI scheme semantics.
>        Strings of the form 'jabber:*' and 'jabber:*:*' were
>        used as XML namespace names during development of the
>        technology that became the Extensible Messaging and
>        Presence Protocol (XMPP).  The scheme was never used
>        for any other purpose.  The only namespace names
>        minted with this scheme are listed above.  No other
>        strings were minted, and no other strings shall be
>        minted.  Note that defining new URI schemes for XML
>        namespaces is now discouraged.  The 'jabber' scheme
>        was defined before standard best practices emerged.
> 
>     Encoding considerations.
>        Encoded as UTF-8 within XMPP protocol streams.
> 
>> This is irrelevant. See http://tools.ietf.org/html/rfc4395#section-2.6.
> 
>> I would write this as following:
> 
>>     Encoding considerations.
>>       None. All characters are within the characters allowed in URIs.

You are right. How about the following...

   Encoding considerations.
      None. Because the limited number of URIs (XML namespace
      names) minted with this scheme contain characters only
      from the ASCII range, encoding of internationalized code
      points is out of scope.  In addition, these namespace names
      do not contain any text fields that would be subject to
      specialized encoding.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/