Re: [Wish] Lecturing and WebRTC

[Juliusz Chroboczek <[e-mail]>]

Hi Lorenzo,

May I have an autograph, please?

> shared the slides for a presentation you did on Galene [...]  I'll have
> to see if the video of the presentation is available somewhere.

The slides are here:

  https://galene.org/galene-20210222.pdf

The raw video footage is here, but it's a mess (400MB tarfile, one
unseekable WebM per stream):

  https://galene.org/galene-20210222.tar

> but the different lifetimes for different streams assumes support for
> renegotiations [...] In this case, it seems simpler to push streams
> which are supposed to have different lifetimes as separate "broadcasts",

Yes, you could carry each stream within a separate session.  But it does
still imply the need to renegotiate something, either the set of streams
or the set of sessions.

> this means losing the ability of having everything on the same PeerConnection

You lose a few UDP ports, and exchange a few extra packets with your STUN
server.  Am I missing anything?

> I think the main point discussed today was whether or not, as a WISH
> client, you should be supposed to advertise [relayed] candidates, either
> via trickle or as part of your SDP offer. Even if they're not, if your
> WebRTC server is publicly reachable then it should still be able to make
> use of them nevertheless, by discovering them via prflx candidates.

I'm not sure I follow.  Suppose you're on an Eduroam network, so the only
outgoing traffic allowed is TCP/443 and TCP/1194.  You run your signalling
server on 443, your TURN server on 1194.

Since the client cannot reach any UDP ports, how is it going to learn
about the TURN server on port 1194 if it's not signalled explicitly?

-- Juliusz