
From ietf-secretariat@ietf.org  Fri Aug 23 12:48:34 2013
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF1C11E820A; Fri, 23 Aug 2013 12:48:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.933
X-Spam-Level: 
X-Spam-Status: No, score=-103.933 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2gn+ZOQC-8L; Fri, 23 Aug 2013 12:48:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0FCE21F9C83; Fri, 23 Aug 2013 12:48:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: ted.ietf@gmail.com, fluffy@cisco.com, magnus.westerlund@ericsson.com, pntaw@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130823194820.25946.44920.idtracker@ietfa.amsl.com>
Date: Fri, 23 Aug 2013 12:48:20 -0700
Subject: [pntaw] New Non-WG Mailing List: pntaw -- Discussion list for practices	related to proxies, NATs, TURN, and WebRTC
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 19:48:34 -0000

A new IETF non-working group email list has been created.

List address: pntaw@ietf.org
Archive: http://www.ietf.org/mail-archive/web/pntaw/
To subscribe: https://www.ietf.org/mailman/listinfo/pntaw

Purpose: This mailing list will discuss how webrtc clients, proxies, NATs a=
nd TURN servers interact.

For additional information, please contact the list administrators.

From harald@alvestrand.no  Thu Aug 29 04:09:27 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D4DF21F9BF3 for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 04:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.533
X-Spam-Level: 
X-Spam-Status: No, score=-110.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FmO4Gu90CZXX for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 04:09:22 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 1C10121F9C16 for <pntaw@ietf.org>; Thu, 29 Aug 2013 04:09:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id E0F7D39E469 for <pntaw@ietf.org>; Thu, 29 Aug 2013 13:09:20 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IMdHlYXm9DpQ for <pntaw@ietf.org>; Thu, 29 Aug 2013 13:09:20 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:b467:e401:c859:de4e] (unknown [IPv6:2001:470:de0a:27:b467:e401:c859:de4e]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 5621839E03B for <pntaw@ietf.org>; Thu, 29 Aug 2013 13:09:20 +0200 (CEST)
Message-ID: <521F2C1D.30908@alvestrand.no>
Date: Thu, 29 Aug 2013 13:10:21 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: pntaw@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [pntaw] First message - request for description
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 11:09:27 -0000

I see that so far, no messages have been sent to the list.
I would like to request that the RTCWEB chairs, who are the admins of 
this list, send a message where they describe:

- What do they see as in-scope topics for this list?
- What do they see as out-of-scope topics for this list?
- What conclusions, if any, do they wish the list to draw?
- On what timescale do they expect those conclusions to be drawn?

In particular, I'd like to know if the perennial discussion of SIP 
proxies that snoop on SDP message bodies as they go by and use that 
information to open/shut ports on associated media-plane firewalls is 
inside or outside the scope of this mailing list.

               Harald


From magnus.westerlund@ericsson.com  Thu Aug 29 23:07:36 2013
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B224521F9FAD for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 23:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.682
X-Spam-Level: 
X-Spam-Status: No, score=-105.682 tagged_above=-999 required=5 tests=[AWL=0.567, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a6NNp00GY0DO for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 23:07:22 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id C03D421F9F40 for <pntaw@ietf.org>; Thu, 29 Aug 2013 23:07:21 -0700 (PDT)
X-AuditID: c1b4fb30-b7f9a8e000005620-23-52203693f4b1
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 7A.EE.22048.39630225; Fri, 30 Aug 2013 08:07:15 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.19) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.2.328.9; Fri, 30 Aug 2013 08:07:12 +0200
Message-ID: <522036AF.4070103@ericsson.com>
Date: Fri, 30 Aug 2013 08:07:43 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: <pntaw@ietf.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrEJMWRmVeSWpSXmKPExsUyM+Jvje5kM4Ugg9sPrS1+/DnM4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujD2z9rAVrOCouPcmsIHxNlsXIyeHhICJxI+FM5kgbDGJC/fW A8W5OIQEDjNKfPrwgwnCWcYoMWHzXbAqXgFtiYuTz7OC2CwCqhIL901jBrHZBCwkbv5oBJsq KhAs0b79KxtEvaDEyZlPWEBsEQERiWkL+xlBbGEBJYllJ24yQ2yWlNi26Bg7iM0soCcx5WoL I4QtL7H97RywGiGgvQ1NHawTGPlnIRk7C0nLLCQtCxiZVzGy5yZm5qSXm29iBIbTwS2/DXYw brovdohRmoNFSZx3s96ZQCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2M+29GzGusYBDWdJpp 7izTHfrnR9WHM82+K8/8uCu9tGiq06rJlq+8Tlfc3GwgF2doJWrLoJN29mqbkvuMEn2zUv5T fBMdbwusinv0Vs2+TI3f6vKnZXGz95bt597Dx/lGdZlOe9DLmT1n8pdk/q8u5D3Y4JvSXbXJ gflw/p01L9d2qMvdYMpVYinOSDTUYi4qTgQABTzQzvUBAAA=
Subject: [pntaw] Purpose of the PNTAW list
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 06:07:36 -0000

Howdy,

The RTCWEB chairs requested this list because we believe that there are
a set of webrtc-related proposals for proxy, firewall, and turn server
behavior which have implications beyond the scope of the RTCWEB work.
In order to get security folk, proxy people, and turn server clueful
folks to participate, we felt a focused list would be useful.  While
RTCWEB is currently quiet, it occasionally creates message load that
would deter their participation in the main list.

We think documents which primarily focus on the behavior of (or propose
changes to the behavior of) proxies, firewalls, or TURN servers should
get discussed here.  We are still gathering participants for that
discussion, so we hope to kick it off mid-next week.

This list will not, however, lead to a separate working group.  Our aim
is for work here to get review and then assignment to an existing
working group.  Sometimes that will be RTCWEB; sometimes it will be
other groups.

Hope that clarifies things.

Magnus Westerlund
Ted Hardie
Cullen Jennings


From melinda.shore@gmail.com  Thu Aug 29 23:16:44 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E98C21E8093 for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 23:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level: 
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id phCUBT6tTNFF for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 23:16:43 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id C740321E805A for <pntaw@ietf.org>; Thu, 29 Aug 2013 23:16:43 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb10so1887749pad.23 for <pntaw@ietf.org>; Thu, 29 Aug 2013 23:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ICaf85yeqBkUoGNbl/uVekJBibTQLxyRgx5TOiI371o=; b=xdhpssxdyCz6fAXTP3vWGx47/zkpkox0qnWhP0/t72KtGjy2zbRPKPYxuHZ9r7Pz6G /vMvQyRpPgJ6VzUEzXDfF+5TEhJwy13TtMSOtMyNEkoqv+kNWimdFGyHEhm7+HVglN2n CvbEK3KYjQJGPX8IvcZPLDPsZ1Xjo9Uw8CbtFA2XeSYVhyj0vRvf+tl4Dw1xQPYgSmgk DQJXQqIYYP40Eguv1FPnwrpWyeWnpzUVpXOrsbSFUpv9KDZBAdSdMRr2E4S2+4iDdwOG jnCD834d6xaoC2n1rpcAviInRrMwmwWO3Y+J/823iCjvZ03MRRdTwL6SQHPOA4b3JhcA sf7A==
X-Received: by 10.68.254.138 with SMTP id ai10mr7969451pbd.151.1377843403543;  Thu, 29 Aug 2013 23:16:43 -0700 (PDT)
Received: from spandex.local (209-193-56-207-rb1.fai.dsl.dynamic.acsalaska.net. [209.193.56.207]) by mx.google.com with ESMTPSA id ys4sm42250482pbb.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 29 Aug 2013 23:16:42 -0700 (PDT)
Message-ID: <522038BD.9070603@gmail.com>
Date: Thu, 29 Aug 2013 22:16:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <522036AF.4070103@ericsson.com>
In-Reply-To: <522036AF.4070103@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: pntaw@ietf.org
Subject: Re: [pntaw] Purpose of the PNTAW list
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 06:16:44 -0000

On 8/29/13 10:07 PM, Magnus Westerlund wrote:
> This list will not, however, lead to a separate working group.  Our aim
> is for work here to get review and then assignment to an existing
> working group.  Sometimes that will be RTCWEB; sometimes it will be
> other groups.

Is the intent to limit this to RAI-related concerns?

Melinda



From magnus.westerlund@ericsson.com  Thu Aug 29 23:27:29 2013
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2789C21E809C for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 23:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.907
X-Spam-Level: 
X-Spam-Status: No, score=-103.907 tagged_above=-999 required=5 tests=[AWL=-1.308, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vpa9l4ta2pyF for <pntaw@ietfa.amsl.com>; Thu, 29 Aug 2013 23:27:23 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 70B2A21E808C for <pntaw@ietf.org>; Thu, 29 Aug 2013 23:27:21 -0700 (PDT)
X-AuditID: c1b4fb38-b7fcf8e0000062b8-3b-52203b4843ab
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 83.52.25272.84B30225; Fri, 30 Aug 2013 08:27:21 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.148) by smtp.internal.ericsson.com (153.88.183.77) with Microsoft SMTP Server id 14.2.328.9; Fri, 30 Aug 2013 08:27:20 +0200
Message-ID: <52203B67.2010002@ericsson.com>
Date: Fri, 30 Aug 2013 08:27:51 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
References: <522036AF.4070103@ericsson.com> <522038BD.9070603@gmail.com>
In-Reply-To: <522038BD.9070603@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyM+Jvja6ntUKQwZ4lHBZtbbNYLH78Oczi wOSxc9Zddo8lS34yBTBFcdmkpOZklqUW6dslcGVMP9rKWNDJWbHr9Wr2BsYN7F2MnBwSAiYS 97s3MEHYYhIX7q1n62Lk4hASOMoocaRnMguEs5xRYu3HnWBVvALaEv+3vGYGsVkEVCUe/PrO CmKzCVhI3PzRyAZiiwoES7Rv/8oGUS8ocXLmExYQWwSod/vdBjCbWUBE4tnJjWC2sICexL69 e8BmCgl4SOw93QvUy8HBKaApcehHFsRxkhLbFh1jh2jVk5hytYURwpaXaN46G6pVW6KhqYN1 AqPQLCSbZyFpmYWkZQEj8ypGjuLU4qTcdCODTYzAYD245bfFDsbLf20OMUpzsCiJ827ROxMo JJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgfFur8J7530eRxqCtTgMWW8Z1/oyH/BwWilt0Kp8 dC9TN8MOc5NAo8NqLz0epOZ6fq7Zu+mpyy+td2Ubjx3vUODfs7Jt2dPLP20Oz1m6NEy6r2i1 WVys2IYZ/89POraiO2zLWqdFJx89euw1hyPImdnqy5m/RUlfA7XOVjyKzPVr6ntg02CQlqvE UpyRaKjFXFScCAB8BY1pJAIAAA==
Cc: pntaw@ietf.org
Subject: Re: [pntaw] Purpose of the PNTAW list
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 06:27:29 -0000

On 2013-08-30 08:16, Melinda Shore wrote:
> On 8/29/13 10:07 PM, Magnus Westerlund wrote:
>> This list will not, however, lead to a separate working group.  Our aim
>> is for work here to get review and then assignment to an existing
>> working group.  Sometimes that will be RTCWEB; sometimes it will be
>> other groups.
> 
> Is the intent to limit this to RAI-related concerns?
> 

No, definitely not regarding concerns or issues. As a RTCWEB WG chair I
clearly want benefit for the work in my WG. However, this is a separate
list for the reason to explore also others needs in the area of NAT/FW
traversal and allow for synergies or expose contradictory requirements.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From sergio.garcia.murillo@gmail.com  Fri Aug 30 01:42:11 2013
Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 889D411E80F2 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 01:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zj-ev6dZ2fh7 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 01:42:11 -0700 (PDT)
Received: from mail-ee0-x22d.google.com (mail-ee0-x22d.google.com [IPv6:2a00:1450:4013:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id B4D0211E80EA for <pntaw@ietf.org>; Fri, 30 Aug 2013 01:42:10 -0700 (PDT)
Received: by mail-ee0-f45.google.com with SMTP id c50so756328eek.32 for <pntaw@ietf.org>; Fri, 30 Aug 2013 01:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=z6DwjBjiu6lL2dyuUsj4Ex9UtnRfuPKyAe/dv5l1POY=; b=v67+iDRbpvsJ1O6WmEkR0C1X333KDYWXBEkmCBamA60jRMVXU9nsRusRykfzYwCxRE bBeNuprMDusnvEw8EEuS/AjvX0TMMnRhsGziS48KKwmmNiaLhMF60LQRT89argMTiOol 9nWzcTmggyp0SkvZIzDOqLtAjAr7arlePTvHEoqDh8eP3k6q50DRXCJAycv81QQY12s5 5kZ3CqIbUEdSSR3pu86UKiPnjIt6DkTrNJo0w5EYJ3hevwB8actxKNc1i7XovwzEAJOl aOLTgdLrKqnOCQBxJR6daTQKuqzNsPSGwBGnadrWR/4pZtGdCiI7O9/DM7pz5UtnM6ri oD9w==
X-Received: by 10.15.26.7 with SMTP id m7mr1791203eeu.56.1377852128633; Fri, 30 Aug 2013 01:42:08 -0700 (PDT)
Received: from [192.168.1.45] (141.Red-83-50-134.dynamicIP.rima-tde.net. [83.50.134.141]) by mx.google.com with ESMTPSA id b45sm52753985eef.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 Aug 2013 01:42:07 -0700 (PDT)
Message-ID: <52205AE1.9010807@gmail.com>
Date: Fri, 30 Aug 2013 10:42:09 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: pntaw@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 08:42:11 -0000

Hi all,

I will shoot first.

It is great to finally see some real interest in what I consider to be 
the blocking point for webrtc in order to run business on top of it, 
which is the ability to be able to connect through corporate firewalls.

I have seen some people arguing that with just TURN over TCP on port 443 
the problem will be solved, but I seriously doubt it. Neither TURN over 
SSL would do, as most web filters do DPI and will not enable the 
connection. Also, I have heard lots of voices that says we are trying to 
override network admin policies with dirty tricks. With whom, I could agree.

So, the only way I see to move forward and overcome this issues is by 
playing according to the WEB rules, and use HTTP standards to enable 
media connectivity in WebRTC that would play nicely with current 
corporate HTTP proxies and web filters.

And,  for me the most viable solution would be to enable TURN over 
websockets. As most WebRTC services relay on websockets in one way or 
another for signaling, we could assume that media would work on 100% of 
the cases where signaling is working today.
Also, as it is an http based solution, network administrators could 
apply corporate policies and block connections to not-trusted TURN servers.

Best regards
Sergio

From victor.pascual.avila@gmail.com  Fri Aug 30 03:12:14 2013
Return-Path: <victor.pascual.avila@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6622521E80A3 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 03:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Jlxsq8x0R9U for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 03:12:14 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id AFA0521E809C for <pntaw@ietf.org>; Fri, 30 Aug 2013 03:12:12 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id x18so1698767lbi.17 for <pntaw@ietf.org>; Fri, 30 Aug 2013 03:12:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Jks3NfnacfFtTvk/X7oi4dUI3XSQDhhSFRdEeyyNLtM=; b=lh819jD8cs0WiAV9AciBAtDk4TEyV+6dmtGLZEjjBPnj6wkk0gJ6A8vBc6dG192zUJ ErrTnq2OFa2QgRrqgDGrDyIpQd1kllU4w4Fvb1POY8PT321rg/9KOC87PJf8H9SO3ZqM OelH+zlTIMmFNp8S1/awuHqFtUS6g1pjum+M3kyjYhu0y3cYH9d0rV3Kym/5jE4oDBjN VpDTzzUGiy53g3XUevXNUn0Et/x84np4r81ymW5Oz23CB31pFSoeYMf2BN1zGv0zxcz8 6OeJ40JfwtE3ODfKqPGDb7o+K61MqgfQHiuUKdc1zUM9G1ysNdpiiluC4vfaTvQzE1b6 ooaw==
MIME-Version: 1.0
X-Received: by 10.112.167.3 with SMTP id zk3mr7283668lbb.23.1377857531027; Fri, 30 Aug 2013 03:12:11 -0700 (PDT)
Received: by 10.114.68.135 with HTTP; Fri, 30 Aug 2013 03:12:10 -0700 (PDT)
Date: Fri, 30 Aug 2013 12:12:10 +0200
Message-ID: <CAGTXFp92jSzQz05uHngzscz88n=fT_JPbEvQRxgeUUqPVRQUyQ@mail.gmail.com>
From: Victor Pascual Avila <victor.pascual.avila@gmail.com>
To: pntaw@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [pntaw] Real-time media over TCP
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 10:12:14 -0000

Hi,

Real-time media over TCP has some inherent challenges -- is this
something we're planning to discuss here? We did RTP over TCP (+ HTTP
CONNECT) in the past and ended up using multiple connections along
with application-layer redundancy. I'm wondering whether we'll be able
to do the same when moving to WebRTC

Thanks,
-Victor

From lorenzo@meetecho.com  Fri Aug 30 04:45:57 2013
Return-Path: <lorenzo@meetecho.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0939F21F9B07 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 04:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id siUYu0DZ-I22 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 04:45:52 -0700 (PDT)
Received: from smtpdg5.aruba.it (smtpdg223.aruba.it [62.149.158.223]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF6421F9A6C for <pntaw@ietf.org>; Fri, 30 Aug 2013 04:45:39 -0700 (PDT)
Received: from rainpc ([95.247.154.154]) by smtpcmd02.ad.aruba.it with bizsmtp id JzlW1m00q3L8Z5b01zlWtc; Fri, 30 Aug 2013 13:45:32 +0200
Date: Fri, 30 Aug 2013 13:45:31 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <20130830134531.787fda3c@rainpc>
In-Reply-To: <52205AE1.9010807@gmail.com>
References: <52205AE1.9010807@gmail.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.19; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: pntaw@ietf.org
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 11:45:57 -0000

On Fri, 30 Aug 2013 10:42:09 +0200
Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> wrote:

> Hi all,
> 
> I will shoot first.
> 
> It is great to finally see some real interest in what I consider to be 
> the blocking point for webrtc in order to run business on top of it, 
> which is the ability to be able to connect through corporate firewalls.
> 
> I have seen some people arguing that with just TURN over TCP on port 443 
> the problem will be solved, but I seriously doubt it. Neither TURN over 
> SSL would do, as most web filters do DPI and will not enable the 
> connection. Also, I have heard lots of voices that says we are trying to 
> override network admin policies with dirty tricks. With whom, I could agree.
> 


That's the main objection I got when I published the (now expired) draft I published a year ago to throw the proverbial "stone in the lake" about an HTTP fallback solution. As I said at the time, I agree with you that the solution doesn't have to be sneaky, and that it could very well be conceived to be network admin-friendly/controllable.


> So, the only way I see to move forward and overcome this issues is by 
> playing according to the WEB rules, and use HTTP standards to enable 
> media connectivity in WebRTC that would play nicely with current 
> corporate HTTP proxies and web filters.
> 
> And,  for me the most viable solution would be to enable TURN over 
> websockets. As most WebRTC services relay on websockets in one way or 
> another for signaling, we could assume that media would work on 100% of 
> the cases where signaling is working today.
> Also, as it is an http based solution, network administrators could 
> apply corporate policies and block connections to not-trusted TURN servers.
> 
> Best regards
> Sergio


I'm not an expert in websockets, which is why in my rough proposal I described a way to do this using plain HTTP, but I guess they'd be good for the purpose as well. The only doubt I have is that, as far as I know, not always websockets are able to traverse some more restrictive components: the popular BitDefender firewall, for instance, apparently doesn't let it through.

Anyway, I'd personally support a work in that direction, and would be willing to help working on it too if needed.

Lorenzo

> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


-- 
Lorenzo Miniero, COB

Meetecho s.r.l.
Web Conferencing and Collaboration Tools
http://www.meetecho.com

From sergio.garcia.murillo@gmail.com  Fri Aug 30 04:55:45 2013
Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B46D21F938E for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 04:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXqmWLiQko5m for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 04:55:36 -0700 (PDT)
Received: from mail-ea0-x22f.google.com (mail-ea0-x22f.google.com [IPv6:2a00:1450:4013:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 2633321F91C9 for <pntaw@ietf.org>; Fri, 30 Aug 2013 04:55:34 -0700 (PDT)
Received: by mail-ea0-f175.google.com with SMTP id m14so852743eaj.6 for <pntaw@ietf.org>; Fri, 30 Aug 2013 04:55:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=tKj+BJusKvPMgGTZYcDqa7KkkFqgoDYXHRaRMnHWOwU=; b=qWYewSnTfildYglz/0S7OBekWLzQVEPNCg33GZ3GeTeBbMpjRrgZ4pUV9Sje7JIZmk ctTdgiF7bVN33k0CHw+A/bwFhsoQo3aUcad9S5qcQE1emtg7gCnIRG8j7SOFIFj00bfc BMlZcRLKL0bMf0H3WTOKJx9yOiyFf1aCYjN2WKq/SnK/ennk9LLhu/VyABV2X8sBtGRY lcBTEvPzTb0mR1rHUyk0Uq/Dubsv84KRSYMOsW34uVqCpS9T9P27ANhkOHAL7hpxuNt0 Z/5NKzztmVKj/rC6dImEyNfJb1vq7Pua/qYoU3+8rNPkuFpqXtSDRA+1enjUMMu0k//k uv9w==
X-Received: by 10.14.0.201 with SMTP id 49mr351406eeb.85.1377863733720; Fri, 30 Aug 2013 04:55:33 -0700 (PDT)
Received: from [192.168.1.45] (141.Red-83-50-134.dynamicIP.rima-tde.net. [83.50.134.141]) by mx.google.com with ESMTPSA id a43sm54112463eep.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 Aug 2013 04:55:32 -0700 (PDT)
Message-ID: <52208836.6050402@gmail.com>
Date: Fri, 30 Aug 2013 13:55:34 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Lorenzo Miniero <lorenzo@meetecho.com>
References: <52205AE1.9010807@gmail.com> <20130830134531.787fda3c@rainpc>
In-Reply-To: <20130830134531.787fda3c@rainpc>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: pntaw@ietf.org
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 11:55:45 -0000

El 30/08/2013 13:45, Lorenzo Miniero escribió:
>
> [..]
>
> I'm not an expert in websockets, which is why in my rough proposal I described a way to do this using plain HTTP, but I guess they'd be good for the purpose as well. The only doubt I have is that, as far as I know, not always websockets are able to traverse some more restrictive components: the popular BitDefender firewall, for instance, apparently doesn't let it through.

 From what I have seen, most people using webrtc are doing the signaling 
via websocket, either using SIP over websockets, or any other custom 
protocol. So, if websockets are not supported, you already have a 
problem as you will not be able to set up the SDP O/A negotiation in the 
first place.

> Anyway, I'd personally support a work in that direction, and would be willing to help working on it too if needed.

Thank you very much Lorenzo, anyone else on board?

Best regards
Sergio

From spromano@unina.it  Fri Aug 30 04:59:05 2013
Return-Path: <spromano@unina.it>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F20A721E80C0 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 04:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CWxMtrIWox3u for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 04:59:01 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 286BA21E80BC for <pntaw@ietf.org>; Fri, 30 Aug 2013 04:59:00 -0700 (PDT)
Received: from u665211.xgsnuf61.imtp.tachikawa.mopera.net ([91.255.122.61]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id r7UBwrUT023511 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 30 Aug 2013 13:58:55 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <20130830134531.787fda3c@rainpc>
References: <52205AE1.9010807@gmail.com> <20130830134531.787fda3c@rainpc>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----1TKWKUFRJRG39M91A2H0KLWXT9VEIR"
From: Simon Pietro Romano <spromano@unina.it>
Date: Fri, 30 Aug 2013 13:58:50 +0200
To: Lorenzo Miniero <lorenzo@meetecho.com>, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <73abe274-acc2-4e37-847c-a660bbd2859c@email.android.com>
Cc: pntaw@ietf.org
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 11:59:06 -0000

------1TKWKUFRJRG39M91A2H0KLWXT9VEIR
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

+1 to the plain HTTP fallback solution proposed by Lorenzo a while ago.

Simon

Lorenzo Miniero <lorenzo@meetecho.com> ha scritto:
>On Fri, 30 Aug 2013 10:42:09 +0200
>Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> wrote:
>
>> Hi all,
>> 
>> I will shoot first.
>> 
>> It is great to finally see some real interest in what I consider to
>be 
>> the blocking point for webrtc in order to run business on top of it, 
>> which is the ability to be able to connect through corporate
>firewalls.
>> 
>> I have seen some people arguing that with just TURN over TCP on port
>443 
>> the problem will be solved, but I seriously doubt it. Neither TURN
>over 
>> SSL would do, as most web filters do DPI and will not enable the 
>> connection. Also, I have heard lots of voices that says we are trying
>to 
>> override network admin policies with dirty tricks. With whom, I could
>agree.
>> 
>
>
>That's the main objection I got when I published the (now expired)
>draft I published a year ago to throw the proverbial "stone in the
>lake" about an HTTP fallback solution. As I said at the time, I agree
>with you that the solution doesn't have to be sneaky, and that it could
>very well be conceived to be network admin-friendly/controllable.
>
>
>> So, the only way I see to move forward and overcome this issues is by
>
>> playing according to the WEB rules, and use HTTP standards to enable 
>> media connectivity in WebRTC that would play nicely with current 
>> corporate HTTP proxies and web filters.
>> 
>> And,  for me the most viable solution would be to enable TURN over 
>> websockets. As most WebRTC services relay on websockets in one way or
>
>> another for signaling, we could assume that media would work on 100%
>of 
>> the cases where signaling is working today.
>> Also, as it is an http based solution, network administrators could 
>> apply corporate policies and block connections to not-trusted TURN
>servers.
>> 
>> Best regards
>> Sergio
>
>
>I'm not an expert in websockets, which is why in my rough proposal I
>described a way to do this using plain HTTP, but I guess they'd be good
>for the purpose as well. The only doubt I have is that, as far as I
>know, not always websockets are able to traverse some more restrictive
>components: the popular BitDefender firewall, for instance, apparently
>doesn't let it through.
>
>Anyway, I'd personally support a work in that direction, and would be
>willing to help working on it too if needed.
>
>Lorenzo
>
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
>
>
>-- 
>Lorenzo Miniero, COB
>
>Meetecho s.r.l.
>Web Conferencing and Collaboration Tools
>http://www.meetecho.com
>_______________________________________________
>pntaw mailing list
>pntaw@ietf.org
>https://www.ietf.org/mailman/listinfo/pntaw

------1TKWKUFRJRG39M91A2H0KLWXT9VEIR
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head></head><body>+1 to the plain HTTP fallback solution proposed by Lorenzo a while ago.<br>
<br>
Simon<br><br><div class="gmail_quote">Lorenzo Miniero &lt;lorenzo@meetecho.com&gt; ha scritto:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Fri, 30 Aug 2013 10:42:09 +0200<br />Sergio Garcia Murillo &lt;sergio.garcia.murillo@gmail.com&gt; wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Hi all,<br /><br />I will shoot first.<br /><br />It is great to finally see some real interest in what I consider to be <br />the blocking point for webrtc in order to run business on top of it, <br />which is the ability to be able to connect through corporate firewalls.<br /><br />I have seen some people arguing that with just TURN over TCP on port 443 <br />the problem will be solved, but I seriously doubt it. Neither TURN over <br />SSL would do, as most web filters do DPI and will not enable the <br />connection. Also, I have heard lots of voices that says we are trying to <br />override network admin policies with dirty tricks. With whom, I could agree.</blockquote><br /><br /><br />That's the main objection I got !
 when I
published the (now expired) draft I published a year ago to throw the proverbial "stone in the lake" about an HTTP fallback solution. As I said at the time, I agree with you that the solution doesn't have to be sneaky, and that it could very well be conceived to be network admin-friendly/controllable.<br /><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">So, the only way I see to move forward and overcome this issues is by <br />playing according to the WEB rules, and use HTTP standards to enable <br />media connectivity in WebRTC that would play nicely with current <br />corporate HTTP proxies and web filters.<br /><br />And,  for me the most viable solution would be to enable TURN over <br />websockets. As most WebRTC services relay on websockets in one way or <br />another for signaling, we could assume that media would work on 100% of <br />the cases where signaling is working today.<br />Al!
 so, as
it is an http based solution, network administrators could <br />apply corporate policies and block connections to not-trusted TURN servers.<br /><br />Best regards<br />Sergio</blockquote><br /><br />I'm not an expert in websockets, which is why in my rough proposal I described a way to do this using plain HTTP, but I guess they'd be good for the purpose as well. The only doubt I have is that, as far as I know, not always websockets are able to traverse some more restrictive components: the popular BitDefender firewall, for instance, apparently doesn't let it through.<br /><br />Anyway, I'd personally support a work in that direction, and would be willing to help working on it too if needed.<br /><br />Lorenzo<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><hr /><br />pntaw mailing list<br />pntaw@ietf.org<br /><a
href="https://www.ietf.org/mailman/listinfo/pntaw">https://www.ietf.org/mailman/listinfo/pntaw</a></blockquote><br /></pre></blockquote></div></body></html>
------1TKWKUFRJRG39M91A2H0KLWXT9VEIR--


From thomas.stach@siemens-enterprise.com  Fri Aug 30 05:40:22 2013
Return-Path: <thomas.stach@siemens-enterprise.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF4F521F909A for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 224YsfYV+YDi for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:40:18 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 63F2C21F88A9 for <pntaw@ietf.org>; Fri, 30 Aug 2013 05:35:04 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 64ECE1EB8597; Fri, 30 Aug 2013 14:34:57 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.174]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Fri, 30 Aug 2013 14:34:57 +0200
From: "Stach, Thomas" <thomas.stach@siemens-enterprise.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpVzeSFPe8Kl+LUCjnsamYIV4h5mtqQnw
Date: Fri, 30 Aug 2013 12:34:56 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net>
References: <52205AE1.9010807@gmail.com>
In-Reply-To: <52205AE1.9010807@gmail.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 12:40:23 -0000

Sergio,

Some comments inline

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Sergio Garcia Murillo
> Sent: Freitag, 30. August 2013 10:42
> To: pntaw@ietf.org
> Subject: [pntaw] TURN over websockets
>=20
> Hi all,
>=20
> I will shoot first.
>=20
> It is great to finally see some real interest in what I consider to be
> the blocking point for webrtc in order to run business on top of it,
> which is the ability to be able to connect through corporate firewalls.
>=20
> I have seen some people arguing that with just TURN over TCP on port
> 443
> the problem will be solved, but I seriously doubt it. Neither TURN over
> SSL would do, as most web filters do DPI and will not enable the
> connection. Also, I have heard lots of voices that says we are trying
> to
> override network admin policies with dirty tricks. With whom, I could
> agree.
[TS] I'm not sure if you are referencing draft-hutton-rtcweb-nat-firewall-c=
onsiderations here.
Nevertheless the draft mentions TURN over TCP to port 443.=20
The goal behind this is certainly not to sneak WEBRTC media streams through=
 heavily fortified networks that have DPI deployed.
The goal rather to address a scenario e.g. at a small hotel with a not-so-s=
killed network admin, that opened his firewall on TCP port 80/443 to allow =
its guests to do some web browsing, but is afraid of opening its firewall f=
or UDP traffic.
If we want to deploy WEBRTC in such an environment TURN over TLS to port 44=
3 would do the job.=20

>=20
> So, the only way I see to move forward and overcome this issues is by
> playing according to the WEB rules, and use HTTP standards to enable
> media connectivity in WebRTC that would play nicely with current
> corporate HTTP proxies and web filters.
[TS] Playing nicely with HTTP proxies is also a use case draft-hutton-rtcwe=
b-nat-firewall-considerations.
Usage of the HTTP CONNECT method is proposed here. The request URI would in=
clude the TURN server (preferably even to the well-known STUN port). If the=
 network admin put the TURN server into its whitelist, that could hardly be=
 considered as sneaking unwanted traffic through.
>=20
> And,  for me the most viable solution would be to enable TURN over
> websockets.=20
[TS] This would require updates to the TURN protocol and the TURN software,=
 whereas the proposals in draft-hutton-rtcweb-nat-firewall-considerations u=
se the original transports.
As most WebRTC services relay on websockets in one way or
> another for signaling, we could assume that media would work on 100% of
> the cases where signaling is working today.
> Also, as it is an http based solution, network administrators could
> apply corporate policies and block connections to not-trusted TURN
> servers.
[TS] which could also be done by white-listing the TURN server address via =
TCP without any further intermediate HTTP/Websocket layers.

Regards=20
Thomas

>=20
> Best regards
> Sergio
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From Markus.Isomaki@nokia.com  Fri Aug 30 05:53:04 2013
Return-Path: <Markus.Isomaki@nokia.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C2E21F9EBE for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pKCX+sUt5Og4 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:52:59 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id B0C0E21F9EDA for <pntaw@ietf.org>; Fri, 30 Aug 2013 05:52:58 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.49]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r7UCqs5E032418 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 30 Aug 2013 15:52:55 +0300
Received: from 008-AM1MPN1-041.mgdnok.nokia.com ([169.254.1.88]) by 008-AM1MMR2-015.mgdnok.nokia.com ([65.54.30.49]) with mapi id 14.03.0136.001; Fri, 30 Aug 2013 12:52:53 +0000
From: <Markus.Isomaki@nokia.com>
To: <thomas.stach@siemens-enterprise.com>, <sergio.garcia.murillo@gmail.com>,  <pntaw@ietf.org>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpVzYQo/k4hTeV0+AGm8aLH5XBJmtr/AAgAACHhA=
Date: Fri, 30 Aug 2013 12:52:53 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A092563@008-AM1MPN1-041.mgdnok.nokia.com>
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net>
In-Reply-To: <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IgC3RfpT360Wbh6Q8tif6x4XQRPwZRviPCUbwaw11cFKjbsScP07csiUIg9YWTUGorTrZaXDcR82/ckJ5rb+gt5KN9lpBV6pcDddCrfH8vucFLFBIJnhkWFrLXKKGAKakNRTDj7fp/mIdB8APRupHn+bMrFWHhyRKzr7qfMMbpA4sDhQPLbGqEGDe6zmGRE47HmA0bDQYJvKCD82mbvZXVlH9BTnoi1cc5TetWLF4AsJ
x-originating-ip: [172.21.80.83]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 12:53:04 -0000

Hi Sergio, Thomas,

I also assume that we should run TURN over TLS directly, or by establishing=
 that connection via a proxy using HTTP CONNECT. The first method would wor=
k in networks that allow outbound TLS/TCP connections, while the other woul=
d work even in networks that only allow outbound communication via a proxy.

As Thomas says, the benefit of TURN/TLS instead of TURN/WS/TLS is that no c=
hanges would need to be applied to existing TURN servers. Only the client s=
ide establishment (by the browser) would need to include the use of HTTP CO=
NNECT.=20

But is there some advantage why Websockets should be used? WS does have the=
 explicit HTTP based handshake, which is supposed to make it somehow middle=
box "friendlier". But I don't know how that is better than HTTP CONNECT in =
that sense.

Regards,
	Markus


> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of ext Stach, Thomas
> Sent: 30 August, 2013 15:35
> To: Sergio Garcia Murillo; pntaw@ietf.org
> Subject: Re: [pntaw] TURN over websockets
>=20
> Sergio,
>=20
> Some comments inline
>=20
> > -----Original Message-----
> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> > Of Sergio Garcia Murillo
> > Sent: Freitag, 30. August 2013 10:42
> > To: pntaw@ietf.org
> > Subject: [pntaw] TURN over websockets
> >
> > Hi all,
> >
> > I will shoot first.
> >
> > It is great to finally see some real interest in what I consider to be
> > the blocking point for webrtc in order to run business on top of it,
> > which is the ability to be able to connect through corporate firewalls.
> >
> > I have seen some people arguing that with just TURN over TCP on port
> > 443
> > the problem will be solved, but I seriously doubt it. Neither TURN
> > over SSL would do, as most web filters do DPI and will not enable the
> > connection. Also, I have heard lots of voices that says we are trying
> > to override network admin policies with dirty tricks. With whom, I
> > could agree.
> [TS] I'm not sure if you are referencing draft-hutton-rtcweb-nat-firewall=
-
> considerations here.
> Nevertheless the draft mentions TURN over TCP to port 443.
> The goal behind this is certainly not to sneak WEBRTC media streams throu=
gh
> heavily fortified networks that have DPI deployed.
> The goal rather to address a scenario e.g. at a small hotel with a not-so=
-skilled
> network admin, that opened his firewall on TCP port 80/443 to allow its
> guests to do some web browsing, but is afraid of opening its firewall for=
 UDP
> traffic.
> If we want to deploy WEBRTC in such an environment TURN over TLS to port
> 443 would do the job.
>=20
> >
> > So, the only way I see to move forward and overcome this issues is by
> > playing according to the WEB rules, and use HTTP standards to enable
> > media connectivity in WebRTC that would play nicely with current
> > corporate HTTP proxies and web filters.
> [TS] Playing nicely with HTTP proxies is also a use case draft-hutton-rtc=
web-
> nat-firewall-considerations.
> Usage of the HTTP CONNECT method is proposed here. The request URI
> would include the TURN server (preferably even to the well-known STUN
> port). If the network admin put the TURN server into its whitelist, that =
could
> hardly be considered as sneaking unwanted traffic through.
> >
> > And,  for me the most viable solution would be to enable TURN over
> > websockets.
> [TS] This would require updates to the TURN protocol and the TURN
> software, whereas the proposals in draft-hutton-rtcweb-nat-firewall-
> considerations use the original transports.
> As most WebRTC services relay on websockets in one way or
> > another for signaling, we could assume that media would work on 100%
> > of the cases where signaling is working today.
> > Also, as it is an http based solution, network administrators could
> > apply corporate policies and block connections to not-trusted TURN
> > servers.
> [TS] which could also be done by white-listing the TURN server address vi=
a
> TCP without any further intermediate HTTP/Websocket layers.
>=20
> Regards
> Thomas
>=20
> >
> > Best regards
> > Sergio
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From simon.perreault@viagenie.ca  Fri Aug 30 05:53:36 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EAF921F9EBE for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.34
X-Spam-Level: 
X-Spam-Status: No, score=-2.34 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ka8JHWeaaM8c for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:53:32 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2023421F9DF3 for <pntaw@ietf.org>; Fri, 30 Aug 2013 05:53:32 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:804a:3155:d42a:4a6]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 838DF4042A for <pntaw@ietf.org>; Fri, 30 Aug 2013 08:53:30 -0400 (EDT)
Message-ID: <522095CB.9030109@viagenie.ca>
Date: Fri, 30 Aug 2013 14:53:31 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: pntaw@ietf.org
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net>
In-Reply-To: <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 12:53:36 -0000

Le 2013-08-30 14:34, Stach, Thomas a écrit :
> The goal behind this is certainly not to sneak WEBRTC media streams
> through heavily fortified networks that have DPI deployed. The goal
> rather to address a scenario e.g. at a small hotel with a
> not-so-skilled network admin, that opened his firewall on TCP port
> 80/443 to allow its guests to do some web browsing, but is afraid of
> opening its firewall for UDP traffic. If we want to deploy WEBRTC in
> such an environment TURN over TLS to port 443 would do the job.

+1

I too am not convinced that we need anything more than TURN over TLS to
port 443.

Simon

From sergio.garcia.murillo@gmail.com  Fri Aug 30 05:56:47 2013
Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E7121F9F9F for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id twm45TokPBjS for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:56:46 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 34D0521F9F9D for <pntaw@ietf.org>; Fri, 30 Aug 2013 05:56:46 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id l12so1759440wiv.7 for <pntaw@ietf.org>; Fri, 30 Aug 2013 05:56:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=c/BxKQnKJ6u4uumQCGfvwa01Mi0nrwe8y5Z9kXv2OfU=; b=YgxaXijJ7uxqPIVI5tLvewEn6BYxxE1Givf7TYcNr/6mh3WKAGrvDydxXfgp1YieE0 MfDElg47FB3NP6gMNKuxb0x+XT7s+W7X1+LiZuVlpgoztbRKNY1Hk7tiwwo/gaD3W4W7 v8LXblQf2Ta9uHXIyESjNTb5Hcii3qqgbDSy86nyxv7KtJAluqbuYzKf6feNyKB0sEda P6aPZIfx5ySBzAM6rFt9EbnM+Wj2HG6PsHhwb/Ad8JDpe/5AN4olMCbMj37P4kFhljkc X3GHEn5NANMHHEVcpCCXkT+A4BjOY/d6dsH9aD/hkclTpQ8c+0+0WfLkqzLnUmRfWoqz XSKQ==
X-Received: by 10.194.24.168 with SMTP id v8mr10946331wjf.28.1377867404814; Fri, 30 Aug 2013 05:56:44 -0700 (PDT)
Received: from [192.168.1.45] (141.Red-83-50-134.dynamicIP.rima-tde.net. [83.50.134.141]) by mx.google.com with ESMTPSA id i3sm4057164wiw.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 Aug 2013 05:56:44 -0700 (PDT)
Message-ID: <5220968E.2050708@gmail.com>
Date: Fri, 30 Aug 2013 14:56:46 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Stach, Thomas" <thomas.stach@siemens-enterprise.com>
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net>
In-Reply-To: <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 12:56:47 -0000

Hi Thomas,

Inline.

El 30/08/2013 14:34, Stach, Thomas escribió:
> Sergio,
>
> Some comments inline
>
>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
>> Of Sergio Garcia Murillo
>> Sent: Freitag, 30. August 2013 10:42
>> To: pntaw@ietf.org
>> Subject: [pntaw] TURN over websockets
>>
>> Hi all,
>>
>> I will shoot first.
>>
>> It is great to finally see some real interest in what I consider to be
>> the blocking point for webrtc in order to run business on top of it,
>> which is the ability to be able to connect through corporate firewalls.
>>
>> I have seen some people arguing that with just TURN over TCP on port
>> 443
>> the problem will be solved, but I seriously doubt it. Neither TURN over
>> SSL would do, as most web filters do DPI and will not enable the
>> connection. Also, I have heard lots of voices that says we are trying
>> to
>> override network admin policies with dirty tricks. With whom, I could
>> agree.
> [TS] I'm not sure if you are referencing draft-hutton-rtcweb-nat-firewall-considerations here.
> Nevertheless the draft mentions TURN over TCP to port 443.
And also does mention TURN over websockets, while it consider it to be 
not necessary.
> The goal behind this is certainly not to sneak WEBRTC media streams through heavily fortified networks that have DPI deployed.
> The goal rather to address a scenario e.g. at a small hotel with a not-so-skilled network admin, that opened his firewall on TCP port 80/443 to allow its guests to do some web browsing, but is afraid of opening its firewall for UDP traffic.
> If we want to deploy WEBRTC in such an environment TURN over TLS to port 443 would do the job.

Maybe that is your scenario, definitively not mine. Try doing some 
serious business with banking, insurance or such kind of sector and you 
won't find no-so-skilled admin but a full flavor DPI web filter in 
place. Then try to go to their admin it department and ask them to do 
some funny configuration on their firewalls.

I really doubt that TURN over TLS would work in 100% of this scenarios.


>> So, the only way I see to move forward and overcome this issues is by
>> playing according to the WEB rules, and use HTTP standards to enable
>> media connectivity in WebRTC that would play nicely with current
>> corporate HTTP proxies and web filters.
> [TS] Playing nicely with HTTP proxies is also a use case draft-hutton-rtcweb-nat-firewall-considerations.
> Usage of the HTTP CONNECT method is proposed here. The request URI would include the TURN server (preferably even to the well-known STUN port). If the network admin put the TURN server into its whitelist, that could hardly be considered as sneaking unwanted traffic through.
>> And,  for me the most viable solution would be to enable TURN over
>> websockets.
> [TS] This would require updates to the TURN protocol and the TURN software, whereas the proposals in draft-hutton-rtcweb-nat-firewall-considerations use the original transports.

Yes, it would require additions to the TURN protocol and new 
developments on TURN software.

> As most WebRTC services relay on websockets in one way or
>> another for signaling, we could assume that media would work on 100% of
>> the cases where signaling is working today.
>> Also, as it is an http based solution, network administrators could
>> apply corporate policies and block connections to not-trusted TURN
>> servers.
> [TS] which could also be done by white-listing the TURN server address via TCP without any further intermediate HTTP/Websocket layers.

Try to open a firewall in a corporate location, good luck! White listing 
in the web filter would be much more doable.

Best regards
Sergio

From Markus.Isomaki@nokia.com  Fri Aug 30 05:58:14 2013
Return-Path: <Markus.Isomaki@nokia.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A86621F9FDA for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.49
X-Spam-Level: 
X-Spam-Status: No, score=-6.49 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVY3UceexF1z for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 05:58:08 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7622A21F9F40 for <pntaw@ietf.org>; Fri, 30 Aug 2013 05:58:04 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.25]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r7UCvseD005788 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 30 Aug 2013 15:57:57 +0300
Received: from 008-AM1MPN1-041.mgdnok.nokia.com ([169.254.1.88]) by 008-AM1MMR1-009.mgdnok.nokia.com ([65.54.30.25]) with mapi id 14.03.0136.001; Fri, 30 Aug 2013 12:57:55 +0000
From: <Markus.Isomaki@nokia.com>
To: <simon.perreault@viagenie.ca>, <pntaw@ietf.org>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpVzYQo/k4hTeV0+AGm8aLH5XBJmtr/AAgAAFMYCAAAA30A==
Date: Fri, 30 Aug 2013 12:57:54 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A092593@008-AM1MPN1-041.mgdnok.nokia.com>
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <522095CB.9030109@viagenie.ca>
In-Reply-To: <522095CB.9030109@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IgC3RfpT360Wbh6Q8tif6x4XQRPwZRviPCUbwaw11cFKjbsScP07csiUIg9YWTUGorTrZaXDcR82/ckJ5rb+gt5KN9lpBV6pcDddCrfH8vucFLFBIJnhkWFrLXKKGAKakNRTDj7fp/mIdB8APRupHn+bMrFWHhyRKzr7qfMMbpA4sDhQPLbGqEGDe6zmGRE47HmA0bDQYJvKCD82mbvZXVlH9BTnoi1cc5TetWLF4AsJ
x-originating-ip: [172.21.80.83]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 12:58:14 -0000

Hi Simon,

Simon Perrault wrote:
>=20
> Le 2013-08-30 14:34, Stach, Thomas a =E9crit :
> > The goal behind this is certainly not to sneak WEBRTC media streams
> > through heavily fortified networks that have DPI deployed. The goal
> > rather to address a scenario e.g. at a small hotel with a
> > not-so-skilled network admin, that opened his firewall on TCP port
> > 80/443 to allow its guests to do some web browsing, but is afraid of
> > opening its firewall for UDP traffic. If we want to deploy WEBRTC in
> > such an environment TURN over TLS to port 443 would do the job.
>=20
> +1
>=20
> I too am not convinced that we need anything more than TURN over TLS to
> port 443.
>=20

I think we should also address networks that only allow outbound communicat=
ion via an explicit HTTP/web proxy. I use one such network daily... So it s=
hould be possible to use HTTP CONNECT to establish the TURN over TLS connec=
tion via that proxy.=20

Markus

From simon.perreault@viagenie.ca  Fri Aug 30 06:02:56 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 714C321E8095 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.383
X-Spam-Level: 
X-Spam-Status: No, score=-2.383 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQRkRKEBI2D2 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:02:56 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id DEDC821E808A for <pntaw@ietf.org>; Fri, 30 Aug 2013 06:02:55 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:804a:3155:d42a:4a6]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 491094042A for <pntaw@ietf.org>; Fri, 30 Aug 2013 09:02:55 -0400 (EDT)
Message-ID: <52209800.7050205@viagenie.ca>
Date: Fri, 30 Aug 2013 15:02:56 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: pntaw@ietf.org
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <522095CB.9030109@viagenie.ca> <E44893DD4E290745BB608EB23FDDB7620A092593@008-AM1MPN1-041.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A092593@008-AM1MPN1-041.mgdnok.nokia.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 13:02:56 -0000

Le 2013-08-30 14:57, Markus.Isomaki@nokia.com a écrit :
>> I too am not convinced that we need anything more than TURN over TLS to
>> port 443.
> 
> I think we should also address networks that only allow outbound communication via an explicit HTTP/web proxy. I use one such network daily... So it should be possible to use HTTP CONNECT to establish the TURN over TLS connection via that proxy. 

Agreed. TURN/TLS over 443 through a proxy or not, up to the client.
Servers won't see the difference.

Simon

From sergio.garcia.murillo@gmail.com  Fri Aug 30 06:04:49 2013
Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45FB121E80A3 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jE0p+mXW9eYc for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:04:48 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 69C3921E808A for <pntaw@ietf.org>; Fri, 30 Aug 2013 06:04:47 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hi5so520074wib.5 for <pntaw@ietf.org>; Fri, 30 Aug 2013 06:04:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=6R1BdHIgGER0+tE6IcrwYiElfneopJTTTQv3Oowsofs=; b=cZ2uWJs4TUm/m8yK5I1Q9O8kC6LNw8dZUaAMcqFUMVhKVdJMi9U5sQrD/hiDzKGc6b tF5l+uk/xsAocbfGRkej409yj0IOHGVXVHxxJ+GmLMXgOxkn9N7IHWzw1zA+577kkIjC N/EHCydN6gVfieFiRHcZ6us7yJNmHoDMy9eh63o04Pk7EYuIFk8Ibz+WG7/mI4Ss+RRO 8kQh2mLkaIuH8X27tQ6UiFMVDuH9WfHvbC/uCUCplLux4y6kJ838W3kY5Rbeixr3bIS2 0Q6iB9LHmhHWJX3H4udAcBTN8yyyx1mt+2hcmZIaoebPxqOJ7sV9acV23WreUh9K/mi6 VZsA==
X-Received: by 10.180.160.240 with SMTP id xn16mr2360268wib.62.1377867885406;  Fri, 30 Aug 2013 06:04:45 -0700 (PDT)
Received: from [192.168.1.45] (141.Red-83-50-134.dynamicIP.rima-tde.net. [83.50.134.141]) by mx.google.com with ESMTPSA id q5sm1058140wix.8.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 Aug 2013 06:04:44 -0700 (PDT)
Message-ID: <5220986A.1080702@gmail.com>
Date: Fri, 30 Aug 2013 15:04:42 +0200
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Markus.Isomaki@nokia.com
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <E44893DD4E290745BB608EB23FDDB7620A092563@008-AM1MPN1-041.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A092563@008-AM1MPN1-041.mgdnok.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: pntaw@ietf.org, thomas.stach@siemens-enterprise.com
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 13:04:49 -0000

Hi Markus,

I see some benefits for websockets over HTTP connect, but may be due to 
my own deployment choices, but I would be ok with it also.

One point that I see against http connect is that it is meant to be used 
as a fallback scenario, while with websockets you could use it always, 
regardless if there is any http proxy in place or not.

Best regards
Sergio

El 30/08/2013 14:52, Markus.Isomaki@nokia.com escribió:
> Hi Sergio, Thomas,
>
> I also assume that we should run TURN over TLS directly, or by establishing that connection via a proxy using HTTP CONNECT. The first method would work in networks that allow outbound TLS/TCP connections, while the other would work even in networks that only allow outbound communication via a proxy.
>
> As Thomas says, the benefit of TURN/TLS instead of TURN/WS/TLS is that no changes would need to be applied to existing TURN servers. Only the client side establishment (by the browser) would need to include the use of HTTP CONNECT.
>
> But is there some advantage why Websockets should be used? WS does have the explicit HTTP based handshake, which is supposed to make it somehow middlebox "friendlier". But I don't know how that is better than HTTP CONNECT in that sense.
>
> Regards,
> 	Markus
>
>
>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
>> Of ext Stach, Thomas
>> Sent: 30 August, 2013 15:35
>> To: Sergio Garcia Murillo; pntaw@ietf.org
>> Subject: Re: [pntaw] TURN over websockets
>>
>> Sergio,
>>
>> Some comments inline
>>
>>> -----Original Message-----
>>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
>> Behalf
>>> Of Sergio Garcia Murillo
>>> Sent: Freitag, 30. August 2013 10:42
>>> To: pntaw@ietf.org
>>> Subject: [pntaw] TURN over websockets
>>>
>>> Hi all,
>>>
>>> I will shoot first.
>>>
>>> It is great to finally see some real interest in what I consider to be
>>> the blocking point for webrtc in order to run business on top of it,
>>> which is the ability to be able to connect through corporate firewalls.
>>>
>>> I have seen some people arguing that with just TURN over TCP on port
>>> 443
>>> the problem will be solved, but I seriously doubt it. Neither TURN
>>> over SSL would do, as most web filters do DPI and will not enable the
>>> connection. Also, I have heard lots of voices that says we are trying
>>> to override network admin policies with dirty tricks. With whom, I
>>> could agree.
>> [TS] I'm not sure if you are referencing draft-hutton-rtcweb-nat-firewall-
>> considerations here.
>> Nevertheless the draft mentions TURN over TCP to port 443.
>> The goal behind this is certainly not to sneak WEBRTC media streams through
>> heavily fortified networks that have DPI deployed.
>> The goal rather to address a scenario e.g. at a small hotel with a not-so-skilled
>> network admin, that opened his firewall on TCP port 80/443 to allow its
>> guests to do some web browsing, but is afraid of opening its firewall for UDP
>> traffic.
>> If we want to deploy WEBRTC in such an environment TURN over TLS to port
>> 443 would do the job.
>>
>>> So, the only way I see to move forward and overcome this issues is by
>>> playing according to the WEB rules, and use HTTP standards to enable
>>> media connectivity in WebRTC that would play nicely with current
>>> corporate HTTP proxies and web filters.
>> [TS] Playing nicely with HTTP proxies is also a use case draft-hutton-rtcweb-
>> nat-firewall-considerations.
>> Usage of the HTTP CONNECT method is proposed here. The request URI
>> would include the TURN server (preferably even to the well-known STUN
>> port). If the network admin put the TURN server into its whitelist, that could
>> hardly be considered as sneaking unwanted traffic through.
>>> And,  for me the most viable solution would be to enable TURN over
>>> websockets.
>> [TS] This would require updates to the TURN protocol and the TURN
>> software, whereas the proposals in draft-hutton-rtcweb-nat-firewall-
>> considerations use the original transports.
>> As most WebRTC services relay on websockets in one way or
>>> another for signaling, we could assume that media would work on 100%
>>> of the cases where signaling is working today.
>>> Also, as it is an http based solution, network administrators could
>>> apply corporate policies and block connections to not-trusted TURN
>>> servers.
>> [TS] which could also be done by white-listing the TURN server address via
>> TCP without any further intermediate HTTP/Websocket layers.
>>
>> Regards
>> Thomas
>>
>>> Best regards
>>> Sergio
>>> _______________________________________________
>>> pntaw mailing list
>>> pntaw@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pntaw
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw


From thomas.stach@siemens-enterprise.com  Fri Aug 30 06:24:37 2013
Return-Path: <thomas.stach@siemens-enterprise.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8ED011E810D for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NB4-QtRk+GwS for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:24:32 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 57A4B11E8111 for <pntaw@ietf.org>; Fri, 30 Aug 2013 06:24:32 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 8A0CA1EB847E; Fri, 30 Aug 2013 15:24:31 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.174]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Fri, 30 Aug 2013 15:24:31 +0200
From: "Stach, Thomas" <thomas.stach@siemens-enterprise.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpVzeSFPe8Kl+LUCjnsamYIV4h5mtqQnw///regCAACaXIA==
Date: Fri, 30 Aug 2013 13:24:30 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE12179BF9D6@MCHP04MSX.global-ad.net>
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <5220968E.2050708@gmail.com>
In-Reply-To: <5220968E.2050708@gmail.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 13:24:37 -0000

