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

Justin Uberti <juberti@google.com> Thu, 23 October 2014 19:32 UTC

Return-Path: <juberti@google.com>
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 819121ACEB3 for <rtcweb@ietfa.amsl.com>; Thu, 23 Oct 2014 12:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 IO_sKiy5ww25 for <rtcweb@ietfa.amsl.com>; Thu, 23 Oct 2014 12:32:36 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D44801ACFC5 for <rtcweb@ietf.org>; Thu, 23 Oct 2014 12:32:15 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id wn1so1270760obc.6 for <rtcweb@ietf.org>; Thu, 23 Oct 2014 12:32:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=O2aU79u5sjIz3YkMPY8zpmrFq6EGOrH2sqAmCvRpA/s=; b=hue6XxUmmndkJdhgb3NPEJt9nPHbZuZSuDqIuKYLcnpgWZbIhf/ivY/5R8wlooDqdR a5T/I4aR7PeHZQ/7bnPemQP9E9LUC/eZCU2QHC/yBbSgnockNM2WwhA0DZFSyWo9BBHA EqHGCdJgIYQKVvh0hHk/SBnhy9NqI5wgYgHuz2JUyn6vrho5Aoy5IJeABF2CXCCOE9x0 VjEgCRDA++OXbKrqpnfWD9mzPlknA9oCSNwwRH2S0EwF1bXpzPBZkuf7/YhVVhF5U6tt RswhEkH0UGCDgRn51dGJ/nNJYEHjJ36JaHs3/pU+gnrw0dlN60PM7Yl8mn+yWhTvpGeQ PJEw==
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:from:date :message-id:subject:to:cc:content-type; bh=O2aU79u5sjIz3YkMPY8zpmrFq6EGOrH2sqAmCvRpA/s=; b=V70b4f5VBm/OMPBdlxnrG+BwJhpgokyzboKO6j6O+o77pjy65dtzJ/MWNyWnbZZoJE +Yo8Ec5xs6xkAaLCTPYVCLcdiYyRPx6zpXGGx1OXcdEh7tZueAskgKTuwx+NSqUSzmBN cxtFct6qZjgs/rBJU6g39bWGVPPf0zBRbhviVfjDniVu+TPR85/bY9zG8RoeWLVzQqja TB3vGH8VAZEuoXpMjNYRDCQfVUoxJcK32e06D1fXGpL9sAgAgzasgY841ca0Q0hs9NxN W5WG6Vu1tT/8L8LDyLK85zftziWE/oACnw86U/7/D/PqYD2Qtfuhi2eGz9eFJ/r1Yc7y fvNA==
X-Gm-Message-State: ALoCoQlmKgboTX7v0C075g/PSeCcIkacAQgqvN9caGbu9mK/pbkfoT7VfwuZ5MGKldzeGiqc1ojz
X-Received: by 10.202.199.65 with SMTP id x62mr3511134oif.61.1414092735035; Thu, 23 Oct 2014 12:32:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.251.230 with HTTP; Thu, 23 Oct 2014 12:31:54 -0700 (PDT)
In-Reply-To: <27059BBA-4094-469F-BE8B-156C0692A02F@edvina.net>
References: <E83AFA16-EB5C-4F2A-AEB7-662026519D67@edvina.net> <7594FB04B1934943A5C02806D1A2204B1D4C18C0@ESESSMB209.ericsson.se> <CAHbrMsBrRFZ5FYZy1kFKk8xADX7OW_LRZ765Laou+er8bnZTHw@mail.gmail.com> <27059BBA-4094-469F-BE8B-156C0692A02F@edvina.net>
From: Justin Uberti <juberti@google.com>
Date: Thu, 23 Oct 2014 12:31:54 -0700
Message-ID: <CAOJ7v-1ybR6ikzJZg5FELYqpLgS-cG8PHXkYa2urD70HQH03DQ@mail.gmail.com>
To: "Olle E. Johansson" <oej@edvina.net>
Content-Type: multipart/alternative; boundary="001a11c17e5e26e40e05061c1fd8"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/VGr9m5FciI8bscJmw7NPpZP-Unw
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: Thu, 23 Oct 2014 19:32:37 -0000

Generally, I think there is a fair amount of confusion about how these
various types of TURN servers are going to work. The RETURN draft takes a
first stab at defining the interactions here, and ideally it can be adopted
as a WG draft and referred to by -transports.

On Thu, Oct 23, 2014 at 5:26 AM, Olle E. Johansson <oej@edvina.net> wrote:

>
> On 22 Oct 2014, at 16:57, Benjamin Schwartz <bemasc@webrtc.org> wrote:
>
> 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.
>
> Cool! I'll take a look at that. Maybe Haralds draft need to refer to that.
>
> /O
>
>
> 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
>>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>