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

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Mon, 14 October 2019 16:27 UTC

Return-Path: <evyncke@cisco.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 A6E8812081C; Mon, 14 Oct 2019 09:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=g0FcRM/O; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=C+p8sScQ
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 UCV9bp8zfMo9; Mon, 14 Oct 2019 09:27:33 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7405312018D; Mon, 14 Oct 2019 09:27:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5284; q=dns/txt; s=iport; t=1571070453; x=1572280053; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Z3OUKkoxpWi35Yqet9G9aieCgrQg1o03MxPI5qCideU=; b=g0FcRM/OMb/yKXIsMoM7BWEgDKuKZop8zMx2wh/E1BAu0fHaVmQ3pA8e ogE5r5+RlrF9j4AHp3AAr6Tp1EPmZ2ARXKNXZFVXLlE5HZ4xw+VpgTjuR hq+X0QhboDy+8JlGF18XZmuyJCTFXz9Wy0rJSTVIZTa98ZnyalN+gZYX0 s=;
IronPort-PHdr: =?us-ascii?q?9a23=3A2hmP3xHa0WjE5UC6meNUT51GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4z1A3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+efP0fioxH8lqX15+9Hb9Ok9QS47z?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DjAABvoaRd/4ENJK1mDgwBAQEBAQE?= =?us-ascii?q?BAQEDAQEBAREBAQECAgEBAQGBe4FLKScFbFcgBAsqhCSDRwOKSII3JZd+gUK?= =?us-ascii?q?BEANUCQEBAQwBAS0CAQGEQAIXgkckOBMCAwkBAQQBAQECAQUEbYUtDIVLAQE?= =?us-ascii?q?BBBIREQwBATcBCwQCAQgRBAEBAwImAgICMBUICAIEAQ0FIoMAAYJGAy4BAqR?= =?us-ascii?q?TAoE4iGF1gTKCfQEBBYUGGIIXAwaBDCiMDhiBQD+BEScME4JMPoN9DwUBEgE?= =?us-ascii?q?fF4J3MoIsjGUyIYI3nGpuCoIikRWEBBuCOot6iwyOLYE/l3gCBAIEBQIOAQE?= =?us-ascii?q?FgWkiDVpxcBVlAYJBUBAUgU+BJwELgkCKGDt0gSmNZoJFAQE?=
X-IronPort-AV: E=Sophos;i="5.67,296,1566864000"; d="scan'208";a="643686857"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 14 Oct 2019 16:27:32 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x9EGRWrs011181 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 14 Oct 2019 16:27:32 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 14 Oct 2019 11:27:31 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 14 Oct 2019 11:27:31 -0500
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 14 Oct 2019 11:27:31 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=A8U1KbQx2EC/imCdNsIThXRxTFi+VnpFpJFd6uz74YVdavdrPt9HS16ZyWt3DLJFRBfCoQqqTZTm2EmB3NDpxYlSrB0MmvfxN2pVlRkguhkQt7+EcXaulbCGpo6kodiRXLj7XmYQA6sEksZI+sSEWJCXCxa9aZU0/qjU/ovNivuZ+amQ4HtrtjhnZzpfjhIogq/vEEtiGXjx+G0skwOmdfib2W/hA4iA3yOxHxXti9NxKGjLP8OmpuLG6zhie1mdtNk7pnK8WmYkwxOTzfptZlIaAlMooJFGzR2oZSWS/ZTcKZ7TSmfZ5OSr5Zk2ZBYZTgLzK9zBAr+akqi6UzbAFw==
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=Z3OUKkoxpWi35Yqet9G9aieCgrQg1o03MxPI5qCideU=; b=hk5QSS9FrtryydA1aw+hJijB6eEaf0Mquzsdi9WtRY4Rp8jHGXoZSYm9OVBAw1xzb8/cVtaWX/HYQ5gu4f9SeI45d8EPGVSJTcm4eLxwoT4z+N5NSy0F8wZSgdjOc2HUHO9aBXiqS5/i9zoD6QuCDg/JyLPlZNUI7mxDREZg9be4/MFSnah2y1RXHg6I6fYLsGKb3fMLwdRegjMi3iwFglcHlil4XuzTiPPFsuy4jDJqPWDW04u9AOoqV/jeGKXCNonD0diYxV1yko2eEA2Gw0u+1T5eP67yvsIedtLIihru3QbKL8daFgueHEbItAV5AmboubgVfVw8EeytdYU5pg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Z3OUKkoxpWi35Yqet9G9aieCgrQg1o03MxPI5qCideU=; b=C+p8sScQiZtMDsWx1DwK4bDdx7wyJQQQSlgicWj/MaJgeARJVZciCjKrGopblCecAptBN9UXLH7knd0GiZQBJpFiIkvigLXb0jgTVpBpcO/k/A3mPMM6WkQ66br0c1gj5q7ZOZZZa49Hid9hbT8LjwjCQLkiFHpAQvgs0wFp6Sk=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB3661.namprd11.prod.outlook.com (20.178.252.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.21; Mon, 14 Oct 2019 16:27:30 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a%7]) with mapi id 15.20.2347.021; Mon, 14 Oct 2019 16:27:29 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Michael McBride <michael.mcbride@futurewei.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: AQHVgkAY0N6Z+kqf+kWm4acOtxmCt6dZ2dYAgAB3PQCAACR9AA==
Date: Mon, 14 Oct 2019 16:27:29 +0000
Message-ID: <BD0ACC12-D712-4334-A562-EE3194C205EC@cisco.com>
References: <157102397341.20776.9338396539567675909@ietfa.amsl.com> <FF93FA7D-31F9-4EC6-A617-B1FAB93ADEE4@cisco.com> <BYAPR13MB28079FFE37E3F085C194E39EF4900@BYAPR13MB2807.namprd13.prod.outlook.com>
In-Reply-To: <BYAPR13MB28079FFE37E3F085C194E39EF4900@BYAPR13MB2807.namprd13.prod.outlook.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:e9f7:9043:77eb:a55c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: df6252d7-8ac6-4734-6c01-08d750c36878
x-ms-traffictypediagnostic: MN2PR11MB3661:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB36615EC98856149F571F37CAA9900@MN2PR11MB3661.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01901B3451
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(39860400002)(376002)(346002)(136003)(13464003)(504964003)(52544003)(199004)(189003)(6506007)(71190400001)(99286004)(2201001)(25786009)(8936002)(81166006)(81156014)(8676002)(186003)(76176011)(5660300002)(14454004)(45080400002)(71200400001)(58126008)(102836004)(2501003)(54906003)(53546011)(110136005)(33656002)(86362001)(316002)(478600001)(7736002)(6116002)(305945005)(476003)(2906002)(486006)(11346002)(256004)(14444005)(6306002)(2616005)(36756003)(4326008)(66446008)(64756008)(66556008)(66476007)(66946007)(76116006)(91956017)(6486002)(6436002)(6246003)(6512007)(46003)(229853002)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3661; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: k8v9HYVT00tcPzfdFiJ78xROpOhNzVzeEVALWC7Xcf7M5nmifXJ2ns46O5e6KWjRzSWxpkg/z7ce9y8OYP/R8ti6GPEOhrLzitONTVXxwnHweT+0DXjVwoqogTWlbImbe4Z/dS6wyRW8B7jEP70lRCYEvqY20HpeeU05AqdZYT2MDlL4TsSDUd0ntVVaxjLit7rQ5s0/uS8Oc1X6228k0xbKqhfS5ksryhfArEKVqNl8F4TYgmntKi4xDRDKiVsyJsYA0XgQLDyoHJQ2eRrUGOhV6/pe8Cr20ZxALVZD2VzVWlQw0Lwfbq3M8SyknYLsVeTIeskxCRVw+AFs+9ROiHLwB2SZk5WniwoZD1XkZHz7AaTTZ6cmnOKg6GVlsA3iq6+n+Pz2cT1eOhF/L9ye7uvfl0NgRbnuZKFsUeXqOoFlVD1+x7o5+98DtoNZNV3X2Q3QFZmhSnCN1s/qnzpWXw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <3ACE6D75304F96488E375A1F435DB0B0@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: df6252d7-8ac6-4734-6c01-08d750c36878
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Oct 2019 16:27:29.6132 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vbzaxnVlIFh7FgH/QqJ3JpCXbEgBQCXs8saogGo/fmfsu9oTYOoMHnShHY2TAoUjalb14MEMpVzHNVuNPtdj8w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3661
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.21, xch-aln-011.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/_n6ILjAAIWfTkWeBJZM0emca8S0>
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:27:36 -0000

Mike

Nothing urgent on my side but I will wait for this new revision before going forward with the publication process to avoid duplicate reviews.

Regards and thank you in advance

-éric

On 14/10/2019, 18:17, "Michael McBride" <michael.mcbride@futurewei.com> wrote:

    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>rg>; 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.