IETF Logo Mail Archive

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

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Thu, 18 December 2014 17:23 UTC

Return-Path: <fluffy@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 684E11A87A4 for <rtcweb@ietfa.amsl.com>; Thu, 18 Dec 2014 09:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level:
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 8M7mS5dHqY7S for <rtcweb@ietfa.amsl.com>; Thu, 18 Dec 2014 09:23:40 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C22451A8AE0 for <rtcweb@ietf.org>; Thu, 18 Dec 2014 09:23:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=831; q=dns/txt; s=iport; t=1418923419; x=1420133019; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1otFeCbmIy4n4qkKimpmdFotSiTUcWPowd44a6sZNTs=; b=CDtgjisyx0AaaxbIQYBnaF1sHL3ET7y1skgShZQEXMY7r+NOpkRCPNOw xwedYZKRnJjPPlIpWSjNo8AALV+NCW8xzMxn5qOs8mTtUBcGTFj3g/dT/ +2d0ui4dsdQYjtlj66FltDIKP7KbVGXB2FKo5cZ85iG0XRMWhBTiyS6Qo k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlcFABANk1StJV2S/2dsb2JhbABagmQiUlgExhIKhShKAoEiFgEBAQEBfYQMAQEBAwEBAQE3NAsFCwIBCBgeECcLJQIEDgWIJAgBDNUiAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSPPzMHgxaBEwEEjgqDPoUykUIig2xvAYFEfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,601,1413244800"; d="scan'208";a="106648921"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-5.cisco.com with ESMTP; 18 Dec 2014 17:23:39 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id sBIHNcPu019106 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Dec 2014 17:23:39 GMT
Received: from xmb-aln-x02.cisco.com ([fe80::8c1c:7b85:56de:ffd1]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Thu, 18 Dec 2014 11:23:38 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>
Thread-Topic: [rtcweb] rtcweb-transports reference to TRAM discovery
Thread-Index: AQHQGudcsQQgzLcHBE28skFLAtCSOQ==
Date: Thu, 18 Dec 2014 17:23:37 +0000
Message-ID: <6946D534-CBE7-4D1A-8C26-4D2FE07136D1@cisco.com>
References: <9F33F40F6F2CD847824537F3C4E37DDF1E63FB08@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF1E63FB08@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AC6865478E08CA4FA4B996B6823E9859@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/__mhiJ0RyiMmYT5JpF7eF-ijt-c
Cc: "rtcweb@ietf.org" <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: Thu, 18 Dec 2014 17:23:42 -0000

It seems that in the mobile case and many residential cases, doing that draft would allow a service provider to force all the traffic through a TURN server of the service providers choosing. Am I reading this correctly because I am pretty sure I would not be in favor of that.


> On Dec 15, 2014, at 7:42 AM, Hutton, Andrew <andrew.hutton@unify.com> wrote:
> 
> I am thinking that https://tools.ietf.org/html/draft-ietf-rtcweb-transports-07#section-3.4 should include a requirement that a WebRTC Browser MUST support the TURN server discovery as described in https://tools.ietf.org/html/draft-ietf-tram-turn-server-discovery-00.
>  
>  
> Andy
>  
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email