[OPSAWG] Ignas Bagdonas' No Objection on draft-ietf-opsawg-mud-20: (with COMMENT)

Ignas Bagdonas <ibagdona@gmail.com> Tue, 17 April 2018 14:08 UTC

Return-Path: <ibagdona@gmail.com>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 430CF12D94E; Tue, 17 Apr 2018 07:08:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ignas Bagdonas <ibagdona@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-opsawg-mud@ietf.org, Joe Clarke <jclarke@cisco.com>, opsawg-chairs@ietf.org, jclarke@cisco.com, opsawg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152397412726.11591.16253547587352358712.idtracker@ietfa.amsl.com>
Date: Tue, 17 Apr 2018 07:08:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/I-i6DLJ6RDwUOAW2rScYs4ftsfE>
Subject: [OPSAWG] Ignas Bagdonas' No Objection on draft-ietf-opsawg-mud-20: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 17 Apr 2018 14:08:47 -0000

Ignas Bagdonas has entered the following ballot position for
draft-ietf-opsawg-mud-20: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

S2.1: Valid MUD file will contain "mud" and "acls" containers - what if it does
not, especially if it does not contain an ACL container - how will the
connectivity requirement be interpreted then?

A few nits:

s/MUR-URL/MUD-URL

s/yang/YANG in the document and module description fields.

s/dns/DNS in the modules.

S1, MUD building blocks section: "A URL that is can be used"