There are various cases where it might [have been] useful, including security labelling - some existing implementations treat differently labelled chat messages as belonging to a different session, and I imagine other cases where you can have multiple conversations with the same endpoints at both ends might exist.
The SIP and '136 use-cases might not be terribly current, but as a building block it doesn't seem an unreasonable framework. On 4 September 2014 16:13, Philipp Hancke <[email protected]> wrote: > Am 14.01.2008 um 21:32 schrieb XMPP Extensions Editor: > >> Version 1.2 of XEP-0155 (Stanza Session Negotiation) has been released. >> >> Abstract: This specification defines a method for formally negotiating >> the exchange of XML stanzas between two XMPP entities. The method uses >> feature negotiation forms sent via XMPP message stanzas to enable session >> initiation between entities that do not share presence information or have >> knowledge of full JabberIDs and therefore is also suitable for use across >> gateways to SIP-based systems. A wide range of session parameters can be >> negotiated, including the use of end-to-end encryption, chat state >> notifications, XHTML-IM formatting, and message archiving. >> >> Changelog: Specified that IM message bodies must not be included; added >> boolean multisession field to explicitly determine whether multiple >> concurrent sessions are allowed between the full JIDs of the parties. (psa) >> >> Diff: http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/ >> xep-0155.xml?r1=662&r2=1574 >> >> URL: http://www.xmpp.org/extensions/xep-0155.html >> >> > Old thread alert... just stumbled about this. > > It doesn't seem to have gotten much traction since 2008. Its main purpose > seems to be SIP-interop and the IETF STOX WG has not used it afaics. Shall > we deprecate this in favor of RFC 7247 et al? > > Kev: possible agenda item for the next council meeting >
