Re: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)

Mach Chen <mach.chen@huawei.com> Sun, 08 April 2018 08:23 UTC

Return-Path: <mach.chen@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 7319A127775; Sun, 8 Apr 2018 01:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UcsFW9Ak00io; Sun, 8 Apr 2018 01:23:16 -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 4D64B126CE8; Sun, 8 Apr 2018 01:23:16 -0700 (PDT)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 63127C6CCA45; Sun, 8 Apr 2018 09:23:12 +0100 (IST)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.382.0; Sun, 8 Apr 2018 09:23:14 +0100
Received: from DGGEML510-MBX.china.huawei.com ([169.254.2.73]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0361.001; Sun, 8 Apr 2018 16:23:07 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
CC: "i2rs@ietf.org" <i2rs@ietf.org>, "draft-ietf-i2rs-rib-data-model@ietf.org" <draft-ietf-i2rs-rib-data-model@ietf.org>, "i2rs-chairs@ietf.org" <i2rs-chairs@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>
Thread-Topic: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)
Thread-Index: AQHTy13moi2oBFWZPEShrejzOgw/4qP2htDA
Date: Sun, 08 Apr 2018 08:23:07 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2923A8146@dggeml510-mbx.china.huawei.com>
References: <152276819613.22739.3895944015063617381.idtracker@ietfa.amsl.com>
In-Reply-To: <152276819613.22739.3895944015063617381.idtracker@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.111.194.201]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/X4NqpVnN1E1NAK2XAahHXnl_BTU>
Subject: Re: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10: (with COMMENT)
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: Sun, 08 Apr 2018 08:23:18 -0000

Hi Alissa,

Thanks for your comments!

Please see my responses inline...

> -----Original Message-----
> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Alissa Cooper
> Sent: Tuesday, April 03, 2018 11:10 PM
> To: The IESG <iesg@ietf.org>
> Cc: i2rs@ietf.org; draft-ietf-i2rs-rib-data-model@ietf.org; i2rs-chairs@ietf.org;
> shares@ndzh.com
> Subject: [i2rs] Alissa Cooper's No Objection on draft-ietf-i2rs-rib-data-model-10:
> (with COMMENT)
> 
> Alissa Cooper has entered the following ballot position for
> draft-ietf-i2rs-rib-data-model-10: 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-i2rs-rib-data-model/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Sec 1.2:
> 
> "YANG tree diagrams provide a concise representation of a YANG module,
>    and SHOULD be included to help readers understand YANG module
>    structure."
> 
> This document does not seem like an appropriate place to have normative
> guidance about this. And if this sentence is removed, I don't see the point of
> including Section 1.2 otherwise. This would also imply deleting the reference to
> I-D.ietf-netmod-yang-tree-diagrams.

This results from a YANG doctor review.  I saw it also occurs in other published documents. I personally think it's no harm to keep it, how do you think?

> 
> Sec 2.1: Again here I'm confused about the use of normative language. Why do
> you need to specify normative requirements for what this very document is
> specifying? Or are these supposed to be requirements on implementations?

OK, how about this:

"...a RIB data model needs to specify a way for an external entity to learn about the functional capabilities of a network device." And 

" The RIB data model needs a way to expose the nexthop chaining capability supported by a given network device."

> 
> Sec 2.5: s/causes/caused/

Done

The above updates will be reelected in version-11.

Thanks,
Mach
> 
> 
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs