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

IM


Click on the red underlined text to get to the source

... XMPP that provide the basic functionality expected of an instant messaging (IM) and presence application as defined in RFC 2779 [IMP-REQS ...


... to reply, but without a conversation history. An IM application SHOULD support all of the foregoing message types; if an application receives a message with no 'type' attribute or the ...


... IM and Presence Compliance Requirements ...
... presence subscriptions, roster storage and manipulation, privacy lists, and IM-specific routing and delivery ...
... protocols: o Generation and handling of the IM-specific semantics of XML stanzas as defined by the XML schemas ...


... Appendix C. Differences Between Jabber IM/Presence Protocols and XMPP ...
... Jabber community assumed that every client is an IM client and therefore initiated an IM session ...
... client is an IM client and therefore initiated an IM session upon successful authentication and resource binding ...
... JSF]). XMPP maintains a stricter separation between core functionality and IM functionality; therefore, an IM session is not ...
... XMPP maintains a stricter separation between core functionality and IM functionality; therefore, an IM session is not created ...


... XMPP Working Group has concentrated especially on IM session establishment and communication blocking (privacy lists ...



Google
Web
RFC-Ref