Re: [OPSAWG] I-D Action: draft-ietf-opsawg-mud-08.txt

Eliot Lear <lear@cisco.com> Fri, 11 August 2017 20:11 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 65B161325DD for <opsawg@ietfa.amsl.com>; Fri, 11 Aug 2017 13:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.986
X-Spam-Level:
X-Spam-Status: No, score=-11.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514, 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 uabPJz3D0cg3 for <opsawg@ietfa.amsl.com>; Fri, 11 Aug 2017 13:11:00 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52EAC132530 for <opsawg@ietf.org>; Fri, 11 Aug 2017 13:11:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3705; q=dns/txt; s=iport; t=1502482260; x=1503691860; h=subject:cc:references:from:message-id:date:mime-version: in-reply-to; bh=w9r0lvQF1GUHpR8oLw8axIwj1YqfLOqT900nTbkBK5Y=; b=Izo/8u1tTzQC3JIzn4Ugl8p2TvZZxsjVZaAwKp+vPY56YhIAG6e6W1TS R7nD5z6CDshaFwejYOq17rdOlIdMStB8Ys7YxN6WWwCXH/GD8K33LodHG CawoKtlDoFL6m+DAQ5Vd0fQpOcYTsujmX0xIsHYchtlTrDSD6K4ryRQQZ U=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CqAADpDY5Z/4gNJK1dGQEBAQEBAQEBAQEBBwEBAQEBg1pkgQUPjhGQDIFulheCEgcaC4RMTwImhFA/GAECAQEBAQEBAWsohRAJAQEBAwEBIUsLEAsSBioCAiciDhMGAgEBhW6EPRCrZIImi2ABAQEBAQUBAQEBAQETD4MoggKDWoJ8gyaEYBOCTgWKBIgPjhOEMYIhgQGMZ4IPWYUEg1eHEYlkjC8fOIEKMiEIHBUfKnYPhjUgNoovAQEF
X-IronPort-AV: E=Sophos;i="5.41,359,1498521600"; d="asc'?scan'208";a="279445355"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Aug 2017 20:10:59 +0000
Received: from [10.41.34.92] ([10.41.34.92]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7BKAxti000492 for <opsawg@ietf.org>; Fri, 11 Aug 2017 20:10:59 GMT
Cc: opsawg@ietf.org
References: <150248175729.24498.16927681607334663849@ietfa.amsl.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <9956db24-0a43-c739-d729-c580ff037cc7@cisco.com>
Date: Fri, 11 Aug 2017 13:10:58 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <150248175729.24498.16927681607334663849@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="BdDXKBofUJlrPc9OmkVpDUKVWdBV5PRlw"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/IAT2zkhkKNfU8_rjQBd375U5JBo>
Subject: Re: [OPSAWG] I-D Action: draft-ietf-opsawg-mud-08.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 11 Aug 2017 20:11:02 -0000

Hi everyone,

As promised, this update corrects all examples (we just didn't have time
to do that for the IETF) and adds a bit more wording around the
abstractions so as to give some guidance on how to translate
abstractions.  In addition, some guidance is given relating to how to
instantiate the ACL model, given the use of features.

Finally, the MUD file maker has been updated, and can now be reached at
mudmaker.org.

With this, I would ask that we start  the various YANG doctor and other
directorate reviews.

Eliot


On 8/11/17 1:02 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Operations and Management Area Working Group WG of the IETF.
>
>         Title           : Manufacturer Usage Description Specification
>         Authors         : Eliot Lear
>                           Ralph Droms
>                           Dan Romascanu
> 	Filename        : draft-ietf-opsawg-mud-08.txt
> 	Pages           : 48
> 	Date            : 2017-08-11
>
> Abstract:
>    This memo specifies a component-based architecture for manufacturer
>    usage descriptions (MUD).  This includes two YANG modules, IPv4 and
>    IPv6 DHCP options, an LLDP TLV, a URL suffix specification, an X.509
>    certificate extension and a means to sign and verify the
>    descriptions.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-opsawg-mud-08
> https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-mud-08
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-mud-08
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>