IETF Logo Mail Archive

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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Thu, 29 November 2012 05:08 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 9C01121E8039 for <uri-review@ietfa.amsl.com>; Wed, 28 Nov 2012 21:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.722
X-Spam-Level:
X-Spam-Status: No, score=-101.722 tagged_above=-999 required=5 tests=[AWL=2.068, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 kUYedcaqy84k for <uri-review@ietfa.amsl.com>; Wed, 28 Nov 2012 21:08:19 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBF321E804A for <uri-review@ietf.org>; Wed, 28 Nov 2012 21:08:18 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id qAT589xD010298 for <uri-review@ietf.org>; Thu, 29 Nov 2012 14:08:09 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 7047_68b6_c47f4148_39e2_11e2_87e6_001d096c566a; Thu, 29 Nov 2012 14:08:09 +0900
Received: from [IPv6:::1] ([133.2.210.1]:35786) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S1619C11> for <uri-review@ietf.org> from <duerst@it.aoyama.ac.jp>; Thu, 29 Nov 2012 14:08:11 +0900
Message-ID: <50B6EDB3.5000307@it.aoyama.ac.jp>
Date: Thu, 29 Nov 2012 14:08:03 +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.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
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> <50B6E2BD.9030101@stpeter.im>
In-Reply-To: <50B6E2BD.9030101@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
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 05:08:19 -0000

On 2012/11/29 13:21, Peter Saint-Andre wrote:
> On 11/28/12 9:14 PM, "Martin J. Dürst" wrote:
>> Hello Peter,
>>
>> On 2012/11/29 8:19, Peter Saint-Andre wrote:

>>      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.

Ship it.    Regards,   Martin.

v2.23.0 | Report a Bug | By Email