[OPSAWG] Opsdir telechat review of draft-ietf-opsawg-mud-20

Scott Bradner <sob@sobco.com> Tue, 10 April 2018 13:03 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Scott Bradner <sob@sobco.com>
To: ops-dir@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152336540077.13556.13954379711415125489@ietfa.amsl.com>
Date: Tue, 10 Apr 2018 06:03:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/oLrs2YfhRAYYr7Tw962gYMVrfRg>
Subject: [OPSAWG] Opsdir telechat review of draft-ietf-opsawg-mud-20

Reviewer: Scott Bradner
Review result: Has Nits

I did an OPS-DIR review of Manufacturer Usage Description Specification <
draft-ietf-opsawg-mud > The specification is well written and clear (I also
agree with Robert Spark's nits).

One suggestion about document organization: I would either move the discussion
of what should be done if the MUD controller can not retrieve the MUD file for
some reason or another out of the security considerations section to after
section 1.9 or at least include a forward pointer to the discussion.

[OPSAWG] Opsdir telechat review of draft-ietf-ops… Scott Bradner
Re: [OPSAWG] Opsdir telechat review of draft-ietf… Eliot Lear
Re: [OPSAWG] Opsdir telechat review of draft-ietf… Scott Bradner