Re: [pntaw] draft-hutton-rtcweb-nat-firewall-considerations

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Wed, 04 September 2013 14:01 UTC

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 5FE2D21E80C2 for <pntaw@ietfa.amsl.com>; Wed, 4 Sep 2013 07:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level:
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, 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 vl9IszFF+Tnu for <pntaw@ietfa.amsl.com>; Wed, 4 Sep 2013 07:01:31 -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 4342C11E81B5 for <pntaw@ietf.org>; Wed, 4 Sep 2013 07:01:31 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 5A41B23F04B7; Wed, 4 Sep 2013 16:01:28 +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; Wed, 4 Sep 2013 16:01:28 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, "pntaw@ietf.org" <pntaw@ietf.org>
Thread-Topic: [pntaw] draft-hutton-rtcweb-nat-firewall-considerations
Thread-Index: Ac6li3yHiavbr66zRBS13ndrj3kqWQBHbTyAAAGtc4AAscEfkA==
Date: Wed, 04 Sep 2013 14:01:27 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BAB2D8@MCHP04MSX.global-ad.net>
References: <9F33F40F6F2CD847824537F3C4E37DDF17BA590C@MCHP04MSX.global-ad.net> <BLU169-W550866EED2D3C94D56050B93370@phx.gbl> <BLU404-EAS263C160169554B82B52076293370@phx.gbl>
In-Reply-To: <BLU404-EAS263C160169554B82B52076293370@phx.gbl>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
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: Wed, 04 Sep 2013 14:01:36 -0000

On: 01 September 2013 04:09 Bernard Aboba [mailto:bernard_aboba@hotmail.com] wrote:
> 
> 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 emerging, and we do want WebRTC to work in those cases.
> 

[AndyH] Agreed we will need to have a deeper look at IPV6 issues in a future update.