> -----Original Message-----
> From: Sergio Garcia Murillo [mailto:sergio.garcia.murillo@gmail.com]
> Sent: Freitag, 30. August 2013 14:57
> To: Stach, Thomas
> Cc: pntaw@ietf.org
> Subject: Re: [pntaw] TURN over websockets
>=20
> Hi Thomas,
>=20
> Inline.
>=20
> El 30/08/2013 14:34, Stach, Thomas escribi=F3:
> > Sergio,
> >
> > Some comments inline
> >
> >> -----Original Message-----
> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> >> Of Sergio Garcia Murillo
> >> Sent: Freitag, 30. August 2013 10:42
> >> To: pntaw@ietf.org
> >> Subject: [pntaw] TURN over websockets
> >>
> >> Hi all,
> >>
> >> I will shoot first.
> >>
> >> It is great to finally see some real interest in what I consider to
> be
> >> the blocking point for webrtc in order to run business on top of it,
> >> which is the ability to be able to connect through corporate
> firewalls.
> >>
> >> I have seen some people arguing that with just TURN over TCP on port
> >> 443
> >> the problem will be solved, but I seriously doubt it. Neither TURN
> over
> >> SSL would do, as most web filters do DPI and will not enable the
> >> connection. Also, I have heard lots of voices that says we are
> trying
> >> to
> >> override network admin policies with dirty tricks. With whom, I
> could
> >> agree.
> > [TS] I'm not sure if you are referencing draft-hutton-rtcweb-nat-
> firewall-considerations here.
> > Nevertheless the draft mentions TURN over TCP to port 443.
> And also does mention TURN over websockets, while it consider it to be
> not necessary.
> > The goal behind this is certainly not to sneak WEBRTC media streams
> through heavily fortified networks that have DPI deployed.
> > The goal rather to address a scenario e.g. at a small hotel with a
> not-so-skilled network admin, that opened his firewall on TCP port
> 80/443 to allow its guests to do some web browsing, but is afraid of
> opening its firewall for UDP traffic.
> > If we want to deploy WEBRTC in such an environment TURN over TLS to
> port 443 would do the job.
>=20
> Maybe that is your scenario, definitively not mine. Try doing some
> serious business with banking, insurance or such kind of sector and you
> won't find no-so-skilled admin but a full flavor DPI web filter in
> place. Then try to go to their admin it department and ask them to do
> some funny configuration on their firewalls.
>=20
> I really doubt that TURN over TLS would work in 100% of this scenarios.
[TS] Certainly not, but it would already increase the number of working sce=
narios considerably.
I'd prefer to go on step by step and start with specifying the browser shou=
ld use TURN over TLS (including the HTTP proxy case). The more sophisticate=
d stuff could follow.

