IETF Logo Mail Archive

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

Larry Masinter <masinter@adobe.com> Wed, 28 November 2012 22:05 UTC

Return-Path: <masinter@adobe.com>
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 7128321F8457; Wed, 28 Nov 2012 14:05:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level:
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_66=0.6, 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 NBpYyE2imZaS; Wed, 28 Nov 2012 14:05:59 -0800 (PST)
Received: from exprod6og115.obsmtp.com (exprod6og115.obsmtp.com [64.18.1.35]) by ietfa.amsl.com (Postfix) with ESMTP id 002B721F894B; Wed, 28 Nov 2012 14:05:56 -0800 (PST)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob115.postini.com ([64.18.5.12]) with SMTP ID DSNKULaKv4Tf20/hHFF27ko1Moi0azFfC9Y4@postini.com; Wed, 28 Nov 2012 14:05:58 PST
Received: from inner-relay-1.corp.adobe.com (inner-relay-1.corp.adobe.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id qASM5nHP007635; Wed, 28 Nov 2012 14:05:50 -0800 (PST)
Received: from nacas02.corp.adobe.com (nacas02.corp.adobe.com [10.8.189.100]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id qASM5mNc011798; Wed, 28 Nov 2012 14:05:49 -0800 (PST)
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nacas02.corp.adobe.com ([10.8.189.100]) with mapi; Wed, 28 Nov 2012 14:05:48 -0800
From: Larry Masinter <masinter@adobe.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Graham Klyne <GK@ninebynine.org>
Date: Wed, 28 Nov 2012 14:05:45 -0800
Thread-Topic: [Uri-review] [apps-discuss] XMPP jabber: URI scheme not registered?
Thread-Index: Ac3Nmik2CTw2bq55Qt6ov8YIw0cz1gAGZC3g
Message-ID: <C68CB012D9182D408CED7B884F441D4D1E371700C3@nambxv01a.corp.adobe.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70F75EE78@xmb-rcd-x10.cisco.com> <50B4F2F0.3050406@stpeter.im> <50B652A7.2030502@ninebynine.org> <50B65E7D.9050005@stpeter.im>
In-Reply-To: <50B65E7D.9050005@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "julian.reschke@gmx.de" <julian.reschke@gmx.de>, "uri-review@ietf.org" <uri-review@ietf.org>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "xmpp@ietf.org" <xmpp@ietf.org>, "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: Wed, 28 Nov 2012 22:05:59 -0000

How about avoiding giving BNF which you then prohibit using? Just list them:


URI scheme name
    jabber

Status:
    Permanent

URI scheme syntax:
     One of the following:
       - jabber:client
       - jabber:component:accept
       - jabber:component:connect
       - jabber:iq:auth
       - jabber:iq:gateway
       - jabber:iq:last
       - jabber:iq:oob
       - jabber:iq:privacy
       - jabber:iq:private
       - jabber:iq:register
       - jabber:iq:roster
       - jabber:iq:rpc
       - jabber:iq:search
       - jabber:iq:version
       - jabber:server
       - jabber:x:conference
       - jabber:x:data
       - jabber:x:encrypted
       - jabber:x:oob
       - jabber:x:signed

  URI scheme semantics.
        These URIs were used as   XML namespaces during development of the technology
        that became the Extensible Messaging and Presence Protocol (XMPP).  
       The scheme was never used (and should not be used) for any
        other purpose; no other "jabber:" URIs shall be minted.

   Encoding considerations.
        ASCII (UTF-8) within XMPP protocol streams.

 Applications/protocols that use this URI scheme name.

       Extensible Messaging and Presence Protocol (XMPP).


  Interoperability considerations.
       The 'jabber' scheme must not be used to identify or
       enable interaction with XMPP addresses; the 'xmpp'
       scheme defined in RFC 5122 is to be used in such
       cases.


  Security considerations.
       See Section 13 of RFC 6120.


  Contact.
       Peter Saint-Andre <stpeter@jabber.org>


   Author/Change controller.
       XMPP WG <xmpp@ietf.org>
   References.
       RFC 6120

v2.23.0 | Report a Bug | By Email