Re: [Wish] Trickle ICE and ICE restart

[Juliusz Chroboczek <[e-mail]>]

> If we could just extend the ABNF grammar, we could just send the candidates at
> session level, and maybe even omit the ice-pwd attribute:

Agreed on both counts.  Galene currently ignores both the m-line and the ice-pwd.

> 2) There is a potential race condition between 2 PATCH requests, one for
> updating candidates and another one for ice restart.

> We have 3 different ways of solving this:
> - Force the client to send the PATCH request sequentially and not allow it to
> have 2 in-flight requests (which can cause problems if the first request is
> sent while there was poor connectivity and the ice restart is sent just after
> the connectivity is restored).

I agree, it's important to be able to send a restart at any time.

> - Force the server to remember past usernames for the client and discard
> requests with past usernames. (This is the one I am going to implement)
> - Remove the ice-pwd field from the sdp fragment so the server can
> differentiate between both.

I think it should be possible for the server to differentiate between the
two before even starting to parse the SDP.  We could use different MIME
types, different HTTP requests, use a custom HTTP header, or add an extra
line at the beginning of the body.

> 4) There is a bug in chrome that returns a different value for the ice username
> on the ice transport api than the one set on the local description.

I think there are more bugs in Chrome :-/

-- Juliusz