Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 04 May 2018 02:08 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 849DD126DCA; Thu, 3 May 2018 19:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 MwWJeuJHME3m; Thu, 3 May 2018 19:08:45 -0700 (PDT)
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 E6274127286; Thu, 3 May 2018 19:08:44 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 9144717BADC42; Fri, 4 May 2018 03:08:41 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 4 May 2018 03:08:42 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.29]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0361.001; Fri, 4 May 2018 10:08:38 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Ladislav Lhotka <lhotka@nic.cz>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "i2rs@ietf.org" <i2rs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org" <draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org>
Thread-Topic: Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04
Thread-Index: AQHT4hoIU9osNzC9q0uYjvWwfuv4MqQd3dlg
Date: Fri, 04 May 2018 02:08:37 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C92798440318@NKGEML515-MBS.china.huawei.com>
References: <152526794842.11272.8213634409290285584@ietfa.amsl.com>
In-Reply-To: <152526794842.11272.8213634409290285584@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.151.75]
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/i2rs/7IZ4OQFxf5W-OnGBPzCGwoRDVvc>
Subject: Re: [i2rs] Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2018 02:08:46 -0000

Hi Lada, 

Thanks a lot for your review comments. Please see some replies inline:

> -----Original Message-----
> From: Ladislav Lhotka [mailto:lhotka@nic.cz]
> Sent: Wednesday, May 02, 2018 9:32 PM
> To: yang-doctors@ietf.org
> Cc: i2rs@ietf.org; ietf@ietf.org;
> draft-ietf-i2rs-yang-l2-network-topology.all@ietf.org
> Subject: Yangdoctors early review of draft-ietf-i2rs-yang-l2-network-topology-04
> 
> Reviewer: Ladislav Lhotka
> Review result: Ready
> 
> This draft and YANG modules contained therein fit into the framework of I2RS
> network topology models. I have no substantial comments, from the YANG point
> of view this document is ready to be published.
> 
> Comments and questions:
> 
> 1. What is the purpose of the 'flag-type' type and 'flag-identity' identity?
> There are no identities derived from the latter.

The "flag-type" type is used in the grouping "l2-network-attributes", "l2-node-attributes" and "l2-link-attributes".

While there is no identities derived from the "flag-identity", it is used in the typedef flag-type. Is this OK?

> 2. Some descriptions overuse capitalization. For example, instead of 'VLAN Name'
> I would suggest 'VLAN name'.

Thanks for catching this. Will fix in next revision.

> 3. An example of an instance document in an appendix would be very helpful.

Thanks for your suggestion. We will add an example to the appendix.

Best regards,
Jie