Re: [Int-area] Warren Kumari's Discuss on draft-ietf-intarea-broadcast-consider-08: (with DISCUSS and COMMENT)
Rolf Winter <rolf.winter@hs-augsburg.de> Thu, 25 January 2018 13:35 UTC
Return-Path: <rolf.winter@hs-augsburg.de>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C096120725; Thu, 25 Jan 2018 05:35:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Ve4fx-5Mf-3W; Thu, 25 Jan 2018 05:35:21 -0800 (PST)
Received: from fly2.rz.hs-augsburg.de (fly2.RZ.HS-Augsburg.DE [141.82.11.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02B3D12D84C; Thu, 25 Jan 2018 05:35:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by fly2.rz.hs-augsburg.de (Postfix) with ESMTP id ACC65120C63; Thu, 25 Jan 2018 14:34:54 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at hs-augsburg.de
Received: from fly2.rz.hs-augsburg.de ([127.0.0.1]) by localhost (fly2.rz.hs-augsburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rpHVHFRqC-2p; Thu, 25 Jan 2018 14:34:53 +0100 (CET)
Received: from [192.168.1.148] (nightswatch.informatik.hs-augsburg.de [141.82.79.79]) by fly2.rz.hs-augsburg.de (Postfix) with ESMTPSA id D7B7E120A37; Thu, 25 Jan 2018 14:34:52 +0100 (CET)
To: Warren Kumari <warren@kumari.net>, The IESG <iesg@ietf.org>
Cc: int-area@ietf.org, draft-ietf-intarea-broadcast-consider@ietf.org, intarea-chairs@ietf.org
References: <151683830485.15937.3354694058245169389.idtracker@ietfa.amsl.com>
From: Rolf Winter <rolf.winter@hs-augsburg.de>
Message-ID: <ac3e169b-30ce-0b97-a6a2-b4397c467631@hs-augsburg.de>
Date: Thu, 25 Jan 2018 14:35:09 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <151683830485.15937.3354694058245169389.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/SvDAFQWbmOmuOGzyH25toEb_H4c>
Subject: Re: [Int-area] Warren Kumari's Discuss on draft-ietf-intarea-broadcast-consider-08: (with DISCUSS and COMMENT)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 13:35:24 -0000
Warren, I think I understand the issue you have with that bit of text. draft-perkins-intarea-multicast-ieee802 discusses a bunch of bcast/mcast management features that certain classes of APs provide. We have one example of this in the draft (and should point to draft-perkins-intarea-multicast-ieee802 for more examples). The problem is, that these features target specific protocols, i.e. ones that are standardized and worth paying attention to. The rest can only be dealt with by not rebroadcasting frames over the wireless medium. That is the best you can do. And it is done for performance reasons on networks such as the IETF meeting network, but I guess not for privacy reasons. All we really wanted to say was, that as a network administrator you can protect your users from the privacy risks described in the document, but you might affect certain applications, potentially rendering them useless. And we wanted it to be value-free because this in not a black and white thing in my personal opinion. As a suggestion, we would add draft-mcbride-mboned-wifi-mcast-problem-statement and respective text. Since we already have the other draft in the document, we would point to the already implemented things in draft-perkins-intarea-multicast-ieee802, which really makes a good point for reusing IETF-specified protocols and not invent something new. Would that clear your discuss? Best, Rolf Am 25.01.18 um 00:58 schrieb Warren Kumari: > Warren Kumari has entered the following ballot position for > draft-ietf-intarea-broadcast-consider-08: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-intarea-broadcast-consider/ > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > Sorry for the late DISCUSS. I'm likely to clear after discussions on the call > tomorrow. > > I'm somewhat surprised at how much this document glosses over the (sometimes > extensive) broadcast/multicast twiddling that Access Points and similar do (a > fair bit of discussion of which can be found in > draft-perkins-intarea-multicast-ieee802 (which I think will be expiring) or > draft-mcbride-mboned-wifi-mcast-problem-statement). Simply saying: "A feature > not uncommonly found on access points e.g. is to filter broadcast and multicast > traffic. This will potentially break certain applications or some of their > functionality but will also protect the users from potentially leaking > sensitive information." seems to be shrugging off all of the privacy benefits > (or possibly harms) that this might create. > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > I found this sentence very confusing: > " For one, non-standard protocols will likely not receive operational > attention and support in making them more secure such as e.g. DHCP snooping > does for DHCP because they typically are not documented. " -- I know what it > is trying to say, but I don't think it accomplishes what it intends to. > > > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area >
- [Int-area] Warren Kumari's Discuss on draft-ietf-… Warren Kumari
- Re: [Int-area] Warren Kumari's Discuss on draft-i… Rolf Winter
- Re: [Int-area] Warren Kumari's Discuss on draft-i… Warren Kumari