Re: [OPSAWG] The future of MUD work

Warren Kumari <warren@kumari.net> Thu, 01 August 2019 22:10 UTC

Return-Path: <warren@kumari.net>
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 772E41201F8 for <opsawg@ietfa.amsl.com>; Thu, 1 Aug 2019 15:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 uBanq1epEjIt for <opsawg@ietfa.amsl.com>; Thu, 1 Aug 2019 15:10:04 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D83C31201ED for <opsawg@ietf.org>; Thu, 1 Aug 2019 15:10:03 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id l9so71892993qtu.6 for <opsawg@ietf.org>; Thu, 01 Aug 2019 15:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=NKtHHvT+Z9i8Lr1pzT/gdcjI/mPchtv2AsrjlBfd6ck=; b=1aZ+0Tf+5EF5w+sEQXZcf8hx+dgRdfUNcnygtCaxhd/TM/vsiZmz8JTijXQ2iGHgiD q4NeyltCmzkf0ur89AUakjlo5kpr2tclz2T2LnuvcbAsPuxWXkdbFaxNKYkYCysPfa/E +j67mCzYUOzn9kwVBX0mLJCh6FplIRmZA1qpLpbKm6D7T97JW0TcPunNXN8S046HdpEg KUIZ35NSwDRS29fgfwk7UlPWnr/5s4+LTw2SwStx7LdnlJ8RpZPMpI80OTjMqRBG+pZg Ifq1BLRsUSNfrV+lLd/D5V65YLnCQaszdHEBgjxvbfaDXybheoQqqlhYUoL+LiMLm1RK U0oQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=NKtHHvT+Z9i8Lr1pzT/gdcjI/mPchtv2AsrjlBfd6ck=; b=NcNYSsidscUJM0wfZmfaqGvCNyeSDD6g6JlFEK5uu+Ve0+ZaFs0EKmb1bGdx/+uO2F /EGrWrOyOFgs7ouuQx6f5KQ04zxKEkw0X4gqM38tk8pj5pYTVcWA5ngn7ACdA0f4afFY CnjXxnC0iM/kb2YwFjAiS8VcgNyOZKYM0vmCCyKp/p2piwzhibpyGcUcmZoel/eMMcJL /+UjsBJSqrPm0GxUdauShT3i0Wu8mNgL8XWTmyB2/HXQqmgSN1XRRpuYxQ6H5i75aEFQ 44CRl8R5p+i9Fvet0HxPrpucAzorx+52e9LElB75N3FCU3x4zB1kTu+9kVAmosWwAaJz 1q9Q==
X-Gm-Message-State: APjAAAVUp8QZVTQn10ewZACU3Av0s/oFhvYgd3PJN1XwXgNAAv+tQrnh xei0vGVL4BV8GaZ9nQB56ZVYJTcDettIOJWkzqFDFSuiL0CBgg==
X-Google-Smtp-Source: APXvYqy4gvqnvmeD8hqocb+XrUd0S2d0zGcSNYfI/rRGhtcjnOjyJhh+oUdQOugw++C3Agxd/rtlGBq+5JrZY8E2IdE=
X-Received: by 2002:ac8:3811:: with SMTP id q17mr89885087qtb.315.1564697402105; Thu, 01 Aug 2019 15:10:02 -0700 (PDT)
MIME-Version: 1.0
References: <D9AF7D6E-7434-4AE4-A2A5-26CD52C2FE20@cisco.com>
In-Reply-To: <D9AF7D6E-7434-4AE4-A2A5-26CD52C2FE20@cisco.com>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 01 Aug 2019 18:09:24 -0400
Message-ID: <CAHw9_i+BkvmeUyTpHV6iKhVGCRrUePthOPLj-RuiHginbvrGjQ@mail.gmail.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "ops-ads@ietf.org" <ops-ads@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/1UywcabTu1J9d086KE-mx8gp7Jo>
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: Thu, 01 Aug 2019 22:10:07 -0000

On Mon, Jul 29, 2019 at 5:44 PM Joe Clarke (jclarke) <jclarke@cisco.com> wrote:
>
> 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.


I *personally* believe that a WG focused on MUD makes sense - I think
that there are enough people interested in the topic, and enough work
to make it worthwhile - this will allow us to corral the work into a
single place and allow people interested in MUD to focus on that.
Forming a short lived WG *should not* be a large undertaking -  Yes,
it does require some process wonkery with charters and such, but we
should be able to use the existing work as proof that there is
interest, etc.
If it turns out this is not enough work to justify an entire meeting
slot, we can have a joint OpsAWG / MUD meeting (which I'll agree is
only a marginal change from the current situation :-) ). If, on the
other hand, there is sufficient work for a slot, it will free up time
in OpsAWG and allow OpsAWG to work on other stuff.

Note that these are my personal views - the MUD WG, if it were to be
created, would presumably be on the Management side of Ops & Mgmt, and
so Ignas will have to approve / make the decision.
W



>
> 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?
>
> Joe



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf