IETF Logo Mail Archive

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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Mon, 03 December 2012 07:38 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 D0CEC21F8AF5 for <uri-review@ietfa.amsl.com>; Sun, 2 Dec 2012 23:38:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.445
X-Spam-Level:
X-Spam-Status: No, score=-99.445 tagged_above=-999 required=5 tests=[AWL=-1.144, BAYES_05=-1.11, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, 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 2hbMUtXcjOpE for <uri-review@ietfa.amsl.com>; Sun, 2 Dec 2012 23:38:42 -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 07F4621F8AEB for <uri-review@ietf.org>; Sun, 2 Dec 2012 23:38:41 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id qB37cWl6023896 for <uri-review@ietf.org>; Mon, 3 Dec 2012 16:38:32 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 3bde_d7f1_6fe38512_3d1c_11e2_8511_001d096c5782; Mon, 03 Dec 2012 16:38:31 +0900
Received: from [IPv6:::1] ([133.2.210.1]:49626) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S161B2C7> for <uri-review@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 3 Dec 2012 16:38:32 +0900
Message-ID: <50BC56F5.5020708@it.aoyama.ac.jp>
Date: Mon, 03 Dec 2012 16:38:29 +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: Graham Klyne <GK@ninebynine.org>
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> <gokdb8hcanf2j32jc0rern9am6tgf8sr2s@hive.bjoern.hoehrmann.de> <50B6E049.9050401@stpeter.im> <f1pdb89cmbdqqkvk8jo5sv7olbddv1a4qs@hive.bjoern.hoehrmann.de> <50B6E9D8.5090109@stpeter.im> <50B770B8.1030400@ninebynine.org>
In-Reply-To: <50B770B8.1030400@ninebynine.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "uri-review@ietf.org" <uri-review@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, "xmpp@ietf.org" <xmpp@ietf.org>
Subject: Re: [Uri-review] [xmpp] 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: Mon, 03 Dec 2012 07:38:42 -0000

On 2012/11/29 23:27, Graham Klyne wrote:

> (FWIW, I thought it was easier to just say "encoded as UTF-8 within XMPP
> streams" than to explain why that's not relevant or out-of-scope.)

It may be easier, but it's technically wrong. This may not hurt here, 
but it may hurt somewhere else down the line because people may get 
confused.

Regards,    Martin.


> So, as Martin says, just "ship it" (with or without the above point).
>
> #g
> --
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>

v2.23.0 | Report a Bug | By Email