Hello, I am reading the XEP-96 and see in the requirements section: "Enable seamless file transfer, including fall-back mechanisms as appropriate", then I see that socks5 and IBB are must be implemented in a XEP-96 compatible implementation. Ok, we can try to use socks5 and if it fail we will fallback to ibb and then we will guaranteed done with our transfer. But where is described HOW this fallback should be negotiated? The flow:
1. SI Request. We are must to include both socks5 and IBB as our stream-methods. 2. SI Response will always reply with socks5 because it must support both of protocols and socks5 is with high priority. 3. SOCKS5 is failed to establish a stream. 4. What we have to do next? Send again a SI request with only IBB included as our stream-methods? Should the recipient to ask again about the file transfer? How should it determine that it should not, if it's not? That's really unclear with the current XEP. The second thing is: maybe we should to remove the requirement to support both socks5 and ibb? Because it's not carried out de-facto by several implementations and not each platform can easily implement both bytestreams. -- With best regards, Sergey Dobrov, XMPP Developer and JRuDevels.org founder.
