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

"Hutton, Andrew" <andrew.hutton@unify.com> Mon, 20 January 2014 12:11 UTC

Return-Path: <andrew.hutton@unify.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 842D71A012B for <rtcweb@ietfa.amsl.com>; Mon, 20 Jan 2014 04:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U5MokjOq5nPQ for <rtcweb@ietfa.amsl.com>; Mon, 20 Jan 2014 04:11:31 -0800 (PST)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id A08F01A0123 for <rtcweb@ietf.org>; Mon, 20 Jan 2014 04:11:30 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id CB4C71EB84DA for <rtcweb@ietf.org>; Mon, 20 Jan 2014 13:11:29 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.183]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Mon, 20 Jan 2014 13:11:15 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
Thread-Index: AQHPFdOd2Vn6yFd4yUSx85JgARaXd5qNhV9A
Date: Mon, 20 Jan 2014 12:11:15 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17CBE39F@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [rtcweb] FW: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 12:11:32 -0000

Would like to notify the RTCWEB list of the update although comments I believe still need to be made on the PNTAW list.

I updated draft-hutton-rtcweb-nat-firewall-consideration.

The main change is that the draft now explores the different options that are available for handling such things as HTTP Proxies in a WebRTC environment and no longer recommends a specific solution. 

Would be good to restart the discussion on these options and determining the best way forward to ensuring we get some defined standardized behavior for WebRTC for these scenarios.

So please go ahead and make comments on the PNTAW list please.

Regards
Andy



-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: 20 January 2014 11:35
To: i-d-announce@ietf.org
Subject: I-D Action: draft-hutton-rtcweb-nat-firewall-considerations-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : RTCWEB Considerations for NATs, Firewalls and HTTP proxies
        Authors         : Thomas Stach
                          Andrew Hutton
                          Justin Uberti
	Filename        : draft-hutton-rtcweb-nat-firewall-considerations-03.txt
	Pages           : 14
	Date            : 2014-01-20

Abstract:
   This document describes mechanism to enable media stream
   establishment for Real-Time Communication in WEB-browsers (WebRTC) in
   the presence of network address translators, firewalls and HTTP
   proxies.  HTTP proxy and firewall deployed in many private network
   domains introduce obstacles to the successful establishment of media
   stream via WebRTC.  This document examines some of these deployment
   scenarios and specifies requirements on WebRTC enabled web browsers
   designed to provide the best possible chance of media connectivity
   between WebRTC peers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hutton-rtcweb-nat-firewall-considerations/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-hutton-rtcweb-nat-firewall-considerations-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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