Bug 22931

Summary: Channel.Type.DatagramTube
Product: Telepathy Reporter: Simon McVittie <smcv>
Component: tp-specAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: enhancement    
Priority: lowest    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard: later
i915 platform: i915 features:

Description Simon McVittie 2009-07-24 04:52:08 UTC 
12:24 < smcv> youmin: there are a couple of features you might be looking for, 
              and we don't implement either of them yet :-(
12:25 < youmin> @scmv tell me
12:25 < smcv> either: we do the Jingle/NAT traversal/pseudo-TCP and present you 
              with something that looks to you like TCP
12:25 < smcv> or: we present you with something that looks like UDP, and you do 
              an existing packet-based protocol over ti
12:25 < smcv> I don't know which of them you want, but neither exists yet

The first feature there is Bug #22930.

The second feature mentioned there is a datagram ("UDP") tube; I'm filing this bug to represent it. When the spec has been written (quite easy, just copy/paste/change StreamTube) it will need implementations in at least Gabble (Jingle) and Salut (easy: UDP forwarding onto the local LAN).

One day, we would like to make OpenArena or ioquake3 into a UDP tubes client, so you can run a Quake 3 listen server behind a firewall and share it with your IM contacts :-) It could also be interesting to have OpenVPN integration.

This is a lower priority than Bug #22930, I think.
Comment 1 GitLab Migration User 2019-12-03 20:18:18 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/29.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.