>=20
>=20
> >> So, the only way I see to move forward and overcome this issues is
> by
> >> playing according to the WEB rules, and use HTTP standards to enable
> >> media connectivity in WebRTC that would play nicely with current
> >> corporate HTTP proxies and web filters.
> > [TS] Playing nicely with HTTP proxies is also a use case draft-
> hutton-rtcweb-nat-firewall-considerations.
> > Usage of the HTTP CONNECT method is proposed here. The request URI
> would include the TURN server (preferably even to the well-known STUN
> port). If the network admin put the TURN server into its whitelist,
> that could hardly be considered as sneaking unwanted traffic through.
> >> And,  for me the most viable solution would be to enable TURN over
> >> websockets.
> > [TS] This would require updates to the TURN protocol and the TURN
> software, whereas the proposals in draft-hutton-rtcweb-nat-firewall-
> considerations use the original transports.
>=20
> Yes, it would require additions to the TURN protocol and new
> developments on TURN software.
>=20
> > As most WebRTC services relay on websockets in one way or
> >> another for signaling, we could assume that media would work on 100%
> of
> >> the cases where signaling is working today.
> >> Also, as it is an http based solution, network administrators could
> >> apply corporate policies and block connections to not-trusted TURN
> >> servers.
> > [TS] which could also be done by white-listing the TURN server
> address via TCP without any further intermediate HTTP/Websocket layers.
>=20
> Try to open a firewall in a corporate location, good luck! White
> listing
> in the web filter would be much more doable.
[TS] ... which is what I meant.

Regards
Thomas
>=20
> Best regards
> Sergio

From tireddy@cisco.com  Fri Aug 30 06:53:44 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9393E11E8111 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E9+ex83V2ary for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 06:53:39 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id BAF6D21F9F5B for <pntaw@ietf.org>; Fri, 30 Aug 2013 06:53:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2018; q=dns/txt; s=iport; t=1377870819; x=1379080419; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Lfd1zMGN6qz9eW4hSkb7AhXjIhmDRM9WLHH/qwvNkas=; b=iG2jUkFbSSxloVfH9fHVECyGvEFcJfg1a6NrcUhMl3QtiblgxTd3/D8X 90DmNSBXIN9ak2vuJcd/H0pY8pmslHE7XWwUR9RAzscaUzITKzcVngbCw MV6GxLEVl7JpBlwKtA6OAa4znwj5RM+qEL4VKnuDaQBoQCuxdY+Q3C+Ta M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAKCiIFKtJXG//2dsb2JhbABagwc1UcBPgR4WdIIkAQEBBAEBATc0FwQCAQgRBAEBCxQJBycLFAkIAgQBEggTh2YMuTaPQzgGgxaBAAOUGYUJkDeDIIIq
X-IronPort-AV: E=Sophos;i="4.89,990,1367971200"; d="scan'208";a="250734643"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 30 Aug 2013 13:53:38 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r7UDrcE1020624 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 30 Aug 2013 13:53:38 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.8]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Fri, 30 Aug 2013 08:53:38 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpVzYlJ1THI1FykWlGCDZp+nOV5mtdRzA
Date: Fri, 30 Aug 2013 13:53:37 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A19034557@xmb-rcd-x10.cisco.com>
References: <52205AE1.9010807@gmail.com>
In-Reply-To: <52205AE1.9010807@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.32.182]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 13:53:44 -0000

The other way to solve the Firewall problem is use PCP. For more details re=
fer to sections 3.1, 3.2 of draft http://tools.ietf.org/html/draft-penno-rt=
cweb-pcp-00 which addresses the problem of Enterprise Firewalls permitting =
P2P media streams.=20

-Tiru.

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf Of
> Sergio Garcia Murillo
> Sent: Friday, August 30, 2013 2:12 PM
> To: pntaw@ietf.org
> Subject: [pntaw] TURN over websockets
>=20
> Hi all,
>=20
> I will shoot first.
>=20
> It is great to finally see some real interest in what I consider to be
> the blocking point for webrtc in order to run business on top of it,
> which is the ability to be able to connect through corporate firewalls.
>=20
> I have seen some people arguing that with just TURN over TCP on port 443
> the problem will be solved, but I seriously doubt it. Neither TURN over
> SSL would do, as most web filters do DPI and will not enable the
> connection. Also, I have heard lots of voices that says we are trying to
> override network admin policies with dirty tricks. With whom, I could agr=
ee.
>=20
> So, the only way I see to move forward and overcome this issues is by
> playing according to the WEB rules, and use HTTP standards to enable
> media connectivity in WebRTC that would play nicely with current
> corporate HTTP proxies and web filters.
>=20
> And,  for me the most viable solution would be to enable TURN over
> websockets. As most WebRTC services relay on websockets in one way or
> another for signaling, we could assume that media would work on 100% of
> the cases where signaling is working today.
> Also, as it is an http based solution, network administrators could
> apply corporate policies and block connections to not-trusted TURN server=
s.
>=20
> Best regards
> Sergio
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From andrew.hutton@siemens-enterprise.com  Fri Aug 30 07:16:30 2013
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7C4211E810A for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 07:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level: 
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-xDQlvUQY4b for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 07:16:20 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 0A55111E8108 for <pntaw@ietf.org>; Fri, 30 Aug 2013 07:16:19 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 7860823F04CE for <pntaw@ietf.org>; Fri, 30 Aug 2013 16:16:16 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.174]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0123.003; Fri, 30 Aug 2013 16:16:16 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: draft-hutton-rtcweb-nat-firewall-considerations
Thread-Index: Ac6li3yHiavbr66zRBS13ndrj3kqWQ==
Date: Fri, 30 Aug 2013 14:16:15 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BA590C@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: multipart/alternative; boundary="_000_9F33F40F6F2CD847824537F3C4E37DDF17BA590CMCHP04MSXglobal_"
MIME-Version: 1.0
Subject: [pntaw] draft-hutton-rtcweb-nat-firewall-considerations
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 14:16:30 -0000

--_000_9F33F40F6F2CD847824537F3C4E37DDF17BA590CMCHP04MSXglobal_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

One of the reasons for establishing the pntaw mailing list was to discuss h=
ttp://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-0=
1

This draft discusses the interaction between webrtc browsers and Web Proxie=
s, Firewalls and TURN servers and makes some proposals on what needs to be =
implemented in webrtc browsers.  We have already received a few comments bo=
th on the rtcweb list and off list so we are working on an update which we =
hope to submit within the next couple of weeks.

As some people have recently stated on the rtcweb list this is an important=
 aspect of webrtc that needs to be tackled to enable webrtc deployments in =
many restricted environments.

The draft discusses the use of HTTP CONNECT in environments with web proxie=
s to enable a tunnel to be established to the TURN server but this does not=
 require any TURN enhancements which some people seem to have thought to be=
 the case.  A small number of people have told me that this might be contro=
