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

Qin Wu <bill.wu@huawei.com> Thu, 22 February 2018 03:30 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: lime@ietfa.amsl.com
Delivered-To: lime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A071B124207; Wed, 21 Feb 2018 19:30:49 -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 2UDUN2wfIC_3; Wed, 21 Feb 2018 19:30:48 -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 6C9451204DA; Wed, 21 Feb 2018 19:30:46 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 175B5B9746A48; Thu, 22 Feb 2018 03:30:43 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 22 Feb 2018 03:30:44 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.231]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0361.001; Thu, 22 Feb 2018 11:30:38 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-lime-yang-connection-oriented-oam-model@ietf.org" <draft-ietf-lime-yang-connection-oriented-oam-model@ietf.org>, "rbonica@juniper.net" <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "rbonica@juniper.net" <rbonica@juniper.net>, "lime@ietf.org" <lime@ietf.org>
Thread-Topic: Adam Roach's No Objection on draft-ietf-lime-yang-connection-oriented-oam-model-05: (with COMMENT)
Thread-Index: AQHTq4H2gzuk0URW70uqUKovFZXN+aOvw+bw
Date: Thu, 22 Feb 2018 03:30:37 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AD64355@nkgeml513-mbs.china.huawei.com>
References: <151926527112.21223.15521836555061015139.idtracker@ietfa.amsl.com>
In-Reply-To: <151926527112.21223.15521836555061015139.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.67]
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/lime/7YK8Cv78mQ5iwffUqAKNRgDl5Ik>
Subject: Re: [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
Precedence: list
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 03:30:50 -0000

Thanks Adam, all nits are fixed.

-Qin
-----邮件原件-----
发件人: Adam Roach [mailto:adam@nostrum.com] 
发送时间: 2018年2月22日 10:08
收件人: The IESG
抄送: draft-ietf-lime-yang-connection-oriented-oam-model@ietf.org; rbonica@juniper.net; lime-chairs@ietf.org; rbonica@juniper.net; lime@ietf.org
主题: Adam Roach's No Objection on draft-ietf-lime-yang-connection-oriented-oam-model-05: (with COMMENT)

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..."