Re: [rtcweb] rtcweb-transports reference to TRAM discovery

🔓Dan Wing <dwing@cisco.com> Wed, 17 December 2014 21:59 UTC

Return-Path: <dwing@cisco.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 D45591A876F for <rtcweb@ietfa.amsl.com>; Wed, 17 Dec 2014 13:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level:
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 25mkcwXRAWMV for <rtcweb@ietfa.amsl.com>; Wed, 17 Dec 2014 13:59:01 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 383801A8781 for <rtcweb@ietf.org>; Wed, 17 Dec 2014 13:59:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2005; q=dns/txt; s=iport; t=1418853541; x=1420063141; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=WHlJiyMh7LbZdLXPGxDO3hP3Cqu8kTfcATqcfOXVLEk=; b=gt0plfopVxxDRWBSum3jO66vvVxSXvZKiGhqvA+h0HG/vXId6RFj85Du 7O264GOIhMMUhwJ0nPfwO2p/cWgaG7MFwfh+0icPqHNg6ubOhP2TOYL86 8LMmwFl++XUF2ZaMHRg4EogVbYqUBaNJIBchvS9UCqROmLW2pWEyauI+2 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApcFAEn7kVStJA2B/2dsb2JhbABagwZSWMV3CoUoSgKBIhYBAQEBAX2EDAEBAQMBAQEBNzQLBQsLGC4nMAYTiCQIDdUPAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSPPzMHgxaBEwWJQ4gDhTKFfItEIoQNHTGCQwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,596,1413244800"; d="scan'208";a="380897432"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-5.cisco.com with ESMTP; 17 Dec 2014 21:59:01 +0000
Received: from [10.24.109.157] ([10.24.109.157]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id sBHLwxpT012996 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 17 Dec 2014 21:58:59 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
In-Reply-To: <5491B831.70704@alvestrand.no>
Date: Wed, 17 Dec 2014 13:58:58 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1DDC0E1-8B87-45D9-ACDD-7A53F34A79E2@cisco.com>
References: <9F33F40F6F2CD847824537F3C4E37DDF1E63FB08@MCHP04MSX.global-ad.net> <CABcZeBOpX0vM9NJeKY5e+S13oKrLW3Td53qcxRkCHa2=nv=EGg@mail.gmail.com> <CANO7kWBY1MTU1A2fWo0E5Y6TQ1o+vWSz22pnWz6+5s7SFQcP-g@mail.gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF1E63FD67@MCHP04MSX.global-ad.net> <CAOJ7v-1NnS1QOF-Ujv7a=qCnXrQ0htd0b4TFUDaKgwik9Rd=-Q@mail.gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF1E643D2C@MCHP04MSX.global-ad.net> <5491B831.70704@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/5e8T5s6bg6OlM4XXcumZlDsNedA
Cc: Mark Nottingham <mnot@mnot.net>, RTCWEB <rtcweb@ietf.org>
Subject: Re: [rtcweb] rtcweb-transports reference to TRAM discovery
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, 17 Dec 2014 21:59:03 -0000

On Dec 17, 2014, at 9:06 AM, Harald Alvestrand <harald@alvestrand.no> wrote:

> On 12/17/2014 05:19 PM, Hutton, Andrew wrote:
>> OP: 15 December 2014 22:44 Justin Uberti Wrote:
>>> I think making it a requirement is probably premature until we have a
>>> WG document that explains what should happen when you discover one of
>>> these network-provided TURN servers.
>>> Once https://tools.ietf.org/html/draft-schwartz-rtcweb-return-04 is
>>> accepted as a WG doc, we can add a requirement for support for RETURN
>>> and server discovery.
>>> 
>>> Unclear whether it needs to be MUST-strength until we get some
>>> implementation feedback though.
>>> 
>> -transports already states " WebRTC browsers MUST support configuration of STUN and TURN servers, both from browser configuration and from an application".
>> 
>> So it looks like we already have a requirement but no explanation of what should happen when both are available.
> 
> The last times we've talked about this, people have imagined configuring this via the same mechanism as configuring HTTP proxies (nonstandard script at a nonstandard URL).
> 
> Autodiscovery may be preferable, but it's not clear that it removes the need for the script-like things.

If there is, gathering that requirement seems important.  Mark Nottingham was beginning an effort around WPAD standardization (or something that resembled it).  CC'ing him in case there is useful status on that front.

-d


> 
>> 
>> Looks like we need to adopt draft-schwartz-rtcweb-return and explain this stuff. I would certainly support that and put some effort into getting this done.
>> 
>> Andy
>> _______________________________________________
>> 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