versial but the way I see it is that webrtc brings new types of media to we=
b applications we need to specify the interaction between webrtc browsers a=
nd proxies in the same was as is done for HTTP (See http://tools.ietf.org/h=
tml/draft-ietf-httpbis-p2-semantics-23#section-4.3.6).

Look forward to your comments.

Regards
Andy



--_000_9F33F40F6F2CD847824537F3C4E37DDF17BA590CMCHP04MSXglobal_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>One of the reasons for establishing the pntaw mailing list was to disc=
uss <a href=3D"http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-=
considerations-01"><font color=3D"blue"><u>http://tools.ietf.org/html/draft=
-hutton-rtcweb-nat-firewall-considerations-01</u></font></a></div>
<div>&nbsp;</div>
<div>This draft discusses the interaction between webrtc browsers and Web P=
roxies, Firewalls and TURN servers and makes some proposals on what needs t=
o be implemented in webrtc browsers.&nbsp; We have already received a few c=
omments both on the rtcweb list and off
list so we are working on an update which we hope to submit within the next=
 couple of weeks. </div>
<div>&nbsp;</div>
<div>As some people have recently stated on the rtcweb list this is an impo=
rtant aspect of webrtc that needs to be tackled to enable webrtc deployment=
s in many restricted environments.</div>
<div>&nbsp;</div>
<div>The draft discusses the use of HTTP CONNECT in environments with web p=
roxies to enable a tunnel to be established to the TURN server but this doe=
s not require any TURN enhancements which some people seem to have thought =
to be the case.&nbsp; A small number
of people have told me that this might be controversial but the way I see i=
t is that webrtc brings new types of media to web applications we need to s=
pecify the interaction between webrtc browsers and proxies in the same was =
as is done for HTTP (See <a href=3D"http://tools.ietf.org/html/draft-ietf-h=
ttpbis-p2-semantics-23#section-4.3.6"><font color=3D"blue"><u>http://tools.=
ietf.org/html/draft-ietf-httpbis-p2-semantics-23#section-4.3.6</u></font></=
a>).</div>
<div>&nbsp;</div>
<div>Look forward to your comments.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Andy</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_9F33F40F6F2CD847824537F3C4E37DDF17BA590CMCHP04MSXglobal_--

From marc.blanchet@viagenie.ca  Fri Aug 30 07:28:25 2013
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B38D011E81A1 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 07:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.742
X-Spam-Level: 
X-Spam-Status: No, score=-102.742 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NkKLdmLaTDCv for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 07:28:25 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id DB71011E810A for <pntaw@ietf.org>; Fri, 30 Aug 2013 07:28:24 -0700 (PDT)
Received: from h195.viagenie.ca (h195.viagenie.ca [206.123.31.195]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1F81F403EE; Fri, 30 Aug 2013 10:28:24 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <913383AAA69FF945B8F946018B75898A19034557@xmb-rcd-x10.cisco.com>
Date: Fri, 30 Aug 2013 10:28:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F058FF6A-35F2-4372-AAB7-345F0024E845@viagenie.ca>
References: <52205AE1.9010807@gmail.com> <913383AAA69FF945B8F946018B75898A19034557@xmb-rcd-x10.cisco.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "pntaw@ietf.org" <pntaw@ietf.org>, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 14:28:26 -0000

Le 2013-08-30 =E0 09:53, "Tirumaleswar Reddy (tireddy)" =
<tireddy@cisco.com> a =E9crit :

> The other way to solve the Firewall problem is use PCP.

don't agree.  it would be great, much better design, but all the install =
base of gateways in public wifi, coffee shop wifi, hotel networks, =
etc... are not going to do any PCP.=20

Marc.

> For more details refer to sections 3.1, 3.2 of draft =
http://tools.ietf.org/html/draft-penno-rtcweb-pcp-00 which addresses the =
problem of Enterprise Firewalls permitting P2P media streams.=20
>=20
> -Tiru.
>=20
>> -----Original Message-----
>> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On =
Behalf Of
>> Sergio Garcia Murillo
>> Sent: Friday, August 30, 2013 2:12 PM
>> To: pntaw@ietf.org
>> Subject: [pntaw] TURN over websockets
>>=20
>> Hi all,
>>=20
>> I will shoot first.
>>=20
>> It is great to finally see some real interest in what I consider to =
be
>> the blocking point for webrtc in order to run business on top of it,
>> which is the ability to be able to connect through corporate =
firewalls.
>>=20
>> I have seen some people arguing that with just TURN over TCP on port =
443
>> the problem will be solved, but I seriously doubt it. Neither TURN =
over
>> SSL would do, as most web filters do DPI and will not enable the
>> connection. Also, I have heard lots of voices that says we are trying =
to
>> override network admin policies with dirty tricks. With whom, I could =
agree.
>>=20
>> So, the only way I see to move forward and overcome this issues is by
>> playing according to the WEB rules, and use HTTP standards to enable
>> media connectivity in WebRTC that would play nicely with current
>> corporate HTTP proxies and web filters.
>>=20
>> And,  for me the most viable solution would be to enable TURN over
>> websockets. As most WebRTC services relay on websockets in one way or
>> another for signaling, we could assume that media would work on 100% =
of
>> the cases where signaling is working today.
>> Also, as it is an http based solution, network administrators could
>> apply corporate policies and block connections to not-trusted TURN =
servers.
>>=20
>> Best regards
>> Sergio
>> _______________________________________________
>> pntaw mailing list
>> pntaw@ietf.org
>> https://www.ietf.org/mailman/listinfo/pntaw
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From andrew.hutton@siemens-enterprise.com  Fri Aug 30 08:07:32 2013
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED16921F9C69 for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 08:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rvhMWRAF0gPV for <pntaw@ietfa.amsl.com>; Fri, 30 Aug 2013 08:07:25 -0700 (PDT)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id D1F7921F9E3B for <pntaw@ietf.org>; Fri, 30 Aug 2013 08:07:24 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id D0B301EB8483; Fri, 30 Aug 2013 17:07:16 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.174]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Fri, 30 Aug 2013 17:07:16 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpY0ypJ5QqRVEm0uGHK1KUWxWBJmt2Cng
Date: Fri, 30 Aug 2013 15:07:15 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BA5B9C@MCHP04MSX.global-ad.net>
References: <52205AE1.9010807@gmail.com> <913383AAA69FF945B8F946018B75898A19034557@xmb-rcd-x10.cisco.com> <F058FF6A-35F2-4372-AAB7-345F0024E845@viagenie.ca>
In-Reply-To: <F058FF6A-35F2-4372-AAB7-345F0024E845@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 15:07:32 -0000

P2P is something we can look at in the future but I don't see it as an opti=
on for enabling webrtc deployment in the near term.

We proposed the HTTP Connect mechanism in draft-hutton-rtcweb-nat-firewall-=
considerations because it would significantly improve the chances of enabli=
ng webrtc deployment today and requires no new implementation other than in=
 the webrtc browser.

Regards
Andy



> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Marc Blanchet
> Sent: 30 August 2013 15:28
> To: Tirumaleswar Reddy (tireddy)
> Cc: pntaw@ietf.org; Sergio Garcia Murillo
> Subject: Re: [pntaw] TURN over websockets
>=20
> Le 2013-08-30 =E0 09:53, "Tirumaleswar Reddy (tireddy)"
> <tireddy@cisco.com> a =E9crit :
>=20
> > The other way to solve the Firewall problem is use PCP.
>=20
> don't agree.  it would be great, much better design, but all the
> install base of gateways in public wifi, coffee shop wifi, hotel
> networks, etc... are not going to do any PCP.
>=20
> Marc.
>=20
> > For more details refer to sections 3.1, 3.2 of draft
> http://tools.ietf.org/html/draft-penno-rtcweb-pcp-00 which addresses
> the problem of Enterprise Firewalls permitting P2P media streams.
> >
> > -Tiru.
> >
> >> -----Original Message-----
> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf Of
> >> Sergio Garcia Murillo
> >> Sent: Friday, August 30, 2013 2:12 PM
> >> To: pntaw@ietf.org
> >> Subject: [pntaw] TURN over websockets
> >>
> >> Hi all,
> >>
> >> I will shoot first.
> >>
> >> It is great to finally see some real interest in what I consider to
> be
> >> the blocking point for webrtc in order to run business on top of it,
> >> which is the ability to be able to connect through corporate
> firewalls.
> >>
> >> I have seen some people arguing that with just TURN over TCP on port
> 443
> >> the problem will be solved, but I seriously doubt it. Neither TURN
> over
> >> SSL would do, as most web filters do DPI and will not enable the
> >> connection. Also, I have heard lots of voices that says we are
> trying to
> >> override network admin policies with dirty tricks. With whom, I
> could agree.
> >>
> >> So, the only way I see to move forward and overcome this issues is
> by
> >> playing according to the WEB rules, and use HTTP standards to enable
> >> media connectivity in WebRTC that would play nicely with current
> >> corporate HTTP proxies and web filters.
> >>
> >> And,  for me the most viable solution would be to enable TURN over
> >> websockets. As most WebRTC services relay on websockets in one way
> or
> >> another for signaling, we could assume that media would work on 100%
> of
> >> the cases where signaling is working today.
> >> Also, as it is an http based solution, network administrators could
> >> apply corporate policies and block connections to not-trusted TURN
> servers.
> >>
> >> Best regards
> >> Sergio
> >> _______________________________________________
> >> pntaw mailing list
> >> pntaw@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pntaw
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

From partha@parthasarathi.co.in  Sat Aug 31 09:24:54 2013
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A5D11E8152 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 09:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvGyl-hLm+d2 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 09:24:50 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us2.mailhostbox.com [69.93.141.237]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF1E11E812D for <pntaw@ietf.org>; Sat, 31 Aug 2013 09:24:50 -0700 (PDT)
Received: from userPC (unknown [122.172.179.232]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id DE5FC638CDD; Sat, 31 Aug 2013 16:24:45 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1377966289; bh=NmUkhJ+OYKuK9am1/MLjtHwa9Rv/Ht2uZ++Wj0YsCL4=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=SUAqo6ilAJCaVzZ7ZmzzKY6vyeyH2M8RNA6Wj9W/u0OzcEYMoRWWwpi6axHOfcJIb ZL14LSkIcPpWZii8wVIq2AtELlX/y4Ksbo6FOn9wzXnXRfvXOsCNBMVzLEuC0nJ/6a a7cQ+BEFTmj+uVbpaUMC7stDhQkYJoZZuQcTKIpg=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Sergio Garcia Murillo'" <sergio.garcia.murillo@gmail.com>, "'Stach, Thomas'" <thomas.stach@siemens-enterprise.com>
References: <52205AE1.9010807@gmail.com>	<F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <5220968E.2050708@gmail.com>
In-Reply-To: <5220968E.2050708@gmail.com>
Date: Sat, 31 Aug 2013 21:54:35 +0530
Message-ID: <004e01cea666$98e9b090$cabd11b0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac6lgGULYWCEuoOvRBOX3jgjCAJPWgA5BESg
Content-Language: en-us
X-CTCH-RefID: str=0001.0A0C0203.522218D1.00AC, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.142
Cc: pntaw@ietf.org
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 16:24:54 -0000

Hi all,

In case of (firewall) Policy vs protocol, the policy is the final =
decision
maker and not the protocol. In case TURN over WebSocket is chosen, it is =
a
matter of time for firewall policy enhancement to block these rat holes =
in
the network.=20

Please try to understand from bank perspective that bank network =
security is
more important and end-user *MUST NOT* be allowed to use the traffic =
which
bank could not intercept.

Thanks
Partha

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> Of Sergio Garcia Murillo
> Sent: Friday, August 30, 2013 6:27 PM
> To: Stach, Thomas
> Cc: pntaw@ietf.org
> Subject: Re: [pntaw] TURN over websockets
>=20
> Hi Thomas,
>=20
> Inline.
>=20
> El 30/08/2013 14:34, Stach, Thomas escribi=F3:
> > Sergio,
> >
> > Some comments inline
> >
> >> -----Original Message-----
> >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> Behalf
> >> Of Sergio Garcia Murillo
> >> Sent: Freitag, 30. August 2013 10:42
> >> To: pntaw@ietf.org
> >> Subject: [pntaw] TURN over websockets
> >>
> >> Hi all,
> >>
> >> I will shoot first.
> >>
> >> It is great to finally see some real interest in what I consider to
> be
> >> the blocking point for webrtc in order to run business on top of =
it,
> >> which is the ability to be able to connect through corporate
> firewalls.
> >>
> >> I have seen some people arguing that with just TURN over TCP on =
port
> >> 443
> >> the problem will be solved, but I seriously doubt it. Neither TURN
> over
> >> SSL would do, as most web filters do DPI and will not enable the
> >> connection. Also, I have heard lots of voices that says we are
> trying
> >> to
> >> override network admin policies with dirty tricks. With whom, I
> could
> >> agree.
> > [TS] I'm not sure if you are referencing draft-hutton-rtcweb-nat-
> firewall-considerations here.
> > Nevertheless the draft mentions TURN over TCP to port 443.
> And also does mention TURN over websockets, while it consider it to be
> not necessary.
> > The goal behind this is certainly not to sneak WEBRTC media streams
> through heavily fortified networks that have DPI deployed.
> > The goal rather to address a scenario e.g. at a small hotel with a
> not-so-skilled network admin, that opened his firewall on TCP port
> 80/443 to allow its guests to do some web browsing, but is afraid of
> opening its firewall for UDP traffic.
> > If we want to deploy WEBRTC in such an environment TURN over TLS to
> port 443 would do the job.
>=20
> Maybe that is your scenario, definitively not mine. Try doing some
> serious business with banking, insurance or such kind of sector and =
you
> won't find no-so-skilled admin but a full flavor DPI web filter in
> place. Then try to go to their admin it department and ask them to do
> some funny configuration on their firewalls.
>=20
> I really doubt that TURN over TLS would work in 100% of this =
scenarios.
>=20
>=20
> >> So, the only way I see to move forward and overcome this issues is
> by
> >> playing according to the WEB rules, and use HTTP standards to =
enable
> >> media connectivity in WebRTC that would play nicely with current
> >> corporate HTTP proxies and web filters.
> > [TS] Playing nicely with HTTP proxies is also a use case draft-
> hutton-rtcweb-nat-firewall-considerations.
> > Usage of the HTTP CONNECT method is proposed here. The request URI
> would include the TURN server (preferably even to the well-known STUN
> port). If the network admin put the TURN server into its whitelist,
> that could hardly be considered as sneaking unwanted traffic through.
> >> And,  for me the most viable solution would be to enable TURN over
> >> websockets.
> > [TS] This would require updates to the TURN protocol and the TURN
> software, whereas the proposals in draft-hutton-rtcweb-nat-firewall-
> considerations use the original transports.
>=20
> Yes, it would require additions to the TURN protocol and new
> developments on TURN software.
>=20
> > As most WebRTC services relay on websockets in one way or
> >> another for signaling, we could assume that media would work on =
100%
> of
> >> the cases where signaling is working today.
> >> Also, as it is an http based solution, network administrators could
> >> apply corporate policies and block connections to not-trusted TURN
> >> servers.
> > [TS] which could also be done by white-listing the TURN server
> address via TCP without any further intermediate HTTP/Websocket =
layers.
>=20
> Try to open a firewall in a corporate location, good luck! White
> listing
> in the web filter would be much more doable.
>=20
> Best regards
> Sergio
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw


From martin.thomson@gmail.com  Sat Aug 31 10:33:52 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AAEC21E80CA for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 10:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.603
X-Spam-Level: 
X-Spam-Status: No, score=-2.603 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hpTFEDbZ0+lu for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 10:33:51 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 8AC3B21E80CB for <pntaw@ietf.org>; Sat, 31 Aug 2013 10:33:47 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id k13so2998657wgh.13 for <pntaw@ietf.org>; Sat, 31 Aug 2013 10:33:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/czyf+KVzmvKs/FpMBcwiA6FMU3h7wULOUfrYQGepK0=; b=VdMp4yasvL8TRZ50kss54zcGO3XDukMeZUaM3OUwxALsTRVPf3Lf5BUXuDafI3SzPj I5JAL102dRBIYUZEOCbgjKodf1IZXuqpgZa8te+FeTn6ViRat1f6NdFwWIjAU/dn/Ryh kvSmAGpCE0ZFwjaAcjY8M/O8j2Hg3uO56AcViR4RUvTgh8fEOKyB1cuD0f+Tv5RoSIRy NgOOC/vF8YDMIeZuzc8TSSS6UwpoK1MffKCioGHj3KJxxEVVtwT6fu+YUUzCjGDCHjKI ZT9mL4ccb6dNQqRowStJXw964nZxdnYMsXEzpuW7bu+vAWKu9kAUbBKo1CDiawnD47I9 dMtA==
MIME-Version: 1.0
X-Received: by 10.194.123.227 with SMTP id md3mr15826325wjb.17.1377970426716;  Sat, 31 Aug 2013 10:33:46 -0700 (PDT)
Received: by 10.194.28.39 with HTTP; Sat, 31 Aug 2013 10:33:46 -0700 (PDT)
In-Reply-To: <004e01cea666$98e9b090$cabd11b0$@co.in>
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <5220968E.2050708@gmail.com> <004e01cea666$98e9b090$cabd11b0$@co.in>
Date: Sat, 31 Aug 2013 10:33:46 -0700
Message-ID: <CABkgnnVt-VscwN4r_FovqCYqARxz2YmnBihwvzf6FXPcKcTz1Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Parthasarathi R <partha@parthasarathi.co.in>
Content-Type: text/plain; charset=UTF-8
Cc: pntaw@ietf.org, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "Stach, Thomas" <thomas.stach@siemens-enterprise.com>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 17:33:52 -0000

On 31 August 2013 09:24, Parthasarathi R <partha@parthasarathi.co.in> wrote:
> In case of (firewall) Policy vs protocol, the policy is the final decision
> maker and not the protocol. In case TURN over WebSocket is chosen, it is a
> matter of time for firewall policy enhancement to block these rat holes in
> the network.

I'm glad someone raised this point.  It's core to the discussion.
What, if any, visibility will a firewall or proxy be given into the
purpose of this exchange?   HTTP CONNECT followed by TLS doesn't give
the intermediary much of a chance to enforce policy.

From melinda.shore@gmail.com  Sat Aug 31 10:43:43 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C094821F8C0C for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 10:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4kMCfjFBBTW0 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 10:43:43 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0CC21F8B35 for <pntaw@ietf.org>; Sat, 31 Aug 2013 10:43:43 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so3102901pbb.41 for <pntaw@ietf.org>; Sat, 31 Aug 2013 10:43:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jlGSlVgJbUokupjSe8wTH/jk5fRrNAK8OIF57QPdSG8=; b=mI5aievQjy+AsrKHfPZhcgjZ/G89te3zKHrAVJNynxAqiOmG9MOYgiRqA8/CRUhvq8 H+au3xvjqP5T29X8NWTAgvPCuuolle3q/MCV5e5OmFsCZjAyw2X0iAGG9qJ+3C5JjYLd uq9TGcrRUrL3sRau6qzNH6Y+HIx0L7rRD9Fg8YG4GNIy/UYueD8TkXCCOEQl4q9uY1fL 4c+eUDArcjZBD6Mom0eoYnl9CtigTu3bpo/ai18lPW9I429IdxvV/AA/zjEmGmteGquQ l0cVy/NDeh2UbyqRVxp6ztdiV/PLo5pg7V7Uy3ZKgbDpyNxXYgr55YsAUiGSUSJgjuKf 7DNQ==
X-Received: by 10.66.241.34 with SMTP id wf2mr16954800pac.111.1377971023100; Sat, 31 Aug 2013 10:43:43 -0700 (PDT)
Received: from spandex.local (209-193-56-207-rb1.fai.dsl.dynamic.acsalaska.net. [209.193.56.207]) by mx.google.com with ESMTPSA id fl3sm5837875pad.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 Aug 2013 10:43:42 -0700 (PDT)
Message-ID: <52222B4B.7000900@gmail.com>
Date: Sat, 31 Aug 2013 09:43:39 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: pntaw@ietf.org
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <5220968E.2050708@gmail.com> <004e01cea666$98e9b090$cabd11b0$@co.in> <CABkgnnVt-VscwN4r_FovqCYqARxz2YmnBihwvzf6FXPcKcTz1Q@mail.gmail.com>
In-Reply-To: <CABkgnnVt-VscwN4r_FovqCYqARxz2YmnBihwvzf6FXPcKcTz1Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 17:43:43 -0000

On 8/31/13 9:33 AM, Martin Thomson wrote:
> I'm glad someone raised this point.  It's core to the discussion.
> What, if any, visibility will a firewall or proxy be given into the
> purpose of this exchange?   HTTP CONNECT followed by TLS doesn't give
> the intermediary much of a chance to enforce policy.

Well, arguably NAT is not really a policy enforcement mechanism.
But yes, if you're using firewall/nat traversal technologies to
get around firewall policy enforcement, there's a huge problem.
For what it's worth we've been trying to have *that* discussion
for years.

One of the advantages of using a mechanism that signals the
firewall directly (say, midcom, pcp, etc.) is that it allows
the firewall to accept or deny the request based on policy.
However, it requires a forklift upgrade to pretty much everything
and is extremely difficult to deploy for that reason.  This
is the primary (but not the only) reason that midcom flopped, so
I was surprised to see pcp chartered since it's got the same
barriers to deployment.  But that is a different discussion.

Melinda


From stephen.farrell@cs.tcd.ie  Sat Aug 31 11:53:19 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0F0321E80E4 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 11:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUsfHzMCFprh for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 11:53:12 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id B61FF21E80DF for <pntaw@ietf.org>; Sat, 31 Aug 2013 11:53:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id BA66ABEBE; Sat, 31 Aug 2013 19:53:09 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JaBnlJl1a5Wd; Sat, 31 Aug 2013 19:53:08 +0100 (IST)
Received: from [10.87.48.15] (unknown [86.46.20.4]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 381F3BEB3; Sat, 31 Aug 2013 19:53:08 +0100 (IST)
Message-ID: <52223B93.5030401@cs.tcd.ie>
Date: Sat, 31 Aug 2013 19:53:07 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <5220968E.2050708@gmail.com> <004e01cea666$98e9b090$cabd11b0$@co.in> <CABkgnnVt-VscwN4r_FovqCYqARxz2YmnBihwvzf6FXPcKcTz1Q@mail.gmail.com>
In-Reply-To: <CABkgnnVt-VscwN4r_FovqCYqARxz2YmnBihwvzf6FXPcKcTz1Q@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, pntaw@ietf.org, Parthasarathi R <partha@parthasarathi.co.in>, "Stach, Thomas" <thomas.stach@siemens-enterprise.com>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 18:53:19 -0000

On 08/31/2013 06:33 PM, Martin Thomson wrote:
> On 31 August 2013 09:24, Parthasarathi R <partha@parthasarathi.co.in> wrote:
>> In case of (firewall) Policy vs protocol, the policy is the final decision
>> maker and not the protocol. In case TURN over WebSocket is chosen, it is a
>> matter of time for firewall policy enhancement to block these rat holes in
>> the network.
> 
> I'm glad someone raised this point.  It's core to the discussion.
> What, if any, visibility will a firewall or proxy be given into the
> purpose of this exchange?   HTTP CONNECT followed by TLS doesn't give
> the intermediary much of a chance to enforce policy.

Just a note on this: Proposed solutions that require a man in the
middle attack on TLS are not likely to fare well. The security ADs
(incl me:-) are *very* strongly against messing about with TLS like
that. So I hope this design team effort (or whatever it is) don't
go down that road. And of course there's no need to go there either,
if you want to know what WebRTC stuff is going on, then there should
be fine WebRTC ways to do that that don't involve a TLS MITM attack.

Cheers,
S.

> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
> 

From bernard_aboba@hotmail.com  Sat Aug 31 19:21:32 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51E4B11E81A5 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 19:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.257
X-Spam-Level: 
X-Spam-Status: No, score=-102.257 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_MILLIONSOF=0.315, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNvPSnm9swpG for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 19:21:27 -0700 (PDT)
Received: from blu0-omc2-s2.blu0.hotmail.com (blu0-omc2-s2.blu0.hotmail.com [65.55.111.77]) by ietfa.amsl.com (Postfix) with ESMTP id BE0FC11E80D2 for <pntaw@ietf.org>; Sat, 31 Aug 2013 19:21:26 -0700 (PDT)
Received: from BLU169-W55 ([65.55.111.71]) by blu0-omc2-s2.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 31 Aug 2013 19:21:25 -0700
X-TMN: [A3aWDQMdZM9k3QTRVLuF+keRwloebxr5]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W550866EED2D3C94D56050B93370@phx.gbl>
Content-Type: multipart/alternative; boundary="_d8ccefc6-4043-4027-a8cc-bcaab6dfa8d4_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Date: Sat, 31 Aug 2013 19:21:25 -0700
Importance: Normal
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17BA590C@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17BA590C@MCHP04MSX.global-ad.net>
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Sep 2013 02:21:25.0780 (UTC) FILETIME=[F5788540:01CEA6B9]
Subject: Re: [pntaw] draft-hutton-rtcweb-nat-firewall-considerations
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 02:21:32 -0000

--_d8ccefc6-4043-4027-a8cc-bcaab6dfa8d4_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Here are some comments on the document.  Overall=2C I like the approach tak=
en=2C which is to articulate use cases and the potential solutions to them.=
  However=2C I think it could be a bit clearer about the overall recommenda=
tions and normative dependencies.=20
Section 1
   If an organization wants to support RTCWEB such a TURN server may be=0A=
   located in the DMZ of the private network of that organization where=0A=
   it is still under administrative control.=0A=
=0A=
   In certain environments with very restrictive FW policies a TURN=0A=
   server in the public internet may not be sufficient to establish=0A=
   connectivity towards the RTCWEB peer for RTP-based media [RFC3550].=0A=
   Such policies can include blocking of all UDP based traffic and=0A=
   allowing only HTTP(S) traffic to the TCP ports 80/443.  In addition=0A=
   access to the World Wide Web from inside an organization is often=0A=
   only possible via a HTTP proxy.
[BA] I think the above sentences miss an important distinction=2C which is =
the difference between use of WebRTC internal to an organization and use to=
 communicate externally.  In the internal scenario=2C employees of an organ=
ization use WebRTC to communicate with each other=2C and the corporate IT s=
hop endeavors to configure the corporate NATs=2C Firewalls=2C TURN servers=
=2C etc. to support that.  In the external scenario=2C organization employe=
es use WebRTC to communicate with customers or partners whose IT group may =
or may not be aware of WebRTC.  It is in this external scenario that many o=
f the thorniest issues are likely to arise. An example would be a company s=
ales associate inviting a potential customer to a screen sharing session to=
 demonstrate a new product.=20
Section 2.2

   In the first case the browser needs to use ICE-TCP [RFC6544] and=0A=
   provide active=2C passive and/or simultaneous-open TCP candidates.=0A=
   Assuming the peer also provides TCP candidates=2C a connectivity check=
=0A=
   for a TCP connection between the two peers should be successful.
[BA] Not sure whether "should be successful" is trying to imply that statis=
tically this is expected to succeed in the majority of RTP over TCP cases. =
 That is not my experience - "simultaneous open" isn't supported widely eno=
ugh for that to be the case.=20
   Note that the second case is not to be mixed up with TURN/TCP=0A=
   [RFC6062]=2C which deals with how to establish a TCP connection to the=
=0A=
   peer.  For this document we assume that the TURN server can reach the=0A=
   peer always via UDP=2C possibly via a second TURN server.
[BA] In an external scenario=2C a "second TURN server" is not likely=2C bec=
ause the WebRTC application will only provide a single TURN server.  So it =
seems to me that TURN/TCP [RFC6062] might still be needed (and at least in =
my experience=2C it ends up being used). Section 2.3
   In addition the RTCWEB=0A=
   clients need to be configured to contact the TURN server over the=0A=
   HTTP(S) ports and/or needs to be able to tell the browser accordingly. =
=0A=

[BA] At least in my experience=2C attempting to contact the TURN server ove=
r the HTTP port tends to run afoul of DPI.  So while I don't object to this=
 as a requirement=2C I've not found it particularly useful. =20
Section 3.3.1
   Afterwards=2C the RTCWEB client could upgrade the connection to use=0A=
   TLS=2C forward STUN/TURN traffic via the HTTP proxy and use the TURN=0A=
   server as media relay.  Note that upgrading in this case is not to be=0A=
   misunderstood as usage of the HTTP UPGRADE method as specified in=0A=
   [RFC2817] as this would require the TURN server to support HTTP.=20
 [BA] Can you clarify whether you are advocating support for this native in=
 the browser=2C or rather application implementation?  I'm assuming you mea=
n browser native (so as to be able to take advantage of this in ICE)=2C but=
 it also seems that an application might be able to take advantage of this =
(possibly to do something malicous).=20
Section 4.3
   However=2C the expected benefit in form of an increased success=0A=
   rate for establishment of a media stream seems rather small=2C thus=0A=
   HTTP fallback is left for further study.
[BA] At least in my experience=2C the failure rate for ICE/ICE-TCP is not s=
o small in enterprise use cases (can be as high as 5 percent).  Even if it =
is 1 percent and you are talking about a service handling hundreds of milli=
ons of users that kind of failure rate will generate a very big support bur=
den=2C particularly if the cost of service is small or negligible.  So I'd =
suggest that some testing of the recommendations might be helpful to quanti=
fy what the risk is=3B even "small" failure rates can be a big deal.=20
9.1.  Normative References=0A=
=0A=
   [RFC2119]  Bradner=2C S.=2C "Key words for use in RFCs to Indicate=0A=
              Requirement Levels"=2C BCP 14=2C RFC 2119=2C March 1997.
[BA] Only one normative reference?? Based on the recommendations in Section=
 5=2C I was expecting some of the following references to be normative:=20
   [RFC5245]  Rosenberg=2C J.=2C "Interactive Connectivity Establishment=0A=
              (ICE): A Protocol for Network Address Translator (NAT)=0A=
              Traversal for Offer/Answer Protocols"=2C RFC 5245=2C April=0A=
              2010.=0A=
=0A=
   [RFC5766]  Mahy=2C R.=2C Matthews=2C P.=2C and J. Rosenberg=2C "Traversa=
l Using=0A=
              Relays around NAT (TURN): Relay Extensions to Session=0A=
              Traversal Utilities for NAT (STUN)"=2C RFC 5766=2C April 2010=
.=0A=
=0A=
=0A=
   [RFC6544]  Rosenberg=2C J.=2C Keranen=2C A.=2C Lowekamp=2C B.=2C and A. =
Roach=2C=0A=
              "TCP Candidates with Interactive Connectivity=0A=
              Establishment (ICE)"=2C RFC 6544=2C March 2012.
Also (although Section 5 doesn't recommend this)=2C you might want to consi=
der:=20
   [RFC6062]  Perreault=2C S. and J. Rosenberg=2C "Traversal Using Relays=
=0A=
              around NAT (TURN) Extensions for TCP Allocations"=2C RFC=0A=
              6062=2C November 2010.
IMHO=2C if you're going to support RTP over TCP (not really sure that this =
needs to be mandated for WebRTC)=2C then you'll need RFC 6062 in addition t=
o RFC 6544. =0A=
=0A=
=0A=




From: andrew.hutton@siemens-enterprise.com
To: pntaw@ietf.org
Date: Fri=2C 30 Aug 2013 14:16:15 +0000
Subject: [pntaw] draft-hutton-rtcweb-nat-firewall-considerations

=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
One of the reasons for establishing the pntaw mailing list was to discuss h=
ttp://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-0=
1=0A=
 =0A=
This draft discusses the interaction between webrtc browsers and Web Proxie=
s=2C Firewalls and TURN servers and makes some proposals on what needs to b=
e implemented in webrtc browsers.  We have already received a few comments =
both on the rtcweb list and off=0A=
list so we are working on an update which we hope to submit within the next=
 couple of weeks. =0A=
 =0A=
As some people have recently stated on the rtcweb list this is an important=
 aspect of webrtc that needs to be tackled to enable webrtc deployments in =
many restricted environments.=0A=
 =0A=
The draft discusses the use of HTTP CONNECT in environments with web proxie=
s to enable a tunnel to be established to the TURN server but this does not=
 require any TURN enhancements which some people seem to have thought to be=
 the case.  A small number=0A=
of people have told me that this might be controversial but the way I see i=
t is that webrtc brings new types of media to web applications we need to s=
pecify the interaction between webrtc browsers and proxies in the same was =
as is done for HTTP (See http://tools.ietf.org/html/draft-ietf-httpbis-p2-s=
emantics-23#section-4.3.6).=0A=
 =0A=
Look forward to your comments.=0A=
 =0A=
Regards=0A=
Andy=0A=
 =0A=
 =0A=
=0A=
=0A=
=0A=

_______________________________________________=0A=
pntaw mailing list=0A=
pntaw@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/pntaw 		 	   		  =

--_d8ccefc6-4043-4027-a8cc-bcaab6dfa8d4_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Here are some comments on the do=
cument. &nbsp=3BOverall=2C I like the approach taken=2C which is to articul=
ate use cases and the potential solutions to them. &nbsp=3BHowever=2C I thi=
nk it could be a bit clearer about the overall recommendations and normativ=
e dependencies.&nbsp=3B<div><br></div><div>Section 1</div><div><br></div><d=
iv><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B mar=
gin-bottom: 0px=3B page-break-before: always=3B">   If an organization want=
s to support RTCWEB such a TURN server may be=0A=
   located in the DMZ of the private network of that organization where=0A=
   it is still under administrative control.=0A=
=0A=
   In certain environments with very restrictive FW policies a TURN=0A=
   server in the public internet may not be sufficient to establish=0A=
   connectivity towards the RTCWEB peer for RTP-based media [<a href=3D"htt=
p://tools.ietf.org/html/rfc3550" title=3D"&quot=3BRTP: A Transport Protocol=
 for Real-Time Applications&quot=3B">RFC3550</a>].=0A=
   Such policies can include blocking of all UDP based traffic and=0A=
   allowing only HTTP(S) traffic to the TCP ports 80/443.  In addition=0A=
   access to the World Wide Web from inside an organization is often=0A=
   only possible via a HTTP proxy.</pre><pre class=3D"newpage" style=3D"fon=
t-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: =
always=3B"><br></pre><pre class=3D"newpage" style=3D"font-size: 1em=3B marg=
in-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B">[BA] I t=
hink the above sentences miss an important distinction=2C which is the diff=
erence between use of WebRTC internal to an organization and use to communi=
cate externally.  In the internal scenario=2C employees of an organization =
use WebRTC to communicate with each other=2C and the corporate IT shop ende=
avors to configure the corporate NATs=2C Firewalls=2C TURN servers=2C etc. =
to support that.  In the external scenario=2C organization employees use We=
bRTC to communicate with customers or partners whose IT group may or may no=
t be aware of WebRTC.  It is in this external scenario that many of the tho=
rniest issues are likely to arise. An example would be a company sales asso=
ciate inviting a potential customer to a screen sharing session to demonstr=
ate a new product. </pre><pre class=3D"newpage" style=3D"font-size: 1em=3B =
margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><br>=
</pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B =
margin-bottom: 0px=3B page-break-before: always=3B">Section 2.2</pre><pre c=
lass=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-botto=
m: 0px=3B page-break-before: always=3B"><br></pre><pre class=3D"newpage" st=
yle=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-brea=
k-before: always=3B"><br></pre><pre class=3D"newpage" style=3D"font-size: 1=
em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B=
">   In the first case the browser needs to use ICE-TCP [<a href=3D"http://=
tools.ietf.org/html/rfc6544" title=3D"&quot=3BTCP Candidates with Interacti=
ve Connectivity Establishment (ICE)&quot=3B">RFC6544</a>] and=0A=
   provide active=2C passive and/or simultaneous-open TCP candidates.=0A=
   Assuming the peer also provides TCP candidates=2C a connectivity check=
=0A=
   for a TCP connection between the two peers should be successful.</pre><p=
re class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-b=
ottom: 0px=3B page-break-before: always=3B"><br></pre><pre class=3D"newpage=
" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-=
break-before: always=3B">[BA] Not sure whether "should be successful" is tr=
ying to imply that statistically this is expected to succeed in the majorit=
y of RTP over TCP cases.  That is not my experience - "simultaneous open" i=
sn't supported widely enough for that to be the case. </pre><pre class=3D"n=
ewpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B=
 page-break-before: always=3B"><br></pre><pre class=3D"newpage" style=3D"fo=
nt-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before:=
 always=3B">   Note that the second case is not to be mixed up with TURN/TC=
P=0A=
   [<a href=3D"http://tools.ietf.org/html/rfc6062" title=3D"&quot=3BTravers=
al Using Relays around NAT (TURN) Extensions for TCP Allocations&quot=3B">R=
FC6062</a>]=2C which deals with how to establish a TCP connection to the=0A=
   peer.  For this document we assume that the TURN server can reach the=0A=
   peer always via UDP=2C possibly via a second TURN server.</pre><pre clas=
s=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: =
0px=3B page-break-before: always=3B"><br></pre><pre class=3D"newpage" style=
=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-b=
efore: always=3B">[BA] In an external scenario=2C a "second TURN server" is=
 not likely=2C because the WebRTC application will only provide a single TU=
RN server.  So it seems to me that TURN/TCP [RFC6062] might still be needed=
 (and at least in my experience=2C it ends up being used).&nbsp=3B</pre><pr=
e class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bo=
ttom: 0px=3B page-break-before: always=3B">Section 2.3</pre><pre class=3D"n=
ewpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B=
 page-break-before: always=3B"><br></pre><pre class=3D"newpage" style=3D"fo=
nt-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before:=
 always=3B">   In addition the RTCWEB=0A=
   clients need to be configured to contact the TURN server over the=0A=
   HTTP(S) ports and/or needs to be able to tell the browser accordingly. =
=0A=
</pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B =
margin-bottom: 0px=3B page-break-before: always=3B"><br></pre><pre class=3D=
"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=
=3B page-break-before: always=3B"><font face=3D"Calibri=2C sans-serif">[BA]=
 At least in my experience=2C attempting to contact the TURN server over th=
e HTTP port tends to run afoul of DPI.  So while I don't object to this as =
a requirement=2C I've not found it particularly useful.  </font></pre><pre =
class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bott=
om: 0px=3B page-break-before: always=3B"><font face=3D"Calibri=2C sans-seri=
f"><br></font></pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margi=
n-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><font fac=
e=3D"Calibri=2C sans-serif">Section 3.3.1</font></pre><pre class=3D"newpage=
" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-=
break-before: always=3B"><font face=3D"Calibri=2C sans-serif"><br></font></=
pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B ma=
rgin-bottom: 0px=3B page-break-before: always=3B">   Afterwards=2C the RTCW=
EB client could upgrade the connection to use=0A=
   TLS=2C forward STUN/TURN traffic via the HTTP proxy and use the TURN=0A=
   server as media relay.  Note that upgrading in this case is not to be=0A=
   misunderstood as usage of the HTTP UPGRADE method as specified in=0A=
   [<a href=3D"http://tools.ietf.org/html/rfc2817" title=3D"&quot=3BUpgradi=
ng to TLS Within HTTP/ 1.1&quot=3B">RFC2817</a>] as this would require the =
TURN server to support HTTP. </pre><pre class=3D"newpage" style=3D"font-siz=
e: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: alway=
s=3B"><span style=3D"font-size: 12pt=3B font-family: Calibri=2C sans-serif=
=3B"><br></span></pre><pre class=3D"newpage" style=3D"font-size: 1em=3B mar=
gin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><span s=
tyle=3D"font-size: 12pt=3B font-family: Calibri=2C sans-serif=3B"> [BA] Can=
 you clarify whether you are advocating support for this native in the brow=
ser=2C or rather application implementation?  I'm assuming you mean browser=
 native (so as to be able to take advantage of this in ICE)=2C but it also =
seems that an application might be able to take advantage of this (possibly=
 to do something malicous). </span></pre><pre class=3D"newpage" style=3D"fo=
nt-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before:=
 always=3B"><span style=3D"font-size: 12pt=3B font-family: Calibri=2C sans-=
serif=3B"><br></span></pre><pre class=3D"newpage" style=3D"font-size: 1em=
=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B">=
<span style=3D"font-size: 12pt=3B font-family: Calibri=2C sans-serif=3B">Se=
ction 4.3</span></pre><pre class=3D"newpage" style=3D"font-size: 1em=3B mar=
gin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><span s=
tyle=3D"font-size: 12pt=3B font-family: Calibri=2C sans-serif=3B"><br></spa=
n></pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=
=3B margin-bottom: 0px=3B page-break-before: always=3B">   However=2C the e=
xpected benefit in form of an increased success=0A=
   rate for establishment of a media stream seems rather small=2C thus=0A=
   HTTP fallback is left for further study.</pre><pre class=3D"newpage" sty=
le=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break=
-before: always=3B"><br></pre><pre class=3D"newpage" style=3D"font-size: 1e=
m=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"=
>[BA] At least in my experience=2C the failure rate for ICE/ICE-TCP is not =
so small in enterprise use cases (can be as high as 5 percent).  Even if it=
 is 1 percent and you are talking about a service handling hundreds of mill=
ions of users that kind of failure rate will generate a very big support bu=
rden=2C particularly if the cost of service is small or negligible.  So I'd=
 suggest that some testing of the recommendations might be helpful to quant=
ify what the risk is=3B even "small" failure rates can be a big deal. </pre=
><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margi=
n-bottom: 0px=3B page-break-before: always=3B"><br></pre><pre class=3D"newp=
age" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B pa=
ge-break-before: always=3B"><span class=3D"h3" style=3D"line-height: 0pt=3B=
 display: inline=3B font-size: 12pt=3B font-weight: bold=3B"><h3 style=3D"l=
ine-height: 0pt=3B display: inline=3B font-size: 1em=3B"><a class=3D"selfli=
nk" name=3D"section-9.1" href=3D"http://tools.ietf.org/html/draft-hutton-rt=
cweb-nat-firewall-considerations-01#section-9.1" style=3D"color: black=3B t=
ext-decoration: none=3B">9.1</a>.  Normative References</h3></span>=0A=
=0A=
   [<a name=3D"ref-RFC2119" id=3D"ref-RFC2119">RFC2119</a>]  Bradner=2C S.=
=2C "Key words for use in RFCs to Indicate=0A=
              Requirement Levels"=2C <a href=3D"http://tools.ietf.org/html/=
bcp14">BCP 14</a>=2C <a href=3D"http://tools.ietf.org/html/rfc2119">RFC 211=
9</a>=2C March 1997.</pre><pre class=3D"newpage" style=3D"font-size: 1em=3B=
 margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><br=
></pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B=
 margin-bottom: 0px=3B page-break-before: always=3B">[BA] Only one normativ=
e reference?? Based on the recommendations in Section 5=2C I was expecting =
some of the following references to be normative: </pre><pre class=3D"newpa=
ge" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B pag=
e-break-before: always=3B"><br></pre><pre class=3D"newpage" style=3D"font-s=
ize: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: alw=
ays=3B">   [<a name=3D"ref-RFC5245" id=3D"ref-RFC5245">RFC5245</a>]  Rosenb=
erg=2C J.=2C "Interactive Connectivity Establishment=0A=
              (ICE): A Protocol for Network Address Translator (NAT)=0A=
              Traversal for Offer/Answer Protocols"=2C <a href=3D"http://to=
ols.ietf.org/html/rfc5245">RFC 5245</a>=2C April=0A=
              2010.=0A=
=0A=
   [<a name=3D"ref-RFC5766" id=3D"ref-RFC5766">RFC5766</a>]  Mahy=2C R.=2C =
Matthews=2C P.=2C and J. Rosenberg=2C "Traversal Using=0A=
              Relays around NAT (TURN): Relay Extensions to Session=0A=
              Traversal Utilities for NAT (STUN)"=2C <a href=3D"http://tool=
s.ietf.org/html/rfc5766">RFC 5766</a>=2C April 2010.=0A=
=0A=
=0A=
   [<a name=3D"ref-RFC6544" id=3D"ref-RFC6544">RFC6544</a>]  Rosenberg=2C J=
.=2C Keranen=2C A.=2C Lowekamp=2C B.=2C and A. Roach=2C=0A=
              "TCP Candidates with Interactive Connectivity=0A=
              Establishment (ICE)"=2C <a href=3D"http://tools.ietf.org/html=
/rfc6544">RFC 6544</a>=2C March 2012.</pre><pre class=3D"newpage" style=3D"=
font-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-befor=
e: always=3B"><br></pre><pre class=3D"newpage" style=3D"font-size: 1em=3B m=
argin-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B">Also =
(although Section 5 doesn't recommend this)=2C you might want to consider:&=
nbsp=3B</pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: =
0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><br></pre><pre c=
lass=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-botto=
m: 0px=3B page-break-before: always=3B"><pre class=3D"newpage" style=3D"fon=
t-size: 1em=3B margin-top: 0px=3B margin-bottom: 0px=3B page-break-before: =
always=3B">   [<a name=3D"ref-RFC6062" id=3D"ref-RFC6062">RFC6062</a>]  Per=
reault=2C S. and J. Rosenberg=2C "Traversal Using Relays=0A=
              around NAT (TURN) Extensions for TCP Allocations"=2C <a href=
=3D"http://tools.ietf.org/html/rfc6062">RFC</a>=0A=
              <a href=3D"http://tools.ietf.org/html/rfc6062">6062</a>=2C No=
vember 2010.</pre><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-=
top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><br></pre><=
pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B margin-=
bottom: 0px=3B page-break-before: always=3B">IMHO=2C if you're going to sup=
port RTP over TCP (not really sure that this needs to be mandated for WebRT=
C)=2C then you'll need RFC 6062 in addition to RFC 6544. </pre>=0A=
=0A=
=0A=
</pre><div><br></div><pre class=3D"newpage" style=3D"font-size: 1em=3B marg=
in-top: 0px=3B margin-bottom: 0px=3B page-break-before: always=3B"><br></pr=
e><pre class=3D"newpage" style=3D"font-size: 1em=3B margin-top: 0px=3B marg=
in-bottom: 0px=3B page-break-before: always=3B"><br></pre></div><div><br><d=
iv><hr id=3D"stopSpelling">From: andrew.hutton@siemens-enterprise.com<br>To=
: pntaw@ietf.org<br>Date: Fri=2C 30 Aug 2013 14:16:15 +0000<br>Subject: [pn=
taw] draft-hutton-rtcweb-nat-firewall-considerations<br><br>=0A=
=0A=
=0A=
=0A=
=0A=
<style><!--=0A=
.ExternalClass .ecxEmailQuote {=0A=
padding-left:4pt=3B=0A=
border-left:#800000 2px solid=3B=0A=
}=0A=
=0A=
--></style>=0A=
=0A=
=0A=
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt=3B">=0A=
<div>One of the reasons for establishing the pntaw mailing list was to disc=
uss <a href=3D"http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-=
considerations-01" target=3D"_blank"><font color=3D"blue"><u>http://tools.i=
etf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-01</u></font><=
/a></div>=0A=
<div>&nbsp=3B</div>=0A=
<div>This draft discusses the interaction between webrtc browsers and Web P=
roxies=2C Firewalls and TURN servers and makes some proposals on what needs=
 to be implemented in webrtc browsers.&nbsp=3B We have already received a f=
ew comments both on the rtcweb list and off=0A=
list so we are working on an update which we hope to submit within the next=
 couple of weeks. </div>=0A=
<div>&nbsp=3B</div>=0A=
<div>As some people have recently stated on the rtcweb list this is an impo=
rtant aspect of webrtc that needs to be tackled to enable webrtc deployment=
s in many restricted environments.</div>=0A=
<div>&nbsp=3B</div>=0A=
<div>The draft discusses the use of HTTP CONNECT in environments with web p=
roxies to enable a tunnel to be established to the TURN server but this doe=
s not require any TURN enhancements which some people seem to have thought =
to be the case.&nbsp=3B A small number=0A=
of people have told me that this might be controversial but the way I see i=
t is that webrtc brings new types of media to web applications we need to s=
pecify the interaction between webrtc browsers and proxies in the same was =
as is done for HTTP (See <a href=3D"http://tools.ietf.org/html/draft-ietf-h=
ttpbis-p2-semantics-23#section-4.3.6" target=3D"_blank"><font color=3D"blue=
"><u>http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-23#section-=
4.3.6</u></font></a>).</div>=0A=
<div>&nbsp=3B</div>=0A=
<div>Look forward to your comments.</div>=0A=
<div>&nbsp=3B</div>=0A=
<div>Regards</div>=0A=
<div>Andy</div>=0A=
<div>&nbsp=3B</div>=0A=
<div>&nbsp=3B</div>=0A=
</span></font>=0A=
=0A=
=0A=
<br>_______________________________________________=0A=
pntaw mailing list=0A=
pntaw@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/pntaw</div></div> 		 	   		  </div></=
body>
</html>=

--_d8ccefc6-4043-4027-a8cc-bcaab6dfa8d4_--

From bernard_aboba@hotmail.com  Sat Aug 31 20:09:37 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D219D21E80E1 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 20:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.55
X-Spam-Level: 
X-Spam-Status: No, score=-101.55 tagged_above=-999 required=5 tests=[AWL=-0.820, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, MIME_QP_LONG_LINE=1.396, SARE_MILLIONSOF=0.315, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1AnnBZe+m+b for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 20:09:33 -0700 (PDT)
Received: from blu0-omc2-s5.blu0.hotmail.com (blu0-omc2-s5.blu0.hotmail.com [65.55.111.80]) by ietfa.amsl.com (Postfix) with ESMTP id BB0BD21E80F0 for <pntaw@ietf.org>; Sat, 31 Aug 2013 20:09:32 -0700 (PDT)
Received: from BLU404-EAS263 ([65.55.111.72]) by blu0-omc2-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 31 Aug 2013 20:09:32 -0700
X-TMN: [RlwkdKDYDvzDhX/b5q0OzLMYUMeEtCdD]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU404-EAS263C160169554B82B52076293370@phx.gbl>
Content-Type: multipart/related; boundary="_81c3a899-a578-40a9-9dc6-e120bc4dc14f_"
References: <9F33F40F6F2CD847824537F3C4E37DDF17BA590C@MCHP04MSX.global-ad.net> <BLU169-W550866EED2D3C94D56050B93370@phx.gbl>
From: Bernard Aboba <bernard_aboba@hotmail.com>
In-Reply-To: <BLU169-W550866EED2D3C94D56050B93370@phx.gbl>
Date: Sat, 31 Aug 2013 20:09:27 -0700
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "pntaw@ietf.org" <pntaw@ietf.org>
MIME-Version: 1.0 (1.0)
X-OriginalArrivalTime: 01 Sep 2013 03:09:32.0424 (UTC) FILETIME=[AE0B7080:01CEA6C0]
Subject: Re: [pntaw] draft-hutton-rtcweb-nat-firewall-considerations
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 03:09:37 -0000

--_81c3a899-a578-40a9-9dc6-e120bc4dc14f_
Content-Type: multipart/alternative;
	boundary="Apple-Mail-22E49B92-08B6-4AE4-919B-3A65E8A671B3"
Content-Transfer-Encoding: 7bit

--Apple-Mail-22E49B92-08B6-4AE4-919B-3A65E8A671B3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'd also mention that there is no reference to RFC 6156. With the deployment=
 of IPv6 (and firewalls supporting it), scenarios requiring this are emergin=
g, and we do want WebRTC to work in those cases.

On Aug 31, 2013, at 7:21 PM, "Bernard Aboba" <bernard_aboba@hotmail.com> wro=
te:

> Here are some comments on the document.  Overall, I like the approach take=
n, which is to articulate use cases and the potential solutions to them.  Ho=
wever, I think it could be a bit clearer about the overall recommendations a=
nd normative dependencies.=20
>=20
> Section 1
>=20
>    If an organization wants to support RTCWEB such a TURN server may be
>    located in the DMZ of the private network of that organization where
>    it is still under administrative control.
>=20
>    In certain environments with very restrictive FW policies a TURN
>    server in the public internet may not be sufficient to establish
>    connectivity towards the RTCWEB peer for RTP-based media [RFC3550].
>    Such policies can include blocking of all UDP based traffic and
>    allowing only HTTP(S) traffic to the TCP ports 80/443.  In addition
>    access to the World Wide Web from inside an organization is often
>    only possible via a HTTP proxy.
>=20
> [BA] I think the above sentences miss an important distinction, which is t=
he difference between use of WebRTC internal to an organization and use to c=
ommunicate externally.  In the internal scenario, employees of an organizati=
on use WebRTC to communicate with each other, and the corporate IT shop ende=
avors to configure the corporate NATs, Firewalls, TURN servers, etc. to supp=
ort that.  In the external scenario, organization employees use WebRTC to co=
mmunicate with customers or partners whose IT group may or may not be aware o=
f WebRTC.  It is in this external scenario that many of the thorniest issues=
 are likely to arise. An example would be a company sales associate inviting=
 a potential customer to a screen sharing session to demonstrate a new produ=
ct.=20
>=20
> Section 2.2
>=20
>=20
>    In the first case the browser needs to use ICE-TCP [RFC6544] and
>    provide active, passive and/or simultaneous-open TCP candidates.
>    Assuming the peer also provides TCP candidates, a connectivity check
>    for a TCP connection between the two peers should be successful.
>=20
> [BA] Not sure whether "should be successful" is trying to imply that stati=
stically this is expected to succeed in the majority of RTP over TCP cases. =
 That is not my experience - "simultaneous open" isn't supported widely enou=
gh for that to be the case.=20
>=20
>    Note that the second case is not to be mixed up with TURN/TCP
>    [RFC6062], which deals with how to establish a TCP connection to the
>    peer.  For this document we assume that the TURN server can reach the
>    peer always via UDP, possibly via a second TURN server.
>=20
> [BA] In an external scenario, a "second TURN server" is not likely, becaus=
e the WebRTC application will only provide a single TURN server.  So it seem=
s to me that TURN/TCP [RFC6062] might still be needed (and at least in my ex=
perience, it ends up being used).=20
> Section 2.3
>=20
>    In addition the RTCWEB
>    clients need to be configured to contact the TURN server over the
>    HTTP(S) ports and/or needs to be able to tell the browser accordingly.=20=

>=20
> [BA] At least in my experience, attempting to contact the TURN server over=
 the HTTP port tends to run afoul of DPI.  So while I don't object to this a=
s a requirement, I've not found it particularly useful. =20
>=20
> Section 3.3.1
>=20
>    Afterwards, the RTCWEB client could upgrade the connection to use
>    TLS, forward STUN/TURN traffic via the HTTP proxy and use the TURN
>    server as media relay.  Note that upgrading in this case is not to be
>    misunderstood as usage of the HTTP UPGRADE method as specified in
>    [RFC2817] as this would require the TURN server to support HTTP.=20
>=20
>  [BA] Can you clarify whether you are advocating support for this native i=
n the browser, or rather application implementation?  I'm assuming you mean b=
rowser native (so as to be able to take advantage of this in ICE), but it al=
so seems that an application might be able to take advantage of this (possib=
ly to do something malicous).=20
>=20
> Section 4.3
>=20
>    However, the expected benefit in form of an increased success
>    rate for establishment of a media stream seems rather small, thus
>    HTTP fallback is left for further study.
>=20
> [BA] At least in my experience, the failure rate for ICE/ICE-TCP is not so=
 small in enterprise use cases (can be as high as 5 percent).  Even if it is=
 1 percent and you are talking about a service handling hundreds of millions=
 of users that kind of failure rate will generate a very big support burden,=
 particularly if the cost of service is small or negligible.  So I'd suggest=
 that some testing of the recommendations might be helpful to quantify what t=
he risk is; even "small" failure rates can be a big deal.=20
>=20
> 9.1.  Normative References
>=20
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
>=20
> [BA] Only one normative reference?? Based on the recommendations in Sectio=
n 5, I was expecting some of the following references to be normative:=20
>=20
>    [RFC5245]  Rosenberg, J., "Interactive Connectivity Establishment
>               (ICE): A Protocol for Network Address Translator (NAT)
>               Traversal for Offer/Answer Protocols", RFC 5245, April
>               2010.
>=20
>    [RFC5766]  Mahy, R., Matthews, P., and J. Rosenberg, "Traversal Using
>               Relays around NAT (TURN): Relay Extensions to Session
>               Traversal Utilities for NAT (STUN)", RFC 5766, April 2010.
>=20
>=20
>    [RFC6544]  Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach,
>               "TCP Candidates with Interactive Connectivity
>               Establishment (ICE)", RFC 6544, March 2012.
>=20
> Also (although Section 5 doesn't recommend this), you might want to consid=
er:=20
>=20
>    [RFC6062]  Perreault, S. and J. Rosenberg, "Traversal Using Relays
>               around NAT (TURN) Extensions for TCP Allocations", RFC
>               6062, November 2010.
>=20
> IMHO, if you're going to support RTP over TCP (not really sure that this n=
eeds to be mandated for WebRTC), then you'll need RFC 6062 in addition to RFC=
 6544.=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> From: andrew.hutton@siemens-enterprise.com
> To: pntaw@ietf.org
> Date: Fri, 30 Aug 2013 14:16:15 +0000
> Subject: [pntaw] draft-hutton-rtcweb-nat-firewall-considerations
>=20
> One of the reasons for establishing the pntaw mailing list was to discuss h=
ttp://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-01=

> =20
> This draft discusses the interaction between webrtc browsers and Web Proxi=
es, Firewalls and TURN servers and makes some proposals on what needs to be i=
mplemented in webrtc browsers.  We have already received a few comments both=
 on the rtcweb list and off list so we are working on an update which we hop=
e to submit within the next couple of weeks.
> =20
> As some people have recently stated on the rtcweb list this is an importan=
t aspect of webrtc that needs to be tackled to enable webrtc deployments in m=
any restricted environments.
> =20
> The draft discusses the use of HTTP CONNECT in environments with web proxi=
es to enable a tunnel to be established to the TURN server but this does not=
 require any TURN enhancements which some people seem to have thought to be t=
he case.  A small number of people have told me that this might be controver=
sial but the way I see it is that webrtc brings new types of media to web ap=
plications we need to specify the interaction between webrtc browsers and pr=
oxies in the same was as is done for HTTP (See http://tools.ietf.org/html/dr=
aft-ietf-httpbis-p2-semantics-23#section-4.3.6).
> =20
> Look forward to your comments.
> =20
> Regards
> Andy
> =20
> =20
>=20
> _______________________________________________ pntaw mailing list pntaw@i=
etf.org https://www.ietf.org/mailman/listinfo/pntaw
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw

--Apple-Mail-22E49B92-08B6-4AE4-919B-3A65E8A671B3
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPjxkaXY+SSdkIGFs
c28gbWVudGlvbiB0aGF0IHRoZXJlIGlzIG5vIHJlZmVyZW5jZSB0byBSRkMgNjE1Ni4gV2l0aCB0
aGUgZGVwbG95bWVudCBvZiBJUHY2IChhbmQgZmlyZXdhbGxzIHN1cHBvcnRpbmcgaXQpLCBzY2Vu
YXJpb3MgcmVxdWlyaW5nIHRoaXMgYXJlIGVtZXJnaW5nLCBhbmQgd2UgZG8gd2FudCBXZWJSVEMg
dG8gd29yayBpbiB0aG9zZSBjYXNlcy48L2Rpdj48ZGl2Pjxicj5PbiBBdWcgMzEsIDIwMTMsIGF0
IDc6MjEgUE0sICJCZXJuYXJkIEFib2JhIiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmJlcm5hcmRfYWJv
YmFAaG90bWFpbC5jb20iPmJlcm5hcmRfYWJvYmFAaG90bWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8
YnI+PGJyPjwvZGl2PjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxkaXY+DQoNCjxzdHlsZT48IS0t
DQouaG1tZXNzYWdlIFANCnsNCm1hcmdpbjowcHg7DQpwYWRkaW5nOjBweA0KfQ0KYm9keS5obW1l
c3NhZ2UNCnsNCmZvbnQtc2l6ZTogMTJwdDsNCmZvbnQtZmFtaWx5OkNhbGlicmkNCn0NCi0tPjwv
c3R5bGU+DQo8ZGl2IGRpcj0ibHRyIj5IZXJlIGFyZSBzb21lIGNvbW1lbnRzIG9uIHRoZSBkb2N1
bWVudC4gJm5ic3A7T3ZlcmFsbCwgSSBsaWtlIHRoZSBhcHByb2FjaCB0YWtlbiwgd2hpY2ggaXMg
dG8gYXJ0aWN1bGF0ZSB1c2UgY2FzZXMgYW5kIHRoZSBwb3RlbnRpYWwgc29sdXRpb25zIHRvIHRo
ZW0uICZuYnNwO0hvd2V2ZXIsIEkgdGhpbmsgaXQgY291bGQgYmUgYSBiaXQgY2xlYXJlciBhYm91
dCB0aGUgb3ZlcmFsbCByZWNvbW1lbmRhdGlvbnMgYW5kIG5vcm1hdGl2ZSBkZXBlbmRlbmNpZXMu
Jm5ic3A7PGRpdj48YnI+PC9kaXY+PGRpdj5TZWN0aW9uIDE8L2Rpdj48ZGl2Pjxicj48L2Rpdj48
ZGl2PjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRv
cDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij4g
ICBJZiBhbiBvcmdhbml6YXRpb24gd2FudHMgdG8gc3VwcG9ydCBSVENXRUIgc3VjaCBhIFRVUk4g
c2VydmVyIG1heSBiZQ0KICAgbG9jYXRlZCBpbiB0aGUgRE1aIG9mIHRoZSBwcml2YXRlIG5ldHdv
cmsgb2YgdGhhdCBvcmdhbml6YXRpb24gd2hlcmUNCiAgIGl0IGlzIHN0aWxsIHVuZGVyIGFkbWlu
aXN0cmF0aXZlIGNvbnRyb2wuDQoNCiAgIEluIGNlcnRhaW4gZW52aXJvbm1lbnRzIHdpdGggdmVy
eSByZXN0cmljdGl2ZSBGVyBwb2xpY2llcyBhIFRVUk4NCiAgIHNlcnZlciBpbiB0aGUgcHVibGlj
IGludGVybmV0IG1heSBub3QgYmUgc3VmZmljaWVudCB0byBlc3RhYmxpc2gNCiAgIGNvbm5lY3Rp
dml0eSB0b3dhcmRzIHRoZSBSVENXRUIgcGVlciBmb3IgUlRQLWJhc2VkIG1lZGlhIFs8YSBocmVm
PSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMzNTUwIiB0aXRsZT0iJnF1b3Q7UlRQOiBB
IFRyYW5zcG9ydCBQcm90b2NvbCBmb3IgUmVhbC1UaW1lIEFwcGxpY2F0aW9ucyZxdW90OyI+UkZD
MzU1MDwvYT5dLg0KICAgU3VjaCBwb2xpY2llcyBjYW4gaW5jbHVkZSBibG9ja2luZyBvZiBhbGwg
VURQIGJhc2VkIHRyYWZmaWMgYW5kDQogICBhbGxvd2luZyBvbmx5IEhUVFAoUykgdHJhZmZpYyB0
byB0aGUgVENQIHBvcnRzIDgwLzQ0My4gIEluIGFkZGl0aW9uDQogICBhY2Nlc3MgdG8gdGhlIFdv
cmxkIFdpZGUgV2ViIGZyb20gaW5zaWRlIGFuIG9yZ2FuaXphdGlvbiBpcyBvZnRlbg0KICAgb25s
eSBwb3NzaWJsZSB2aWEgYSBIVFRQIHByb3h5LjwvcHJlPjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0
eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7
IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBjbGFzcz0ibmV3cGFn
ZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206
IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPltCQV0gSSB0aGluayB0aGUgYWJvdmUg
c2VudGVuY2VzIG1pc3MgYW4gaW1wb3J0YW50IGRpc3RpbmN0aW9uLCB3aGljaCBpcyB0aGUgZGlm
ZmVyZW5jZSBiZXR3ZWVuIHVzZSBvZiBXZWJSVEMgaW50ZXJuYWwgdG8gYW4gb3JnYW5pemF0aW9u
IGFuZCB1c2UgdG8gY29tbXVuaWNhdGUgZXh0ZXJuYWxseS4gIEluIHRoZSBpbnRlcm5hbCBzY2Vu
YXJpbywgZW1wbG95ZWVzIG9mIGFuIG9yZ2FuaXphdGlvbiB1c2UgV2ViUlRDIHRvIGNvbW11bmlj
YXRlIHdpdGggZWFjaCBvdGhlciwgYW5kIHRoZSBjb3Jwb3JhdGUgSVQgc2hvcCBlbmRlYXZvcnMg
dG8gY29uZmlndXJlIHRoZSBjb3Jwb3JhdGUgTkFUcywgRmlyZXdhbGxzLCBUVVJOIHNlcnZlcnMs
IGV0Yy4gdG8gc3VwcG9ydCB0aGF0LiAgSW4gdGhlIGV4dGVybmFsIHNjZW5hcmlvLCBvcmdhbml6
YXRpb24gZW1wbG95ZWVzIHVzZSBXZWJSVEMgdG8gY29tbXVuaWNhdGUgd2l0aCBjdXN0b21lcnMg
b3IgcGFydG5lcnMgd2hvc2UgSVQgZ3JvdXAgbWF5IG9yIG1heSBub3QgYmUgYXdhcmUgb2YgV2Vi
UlRDLiAgSXQgaXMgaW4gdGhpcyBleHRlcm5hbCBzY2VuYXJpbyB0aGF0IG1hbnkgb2YgdGhlIHRo
b3JuaWVzdCBpc3N1ZXMgYXJlIGxpa2VseSB0byBhcmlzZS4gQW4gZXhhbXBsZSB3b3VsZCBiZSBh
IGNvbXBhbnkgc2FsZXMgYXNzb2NpYXRlIGludml0aW5nIGEgcG90ZW50aWFsIGN1c3RvbWVyIHRv
IGEgc2NyZWVuIHNoYXJpbmcgc2Vzc2lvbiB0byBkZW1vbnN0cmF0ZSBhIG5ldyBwcm9kdWN0LiA8
L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10
b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+
PGJyPjwvcHJlPjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFy
Z2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdh
eXM7Ij5TZWN0aW9uIDIuMjwvcHJlPjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJmb250LXNp
emU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IHBhZ2UtYnJlYWst
YmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZv
bnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgcGFnZS1i
cmVhay1iZWZvcmU6IGFsd2F5czsiPjxicj48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHls
ZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBw
YWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+ICAgSW4gdGhlIGZpcnN0IGNhc2UgdGhlIGJyb3dz
ZXIgbmVlZHMgdG8gdXNlIElDRS1UQ1AgWzxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9o
dG1sL3JmYzY1NDQiIHRpdGxlPSImcXVvdDtUQ1AgQ2FuZGlkYXRlcyB3aXRoIEludGVyYWN0aXZl
IENvbm5lY3Rpdml0eSBFc3RhYmxpc2htZW50IChJQ0UpJnF1b3Q7Ij5SRkM2NTQ0PC9hPl0gYW5k
DQogICBwcm92aWRlIGFjdGl2ZSwgcGFzc2l2ZSBhbmQvb3Igc2ltdWx0YW5lb3VzLW9wZW4gVENQ
IGNhbmRpZGF0ZXMuDQogICBBc3N1bWluZyB0aGUgcGVlciBhbHNvIHByb3ZpZGVzIFRDUCBjYW5k
aWRhdGVzLCBhIGNvbm5lY3Rpdml0eSBjaGVjaw0KICAgZm9yIGEgVENQIGNvbm5lY3Rpb24gYmV0
d2VlbiB0aGUgdHdvIHBlZXJzIHNob3VsZCBiZSBzdWNjZXNzZnVsLjwvcHJlPjxwcmUgY2xhc3M9
Im5ld3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4t
Ym90dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBj
bGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1h
cmdpbi1ib3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPltCQV0gTm90IHN1
cmUgd2hldGhlciAic2hvdWxkIGJlIHN1Y2Nlc3NmdWwiIGlzIHRyeWluZyB0byBpbXBseSB0aGF0
IHN0YXRpc3RpY2FsbHkgdGhpcyBpcyBleHBlY3RlZCB0byBzdWNjZWVkIGluIHRoZSBtYWpvcml0
eSBvZiBSVFAgb3ZlciBUQ1AgY2FzZXMuICBUaGF0IGlzIG5vdCBteSBleHBlcmllbmNlIC0gInNp
bXVsdGFuZW91cyBvcGVuIiBpc24ndCBzdXBwb3J0ZWQgd2lkZWx5IGVub3VnaCBmb3IgdGhhdCB0
byBiZSB0aGUgY2FzZS4gPC9wcmU+PHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6
ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgcGFnZS1icmVhay1i
ZWZvcmU6IGFsd2F5czsiPjxicj48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9u
dC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJy
ZWFrLWJlZm9yZTogYWx3YXlzOyI+ICAgTm90ZSB0aGF0IHRoZSBzZWNvbmQgY2FzZSBpcyBub3Qg
dG8gYmUgbWl4ZWQgdXAgd2l0aCBUVVJOL1RDUA0KICAgWzxhIGhyZWY9Imh0dHA6Ly90b29scy5p
ZXRmLm9yZy9odG1sL3JmYzYwNjIiIHRpdGxlPSImcXVvdDtUcmF2ZXJzYWwgVXNpbmcgUmVsYXlz
IGFyb3VuZCBOQVQgKFRVUk4pIEV4dGVuc2lvbnMgZm9yIFRDUCBBbGxvY2F0aW9ucyZxdW90OyI+
UkZDNjA2MjwvYT5dLCB3aGljaCBkZWFscyB3aXRoIGhvdyB0byBlc3RhYmxpc2ggYSBUQ1AgY29u
bmVjdGlvbiB0byB0aGUNCiAgIHBlZXIuICBGb3IgdGhpcyBkb2N1bWVudCB3ZSBhc3N1bWUgdGhh
dCB0aGUgVFVSTiBzZXJ2ZXIgY2FuIHJlYWNoIHRoZQ0KICAgcGVlciBhbHdheXMgdmlhIFVEUCwg
cG9zc2libHkgdmlhIGEgc2Vjb25kIFRVUk4gc2VydmVyLjwvcHJlPjxwcmUgY2xhc3M9Im5ld3Bh
Z2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9t
OiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBjbGFzcz0i
bmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1i
b3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPltCQV0gSW4gYW4gZXh0ZXJu
YWwgc2NlbmFyaW8sIGEgInNlY29uZCBUVVJOIHNlcnZlciIgaXMgbm90IGxpa2VseSwgYmVjYXVz
ZSB0aGUgV2ViUlRDIGFwcGxpY2F0aW9uIHdpbGwgb25seSBwcm92aWRlIGEgc2luZ2xlIFRVUk4g
c2VydmVyLiAgU28gaXQgc2VlbXMgdG8gbWUgdGhhdCBUVVJOL1RDUCBbUkZDNjA2Ml0gbWlnaHQg
c3RpbGwgYmUgbmVlZGVkIChhbmQgYXQgbGVhc3QgaW4gbXkgZXhwZXJpZW5jZSwgaXQgZW5kcyB1
cCBiZWluZyB1c2VkKS4mbmJzcDs8L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9u
dC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJy
ZWFrLWJlZm9yZTogYWx3YXlzOyI+U2VjdGlvbiAyLjM8L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdl
IiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTog
MHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+PGJyPjwvcHJlPjxwcmUgY2xhc3M9Im5l
d3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90
dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij4gICBJbiBhZGRpdGlvbiB0aGUg
UlRDV0VCDQogICBjbGllbnRzIG5lZWQgdG8gYmUgY29uZmlndXJlZCB0byBjb250YWN0IHRoZSBU
VVJOIHNlcnZlciBvdmVyIHRoZQ0KICAgSFRUUChTKSBwb3J0cyBhbmQvb3IgbmVlZHMgdG8gYmUg
YWJsZSB0byB0ZWxsIHRoZSBicm93c2VyIGFjY29yZGluZ2x5LiANCjwvcHJlPjxwcmUgY2xhc3M9
Im5ld3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4t
Ym90dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBj
bGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1h
cmdpbi1ib3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPjxmb250IGZhY2U9
IkNhbGlicmksIHNhbnMtc2VyaWYiPltCQV0gQXQgbGVhc3QgaW4gbXkgZXhwZXJpZW5jZSwgYXR0
ZW1wdGluZyB0byBjb250YWN0IHRoZSBUVVJOIHNlcnZlciBvdmVyIHRoZSBIVFRQIHBvcnQgdGVu
ZHMgdG8gcnVuIGFmb3VsIG9mIERQSS4gIFNvIHdoaWxlIEkgZG9uJ3Qgb2JqZWN0IHRvIHRoaXMg
YXMgYSByZXF1aXJlbWVudCwgSSd2ZSBub3QgZm91bmQgaXQgcGFydGljdWxhcmx5IHVzZWZ1bC4g
IDwvZm9udD48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07
IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTog
YWx3YXlzOyI+PGZvbnQgZmFjZT0iQ2FsaWJyaSwgc2Fucy1zZXJpZiI+PGJyPjwvZm9udD48L3By
ZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10b3A6
IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+PGZv
bnQgZmFjZT0iQ2FsaWJyaSwgc2Fucy1zZXJpZiI+U2VjdGlvbiAzLjMuMTwvZm9udD48L3ByZT48
cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBw
eDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+PGZvbnQg
ZmFjZT0iQ2FsaWJyaSwgc2Fucy1zZXJpZiI+PGJyPjwvZm9udD48L3ByZT48cHJlIGNsYXNzPSJu
ZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJv
dHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+ICAgQWZ0ZXJ3YXJkcywgdGhl
IFJUQ1dFQiBjbGllbnQgY291bGQgdXBncmFkZSB0aGUgY29ubmVjdGlvbiB0byB1c2UNCiAgIFRM
UywgZm9yd2FyZCBTVFVOL1RVUk4gdHJhZmZpYyB2aWEgdGhlIEhUVFAgcHJveHkgYW5kIHVzZSB0
aGUgVFVSTg0KICAgc2VydmVyIGFzIG1lZGlhIHJlbGF5LiAgTm90ZSB0aGF0IHVwZ3JhZGluZyBp
biB0aGlzIGNhc2UgaXMgbm90IHRvIGJlDQogICBtaXN1bmRlcnN0b29kIGFzIHVzYWdlIG9mIHRo
ZSBIVFRQIFVQR1JBREUgbWV0aG9kIGFzIHNwZWNpZmllZCBpbg0KICAgWzxhIGhyZWY9Imh0dHA6
Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzI4MTciIHRpdGxlPSImcXVvdDtVcGdyYWRpbmcgdG8g
VExTIFdpdGhpbiBIVFRQLyAxLjEmcXVvdDsiPlJGQzI4MTc8L2E+XSBhcyB0aGlzIHdvdWxkIHJl
cXVpcmUgdGhlIFRVUk4gc2VydmVyIHRvIHN1cHBvcnQgSFRUUC4gPC9wcmU+PHByZSBjbGFzcz0i
bmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1i
b3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6IDEycHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyI+PGJyPjwvc3Bh
bj48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdp
bi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlz
OyI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTJwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNh
bnMtc2VyaWY7Ij4gW0JBXSBDYW4geW91IGNsYXJpZnkgd2hldGhlciB5b3UgYXJlIGFkdm9jYXRp
bmcgc3VwcG9ydCBmb3IgdGhpcyBuYXRpdmUgaW4gdGhlIGJyb3dzZXIsIG9yIHJhdGhlciBhcHBs
aWNhdGlvbiBpbXBsZW1lbnRhdGlvbj8gIEknbSBhc3N1bWluZyB5b3UgbWVhbiBicm93c2VyIG5h
dGl2ZSAoc28gYXMgdG8gYmUgYWJsZSB0byB0YWtlIGFkdmFudGFnZSBvZiB0aGlzIGluIElDRSks
IGJ1dCBpdCBhbHNvIHNlZW1zIHRoYXQgYW4gYXBwbGljYXRpb24gbWlnaHQgYmUgYWJsZSB0byB0
YWtlIGFkdmFudGFnZSBvZiB0aGlzIChwb3NzaWJseSB0byBkbyBzb21ldGhpbmcgbWFsaWNvdXMp
LiA8L3NwYW4+PC9wcmU+PHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVt
OyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6
IGFsd2F5czsiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDEycHQ7IGZvbnQtZmFtaWx5OiBDYWxp
YnJpLCBzYW5zLXNlcmlmOyI+PGJyPjwvc3Bhbj48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBz
dHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4
OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTJw
dDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Ij5TZWN0aW9uIDQuMzwvc3Bhbj48
L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10
b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTJwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMt
c2VyaWY7Ij48YnI+PC9zcGFuPjwvcHJlPjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJmb250
LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IHBhZ2UtYnJl
YWstYmVmb3JlOiBhbHdheXM7Ij4gICBIb3dldmVyLCB0aGUgZXhwZWN0ZWQgYmVuZWZpdCBpbiBm
b3JtIG9mIGFuIGluY3JlYXNlZCBzdWNjZXNzDQogICByYXRlIGZvciBlc3RhYmxpc2htZW50IG9m
IGEgbWVkaWEgc3RyZWFtIHNlZW1zIHJhdGhlciBzbWFsbCwgdGh1cw0KICAgSFRUUCBmYWxsYmFj
ayBpcyBsZWZ0IGZvciBmdXJ0aGVyIHN0dWR5LjwvcHJlPjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0
eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7
IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBjbGFzcz0ibmV3cGFn
ZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206
IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPltCQV0gQXQgbGVhc3QgaW4gbXkgZXhw
ZXJpZW5jZSwgdGhlIGZhaWx1cmUgcmF0ZSBmb3IgSUNFL0lDRS1UQ1AgaXMgbm90IHNvIHNtYWxs
IGluIGVudGVycHJpc2UgdXNlIGNhc2VzIChjYW4gYmUgYXMgaGlnaCBhcyA1IHBlcmNlbnQpLiAg
RXZlbiBpZiBpdCBpcyAxIHBlcmNlbnQgYW5kIHlvdSBhcmUgdGFsa2luZyBhYm91dCBhIHNlcnZp
Y2UgaGFuZGxpbmcgaHVuZHJlZHMgb2YgbWlsbGlvbnMgb2YgdXNlcnMgdGhhdCBraW5kIG9mIGZh
aWx1cmUgcmF0ZSB3aWxsIGdlbmVyYXRlIGEgdmVyeSBiaWcgc3VwcG9ydCBidXJkZW4sIHBhcnRp
Y3VsYXJseSBpZiB0aGUgY29zdCBvZiBzZXJ2aWNlIGlzIHNtYWxsIG9yIG5lZ2xpZ2libGUuICBT
byBJJ2Qgc3VnZ2VzdCB0aGF0IHNvbWUgdGVzdGluZyBvZiB0aGUgcmVjb21tZW5kYXRpb25zIG1p
Z2h0IGJlIGhlbHBmdWwgdG8gcXVhbnRpZnkgd2hhdCB0aGUgcmlzayBpczsgZXZlbiAic21hbGwi
IGZhaWx1cmUgcmF0ZXMgY2FuIGJlIGEgYmlnIGRlYWwuIDwvcHJlPjxwcmUgY2xhc3M9Im5ld3Bh
Z2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9t
OiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBjbGFzcz0i
bmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1i
b3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPjxzcGFuIGNsYXNzPSJoMyIg
c3R5bGU9ImxpbmUtaGVpZ2h0OiAwcHQ7IGRpc3BsYXk6IGlubGluZTsgZm9udC1zaXplOiAxMnB0
OyBmb250LXdlaWdodDogYm9sZDsiPjxoMyBzdHlsZT0ibGluZS1oZWlnaHQ6IDBwdDsgZGlzcGxh
eTogaW5saW5lOyBmb250LXNpemU6IDFlbTsiPjxhIGNsYXNzPSJzZWxmbGluayIgbmFtZT0ic2Vj
dGlvbi05LjEiIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWh1dHRvbi1y
dGN3ZWItbmF0LWZpcmV3YWxsLWNvbnNpZGVyYXRpb25zLTAxI3NlY3Rpb24tOS4xIiBzdHlsZT0i
Y29sb3I6IGJsYWNrOyB0ZXh0LWRlY29yYXRpb246IG5vbmU7Ij45LjE8L2E+LiAgTm9ybWF0aXZl
IFJlZmVyZW5jZXM8L2gzPjwvc3Bhbj4NCg0KICAgWzxhIG5hbWU9InJlZi1SRkMyMTE5IiBpZD0i
cmVmLVJGQzIxMTkiPlJGQzIxMTk8L2E+XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVz
ZSBpbiBSRkNzIHRvIEluZGljYXRlDQogICAgICAgICAgICAgIFJlcXVpcmVtZW50IExldmVscyIs
IDxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2JjcDE0Ij5CQ1AgMTQ8L2E+LCA8
YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMyMTE5Ij5SRkMgMjExOTwvYT4s
IE1hcmNoIDE5OTcuPC9wcmU+PHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTog
MWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgcGFnZS1icmVhay1iZWZv
cmU6IGFsd2F5czsiPjxicj48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1z
aXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFr
LWJlZm9yZTogYWx3YXlzOyI+W0JBXSBPbmx5IG9uZSBub3JtYXRpdmUgcmVmZXJlbmNlPz8gQmFz
ZWQgb24gdGhlIHJlY29tbWVuZGF0aW9ucyBpbiBTZWN0aW9uIDUsIEkgd2FzIGV4cGVjdGluZyBz
b21lIG9mIHRoZSBmb2xsb3dpbmcgcmVmZXJlbmNlcyB0byBiZSBub3JtYXRpdmU6IDwvcHJlPjxw
cmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4
OyBtYXJnaW4tYm90dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9w
cmU+PHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9w
OiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPiAg
IFs8YSBuYW1lPSJyZWYtUkZDNTI0NSIgaWQ9InJlZi1SRkM1MjQ1Ij5SRkM1MjQ1PC9hPl0gIFJv
c2VuYmVyZywgSi4sICJJbnRlcmFjdGl2ZSBDb25uZWN0aXZpdHkgRXN0YWJsaXNobWVudA0KICAg
ICAgICAgICAgICAoSUNFKTogQSBQcm90b2NvbCBmb3IgTmV0d29yayBBZGRyZXNzIFRyYW5zbGF0
b3IgKE5BVCkNCiAgICAgICAgICAgICAgVHJhdmVyc2FsIGZvciBPZmZlci9BbnN3ZXIgUHJvdG9j
b2xzIiwgPGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNTI0NSI+UkZDIDUy
NDU8L2E+LCBBcHJpbA0KICAgICAgICAgICAgICAyMDEwLg0KDQogICBbPGEgbmFtZT0icmVmLVJG
QzU3NjYiIGlkPSJyZWYtUkZDNTc2NiI+UkZDNTc2NjwvYT5dICBNYWh5LCBSLiwgTWF0dGhld3Ms
IFAuLCBhbmQgSi4gUm9zZW5iZXJnLCAiVHJhdmVyc2FsIFVzaW5nDQogICAgICAgICAgICAgIFJl
bGF5cyBhcm91bmQgTkFUIChUVVJOKTogUmVsYXkgRXh0ZW5zaW9ucyB0byBTZXNzaW9uDQogICAg
ICAgICAgICAgIFRyYXZlcnNhbCBVdGlsaXRpZXMgZm9yIE5BVCAoU1RVTikiLCA8YSBocmVmPSJo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM1NzY2Ij5SRkMgNTc2NjwvYT4sIEFwcmlsIDIw
MTAuDQoNCg0KICAgWzxhIG5hbWU9InJlZi1SRkM2NTQ0IiBpZD0icmVmLVJGQzY1NDQiPlJGQzY1
NDQ8L2E+XSAgUm9zZW5iZXJnLCBKLiwgS2VyYW5lbiwgQS4sIExvd2VrYW1wLCBCLiwgYW5kIEEu
IFJvYWNoLA0KICAgICAgICAgICAgICAiVENQIENhbmRpZGF0ZXMgd2l0aCBJbnRlcmFjdGl2ZSBD
b25uZWN0aXZpdHkNCiAgICAgICAgICAgICAgRXN0YWJsaXNobWVudCAoSUNFKSIsIDxhIGhyZWY9
Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzY1NDQiPlJGQyA2NTQ0PC9hPiwgTWFyY2gg
MjAxMi48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1h
cmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3
YXlzOyI+PGJyPjwvcHJlPjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFl
bTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3Jl
OiBhbHdheXM7Ij5BbHNvIChhbHRob3VnaCBTZWN0aW9uIDUgZG9lc24ndCByZWNvbW1lbmQgdGhp
cyksIHlvdSBtaWdodCB3YW50IHRvIGNvbnNpZGVyOiZuYnNwOzwvcHJlPjxwcmUgY2xhc3M9Im5l
d3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90
dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PHByZSBjbGFz
cz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdp
bi1ib3R0b206IDBweDsgcGFnZS1icmVhay1iZWZvcmU6IGFsd2F5czsiPjxwcmUgY2xhc3M9Im5l
d3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90
dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij4gICBbPGEgbmFtZT0icmVmLVJG
QzYwNjIiIGlkPSJyZWYtUkZDNjA2MiI+UkZDNjA2MjwvYT5dICBQZXJyZWF1bHQsIFMuIGFuZCBK
LiBSb3NlbmJlcmcsICJUcmF2ZXJzYWwgVXNpbmcgUmVsYXlzDQogICAgICAgICAgICAgIGFyb3Vu
ZCBOQVQgKFRVUk4pIEV4dGVuc2lvbnMgZm9yIFRDUCBBbGxvY2F0aW9ucyIsIDxhIGhyZWY9Imh0
dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzYwNjIiPlJGQzwvYT4NCiAgICAgICAgICAgICAg
PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjA2MiI+NjA2MjwvYT4sIE5v
dmVtYmVyIDIwMTAuPC9wcmU+PHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTog
MWVtOyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgcGFnZS1icmVhay1iZWZv
cmU6IGFsd2F5czsiPjxicj48L3ByZT48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0iZm9udC1z
aXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBwYWdlLWJyZWFr
LWJlZm9yZTogYWx3YXlzOyI+SU1ITywgaWYgeW91J3JlIGdvaW5nIHRvIHN1cHBvcnQgUlRQIG92
ZXIgVENQIChub3QgcmVhbGx5IHN1cmUgdGhhdCB0aGlzIG5lZWRzIHRvIGJlIG1hbmRhdGVkIGZv
ciBXZWJSVEMpLCB0aGVuIHlvdSdsbCBuZWVkIFJGQyA2MDYyIGluIGFkZGl0aW9uIHRvIFJGQyA2
NTQ0LiA8L3ByZT4NCg0KDQo8L3ByZT48ZGl2Pjxicj48L2Rpdj48cHJlIGNsYXNzPSJuZXdwYWdl
IiBzdHlsZT0iZm9udC1zaXplOiAxZW07IG1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTog
MHB4OyBwYWdlLWJyZWFrLWJlZm9yZTogYWx3YXlzOyI+PGJyPjwvcHJlPjxwcmUgY2xhc3M9Im5l
d3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDFlbTsgbWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90
dG9tOiAwcHg7IHBhZ2UtYnJlYWstYmVmb3JlOiBhbHdheXM7Ij48YnI+PC9wcmU+PC9kaXY+PGRp
dj48YnI+PGRpdj48aHIgaWQ9InN0b3BTcGVsbGluZyI+RnJvbTogPGEgaHJlZj0ibWFpbHRvOmFu
ZHJldy5odXR0b25Ac2llbWVucy1lbnRlcnByaXNlLmNvbSI+YW5kcmV3Lmh1dHRvbkBzaWVtZW5z
LWVudGVycHJpc2UuY29tPC9hPjxicj5UbzogPGEgaHJlZj0ibWFpbHRvOnBudGF3QGlldGYub3Jn
Ij5wbnRhd0BpZXRmLm9yZzwvYT48YnI+RGF0ZTogRnJpLCAzMCBBdWcgMjAxMyAxNDoxNjoxNSAr
MDAwMDxicj5TdWJqZWN0OiBbcG50YXddIGRyYWZ0LWh1dHRvbi1ydGN3ZWItbmF0LWZpcmV3YWxs
LWNvbnNpZGVyYXRpb25zPGJyPjxicj4NCg0KDQoNCg0KPHN0eWxlPjwhLS0NCi5FeHRlcm5hbENs
YXNzIC5lY3hFbWFpbFF1b3RlIHsNCnBhZGRpbmctbGVmdDo0cHQ7DQpib3JkZXItbGVmdDojODAw
MDAwIDJweCBzb2xpZDsNCn0NCg0KLS0+PC9zdHlsZT4NCg0KDQo8Zm9udCBmYWNlPSJDYWxpYnJp
IiBzaXplPSIyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExcHQ7Ij4NCjxkaXY+T25lIG9mIHRo
ZSByZWFzb25zIGZvciBlc3RhYmxpc2hpbmcgdGhlIHBudGF3IG1haWxpbmcgbGlzdCB3YXMgdG8g
ZGlzY3VzcyA8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1odXR0b24t
cnRjd2ViLW5hdC1maXJld2FsbC1jb25zaWRlcmF0aW9ucy0wMSIgdGFyZ2V0PSJfYmxhbmsiPjxm
b250IGNvbG9yPSJibHVlIj48dT5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1odXR0
b24tcnRjd2ViLW5hdC1maXJld2FsbC1jb25zaWRlcmF0aW9ucy0wMTwvdT48L2ZvbnQ+PC9hPjwv
ZGl2Pg0KPGRpdj4mbmJzcDs8L2Rpdj4NCjxkaXY+VGhpcyBkcmFmdCBkaXNjdXNzZXMgdGhlIGlu
dGVyYWN0aW9uIGJldHdlZW4gd2VicnRjIGJyb3dzZXJzIGFuZCBXZWIgUHJveGllcywgRmlyZXdh
bGxzIGFuZCBUVVJOIHNlcnZlcnMgYW5kIG1ha2VzIHNvbWUgcHJvcG9zYWxzIG9uIHdoYXQgbmVl
ZHMgdG8gYmUgaW1wbGVtZW50ZWQgaW4gd2VicnRjIGJyb3dzZXJzLiZuYnNwOyBXZSBoYXZlIGFs
cmVhZHkgcmVjZWl2ZWQgYSBmZXcgY29tbWVudHMgYm90aCBvbiB0aGUgcnRjd2ViIGxpc3QgYW5k
IG9mZg0KbGlzdCBzbyB3ZSBhcmUgd29ya2luZyBvbiBhbiB1cGRhdGUgd2hpY2ggd2UgaG9wZSB0
byBzdWJtaXQgd2l0aGluIHRoZSBuZXh0IGNvdXBsZSBvZiB3ZWVrcy4gPC9kaXY+DQo8ZGl2PiZu
YnNwOzwvZGl2Pg0KPGRpdj5BcyBzb21lIHBlb3BsZSBoYXZlIHJlY2VudGx5IHN0YXRlZCBvbiB0
aGUgcnRjd2ViIGxpc3QgdGhpcyBpcyBhbiBpbXBvcnRhbnQgYXNwZWN0IG9mIHdlYnJ0YyB0aGF0
IG5lZWRzIHRvIGJlIHRhY2tsZWQgdG8gZW5hYmxlIHdlYnJ0YyBkZXBsb3ltZW50cyBpbiBtYW55
IHJlc3RyaWN0ZWQgZW52aXJvbm1lbnRzLjwvZGl2Pg0KPGRpdj4mbmJzcDs8L2Rpdj4NCjxkaXY+
VGhlIGRyYWZ0IGRpc2N1c3NlcyB0aGUgdXNlIG9mIEhUVFAgQ09OTkVDVCBpbiBlbnZpcm9ubWVu
dHMgd2l0aCB3ZWIgcHJveGllcyB0byBlbmFibGUgYSB0dW5uZWwgdG8gYmUgZXN0YWJsaXNoZWQg
dG8gdGhlIFRVUk4gc2VydmVyIGJ1dCB0aGlzIGRvZXMgbm90IHJlcXVpcmUgYW55IFRVUk4gZW5o
YW5jZW1lbnRzIHdoaWNoIHNvbWUgcGVvcGxlIHNlZW0gdG8gaGF2ZSB0aG91Z2h0IHRvIGJlIHRo
ZSBjYXNlLiZuYnNwOyBBIHNtYWxsIG51bWJlcg0Kb2YgcGVvcGxlIGhhdmUgdG9sZCBtZSB0aGF0
IHRoaXMgbWlnaHQgYmUgY29udHJvdmVyc2lhbCBidXQgdGhlIHdheSBJIHNlZSBpdCBpcyB0aGF0
IHdlYnJ0YyBicmluZ3MgbmV3IHR5cGVzIG9mIG1lZGlhIHRvIHdlYiBhcHBsaWNhdGlvbnMgd2Ug
bmVlZCB0byBzcGVjaWZ5IHRoZSBpbnRlcmFjdGlvbiBiZXR3ZWVuIHdlYnJ0YyBicm93c2VycyBh
bmQgcHJveGllcyBpbiB0aGUgc2FtZSB3YXMgYXMgaXMgZG9uZSBmb3IgSFRUUCAoU2VlIDxhIGhy
ZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaHR0cGJpcy1wMi1zZW1h
bnRpY3MtMjMjc2VjdGlvbi00LjMuNiIgdGFyZ2V0PSJfYmxhbmsiPjxmb250IGNvbG9yPSJibHVl
Ij48dT5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWh0dHBiaXMtcDItc2Vt
YW50aWNzLTIzI3NlY3Rpb24tNC4zLjY8L3U+PC9mb250PjwvYT4pLjwvZGl2Pg0KPGRpdj4mbmJz
cDs8L2Rpdj4NCjxkaXY+TG9vayBmb3J3YXJkIHRvIHlvdXIgY29tbWVudHMuPC9kaXY+DQo8ZGl2
PiZuYnNwOzwvZGl2Pg0KPGRpdj5SZWdhcmRzPC9kaXY+DQo8ZGl2PkFuZHk8L2Rpdj4NCjxkaXY+
Jm5ic3A7PC9kaXY+DQo8ZGl2PiZuYnNwOzwvZGl2Pg0KPC9zcGFuPjwvZm9udD4NCg0KDQo8YnI+
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnBudGF3IG1h
aWxpbmcgbGlzdA0KPGEgaHJlZj0ibWFpbHRvOnBudGF3QGlldGYub3JnIj5wbnRhd0BpZXRmLm9y
ZzwvYT4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcG50
YXciPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcG50YXc8L2E+PC9kaXY+
PC9kaXY+IAkJIAkgICAJCSAgPC9kaXY+DQo8L2Rpdj48L2Jsb2NrcXVvdGU+PGJsb2NrcXVvdGUg
dHlwZT0iY2l0ZSI+PGRpdj48c3Bhbj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXzwvc3Bhbj48YnI+PHNwYW4+cG50YXcgbWFpbGluZyBsaXN0PC9zcGFuPjxi
cj48c3Bhbj48YSBocmVmPSJtYWlsdG86cG50YXdAaWV0Zi5vcmciPnBudGF3QGlldGYub3JnPC9h
Pjwvc3Bhbj48YnI+PHNwYW4+PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9wbnRhdyI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wbnRh
dzwvYT48L3NwYW4+PGJyPjwvZGl2PjwvYmxvY2txdW90ZT48L2JvZHk+PC9odG1sPg==

--Apple-Mail-22E49B92-08B6-4AE4-919B-3A65E8A671B3--

--_81c3a899-a578-40a9-9dc6-e120bc4dc14f_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
pntaw mailing list
pntaw@ietf.org
https://www.ietf.org/mailman/listinfo/pntaw

--_81c3a899-a578-40a9-9dc6-e120bc4dc14f_--

From tireddy@cisco.com  Sat Aug 31 20:53:12 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4377511E8111 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 20:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.979
X-Spam-Level: 
X-Spam-Status: No, score=-9.979 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvH1o7rXPyLv for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 20:53:07 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF1B11E8107 for <pntaw@ietf.org>; Sat, 31 Aug 2013 20:53:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4337; q=dns/txt; s=iport; t=1378007587; x=1379217187; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=HLPJtwXxYGaZv+9rkMj8hI9LQo8ar4KalwtGgNNbixg=; b=ldlMQYnnPjectfBqh9xYS6JANpm1n0386gmzDApjFfxezM2zYa2gYlHT 1FgxDmFl7/hWmrkh9y6DRn1/S0A4sqqInhADpYo/CXarnH6iuZ0KcMppC sMck0mbfE99Cf0VgV8Lzvv6VYy4K6e39ZYx2PppqZfMNDIUe0zKg25MSz I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAG+5IlKtJXHA/2dsb2JhbABZgwc1UcBrgR4WdIIkAQEBAwEBAQFrCwwEAgEIEQQBAQsdBycLFAkIAgQBDQUIE4dhBgy5YY9OMQcGgxeBAAOIfYsehQmQN4Mggio
X-IronPort-AV: E=Sophos;i="4.89,1000,1367971200"; d="scan'208";a="254226343"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 01 Sep 2013 03:53:06 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r813r6Eg020582 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 1 Sep 2013 03:53:06 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.8]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Sat, 31 Aug 2013 22:53:06 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, Marc Blanchet <marc.blanchet@viagenie.ca>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpVzYlJ1THI1FykWlGCDZp+nOV5mtdRzAgACuVwCAAAregIAAbEqQ
Date: Sun, 1 Sep 2013 03:53:05 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A1903C610@xmb-rcd-x10.cisco.com>
References: <52205AE1.9010807@gmail.com> <913383AAA69FF945B8F946018B75898A19034557@xmb-rcd-x10.cisco.com> <F058FF6A-35F2-4372-AAB7-345F0024E845@viagenie.ca> <9F33F40F6F2CD847824537F3C4E37DDF17BA5B9C@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17BA5B9C@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.67.234]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 03:53:12 -0000

> -----Original Message-----
> From: Hutton, Andrew [mailto:andrew.hutton@siemens-enterprise.com]
> Sent: Friday, August 30, 2013 8:37 PM
> To: Marc Blanchet; Tirumaleswar Reddy (tireddy)
> Cc: pntaw@ietf.org; Sergio Garcia Murillo
> Subject: RE: [pntaw] TURN over websockets
>=20
> P2P is something we can look at in the future but I don't see it as an op=
tion
> for enabling webrtc deployment in the near term.

I would suggest to evaluate both long term and short term needs. If Corpora=
te, Banks, Insurance and other organizations want to deploy WebRTC then we =
may want to evaluate http://tools.ietf.org/html/draft-penno-rtcweb-pcp-00#s=
ection-3.2 which achieves similar results as existing Firewalls with SIP AL=
G but without the need for DPI of the signaling protocol used for WebRTC.=20

-Tiru.

>=20
> We proposed the HTTP Connect mechanism in draft-hutton-rtcweb-nat-firewal=
l-
> considerations because it would significantly improve the chances of enab=
ling
> webrtc deployment today and requires no new implementation other than in =
the
> webrtc browser.
>=20
> Regards
> Andy
>=20
>=20
>=20
> > -----Original Message-----
> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> > Of Marc Blanchet
> > Sent: 30 August 2013 15:28
> > To: Tirumaleswar Reddy (tireddy)
> > Cc: pntaw@ietf.org; Sergio Garcia Murillo
> > Subject: Re: [pntaw] TURN over websockets
> >
> > Le 2013-08-30 =E0 09:53, "Tirumaleswar Reddy (tireddy)"
> > <tireddy@cisco.com> a =E9crit :
> >
> > > The other way to solve the Firewall problem is use PCP.
> >
> > don't agree.  it would be great, much better design, but all the
> > install base of gateways in public wifi, coffee shop wifi, hotel
> > networks, etc... are not going to do any PCP.
> >
> > Marc.
> >
> > > For more details refer to sections 3.1, 3.2 of draft
> > http://tools.ietf.org/html/draft-penno-rtcweb-pcp-00 which addresses
> > the problem of Enterprise Firewalls permitting P2P media streams.
> > >
> > > -Tiru.
> > >
> > >> -----Original Message-----
> > >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> > Behalf Of
> > >> Sergio Garcia Murillo
> > >> Sent: Friday, August 30, 2013 2:12 PM
> > >> To: pntaw@ietf.org
> > >> Subject: [pntaw] TURN over websockets
> > >>
> > >> Hi all,
> > >>
> > >> I will shoot first.
> > >>
> > >> It is great to finally see some real interest in what I consider to
> > be
> > >> the blocking point for webrtc in order to run business on top of it,
> > >> which is the ability to be able to connect through corporate
> > firewalls.
> > >>
> > >> I have seen some people arguing that with just TURN over TCP on port
> > 443
> > >> the problem will be solved, but I seriously doubt it. Neither TURN
> > over
> > >> SSL would do, as most web filters do DPI and will not enable the
> > >> connection. Also, I have heard lots of voices that says we are
> > trying to
> > >> override network admin policies with dirty tricks. With whom, I
> > could agree.
> > >>
> > >> So, the only way I see to move forward and overcome this issues is
> > by
> > >> playing according to the WEB rules, and use HTTP standards to enable
> > >> media connectivity in WebRTC that would play nicely with current
> > >> corporate HTTP proxies and web filters.
> > >>
> > >> And,  for me the most viable solution would be to enable TURN over
> > >> websockets. As most WebRTC services relay on websockets in one way
> > or
> > >> another for signaling, we could assume that media would work on 100%
> > of
> > >> the cases where signaling is working today.
> > >> Also, as it is an http based solution, network administrators could
> > >> apply corporate policies and block connections to not-trusted TURN
> > servers.
> > >>
> > >> Best regards
> > >> Sergio
> > >> _______________________________________________
> > >> pntaw mailing list
> > >> pntaw@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/pntaw
> > > _______________________________________________
> > > pntaw mailing list
> > > pntaw@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pntaw
> >
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw

From tireddy@cisco.com  Sat Aug 31 21:03:58 2013
Return-Path: <tireddy@cisco.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4E311E8111 for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 21:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.51
X-Spam-Level: 
X-Spam-Status: No, score=-10.51 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XC6IJ9RZsiLF for <pntaw@ietfa.amsl.com>; Sat, 31 Aug 2013 21:03:53 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 10BF511E8107 for <pntaw@ietf.org>; Sat, 31 Aug 2013 21:03:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5576; q=dns/txt; s=iport; t=1378008233; x=1379217833; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Y3VQYQs/FSb2i8TW+DOHxYC+uplupH9Ruh19JJE72cM=; b=DFtyCABJx2una477KcUhU+vDndZeOcUUEvyQd/3ctMQkrC/Nt9SXgWIW zMBaNEy/K4QQIyPZDJYZjipMFmYX81MnO9A31CLEjl7v9wlMt1J+q3yt8 VfVWwHBgjzFQBiT266pmWmc7RaVRLMsGhARNy5hIr9R/g9P+HhpatM2ak I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAM27IlKtJV2Z/2dsb2JhbABDFoMHNVHAa4EeFnSCJAEBAQMBAQEBawsMBAIBCBEEAQELCRQHJwsUCQgCBA4FCBOHYQYMuWIEji4BgR8xBwaDF4EAA4h9ix6VQIMggio
X-IronPort-AV: E=Sophos;i="4.89,1000,1367971200"; d="scan'208";a="254208302"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 01 Sep 2013 04:03:52 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r8143qcZ004625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 1 Sep 2013 04:03:52 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.8]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Sat, 31 Aug 2013 23:03:52 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Parthasarathi R <partha@parthasarathi.co.in>, "'Sergio Garcia Murillo'" <sergio.garcia.murillo@gmail.com>, "'Stach, Thomas'" <thomas.stach@siemens-enterprise.com>
Thread-Topic: [pntaw] TURN over websockets
Thread-Index: AQHOpVzYlJ1THI1FykWlGCDZp+nOV5muA8IAgAAGGgCAAcxlgIAAbzlg
Date: Sun, 1 Sep 2013 04:03:51 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A1903D695@xmb-rcd-x10.cisco.com>
References: <52205AE1.9010807@gmail.com> <F81CEE99482EFE438DAE2A652361EE12179BF94B@MCHP04MSX.global-ad.net> <5220968E.2050708@gmail.com> <004e01cea666$98e9b090$cabd11b0$@co.in>
In-Reply-To: <004e01cea666$98e9b090$cabd11b0$@co.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.67.234]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pntaw@ietf.org" <pntaw@ietf.org>
Subject: Re: [pntaw] TURN over websockets
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 04:03:58 -0000

> -----Original Message-----
> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf Of
> Parthasarathi R
> Sent: Saturday, August 31, 2013 9:55 PM
> To: 'Sergio Garcia Murillo'; 'Stach, Thomas'
> Cc: pntaw@ietf.org
> Subject: Re: [pntaw] TURN over websockets
>=20
> Hi all,
>=20
> In case of (firewall) Policy vs protocol, the policy is the final decisio=
n
> maker and not the protocol. In case TURN over WebSocket is chosen, it is =
a
> matter of time for firewall policy enhancement to block these rat holes i=
n
> the network.
>=20
> Please try to understand from bank perspective that bank network security=
 is
> more important and end-user *MUST NOT* be allowed to use the traffic whic=
h
> bank could not intercept.

+1

-Tiru.

>=20
> Thanks
> Partha
>=20
> > -----Original Message-----
> > From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On Behalf
> > Of Sergio Garcia Murillo
> > Sent: Friday, August 30, 2013 6:27 PM
> > To: Stach, Thomas
> > Cc: pntaw@ietf.org
> > Subject: Re: [pntaw] TURN over websockets
> >
> > Hi Thomas,
> >
> > Inline.
> >
> > El 30/08/2013 14:34, Stach, Thomas escribi=F3:
> > > Sergio,
> > >
> > > Some comments inline
> > >
> > >> -----Original Message-----
> > >> From: pntaw-bounces@ietf.org [mailto:pntaw-bounces@ietf.org] On
> > Behalf
> > >> Of Sergio Garcia Murillo
> > >> Sent: Freitag, 30. August 2013 10:42
> > >> To: pntaw@ietf.org
> > >> Subject: [pntaw] TURN over websockets
> > >>
> > >> Hi all,
> > >>
> > >> I will shoot first.
> > >>
> > >> It is great to finally see some real interest in what I consider to
> > be
> > >> the blocking point for webrtc in order to run business on top of it,
> > >> which is the ability to be able to connect through corporate
> > firewalls.
> > >>
> > >> I have seen some people arguing that with just TURN over TCP on port
> > >> 443
> > >> the problem will be solved, but I seriously doubt it. Neither TURN
> > over
> > >> SSL would do, as most web filters do DPI and will not enable the
> > >> connection. Also, I have heard lots of voices that says we are
> > trying
> > >> to
> > >> override network admin policies with dirty tricks. With whom, I
> > could
> > >> agree.
> > > [TS] I'm not sure if you are referencing draft-hutton-rtcweb-nat-
> > firewall-considerations here.
> > > Nevertheless the draft mentions TURN over TCP to port 443.
> > And also does mention TURN over websockets, while it consider it to be
> > not necessary.
> > > The goal behind this is certainly not to sneak WEBRTC media streams
> > through heavily fortified networks that have DPI deployed.
> > > The goal rather to address a scenario e.g. at a small hotel with a
> > not-so-skilled network admin, that opened his firewall on TCP port
> > 80/443 to allow its guests to do some web browsing, but is afraid of
> > opening its firewall for UDP traffic.
> > > If we want to deploy WEBRTC in such an environment TURN over TLS to
> > port 443 would do the job.
> >
> > Maybe that is your scenario, definitively not mine. Try doing some
> > serious business with banking, insurance or such kind of sector and you
> > won't find no-so-skilled admin but a full flavor DPI web filter in
> > place. Then try to go to their admin it department and ask them to do
> > some funny configuration on their firewalls.
> >
> > I really doubt that TURN over TLS would work in 100% of this scenarios.
> >
> >
> > >> So, the only way I see to move forward and overcome this issues is
> > by
> > >> playing according to the WEB rules, and use HTTP standards to enable
> > >> media connectivity in WebRTC that would play nicely with current
> > >> corporate HTTP proxies and web filters.
> > > [TS] Playing nicely with HTTP proxies is also a use case draft-
> > hutton-rtcweb-nat-firewall-considerations.
> > > Usage of the HTTP CONNECT method is proposed here. The request URI
> > would include the TURN server (preferably even to the well-known STUN
> > port). If the network admin put the TURN server into its whitelist,
> > that could hardly be considered as sneaking unwanted traffic through.
> > >> And,  for me the most viable solution would be to enable TURN over
> > >> websockets.
> > > [TS] This would require updates to the TURN protocol and the TURN
> > software, whereas the proposals in draft-hutton-rtcweb-nat-firewall-
> > considerations use the original transports.
> >
> > Yes, it would require additions to the TURN protocol and new
> > developments on TURN software.
> >
> > > As most WebRTC services relay on websockets in one way or
> > >> another for signaling, we could assume that media would work on 100%
> > of
> > >> the cases where signaling is working today.
> > >> Also, as it is an http based solution, network administrators could
> > >> apply corporate policies and block connections to not-trusted TURN
> > >> servers.
> > > [TS] which could also be done by white-listing the TURN server
> > address via TCP without any further intermediate HTTP/Websocket layers.
> >
> > Try to open a firewall in a corporate location, good luck! White
> > listing
> > in the web filter would be much more doable.
> >
> > Best regards
> > Sergio
> > _______________________________________________
> > pntaw mailing list
> > pntaw@ietf.org
> > https://www.ietf.org/mailman/listinfo/pntaw
>=20
> _______________________________________________
> pntaw mailing list
> pntaw@ietf.org
> https://www.ietf.org/mailman/listinfo/pntaw
