Re: [rtcweb] draft-ietf-rtcweb-transports-07.txt

I just want to mention this:

http://tools.ietf.org/html/draft-ietf-tram-turn-server-discovery-00

I think that both browser and application configuration are included in
step #1 of the discovery algorithm, so that doesn't answer Olle's question.
But we still need to keep the whole discovery process in mind.

Simon

On Wed, Oct 22, 2014 at 8:51 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> The advantage of an application configuration is that it can be
> dynamically provided/updated, based on location based etc - assuming the
> webpage provider has knowledge about STUN/TURN servers, of course.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Olle E.
> Johansson
> Sent: 22 October 2014 17:44
> To: rtcweb@ietf.org
> Subject: [rtcweb] draft-ietf-rtcweb-transports-07.txt
>
> Section 3.4
>
> " WebRTC browsers MUST support configuration of STUN and TURN servers,
>    both from browser configuration and from an application."
>
>
> Should we mention which takes precedence? If configured in the browser,
> start with that server.
> If not use the one provided by the application.
>
> Maybe we should clarify that turn DNS discovery MUST be used to provide
> failover and load balancing.
>
> /O
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>