RFC 3921:Extensible Messaging and Presence Protoco...
RFC-Ref

Stream


Click on the red underlined text to get to the source

... TLS and SASL, and the <message/>, <presence/>, and <iq/> children of the stream root -- provide the building blocks for many types of near-real-time applications ...


... generated by the sender and SHOULD be copied back in any replies. If used, it MUST be unique to that conversation thread within the stream and MUST be consistent throughout that conversation (a client that ...


... session. These are: 1. Stream Authentication -- a client MUST complete stream ...
... Stream Authentication -- a client MUST complete stream authentication as documented in [XMPP-CORE ...
... XML stanzas. 2. Resource Binding -- after completing stream authentication, a client ...
... authentication, a client MUST bind a resource to the stream so that the client's address ...
... session' namespace in the stream features it advertises to a client after the completion of stream ...
... stream features it advertises to a client after the completion of stream authentication as defined in [XMPP-CORE]: ...
... client: <stream:stream xmlns ...
... <stream:stream xmlns='jabber ...
... client' xmlns:stream='http://etherx.jabber.org/streams' id='c2s_345' ...
... version='1.0'> <stream:features> <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'/> ...
... xmlns='urn:ietf:params:xml:ns:xmpp-session'/> </stream:features> Upon being so informed that session establishment ...
... active resource. Which of these the server does is up to the implementation, although it is RECOMMENDED to implement case #1. In case #1, the server SHOULD send a <conflict/> stream error to the active resource, terminate the XML stream and underlying ...
... case #1. In case #1, the server SHOULD send a <conflict/> stream error to the active resource, terminate the XML stream and underlying TCP connection for the active ...
... stanza error to the newly-requested session but maintain the XML stream for that connection so that the newly-requested session ...
... conflict (case #1): <stream:error> <conflict xmlns='urn:ietf:params:xml:ns:xmpp-streams'/> ...
... <conflict xmlns='urn:ietf:params:xml:ns:xmpp-streams'/> </stream:error> </stream:stream ...
... </stream:error> </stream:stream> ...
... stream:error> </stream:stream> Step 2 (alt): Server informs newly-requested session ...



Google
Web
RFC-Ref