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

Peter Saint-Andre <stpeter@stpeter.im> Thu, 29 November 2012 02:51 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 E49E021F89A7; Wed, 28 Nov 2012 18:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.057
X-Spam-Level:
X-Spam-Status: No, score=-102.057 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, J_CHICKENPOX_66=0.6, 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 GkJO8ei3IHu7; Wed, 28 Nov 2012 18:51:11 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0B421F8823; Wed, 28 Nov 2012 18:51:11 -0800 (PST)
Received: from [192.168.1.4] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 36B4B40062; Wed, 28 Nov 2012 19:56:09 -0700 (MST)
Message-ID: <50B69BF5.2040808@stpeter.im>
Date: Wed, 28 Nov 2012 16:19: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: Larry Masinter <masinter@adobe.com>
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>
In-Reply-To: <50B68BBA.1000302@stpeter.im>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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 02:51:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So here is the registration...

###

   URI scheme name.
      jabber

   Status.
      permanent

   URI scheme syntax.
      The only allowable strings are:
      - jabber:client
      - jabber:component:accept
      - jabber:component:connect
      - jabber:component:exec
      - jabber:iq:agent
      - jabber:iq:agents
      - jabber:iq:auth
      - jabber:iq:autoupdate
      - jabber:iq:browse
      - jabber:iq:conference
      - jabber:iq:gateway
      - jabber:iq:groupchat
      - 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:time
      - jabber:iq:version
      - jabber:server
      - jabber:x:autoupdate
      - jabber:x:conference
      - jabber:x:data
      - jabber:x:delay
      - jabber:x:encrypted
      - jabber:x:envelope
      - jabber:x:event
      - jabber:x:expire
      - jabber:x:oob
      - jabber:x:roster
      - jabber:x:signed

   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.

   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

###

Feedback is welcome.

Peter

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlC2m/UACgkQNL8k5A2w/vyA2ACgkKPJN21QgVYrmN8Sk6ZShLpz
6BgAnAkyDYhv2/sbi4fcn3R2h/FmbZvj
=abXm
-----END PGP SIGNATURE-----