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

"Reinaldo Penno (repenno)" <repenno@cisco.com> Mon, 11 March 2013 17:04 UTC

Return-Path: <repenno@cisco.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 50F2A21F89C5 for <rtcweb@ietfa.amsl.com>; Mon, 11 Mar 2013 10:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.443
X-Spam-Level:
X-Spam-Status: No, score=-10.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 HktF2VmPmWyI for <rtcweb@ietfa.amsl.com>; Mon, 11 Mar 2013 10:04:19 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 8087021F8900 for <rtcweb@ietf.org>; Mon, 11 Mar 2013 10:04:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2501; q=dns/txt; s=iport; t=1363021459; x=1364231059; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=rnTInLK7kMEU8CxFsuO8YpBXeh9jZ5fjgkFYaHvUVac=; b=O+tw6YuBf0g21B+fHLHw/HAn9c5bTQHllpUaNF2kKvXB7OaRL9rDm7sS gyJtzNzl2yAbtVPsnUPbT79+XIoRphJAwkqw4s8b91uFtFbeHGqAxGUpT TIxwgOvCTXe5fqIotnTUs1VkIIu4gU2AQrfCevnp4zr5NBgExD0ZYhTwn U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFACUOPlGtJXG//2dsb2JhbABDxGCBXRZ0gikBAQEEAQEBNzQXBgEIEQQBAQsUCS4LFAgBCAIEARIIAYgKDL0/F45dJg0FBoJZYQOXc4pBhRaBVIE2gig
X-IronPort-AV: E=Sophos;i="4.84,825,1355097600"; d="scan'208";a="186216565"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 11 Mar 2013 17:04:19 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2BH4Iv9027478 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 Mar 2013 17:04:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Mon, 11 Mar 2013 12:04:18 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-00.txt
Thread-Index: AQHOHj9zQPNB80XASUa1nEzDk7aFy5igtR3Q///hxoA=
Date: Mon, 11 Mar 2013 17:04:17 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040901B274@xmb-rcd-x04.cisco.com>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF06894839@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.86.68]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5FEFC0CBBC5C574B86756B6A92E1CF46@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 17:04:20 -0000

Hello,

Why not use Port Control Protocol (PCP) to control Firewalls and NATs
explicitly? 

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