Re: [OPSAWG] Fwd: New Version Notification for draft-ietf-opsawg-mud-21.txt

Hello Eliot,

Thanks for the draft. Which version of access-control-list yang model does
this depend on?

I ask because if it is draft 19 of the ACL standard,  I noticed a
discrepancy in your example (possibly my mistake but I thought I should
bring it to your attention):

On page 52 should the following be changed to
ietf-access-control-list:acls  ? And also there's a similar one in the
default Acls later in the draft.

ietf-access-control-list:access-lists

Thanks

On Thu, May 17, 2018 at 11:36 AM, Eliot Lear <lear@cisco.com> wrote:

> Hi everyone,
>
> This draft is intended to address all IESG comments.  Thanks to the IESG
> and reviewers for their contributions.  A summary of the changes is below,
> but people may wish to do a side by side review.
>
> Eliot
>
>
>
>    - Small edits to the abstract
>    - Clarity in the introduction that the focus is on protecting the
>    device.
>    - Many grammatical/wording improvements
>    - Clarity when MUD is most effective.
>    - MUD controller -> MUD manager
>    - Normative language boiler plate change
>    - Clarity on what should happen when a MUD manager can't reach a MUD
>    file server
>    - A few reference updates
>    - Clarity on the validity time of a MUD file
>    - Added references to RFCs 5911 and 5912 for SMI changes
>    - one additional data element (documentation)
>    - one change based on an update to the ACL model during its last call
>    - Subsection numbering for node descriptions.
>    - Improved text around "controller", direction-initiated.
>    - Simplified MUD-URL text.
>    - Optional reserved space added to DHCP, LLDP options
>    - Simplified DHCP processing.
>    - A new certificate field to bind the manufacturer certificate to the
>    mud signer.
>    - A content type definition for the SMI.
>    - Updated security considerations.
>
>
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> To: Ralph Droms <rdroms@gmail.com>, Eliot Lear <lear@cisco.com>, Dan
> Romascanu <dromasca@gmail.com>
> Cc:
> Bcc:
> Date: Thu, 17 May 2018 08:19:52 -0700
> Subject: New Version Notification for draft-ietf-opsawg-mud-21.txt
>
> A new version of I-D, draft-ietf-opsawg-mud-21.txt
> has been successfully submitted by Eliot Lear and posted to the
> IETF repository.
>
> Name:           draft-ietf-opsawg-mud
> Revision:       21
> Title:          Manufacturer Usage Description Specification
> Document date:  2018-05-17
> Group:          opsawg
> Pages:          60
> URL:            https://www.ietf.org/internet-
> drafts/draft-ietf-opsawg-mud-21.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-opsawg-mud-21
> Htmlized:       https://datatracker.ietf.org/
> doc/html/draft-ietf-opsawg-mud
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-mud-21
>
> Abstract:
>    This memo specifies a component-based architecture for manufacturer
>    usage descriptions (MUD).  The goal of MUD is to provide a means for
>    end devices to signal to the network what sort of access and network
>    functionality they require to properly function.  The initial focus
>    is on access control.  Later work can delve into other aspects.
>
>    This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, an
>    LLDP TLV, a URL, an X.509 certificate extension and a means to sign
>    and verify the descriptions.
>
>
>
>
> 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.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>
>

-- 
M. Ranganathan