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

Graham Klyne <GK@ninebynine.org> Tue, 27 November 2012 16:36 UTC

Return-Path: <GK@ninebynine.org>
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 DD98621F8534; Tue, 27 Nov 2012 08:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_66=0.6, RCVD_IN_DNSWL_MED=-4]
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 jZeBAszvXwG3; Tue, 27 Nov 2012 08:36:06 -0800 (PST)
Received: from relay0.mail.ox.ac.uk (relay0.mail.ox.ac.uk [129.67.1.161]) by ietfa.amsl.com (Postfix) with ESMTP id 14B8D21F842C; Tue, 27 Nov 2012 08:36:06 -0800 (PST)
Received: from smtp0.mail.ox.ac.uk ([129.67.1.205]) by relay0.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1TdO8g-0006SQ-28; Tue, 27 Nov 2012 16:36:02 +0000
Received: from zoo-dhcp16.zoo.ox.ac.uk ([129.67.26.221]) by smtp0.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1TdO8g-0001uz-1F; Tue, 27 Nov 2012 16:36:02 +0000
Message-ID: <50B4EBA9.8030700@ninebynine.org>
Date: Tue, 27 Nov 2012 16:34:49 +0000
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <A723FC6ECC552A4D8C8249D9E07425A70F758CD6@xmb-rcd-x10.cisco.com> <50B3D146.3080506@stpeter.im> <50B3F104.6010305@ninebynine.org> <50B3F3A4.2060002@stpeter.im> <50B4E168.5010300@ninebynine.org> <50B4E67A.80502@stpeter.im>
In-Reply-To: <50B4E67A.80502@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Cc: Julian Reschke <julian.reschke@gmx.de>, "uri-review@ietf.org" <uri-review@ietf.org>, "xmpp@ietf.org" <xmpp@ietf.org>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [Uri-review] [apps-discuss] 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: Tue, 27 Nov 2012 16:36:08 -0000

On 27/11/2012 16:12, Peter Saint-Andre wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/27/12 8:51 AM, Graham Klyne wrote:
>> Peter,
>>
>> To be clear about this, are you saying that the apparent
>> requirement in RFC6120 to use namespace jabber:server or
>> jabber:client for "message", "presence" or "iq" stanzas no longer
>> applies?  If I were implementing XMPP based on what I read here, I
>> would think that these namespaces *are* required, which suggests a
>> problem with the XMPP spec.
>
> Yes, jabber:client and jabber:server are required by RFC 6120 (and RFC
> 6121 requires support for jabber:iq:roster).

OK, that's what I originally thought.  In which case, I think the text from RFC 
4395 that you cited does not apply, since use of these jabber: URIs is still 
required (and others as you note below).

I think the appropriate course would be to register the URI scheme, maybe list 
the URIs in use for this scheme, and add a note that no more jabber: URIs should 
be minted.

#g
--

>> (I noticed the other namespaces, but since they all seemed to be
>> urn: URIs I ignored them for this discussion.)
>
> Other old namespaces currently in use are jabber:iq:last,
> jabber:x:conference, jabber:iq:private, jabber:iq:version,
> jabber:iq:register, jabber:iq:rpc, jabber:iq:oob,
> jabber:component:accept, jabber:component:connect, jabber:iq:privacy,
> and jabber:x:data.