[Bug 30176] New: Update SOCKS5 bytestream to use relays with muc contacts

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=30176

           Summary: Update SOCKS5 bytestream to use relays with muc
                    contacts
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: medium
         Component: gabble
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: guillaume.desmottes at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


Currently the SOCKS5 bytestream doesn't use relays when trying to establish a
bytestream with a muc contact (we check in gabble_bytestream_socks5_initiate if
the contact is a muc one and then don't add proxies to the stanza).

In practice that means than sending a file to a muc contact or any muc stream
tubes will fallback to IBB if direct connections are not possible with the
peer. The tube case is the most annoying one as if more applications start
using muc stream tube, the XMPP servers are going to hate us.

That's because  XEP-0065 used to have a bug making impossible to use a relay
with a muc contact. See [1] if you are interested in the glorius XMPP details.
But, as pointed on [2] that's not longer the case and an updated version of the
spec now has a solution [3] for this problem.

We should update our implementation to make use of this updated protocol and
re-enable relays with muc contacts.

[1] http://mail.jabber.org/pipermail/standards/2009-March/021229.html
[2] http://developer.pidgin.im/ticket/8524#comment:3
[3] http://xmpp.org/extensions/tmp/xep-0065-1.8.html#muc

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.