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

wangzitao <wangzitao@huawei.com> Tue, 23 January 2018 03:17 UTC

Return-Path: <wangzitao@huawei.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6DD126C0F; Mon, 22 Jan 2018 19:17:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsSV_jW1_kAp; Mon, 22 Jan 2018 19:17:11 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CAFB1205D3; Mon, 22 Jan 2018 19:17:11 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id B9A80C406F7F4; Tue, 23 Jan 2018 03:17:07 +0000 (GMT)
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 23 Jan 2018 03:17:08 +0000
Received: from DGGEML504-MBS.china.huawei.com ([169.254.11.87]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0361.001; Tue, 23 Jan 2018 11:17:06 +0800
From: wangzitao <wangzitao@huawei.com>
To: Carl Moberg <calle@tail-f.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "draft-ietf-lime-yang-connection-oriented-oam-model.all@ietf.org" <draft-ietf-lime-yang-connection-oriented-oam-model.all@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03
Thread-Index: AdOT9mRYUEM4j8ZmSyWkLn5SZj+pgg==
Date: Tue, 23 Jan 2018 03:17:05 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EA2B8B085D@DGGEML504-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.78.152]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/Kh-PVOD-yYgldZMVEsugu-E9o2M>
Subject: Re: [yang-doctors] Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 03:17:13 -0000

Hi Carl,
Thank you for these good comments!
Please find my reply in-line.

Best Regards!
-Michael

-----邮件原件-----
发件人: Carl Moberg [mailto:calle@tail-f.com] 
发送时间: 2018年1月23日 7:00
收件人: yang-doctors@ietf.org
抄送: draft-ietf-lime-yang-connection-oriented-oam-model.all@ietf.org; lime@ietf.org; ietf@ietf.org
主题: Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03

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. 

+++Michael: agree. The 'interface' may not enough to distinguish different MIPs. We will fix it in next version, and may be define an "id" as the key. 

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.

+++Michael: OK. Will improve it.

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

+++Michael: agree. Will remove it in next version. 

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

+++Michael: OK. Will improve it.