IETF Logo Mail Archive

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

Melinda Shore <melinda.shore@gmail.com> Mon, 23 September 2013 16:07 UTC

Return-Path: <melinda.shore@gmail.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 292A421F9F0E for <pntaw@ietfa.amsl.com>; Mon, 23 Sep 2013 09:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level:
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[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 GJohW1siM7oX for <pntaw@ietfa.amsl.com>; Mon, 23 Sep 2013 09:07:19 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 0540C21F99F3 for <pntaw@ietf.org>; Mon, 23 Sep 2013 09:07:04 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so3433260pdi.27 for <pntaw@ietf.org>; Mon, 23 Sep 2013 09:07:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=J83h5TidYsCXG6QRiqShz79MXnP3DR39dQTY4eEjJDs=; b=iZeNyvAeeuMBxTsNhGq3G7CaUx7RkyQYkkmYTO0yus8eBBuKVHbAJmBDXCyyspYP0R r7EX1Mpvl9bUjsr1mQW/VnHi5iB0YetNYWaDDIZwG98k2DeO5vLxfzRaiLMQN8Gfo3ot 5XP9+MSOZrPUJdqz7Ymr4q7KGi7WNqBpdIAQUcIFi3h4hjJb9r2w6HctwmR73ef+0F5M ux29emV1O1VsHdW2suXHK/9ou8mFo3zsE1PU2EGfCsXns27aVarxqJFHp2MwemysqPQV YKgcLhDk/RGoZlFu0RLnxXixM863srauBw9ciDSdvAyf9lMB2OgYEdOGJdP4+PTe9FWM iQ8w==
X-Received: by 10.66.121.131 with SMTP id lk3mr25772827pab.61.1379952423301; Mon, 23 Sep 2013 09:07:03 -0700 (PDT)
Received: from spandex.local (63-140-98-62.dynamic.dsl.acsalaska.net. [63.140.98.62]) by mx.google.com with ESMTPSA id y5sm35083960pbs.18.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 23 Sep 2013 09:07:02 -0700 (PDT)
Message-ID: <52406723.8030203@gmail.com>
Date: Mon, 23 Sep 2013 08:06:59 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Markus.Isomaki@nokia.com
References: <9F33F40F6F2CD847824537F3C4E37DDF17BCF3A5@MCHP04MSX.global-ad.net> <523CCD06.3030902@gmail.com> <BLU169-W136A55AC013DA147313576D93220@phx.gbl> <523CD42E.8070102@gmail.com> <BLU169-W82036280852F26ED26283C93230@phx.gbl> <523D4F17.2040202@gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF17BD01A8@MCHP04MSX.global-ad.net> <CALDtMrL5pT3MfbQufCphEKq0-pXj+JcfwW__wzG3T6wZ=TuWhg@mail.gmail.com> <9F33F40F6F2CD847824537F3C4E37DDF17BD08EA@MCHP04MSX.global-ad.net> <CALDtMrLcUrxseyiaPc_0AWJw3HPdaBuAS+xpviT2q=y4zmdNgw@mail.gmail.com> <523FD5FD.8030601@gmail.com> <CALDtMrK=9D3qXXK6EeWF4RDk26GHPDgkYfQzdJpD33JNK_MeRw@mail.gmail.com> <523FE3E7.3060101@gmail.com> <E44893DD4E290745BB608EB23FDDB7620A0C0969@008-AM1MPN1-043.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A0C0969@008-AM1MPN1-043.mgdnok.nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: mom040267@gmail.com, pntaw@ietf.org
Subject: Re: [pntaw] New version of 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: Mon, 23 Sep 2013 16:07:20 -0000

On 9/23/13 1:35 AM, Markus.Isomaki@nokia.com wrote:
> There will be networks and administrators that explicitly want to
> restrict WebRTC. I think one part of the WebRTC firewall traversal
> "solution" needs to be an explanation HOW they can do it.

That seems reasonable to me - the network administrator really
needs to be able to say "no" to certain kinds of traffic,
including WebRTC traffic.  I'm not sure that it's possible
to allow more finely-grained policy, which might be desirable,
but this is a start and something to discuss with people who
actually run networks.

Melinda

v2.23.0 | Report a Bug | By Email