[Lime] Adam Roach's No Objection on draft-ietf-lime-yang-connection-oriented-oam-model-05: (with COMMENT)

Adam Roach <adam@nostrum.com> Thu, 22 February 2018 02:07 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: lime@ietf.org
Delivered-To: lime@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA06126C83; Wed, 21 Feb 2018 18:07:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach <adam@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-lime-yang-connection-oriented-oam-model@ietf.org, rbonica@juniper.net, lime-chairs@ietf.org, rbonica@juniper.net, lime@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151926527112.21223.15521836555061015139.idtracker@ietfa.amsl.com>
Date: Wed, 21 Feb 2018 18:07:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/lime/g-3Dehw9SncaPkMHnWsIt58So3U>
Subject: [Lime] Adam Roach's No Objection on draft-ietf-lime-yang-connection-oriented-oam-model-05: (with COMMENT)
X-BeenThere: lime@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." <lime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lime>, <mailto:lime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lime/>
List-Post: <mailto:lime@ietf.org>
List-Help: <mailto:lime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lime>, <mailto:lime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2018 02:07:51 -0000

Adam Roach has entered the following ballot position for
draft-ietf-lime-yang-connection-oriented-oam-model-05: 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-lime-yang-connection-oriented-oam-model/



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

I found some small editorial nits while reviewing this document.

§2.2:

>  Connectivity Verification  - Connectivity Verification are used to
>     verify that a destination is connected.  It are also referred to

"...is used to..."

§3:

>  In this document we define a generic YANG model for connection
>  oriented OAM protocols.  The YANG model defined here is generic in a

Hyphenate "connection-oriented".

>  sense that other technologies can extend it for technology specific
>  needs.

Hyphenate "technology-specific".

>  Figure 1 depicts relationship of different YANG modules.

This sentence seems redundant with the earlier "Figure 1 depicts..." statement.


>          |                    |                  |
>   +-------------------------------------------------------+
>   |                      Uniform API                      |
>   +-------------------------------------------------------+
>
>       Relationship of OAM YANG model to generic (base) YANG model

I presume this is Figure 1. It probably should say so.


In the module:

> typedef ma-name-string {
>   type string;
>   description
>     "Generic administrative name for an
>      Maintenance Association (MA).";
> }

"...for a Maintenance..."