Re: [i2rs] WG LC for draft-ietf-i2rs-rib-data-model - 3rd WG LC (12/7 to 12/21)

Mach Chen <mach.chen@huawei.com> Mon, 11 December 2017 10:48 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 B2C95127058 for <i2rs@ietfa.amsl.com>; Mon, 11 Dec 2017 02:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 2tcDJoaRbF0R for <i2rs@ietfa.amsl.com>; Mon, 11 Dec 2017 02:48:41 -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 58821124205 for <i2rs@ietf.org>; Mon, 11 Dec 2017 02:48:41 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id AE477E8DF7BB9 for <i2rs@ietf.org>; Mon, 11 Dec 2017 10:48:34 +0000 (GMT)
Received: from DGGEML422-HUB.china.huawei.com (10.1.199.39) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 11 Dec 2017 10:48:05 +0000
Received: from DGGEML510-MBX.china.huawei.com ([169.254.2.54]) by dggeml422-hub.china.huawei.com ([10.1.199.39]) with mapi id 14.03.0361.001; Mon, 11 Dec 2017 18:48:01 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Susan Hares <shares@ndzh.com>, "i2rs@ietf.org" <i2rs@ietf.org>
CC: 'Russ White' <russ@riw.us>, 'Alia Atlas' <akatlas@gmail.com>
Thread-Topic: [i2rs] WG LC for draft-ietf-i2rs-rib-data-model - 3rd WG LC (12/7 to 12/21)
Thread-Index: AdNvwYGmMHHNPqS4QOOd4nd1zqunfgCq9Bkw
Date: Mon, 11 Dec 2017 10:48:01 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2922EBE8B@dggeml510-mbx.china.huawei.com>
References: <003101d36fc1$a9790bd0$fc6b2370$@ndzh.com>
In-Reply-To: <003101d36fc1$a9790bd0$fc6b2370$@ndzh.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: multipart/alternative; boundary="_000_F73A3CB31E8BE34FA1BBE3C8F0CB2AE2922EBE8Bdggeml510mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/DCE6oh718znQLfTucfG3gcIh02M>
Subject: Re: [i2rs] WG LC for draft-ietf-i2rs-rib-data-model - 3rd WG LC (12/7 to 12/21)
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: Mon, 11 Dec 2017 10:48:44 -0000

Hi Sue,

I am not aware of any IPR related to this document.

Best regards,
Mach

From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Friday, December 08, 2017 9:13 AM
To: i2rs@ietf.org
Cc: 'Russ White' <russ@riw.us>; 'Alia Atlas' <akatlas@gmail.com>
Subject: [i2rs] WG LC for draft-ietf-i2rs-rib-data-model - 3rd WG LC (12/7 to 12/21)

This is the 3rd WG Last call for draft-ietf-i2rs-rib-data-model.  You can find the draft at:

https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/

In the previous 2 WG LCs, the WG did not change anything with the base model - except those things that impact on the network management datastore architecture (NMDA) or the security considerations.

In this WG LC discussion, please consider these questions?

1)      Is this document ready for publication?

2)      Do you see any technical problems with the document as part of NMDA architecture where the model can be in ephemeral datastore or a configuration datastore.



3)      Do you have any concerns about the security considerations section?


The Authors should again respond to this email indicating if they know of any IPR with this draft.

Susan Hares
Co-chair and shepherd.