Re: [OPSAWG] The future of MUD work

Eliot Lear <lear@cisco.com> Wed, 31 July 2019 08:45 UTC

Return-Path: <lear@cisco.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 5C28A120118; Wed, 31 Jul 2019 01:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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
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 ktVQ1ePKaJu2; Wed, 31 Jul 2019 01:45:27 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13BD61201F8; Wed, 31 Jul 2019 01:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9265; q=dns/txt; s=iport; t=1564562727; x=1565772327; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=Xgqzfo6jg9TltdJT8HS+dDKr4IMqHj0AQP6TyyTkwTA=; b=JyBENslti0UN29H05QjEOoN9uFAU10EJvoX3P7DZ9uex3sCIDcQJndHl z79dDEQ8yQZX13oDYXD8GrDq0KHUXpL6xZp22RE4Iu+DL6/m+xMA1i7P0 41PcY8bvRrR8O28doSFp536L5Nqc5VDEjVx6rUBkhbRqLd6fKlqgXTOBv c=;
X-Files: signature.asc : 195
X-IronPort-AV: E=Sophos;i="5.64,329,1559520000"; d="asc'?scan'208,217";a="14846925"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Jul 2019 08:45:25 +0000
Received: from dhcp-10-61-107-110.cisco.com (dhcp-10-61-107-110.cisco.com [10.61.107.110]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x6V8jOqF012018 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 31 Jul 2019 08:45:25 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <DC608C90-ADBE-4D31-A226-D441F784D5E4@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DB460E03-43F5-451D-BFC3-591A91EE8F1F"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 31 Jul 2019 10:45:23 +0200
In-Reply-To: <849DED7F-6701-4B26-9645-0B076A224C05@cisco.com>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "ops-ads@ietf.org" <ops-ads@ietf.org>, mud@ietf.org
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
References: <D9AF7D6E-7434-4AE4-A2A5-26CD52C2FE20@cisco.com> <849DED7F-6701-4B26-9645-0B076A224C05@cisco.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.107.110, dhcp-10-61-107-110.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/Y4vLFRWrPsYcNFnrhGhn4gFWpA4>
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 08:45:31 -0000

On the other hand, it shouldn’t just be me.  It’d be a very small working group ;-) If others are interested, they should speak up.

> On 30 Jul 2019, at 11:09, Eliot Lear <lear@cisco.com> wrote:
> 
> Signed PGP part
> Hi Joe,
> 
>> On 29 Jul 2019, at 23:44, 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.
>> 
>> 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 it is probably time for at least one WG to spring from OPSAWG.  We didn’t really complete the agenda at the IETF, and a good reason of that was MUD.  There are at least four active drafts on that one subject, one of which we didn’t really talk about (bw-profile).  For me it’s a matter of what can reasonably be coded, tested, and be useful for manufacturers.  In as much as we can bring a bit more focus to manufacturers by offering them more of a venue for discussion, the additional WG would be welcome.  On the other hand, if we find that we’re not making progress, or if we progress extensions quickly, we can close the WG and continue the mailing list, and move back to OPSAWG.  I don’t see a MUD working group as a long term activity (famous last words), but targeted more at producing the necessary for broader adoption and then going out of business.
> 
> Eliot
> 
>> 
>> Joe
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org <mailto:OPSAWG@ietf.org>
>> https://www.ietf.org/mailman/listinfo/opsawg <https://www.ietf.org/mailman/listinfo/opsawg>
> 
> 
>