Stream initiation multi-bytestreams extension

Stream initiation multi-bytestreams extension Extension of XEP-0095 allowing to negotiate more than one bytestream to be used as a fallback. Copyright (c) 2008 Collabora Limited. This document may be distributed under the same terms as the Telepathy specification. si-multiple ProtoXEP Extension Standards Telepathy project XMPP Core XEP-0095 NOT YET ASSIGNED Guillaume Desmottes guillaume.desmottes@collabora.co.uk guillaume.desmottes@collabora.co.uk 0.0.1 2008-12-11 cassidy

First draft.

This document describes an extension of the Stream Initiation (SI) protocol. With current SI protocol, the receiver has to choose which bytestream method he wants to use for the data streaming. If he chooses an efficient method as SOCKS5 (XEP-0065) and this method fails because of network topology, the SI fails and data can't be transferred. The protocol described in this document aims to solve this problem by allowing users to fallback to another bytestream method if the first one failed.

When sending a SI request, the sender informs the receiver that he supports multi-bytestreams by adding the si-multiple node.

]]>

If the receiver support multi-bytestreams as well, he sends a list of the methods supported instead of the normal SI reply. Bytestreams will be try by the sender in that order.

XEP-0047). Each bytestream is negotiated according the protocol described in its XEP. Once a bytestream has been sucessfully established, all the data are send using it and the other methods are not used.

None.

TODO