On Tuesday 01 February 2005 12:49 pm, Peter Saint-Andre wrote: > In some applications, it might be helpful for an XMPP server to assign a > JID to an entity that connects with a stream that is qualified by the > 'jabber:client' namespace (or more precisely assign the node identifier > portion of the entity's JID, just as the server can assign the resource > identifier of the entity's JID using the resource binding protocol). > Chatting with someone via IM just now, we worked out the following: > > 1. entity authenticates via SASL ANONYMOUS > > 2. server tells entity that resource binding is required (via stream > feature) > > 3. entity requests that server create a resource for it > > 4. server replies with full JID: > > <iq type='result' id='bind_2'> > <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'> > <jid>[EMAIL PROTECTED]/someresource</jid> > </bind> > </iq> > > Thoughts?
Yep, looks fine to me. Even though it's not explicitly spelled out in the RFC, I figured the above process could be assumed to work. After all, it is the server that determines the client's true full JID, regardless of the SASL mechanism used. Technically speaking, the anonymous client could even specify an explicit resource; it shouldn't matter either way. -Justin _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
