Re: [OPSAWG] The future of MUD work

tom petch <ietfc@btconnect.com> Wed, 31 July 2019 11:35 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5718C12012A; Wed, 31 Jul 2019 04:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.247
X-Spam-Level:
X-Spam-Status: No, score=0.247 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 BX6ieIS9M0uB; Wed, 31 Jul 2019 04:35:43 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30122.outbound.protection.outlook.com [40.107.3.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C43211200F6; Wed, 31 Jul 2019 04:35:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lV5dLaiFDIEJ5Rpiruhw6pRMMVZZwKfBBNcaQLD6JFl4V81NF/wQgg4Ak2vl4uNMlROux3NuKictb+8ZoIwNCLnteRLORn/mt+OlXjMVxbPCvQJ6AFKrZV6uOcVsRQROYGibktB1323gwn7Jc05eFr6g1wNOlOTW1CY7QuQiKF2zmg6vKGxaV/W+b8FEYbVgXMaN93Fg/KJeIOJKC+t3boMRBlNVPmErbH9i1fsGtj1Sv4mRIAPsHf/87NPAZCuo1E/5zNlFl6+yULatCSeWUyQQiymq/e63mAvCqkNW+Ep6mmbADvbKf9nk4IbGYDI0tFZRmEtdee9aBgiImnb+3g==
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=nLWMKOqMvl7GYs+oLPlfVJNKGbc6Tqt0iEH9zVNWj+w=; b=WUJxJC5Yca0lNU0Joj/6mJUHbhyS9itdsn4gcoh0sbmuNkvy5dh2W/Yju6F5FXNp6HBCHXybc1Ht6FrnmU5YgY+hQ46St55SeEtrwULeV5AEVEwCklfinu2p/Lv6oYmQzEK7UUclrPJR1KA0gSL6Q1NicRrvuiF8nM6LuxCOPMzu8xWsd36gTu2GLRRmXvSSUNNwoSaWMuLXIJvn4Q5toylM8RlcNk3Iq9+6o3jEVAxJciL87Q0yY5dQAl9XVktex0K6YYDHxAG82MFfIRn+OtVrwW4qbOppBJn6/AE8sGQFYbrKAZcyQms99CMds9dY+gA6nQcb1Lql+sHttc6Ynw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=btconnect.com;dmarc=pass action=none header.from=btconnect.com;dkim=pass header.d=btconnect.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=nLWMKOqMvl7GYs+oLPlfVJNKGbc6Tqt0iEH9zVNWj+w=; b=ou6k0UhxpresvgIJ69HnkItRjbpliHu4PZpn3jZPwOKBWVgVnpTEeQO6wz4hi3YSCQL7xWVkr1wm6n9ezLRfFjcwqnDFZ+5r7Ou+LqLmqOp1eIZitGxQmiUyP76af7aiiZ4LcdRTdtCWBG0FaxLCz8oMkrriXVQgLWlVp5C9Jk0=
Received: from AM4PR07MB3204.eurprd07.prod.outlook.com (10.171.188.157) by AM4PR07MB3457.eurprd07.prod.outlook.com (10.171.190.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.11; Wed, 31 Jul 2019 11:35:40 +0000
Received: from AM4PR07MB3204.eurprd07.prod.outlook.com ([fe80::a88c:543d:8b41:5e76]) by AM4PR07MB3204.eurprd07.prod.outlook.com ([fe80::a88c:543d:8b41:5e76%7]) with mapi id 15.20.2136.010; Wed, 31 Jul 2019 11:35:40 +0000
From: tom petch <ietfc@btconnect.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
CC: "ops-ads@ietf.org" <ops-ads@ietf.org>
Thread-Topic: [OPSAWG] The future of MUD work
Thread-Index: AQHVR5QUSTocazEH3EiYlNUpL4MvRg==
Date: Wed, 31 Jul 2019 11:35:40 +0000
Message-ID: <074e01d54793$fc28e200$4001a8c0@gateway.2wire.net>
References: <D9AF7D6E-7434-4AE4-A2A5-26CD52C2FE20@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0274.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a1::22) To AM4PR07MB3204.eurprd07.prod.outlook.com (2603:10a6:205:8::29)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.211.103]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7f8b307f-58c1-4062-5b5c-08d715ab36c9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:AM4PR07MB3457;
x-ms-traffictypediagnostic: AM4PR07MB3457:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <AM4PR07MB345783EB91CCDBA6A36BBF7AA0DF0@AM4PR07MB3457.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 011579F31F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(376002)(346002)(396003)(366004)(51444003)(13464003)(199004)(189003)(26005)(71200400001)(3846002)(71190400001)(102836004)(446003)(256004)(6436002)(14444005)(44736005)(7736002)(6116002)(1556002)(478600001)(966005)(110136005)(66066001)(316002)(25786009)(44716002)(4326008)(62236002)(186003)(6246003)(305945005)(6512007)(9686003)(6306002)(14454004)(61296003)(14496001)(66446008)(64756008)(66556008)(66476007)(68736007)(476003)(486006)(8936002)(2501003)(86362001)(5660300002)(6506007)(6486002)(4720700003)(81816011)(2906002)(66946007)(229853002)(76176011)(81686011)(386003)(50226002)(8676002)(81156014)(81166006)(99286004)(52116002)(53936002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB3457; H:AM4PR07MB3204.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: glTnEoQNNojKJz9g7lGntLxX+qGiOoD7xLV1UMtOO2ViAqe7X6mr+8Bd81mowWpzKjXulyLRNIqrghg7UtEsQ+s5a/BIrx3ICcDDWRru6PIeFWxC597QvwBbCzg6WvvTHUyJizUBbhozkn+CpiWsV2bOVn1Iw1Z2M6OiYOI3L8vyQ273TczQvxWk0gVIKISJ6Xy+oDQlPf1t29TyK60mBjJZ+OdNKCQp39DNhX39tO6L7luatRszROx5SbPn3bxlPSOERqn0MOXtTKQ1EK8mRntW8vmJFlWKSEavP76EwhGUrOtI5dVrmqniqeTd56e1mTPEl3Da9u1qbt4HO6bWZIuoBv/gT60V5stdVO5Aq3G82UuE12z+UIWD8BIBKbjq/wmNo1JDjdlw5c5i4WmwlzyHiYTFwH/AByWWlGWJGpQ=
Content-Type: text/plain; charset="utf-8"
Content-ID: <B55B30E33795BB42971F8BEEA74E51EE@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7f8b307f-58c1-4062-5b5c-08d715ab36c9
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jul 2019 11:35:40.3968 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ietfc@btconnect.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB3457
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/jk7AvvXlFnG154oCNAUhfhE_fqI>
Subject: Re: [OPSAWG] The future of MUD work
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 11:35:45 -0000

----- Original Message -----
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
Sent: Monday, July 29, 2019 10:44 PM

> OpsAWG members and our Ops ADs, it was discussed in opsawg at IETF 105
that with the amount of MUD work being proposed (and discussions
happening outside of opsawg) that perhaps MUD should evolve into its own
WG.  Some cons to this approached were discussed (maybe it would be too
heavy-weight with a charter, milestones, etc.).  However, I wanted to
take this conversation to the list so we can close on it publicly.
>
> Speaking as WG co-chair, I am happy to continue to support the MUD
work in opsawg, but I want to make sure the WG feels compelled to work
on it; and I want to make sure the full community that is interested in
MUD can follow and discuss items here.  That said, it was mentioned in
105 that perhaps a bigger “on-boarding” set of work would be better
served in its own WG.  I think if the scope of MUD grows beyond the
definition and its extensions (as we’ve been seeing the work progress
thus far) it might be better served in its own WG space.
>
> Thoughts?

I think that a WG has a cost, needing chairs (and I think that WG chairs
are in short supply), a different mailing list, different archive,
different name for I-Ds (which create a lack of continuity, making it
hard to track the history of work) another meeting to squeeze into an
IETF meeting.  Splitting off part of a task puts focus on it provided
that there are those interested in focussing on it; I am not sure that
there is here.

And it would focus on the name, as in 'Your name is mud' which, in my
culture, does not have a positive association.

Tom Petch

> Joe
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>