IETF Logo Mail Archive

Re: [rtcweb] Purpose of PNTAW list

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Fri, 30 August 2013 11:48 UTC

Return-Path: <andrew.hutton@siemens-enterprise.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 5FE3311E80F2 for <rtcweb@ietfa.amsl.com>; Fri, 30 Aug 2013 04:48:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level:
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 cnE9D6f41Yk2 for <rtcweb@ietfa.amsl.com>; Fri, 30 Aug 2013 04:48:53 -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 C2B8E11E80EA for <rtcweb@ietf.org>; Fri, 30 Aug 2013 04:48:52 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 1AD5B23F0632; Fri, 30 Aug 2013 13:48:48 +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 13:48:47 +0200
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Purpose of PNTAW list
Thread-Index: AQHOpUdip3yw+R+KLESeNusnNzuK9JmtnhnA
Date: Fri, 30 Aug 2013 11:48:47 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BA52FC@MCHP04MSX.global-ad.net>
References: <522036FD.30007@ericsson.com>
In-Reply-To: <522036FD.30007@ericsson.com>
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: Re: [rtcweb] Purpose of PNTAW list
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: Fri, 30 Aug 2013 11:48:57 -0000

One of the prime reasons for the PNTAW list was to discuss http://tools.ietf.org/html/draft-hutton-rtcweb-nat-firewall-considerations-01. 

I might be being pedantic but this draft discusses the behavior of browsers in the presence of Web Proxies, Firewalls and TURN servers. It does not specify the behavior or propose any change to the behavior of anything other than the WebRTC browser so according to the definition below discussion should remain here. However I know that is not the intention of the chairs and I will move discussion on this draft to PNTAW.

Sorry to raise this again but I previously argued for keeping this draft in RTCWEB because it is all about WebRTC browser behavior and I still hope that it will one day be adopted as a RTCWEB WG draft.

Regards
Andy





> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Magnus Westerlund
> Sent: 30 August 2013 07:09
> To: rtcweb@ietf.org
> Subject: [rtcweb] Purpose of PNTAW list
> 
> Greetings RTCWEB,
> 
> As you have seen the chairs recently asked for the creation of a
> non-working group mailing list called "pntaw" (For "Proxies, NATs, TURN
> and webrtc").  The aim of that list is to enable folks involved in HTTP
> proxy development, NAT Traversal, and TURN to have a focused discussion
> on behavior of those systems in the presence of RTCWEB. Because we
> wanted an overlap with a different set of folks than are typically
> involved in RTCWEB (and because we occasionally have a flood of
> messages), we requested the separate list and topic area.
> 
> It is not, however, planned to be a WG; if there is discussion there
> that results in the need for protocol work, it will go to an existing
> WG, possibly this one.
> 
> So, when should you start discussing an issue there rather than here?
> If the primary purpose of a document is to describe or change the
> behavior of a proxy, NAT, or TURN server, it goes there.  If not, it
> stays here.  If a document currently mixes topic so that some
> discussion
> is in a document but it is not the documents primary purpose, please
> disucss with the chairs how to proceed.
> 
> Hope that helps,
> 
> Magnus Westerlund
> Ted Hardie
> Cullen Jennings
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.10.0 | Report a Bug | By Email