Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: "Michael Ströder" <michael@stroeder.com>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: STUN and TURN
Date: Fri, 08 Jan 2021 17:41:04 +0100	[thread overview]
Message-ID: <87eeiv755r.wl-jch@irif.fr> (raw)
In-Reply-To: <6f88f2e0-7b06-953d-ed8b-53481381a0f0@stroeder.com>

> So I wonder whether using stun: and turn: URLs in the ICE config make sense.

It's not useful, it will only slow down connection establishment.  Every
TURN server acts as a STUN server, if you have a TURN server it will be
used for STUN candidates.

> Do the browsers prefer STUN-trickled addresses over relaying via TURN if
> both are configured.

Yes, Rosenberg is competent ;-)  RFC 8445 Section 5.1.2.2:

   The RECOMMENDED values for type preferences are 126 for host
   candidates, 110 for peer-reflexive candidates, 100 for server-
   reflexive candidates, and 0 for relayed candidates.

("Server-reflexive" means STUN, "relayed" means TURN.)

Browsers are free to tweak the priorities, and chrome correctly sets
a slightly higher priority for Ethernet than for WiFi:

   When choosing type preferences, agents may take into account factors
   such as latency, packet loss, cost, network topology, security,
   privacy, and others.

-- Juliusz

      reply	other threads:[~2021-01-08 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 16:08 [Galene] " Michael Ströder
2021-01-08 16:41 ` Juliusz Chroboczek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eeiv755r.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=galene@lists.galene.org \
    --cc=michael@stroeder.com \
    --subject='[Galene] Re: STUN and TURN' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox