Good morning Emil,
In fact, I was using the term "IP privacy" to mean "IP anonymity" (if
there is such a thing in existing VoIP communications). Sorry for the
OK, I see. Well ... there is such a thing but we don't currently do this
in Jitsi, we concentrate on protecting the data you exchange with your
peer, rather than hiding your IP address.
That said, it would be completely possible to add an option that only
allows conversations through a TURN server or a Jingle Node Relay.
We do support Jingle nodes yes but I am not sure exactly how you see
this as being related to privacy. If you are wondering about
eavesdropping possibilities then it would be worth pointing out that
ZRTP is an end-to-end encryption mechanism so a Jingle Node Relay would
not be able to eavesdrop on media that it is relaying.
Jingle nodes help in the context of IP anonymity because they conceal
the IP address of the communication partners from each others and from
local eavesdroppers. On the other end, they may also hurt IP anonymity
because a malicious jingle node may be able to find out which pairs of
IP addresses communicate with one another. I have a few specific questions:
We currently use provider maintained Jingle Nodes only. Providers know
what who you are calling anyway and the Jingle Node doesn't really have
any other meaningful information.
- When exactly does Jitsi employ Jingle nodes? In particular, is the
motivation for using these nodes only to traverse NATs or were they
introduced also to provide some anonymity to Jitsi's users?
We currently only use Jingle Nodes (and TURN servers) as a last resort
in NAT traversal. We give higher priority to direct communication.
- Do you know the fraction of Jitsi calls that are relayed by Jingle
There's a geographic factor in this and it depends a lot on the kind of
NATs you and your peers are using. In some parts of the worlds (like
France for example) use of relaying may be as low as 10%, in others it
may reach 50%.
Relaying naturally increases the latency of VoIP calls which may
hurt user experience. I was also wondering whether you you had a sense
of the additional latency resulting from this relaying.
Oh that really depends on where you are and where your peers are. In
theory it is possible to even have lower latency when using a relay
(although this is admittedly not a common case).
All in all, I'd say that the latency added from relaying is not going to
be perceptible to users in a majority of the cases. The real problem
with relays is the cost they add to infrastructure. The more you relay,
the more a provider needs to pay for bandwidth and server-side hardware.
This is even more of an issue with video (a lot more than it is with audio).
- How are Jingle nodes currently selected?
We just ask the provider to give us the addresses of whatever Jingle
Node relays it supports.
On 23.02.13, 11:05, Stevens Le Blond wrote: