Re: [rtcweb] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-00.txt

Cameron Byrne <cb.list6@gmail.com> Mon, 11 March 2013 18:07 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E5E011E81A7 for <rtcweb@ietfa.amsl.com>; Mon, 11 Mar 2013 11:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level:
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, NO_RELAYS=-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 gU2UnKW6COxS for <rtcweb@ietfa.amsl.com>; Mon, 11 Mar 2013 11:07:28 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 97C7B11E81C6 for <rtcweb@ietf.org>; Mon, 11 Mar 2013 11:07:27 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id 12so2388771wgh.3 for <rtcweb@ietf.org>; Mon, 11 Mar 2013 11:07:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SvdG8xXBDVEy0bCIgT0OIMMudXJ5AwBnhFhS2ku7o0Y=; b=k9DYzi3Shx58po4Oy7uPH/nP1BtgayNW/8jJ3NdINMcXMunuNxn+jS05UZI00E/EEV IusYrz47Bz7FiXV/zO2fzp8f3uiRxTkknHmOMK51z5p6Tjby6Aj6HttSkSimFGdo6/gE oBewja5W6kOuEQ89MhP8SA6qhbQwxMn08xfpQsOxPYjE8HDbWlZkM0D0YuWct6jCHJJE khEq5PzJp71wJVWnK8W0HBqSjeSfJ9x92/YH/Kfe5s7kwkhQUlROUUkSFB3VNYIvjcG5 mPPYE82xv7qJm5ER/UAtSHKfn4/bHLIsCa6PWpUErkejrG7iF7RrUgftWtv3Hkd/th7f exMA==
MIME-Version: 1.0
X-Received: by 10.194.242.163 with SMTP id wr3mr21144084wjc.35.1363025246459; Mon, 11 Mar 2013 11:07:26 -0700 (PDT)
Received: by 10.194.20.35 with HTTP; Mon, 11 Mar 2013 11:07:26 -0700 (PDT)
In-Reply-To: <513E146D.4060009@alvestrand.no>
References: <45A697A8FFD7CF48BCF2BE7E106F06040901B274@xmb-rcd-x04.cisco.com> <513E146D.4060009@alvestrand.no>
Date: Mon, 11 Mar 2013 11:07:26 -0700
Message-ID: <CAD6AjGSBGY2EEP+yNMZ4sbj6O-XP7hi84PVFMXHdT+nJg8iTzA@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-00.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 18:07:28 -0000

On Mon, Mar 11, 2013 at 10:29 AM, Harald Alvestrand
<harald@alvestrand.no> wrote:
> On 03/11/2013 06:04 PM, Reinaldo Penno (repenno) wrote:
>>
>> Hello,
>>
>> Why not use Port Control Protocol (PCP) to control Firewalls and NATs
>> explicitly?
>
> We can switch to that as soon as 100% of firewalls support it - until then,
> we have to be able to rely on other techniques.
>
> That's the deployment problem in a nutshell... I don't understand how the
> first firewall gets an advantage from having PCP, given that none of the
> apps support it, and I don't understand how the first app gets an advantage
> from having PCP, given that no firewalls support it.
>
> If PCP succeeds despite my misgivings, we can certainly revisit the issue.
>

I am also pessimistic on PCP being deployed and would rather not
confuse the WebRTC community into thinking PCP is requirement for
WebRTC.  I believe TURN is much better solution.  As mobile network
operator, i feel much more comfortable offering TURN as a solution to
customers than PCP.

CB


>
>>
>> Thanks,
>>
>> On 3/11/13 9:56 AM, "Hutton, Andrew"
>> <andrew.hutton@siemens-enterprise.com> wrote:
>>
>>> FYI - We submitted this draft today it relates to the requirements in the
>>> use case draft for rtcweb to work in the presence of firewalls and http
>>> proxies etc.
>>>
>>> Look forward to feedback and hope that this can be considered for
>>> adoption by the working group.
>>>
>>> Regards
>>> Andy
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: i-d-announce-bounces@ietf.org
>>> [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
>>> internet-drafts@ietf.org
>>> Sent: 11 March 2013 06:01
>>> To: i-d-announce@ietf.org
>>> Subject: I-D Action:
>>> draft-hutton-rtcweb-nat-firewall-considerations-00.txt
>>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>>
>>>
>>>         Title           : RTCWEB Considerations for NATs, Firewalls and
>>> HTTP
>>> proxies
>>>         Author(s)       : Thomas Stach
>>>                           Andrew Hutton
>>>                           Justin Uberti
>>>         Filename        :
>>> draft-hutton-rtcweb-nat-firewall-considerations-00.txt
>>>         Pages           : 8
>>>         Date            : 2013-03-11
>>>
>>> Abstract:
>>>    This document describes mechanism to enable media stream
>>>    establishment in the presence of NATs, firewalls and HTTP proxies.
>>>    HTTP proxy and firewall policies applied in many private network
>>>    domains introduce obstacles to the successful establishment of media
>>>    stream via RTCWEB.  This document examines some of these policies and
>>>    develops requirements on the web browsers designed to provide the
>>>    best possible chance of media connectivity between RTCWEB peers.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>>
>>> https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-consider
>>> ations
>>>
>>> There's also a htmlized version available at:
>>>
>>> http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations
>>> -00
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>> _______________________________________________
>>> rtcweb mailing list
>>> rtcweb@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb