IETF Logo Mail Archive

Re: [rtcweb] draft-schwartz-rtcweb-return

"Prashanth Patil (praspati)" <praspati@cisco.com> Thu, 26 March 2015 18:52 UTC

Return-Path: <praspati@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 74CBA1A9248 for <rtcweb@ietfa.amsl.com>; Thu, 26 Mar 2015 11:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.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] 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 uRrE4Q5l0EZe for <rtcweb@ietfa.amsl.com>; Thu, 26 Mar 2015 11:52:05 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E27FC1A9244 for <rtcweb@ietf.org>; Thu, 26 Mar 2015 11:52:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1327; q=dns/txt; s=iport; t=1427395924; x=1428605524; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ABiBg6Ncc8DzB6/yH4cGL/qmAfKpcKFyPtu6Rt6dRnY=; b=bqoAQEmmnkn38V9Y1UF8g2D0zMJaALgBb3Ej5vRoS8k7z7Y3GjgTPfWL NMIGaRhrXfL0t/7jgxqAp0+9+ryvM7ssNGeNh9ziJ6yyP9Y31Lxe/avHN CIPMfg77DvWvAb37ZBt19Wi2UFjA1EsVSmzgQP8l6/QDhp02tkZruHKwB 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B+BgBsVBRV/5xdJa1cgwZSWgTCcYIxCoUsSQKBXUwBAQEBAQF9hBUBAQQBAQE3NBsCAQg2ECcLJQIEARKILw3MBgEBAQEBAQEBAQEBAQEBAQEBARYEiyiEIV6ELQWQUIlvgRuPS4NHIoNub4EDQX8BAQE
X-IronPort-AV: E=Sophos;i="5.11,474,1422921600"; d="scan'208";a="135724123"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP; 26 Mar 2015 18:52:04 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t2QIq4Ud017449 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Thu, 26 Mar 2015 18:52:04 GMT
Received: from xmb-rcd-x07.cisco.com ([169.254.7.249]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0195.001; Thu, 26 Mar 2015 13:52:03 -0500
From: "Prashanth Patil (praspati)" <praspati@cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] draft-schwartz-rtcweb-return
Thread-Index: AQHQZ/XyyqazPaNNdkiBkvhhqUjfFQ==
Date: Thu, 26 Mar 2015 18:52:03 +0000
Message-ID: <D139A2DF.430D1%praspati@cisco.com>
References: <9DA8307B-263C-4951-A55C-36B42D27C08B@cisco.com>
In-Reply-To: <9DA8307B-263C-4951-A55C-36B42D27C08B@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [10.155.208.155]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BD87089FC9049E468BC63C9B36C20452@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/yOdU3GFtaMPGrxx_RzCWg8RES5I>
Subject: Re: [rtcweb] draft-schwartz-rtcweb-return
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, 26 Mar 2015 18:52:06 -0000


On 3/26/15, 8:20 AM, "Cullen Jennings (fluffy)" <fluffy@cisco.com> wrote:

>I'd like to point out that the combination of
>ietf-tram-turn-server-discovery and draft-schwartz-rtcweb-return allow
>any network you are connected to more or less MITM your media and do
>things like rate limit it, generate analytics on who you are talking to,
>force your traffic through an intermediary that is in a  different legal
>jurisdiction and so on.
>
>They are also not clear on how the browser gets the credentials to use
>the discovered TURN server. This seems like a major lacking before we can
>significantly discuss this.

The client should use the REALM attribute (returned in the 401 error
response) to determine the credentials to use for authentication.


-Prashanth

> 
>
>As we have seen from the google proxy deployments, enough revenue can be
>generated from this relaying info to pay for the relay. I'm not keen on
>that happening automatically with no user consent or awareness.
>
>But I don't get how this will work for enterprise deployments - It's just
>very unclear how the JS would end with the appropriate set of TURN
>servers to use. 
>
>
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email