[OPSAWG] Erik Kline's No Objection on draft-ietf-opsawg-model-automation-framework-07: (with COMMENT)

Erik Kline via Datatracker <noreply@ietf.org> Wed, 21 October 2020 06:23 UTC

Return-Path: <noreply@ietf.org>
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 2E7263A10AD; Tue, 20 Oct 2020 23:23:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-opsawg-model-automation-framework@ietf.org, opsawg-chairs@ietf.org, opsawg@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, adrian@olddog.co.uk
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <160326143286.14091.11944083197850852604@ietfa.amsl.com>
Date: Tue, 20 Oct 2020 23:23:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/FTaKSu2z3e15gZ5jY0RpTM0JSUU>
Subject: [OPSAWG] Erik Kline's No Objection on draft-ietf-opsawg-model-automation-framework-07: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Oct 2020 06:23:53 -0000

Erik Kline has entered the following ballot position for
draft-ietf-opsawg-model-automation-framework-07: 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-model-automation-framework/



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

[[ nits ]]

[ section 1 ]

* "processing of customer's" -> "processing of customer", perhaps

* The colon-delimited sentence ending the paragraph doesn't seem to imply
  that list is what should logically follow.  I think the sentence aims to
  imply that in-house and silo nature of existing work has lead the some
  challenges, including the ones listed.  I think a slight reword might
  fix this up pretty easily.

* "between a NETCONF/RESTCONF clients and servers" ->
  "between NETCONF/RESTCONF clients and servers"

* "YANG is transport independent" -> "YANG is a transport-independent"

* "model composing" -> "model composition" perhaps?

* "out of the scope" -> "out of scope"

[ section 3.2 ]

* "that to fulfil the service request"?
  perhaps "that fulfill the service request"?

[ section 3.4 ]

* "to support newly added module", suggest either:
  "to support newly added modules" or "to support a newly added module"
  (probably the former, given subsequent "and features")

[ section 4.2.4 ]

* "or network resources be mis-allocated" ->
  "or network resources might be mis-allocated"