IETF Logo Mail Archive

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

Benjamin Schwartz <bemasc@webrtc.org> Wed, 22 October 2014 14:57 UTC

Return-Path: <bemasc@webrtc.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7505C1ACD12 for <rtcweb@ietfa.amsl.com>; Wed, 22 Oct 2014 07:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6a77cbl1uOkI for <rtcweb@ietfa.amsl.com>; Wed, 22 Oct 2014 07:57:55 -0700 (PDT)
Received: from mail-ob0-f176.google.com (mail-ob0-f176.google.com [209.85.214.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F4601ACD38 for <rtcweb@ietf.org>; Wed, 22 Oct 2014 07:57:54 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id m8so3010005obr.35 for <rtcweb@ietf.org>; Wed, 22 Oct 2014 07:57:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uem9lxg3XNB0MO9Bk8lMWJOkSC4EI41l5chzCy5uyfY=; b=c9ryHeJO9RHv231tdHaTvn4tD0dVQYI5xrnu8T9N1oOfi29hgCpSz5cSAGsXfbtgfr GIGx0H/S1eGbQ3pyleX3aunRG6He5uoWxNaw4OXWC+yMqRty6Dow3OWNWxPl2YfLCBZW 0gCAYq4xJnR7hRTjf9+2m5yBRvjlnOyIrkSocoJPHZI77/8VLCLW/UzqkDovyEXCtzxJ 8BZaewvrmSB+wzwARLoVtHPuIg99N3XMQxsk+48GMxC5lfeZqTJlmcMC5Z/copDmNNDh iwxGsir4s9nWRbMFq1moeqTHo1i1IKiUA49h0TPeX9TuoSRNdgftDm0LcXOfFiunMwHd JS8w==
X-Gm-Message-State: ALoCoQnHOkz2F5hQpaZvEFNAghVBA0VQKLJRZNnq3pum3gDXYzVSVXGqXImlvZSjXkTPeUI30DIn
X-Received: by 10.60.147.196 with SMTP id tm4mr35924110oeb.4.1413989874300; Wed, 22 Oct 2014 07:57:54 -0700 (PDT)
Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com. [209.85.218.49]) by mx.google.com with ESMTPSA id m39sm6452501oik.22.2014.10.22.07.57.53 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Oct 2014 07:57:53 -0700 (PDT)
Received: by mail-oi0-f49.google.com with SMTP id a3so2781785oib.8 for <rtcweb@ietf.org>; Wed, 22 Oct 2014 07:57:53 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.38.135 with SMTP id g7mr36563973obk.19.1413989873791; Wed, 22 Oct 2014 07:57:53 -0700 (PDT)
Received: by 10.182.16.130 with HTTP; Wed, 22 Oct 2014 07:57:53 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D4C18C0@ESESSMB209.ericsson.se>
References: <E83AFA16-EB5C-4F2A-AEB7-662026519D67@edvina.net> <7594FB04B1934943A5C02806D1A2204B1D4C18C0@ESESSMB209.ericsson.se>
Date: Wed, 22 Oct 2014 10:57:53 -0400
Message-ID: <CAHbrMsBrRFZ5FYZy1kFKk8xADX7OW_LRZ765Laou+er8bnZTHw@mail.gmail.com>
From: Benjamin Schwartz <bemasc@webrtc.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="001a11c3302024d5ac0506042c2b"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/esDHdR28ni4wRVH7gi04Q3qf-p4
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] draft-ietf-rtcweb-transports-07.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Oct 2014 14:57:59 -0000

FYI, the purpose of the RETURN draft (
https://tools.ietf.org/html/draft-schwartz-rtcweb-return-03) is to try to
specify the precise interaction and precedence when both the browser and
the application provide TURN servers.  (It's not as simple as "one or the
other".)

I haven't considered the issues related to browser-provided STUN servers,
though.

On Wed, Oct 22, 2014 at 10: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
>

v2.23.0 | Report a Bug | By Email