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

Michael McBride <michael.mcbride@futurewei.com> Mon, 14 October 2019 16:16 UTC

Return-Path: <michael.mcbride@futurewei.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75BCD120116; Mon, 14 Oct 2019 09:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
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 CvgITaU_VvCX; Mon, 14 Oct 2019 09:16:57 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750099.outbound.protection.outlook.com [40.107.75.99]) (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 D8B461200CC; Mon, 14 Oct 2019 09:16:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WratZNnMgRPB+x5HHPZQSdFoC7zdx7w57SaUcAep3OTjkv8oTlNpirTI3dNgM+nu7XJ46lFVhgdyr6ORDjHBj1Aj3Vgz7UKcPfEGGM5ETaaBW2kSe7qrHpkWEmRvEyCv0SV1G7ek6PdNZm+WoqAZdC/jqAmgRRrqbcxPpy54qFxpjTTs0pZo5Mrc1RFpFopc2bW3296mJpiSXw4/hhSJWiazHDbqJOKMwMI4D28/fx+cc/7QxwpzcGY+ZksRPgC7Gh+nEktW0TGS+2WyyqOqh7Ujq3Z5/Bh5m53V95LKegfb5arcJBJVsO32XOoatgm/KcIbnlTu6kUxFbgiVEReJQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=O138rDUETJPCMk3A0+mHRm6+px6CxpEntKPcoGVTAr8=; b=NH2HU0e26cyzPv8pIlbd7n31R70viIJZpoKdDZqX22x0lztof8Kfor04GC2TIUoyfXyFP7bSKGM5rsFq0YEOvXmmYbjs/KPMeAD3wk0sUfZuyi7mHWrkxCzSzyCRquB94DkTdzPGSQ802oVkaO5TXb5RFZqEiB2QDJifCOitFMwf4fGWzR7ACmqDnnlSTsNE4MyYOW3Uy7zbT7qiZ2naI+7I6Jt3vaiVZujug0t5EOgA5KrQhvDlwPzUAUAYYYVnm+dpju36LduNu8gtzDfo9TXCnqJU2fDKlC80YEVrwAGzTzT+UiZ2oBikRkStoXUc4WElA/aPFn85fkHGTkNsVQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=O138rDUETJPCMk3A0+mHRm6+px6CxpEntKPcoGVTAr8=; b=dUmifLIGFwZKMYvAdG/5GNezinPSKKp58zwWy9yu3NXgM5kxXgjoRb+sDiJJAf+JGwvUvyGcwFPBLU/QwCoYNcTiFko1rOFx26kWvILdNWtXJXoTf+S3g7F+DDbR1IzUvL/gNTTxG+qmHeKuO+Tb4FuvkklP6/e70/ZDqeXmnZA=
Received: from BYAPR13MB2807.namprd13.prod.outlook.com (20.178.238.209) by BYASPR01MB0038.namprd13.prod.outlook.com (20.177.187.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.22; Mon, 14 Oct 2019 16:16:53 +0000
Received: from BYAPR13MB2807.namprd13.prod.outlook.com ([fe80::e407:1ca7:7ee9:e0f3]) by BYAPR13MB2807.namprd13.prod.outlook.com ([fe80::e407:1ca7:7ee9:e0f3%7]) with mapi id 15.20.2347.023; Mon, 14 Oct 2019 16:16:53 +0000
From: Michael McBride <michael.mcbride@futurewei.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Kyle Rose <krose@krose.org>, "secdir@ietf.org" <secdir@ietf.org>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
CC: "mboned@ietf.org" <mboned@ietf.org>, "draft-ietf-mboned-ieee802-mcast-problems.all@ietf.org" <draft-ietf-mboned-ieee802-mcast-problems.all@ietf.org>
Thread-Topic: Secdir last call review of draft-ietf-mboned-ieee802-mcast-problems-09
Thread-Index: AQHVgkAUaaRgATgiN0WUu+tThnkKZKdZuE8AgACUnnA=
Date: Mon, 14 Oct 2019 16:16:52 +0000
Message-ID: <BYAPR13MB28079FFE37E3F085C194E39EF4900@BYAPR13MB2807.namprd13.prod.outlook.com>
References: <157102397341.20776.9338396539567675909@ietfa.amsl.com> <FF93FA7D-31F9-4EC6-A617-B1FAB93ADEE4@cisco.com>
In-Reply-To: <FF93FA7D-31F9-4EC6-A617-B1FAB93ADEE4@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=michael.mcbride@futurewei.com;
x-originating-ip: [108.197.145.62]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8c3f5e83-51cf-48cd-bec0-08d750c1ed34
x-ms-traffictypediagnostic: BYASPR01MB0038:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYASPR01MB0038DFB0F9109669863E1DCDF4900@BYASPR01MB0038.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01901B3451
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39840400004)(366004)(396003)(376002)(346002)(136003)(13464003)(504964003)(52544003)(199004)(189003)(6246003)(4326008)(76176011)(45080400002)(102836004)(7696005)(25786009)(478600001)(7736002)(66066001)(74316002)(305945005)(14454004)(6506007)(53546011)(229853002)(26005)(99286004)(71190400001)(9686003)(186003)(55016002)(6436002)(76116006)(6306002)(2501003)(71200400001)(66476007)(33656002)(66946007)(66556008)(64756008)(66446008)(52536014)(486006)(86362001)(476003)(8936002)(81166006)(81156014)(8676002)(316002)(11346002)(2201001)(446003)(110136005)(54906003)(256004)(14444005)(5660300002)(3846002)(2906002)(6116002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYASPR01MB0038; H:BYAPR13MB2807.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9KabedXHrOkcNgPb48yD9/t6mGoaa+lJnh2+OX2LcIfSGcv8T9LtauQVullfIgiLnQWEWR+M0uCA0HdjlAYrDv76wDvmMYKCA9U4YpR7iG3fOHiOlh0pYfBAZIXjbiYyPgGMf09TRCqeUleQrqR9CLAaJar7VHgvv22i0MYnPZnUWMirGp6P0rBkMJneQDJmHguw+XAvWuA+gn/o4FKY9cT1kVp6Z4MrJTGI7F8FS9HgHuEGF6GLX2sooWH6FYgh9ChV25zM9ZwIJQf8BzyRhT/EwJyA8QvxsczsRVtJC4aI7tyr3MHL+XUYnE2EljOnXtctMFbS7r753qewf1y+sD0Yc9mSDCLcXB7/J4+RDSlLpUsTr57KSwxyzVWJVAs79psN+3iGUuDsFINsgK93IrEScc/PoKDMHsR9oZTxx7elx9ondHqXR6ORWBKdEojl40JnOXD5EX0p0OK9z6eZKg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8c3f5e83-51cf-48cd-bec0-08d750c1ed34
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Oct 2019 16:16:52.8875 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rsnFAmaHO5RVPESKjZVvlsbPKxF0cceUK8Wu0gcHRHFBDdKr60tp1YMo2+KDl5ePWAkzgd3c4GvQFkx1uVRrpg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYASPR01MB0038
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/nGFniS4dXQzKl2oAJ5IKGug5dDc>
Subject: Re: [secdir] Secdir last call review of draft-ietf-mboned-ieee802-mcast-problems-09
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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 16:17:00 -0000

Hi Eric,

I spent a fair amount of time addressing your comments and figured we were near the finish line. Such is not the case.  I'll not be able address Gorry's extensive comments by tomorrow or this week. I should have an update sometime next week.

thanks,
mike

-----Original Message-----
From: Eric Vyncke (evyncke) <evyncke@cisco.com>; 
Sent: Monday, October 14, 2019 12:10 AM
To: Kyle Rose <krose@krose.org>;; secdir@ietf.org; gorry@erg.abdn.ac.uk
Cc: mboned@ietf.org; draft-ietf-mboned-ieee802-mcast-problems.all@ietf.org
Subject: Re: Secdir last call review of draft-ietf-mboned-ieee802-mcast-problems-09

Thank you Kyle for the review: nits are nits but let's fix them when the last call ends (later today).

Dear authors, I would appreciate it if a new revision was uploaded on Tuesday 15th (i.e. after the last call expiration) fixing all issues detected in the last call (see Gorry's email dated 2nd October) and Kyle's one below.

Once done, I will proceed with the publication process

Regards and thank you in advance

-éric (shepherding AD for this document)


On 14/10/2019, 05:33, "Kyle Rose via Datatracker" <noreply@ietf.org>; wrote:

    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?
    
    Nits:
    
    Reference dot11aa
    (https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstandards.ieee.org%2Ffindstds%2Fstandard%2F802.11aa-2012.pdf&amp;data=02%7C01%7Cmichael.mcbride%40futurewei.com%7C77e1df14542647effbee08d750758f50%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637066338161419393&amp;sdata=%2BTgTdYtOEqx%2FaVK5%2FKDATO36ZE3%2Ba81GM%2BC9HLfxPro%3D&amp;reserved=0) 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.