[secdir] Secdir last call review of draft-ietf-mboned-ieee802-mcast-problems-09

Kyle Rose via Datatracker <noreply@ietf.org> Mon, 14 October 2019 03:32 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F9D6120018; Sun, 13 Oct 2019 20:32:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kyle Rose via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: mboned@ietf.org, ietf@ietf.org, draft-ietf-mboned-ieee802-mcast-problems.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Kyle Rose <krose@krose.org>
Message-ID: <157102397341.20776.9338396539567675909@ietfa.amsl.com>
Date: Sun, 13 Oct 2019 20:32:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/YfNi6-wnCoWKtrgHjm42pmaKJt4>
Subject: [secdir] Secdir last call review of draft-ietf-mboned-ieee802-mcast-problems-09
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2019 03:32:54 -0000

Reviewer: Kyle Rose
Review result: Has Nits

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
 Document editors and WG chairs should treat these comments just like any other
last call comments.

I marked this "ready with nits" because I see no serious security or privacy
considerations, but I'm confused by the wording in section 7, which begins:

q( This section will provide some recommendations about the usage and
combinations of the multicast enhancements described in Section 4 and Section
5. )

and then proceeds to provide little in the way of such recommendations. Maybe
the phrasing here is just awkward?


Reference dot11aa
(https://standards.ieee.org/findstds/standard/802.11aa-2012.pdf) gives me a
404. Maybe I simply lack the appropriate decoder ring?

The IETF meeting network is referenced three times in section 5.1. For example,

q( The distribution of users on wireless networks / subnets changes from one
IETF meeting to the next (e.g SSIDs are renamed, some SSIDs lose favor, etc). 
This makes utilization for particular SSIDs difficult to predict ahead of time,
but usage can be monitored as attendees use the different networks. )

This feels like a non-sequitur. Maybe some introductory text about using the
IETF meetings as an exemplar would make this read a little better, but it seems
like the advice to operators here should be generic and not connected to
particular goals for network connectivity at IETF meetings.