[jdev] Resource binding

Peter Saint-Andre stpeter at stpeter.im
Wed Mar 3 22:56:43 CST 2010

On 3/3/10 9:18 PM, chris wrote:

> I still haven't read any reasonable argument against multiplexed resource 
> binding.  The two main points made are "it complicates the protocol" and 
> "for what purpose".
> To the first point, it was a very simple change to the protocol in my 
> perception and OPTIONAL (unfortunately) at that.
> To the second point I think this and other threads have answered that 
> question, but essentially it boils down to allowing the only type of XMPP 
> entity, a client, that does not require DNS and custom server support to 
> be something besides an instant messenger or a one off implementation 
> that is only useful within its own network.

As I've already said, if you and other people care about multiplexing
resources on a single XML stream, then write a document defining how it
works and propose it for consideration. Basically all you need to do is:

1. Copy the XML for XEP-0193, as described at
http://xmpp.org/xsf/sourcecontrol.shtml (sorry, the SVN viewer is broken
right now but you can find the XML through git or directly via SVN checkout)

2. Perhaps factor in some of the differences that might be found in
older versions of draft-saintandre-rfc3920bis, such as:


3. Change the namespace for the unbind feature (or perhaps we should
call it "multibind") to something like urn:xmpp:multibind:0 in
accordance with XEP-0053

4. Submit it for consideration by the XMPP Council, as described at

We have an open standards process at the XSF, and most of the hard work
has been done already in this case. If all this is too confusing, feel
free to ping me via IM at stpeter at jabber.org...


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6820 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20100303/85c08ca3/attachment.bin>

More information about the JDev mailing list