[Lime] Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03

Carl Moberg <calle@tail-f.com> Mon, 22 January 2018 22:59 UTC

Return-Path: <calle@tail-f.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 2D53012D82D; Mon, 22 Jan 2018 14:59:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Carl Moberg <calle@tail-f.com>
To: yang-doctors@ietf.org
Cc: draft-ietf-lime-yang-connection-oriented-oam-model.all@ietf.org, lime@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151666198213.29428.5886859342061936318@ietfa.amsl.com>
Date: Mon, 22 Jan 2018 14:59:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/lime/8tOhUPAurjCuu7bblUUQ5JaZoRg>
Subject: [Lime] Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03
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: Mon, 22 Jan 2018 22:59:42 -0000

Reviewer: Carl Moberg
Review result: On the Right Track

This is my review of draft-ietf-lime-yang-connection-oriented-oam-model-03 and
the included YANG module.

Overall, the document is in reasonable shape but needs more attention around
one fundamental aspect, and a short list of minor issues.

My understanding is that this module is intended to be implemented as a network
service model, per the module classification RFC (RFC8199). But e.g. the ‘mip'
list has a key 'interface' of type 'if:interface-ref'. That type is defined in
ietf-interfaces to be a leafref with path "/if:interfaces/if:interface/if:name”
assuming that the module context is a single network element. This seems
self-contradicting and needs to be resolved. 

I would suggest running the YANG module through 'pyang -f yang' to provide
consistent formatting of the module. I think it would also be worth considering
putting the content in the canonical order. E.g. the location of the description
statement in the mip-address grouping makes it hard to read.

The 'session' list is 'ordered-by user', but does not provide any description or
explanation to the meaning of the order.

The content of the description strings are in need of language fixes.