Re: [netmod] Thoughts on draft-clemm-netmod-nmda-diff
Qin Wu <bill.wu@huawei.com> Thu, 09 August 2018 04:01 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDBA130F3F for <netmod@ietfa.amsl.com>; Wed, 8 Aug 2018 21:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 KgiEzEa3ScnQ for <netmod@ietfa.amsl.com>; Wed, 8 Aug 2018 21:01:05 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 4FC36130F72 for <netmod@ietf.org>; Wed, 8 Aug 2018 21:00:12 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 82BB9738BCAC5 for <netmod@ietf.org>; Thu, 9 Aug 2018 05:00:07 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.399.0; Thu, 9 Aug 2018 05:00:07 +0100
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.163]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0399.000; Thu, 9 Aug 2018 11:59:58 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Alexander Clemm <alexander.clemm@huawei.com>, Joe Clarke <jclarke=40cisco.com@dmarc.ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Thoughts on draft-clemm-netmod-nmda-diff
Thread-Index: AdQgO9aPf9MFKlVCS3ix012Wcdg4yQO9zvkAABhodoA=
Date: Thu, 09 Aug 2018 03:59:58 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AF9C187@nkgeml513-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA9AF59763@nkgeml513-mbx.china.huawei.com> <644DA50AFA8C314EA9BDDAC83BD38A2E0EB43AEC@sjceml521-mbx.china.huawei.com>
In-Reply-To: <644DA50AFA8C314EA9BDDAC83BD38A2E0EB43AEC@sjceml521-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.244]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/OWDRIgho3bc32WHt2sgWeYGfVH0>
Subject: Re: [netmod] Thoughts on draft-clemm-netmod-nmda-diff
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2018 04:01:07 -0000
-----邮件原件----- 发件人: Alexander Clemm 发送时间: 2018年8月9日 8:16 收件人: Qin Wu; Joe Clarke; netmod@ietf.org 主题: RE: [netmod] Thoughts on draft-clemm-netmod-nmda-diff Hello Qin, quick responses inline, <ALEX> --- Alex > -----Original Message----- > From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of Qin Wu > Sent: Friday, July 20, 2018 8:26 AM > To: Joe Clarke <jclarke=40cisco.com@dmarc.ietf.org>; netmod@ietf.org > Subject: Re: [netmod] Thoughts on draft-clemm-netmod-nmda-diff > > Add two additional thoughts, > (1) I hope NMDA datastore can be used to compare one datastore at two > different timepoints, so I am not sure source and target defined in > the model are enough to support this case. <ALEX> This would require a "snapshotting" capability. I think this would go beyond the scope of the draft. However, if someone were to define such a capability, perhaps copy the datastore to the equivalent to a "candidate" (or "archive"), then the comparison operation should be applicable to having one of those as source target. </ALEX> [Qin]: I think we can define mirror image datastore to record image at specific time point, in this case, we can use NMDA diff to compare their difference. > (2) NMDA Base events defined in (https://tools.ietf.org/html/draft-wu- > netconf-base-notification-nmda-01 can leverage NMDA diff to perform > NMDA data validation, right now it is up to the server to detect > validation event, but now we might rely on NMDA diff to decide which > object is missing, what failed objects are. NMDA diff becomes a good tool. > On the other hand, user might want to know when applied configuration > start, when applied configuration complete, based on this to see when > to perform NMDA diff. To address this, we might consider two or three > new notifications In the draft-wu-netconf-base-notification-nmda-01 to > help to decide when to use NDMA diff <ALEX> Sure, I think looking at NMDA for scenarios deserving of notification is a worthwhile goal to address in your draft. The nmda-diff draft addresses "on-demand" only. As a side note, it is conceivable to have a difference also notified using a notification, i.e. define the equivalent of a subscription for a datastore compare (to make for a hybrid between YANG-Push and nmda-diff). Personally, I think this would make a lot of sense, although I wouldn't want to go there until we have the existing subscription drafts finished. </ALEX> [Qin]: Yes,I think this is close to the event notification we proposed in draft-wu-netconf-base-notification-nmda-01, i.e., nmda-data-validate. We can support NMDA diff to validate the data. > > -Qin > -----邮件原件-----) > 发件人: netmod [mailto:netmod-bounces@ietf.org] 代表 Joe Clarke > 发送时间: 2018年7月20日 21:52 > 收件人: netmod@ietf.org > 主题: [netmod] Thoughts on draft-clemm-netmod-nmda-diff > > I just had a chance to finish reading this. The in-person meeting > group seems to strongly support this work, and I agree. > > Coming from a serviceability standpoint, I find this might serve as a > precursor to a VCS-like "blame log". Would it be reasonable to > include identifiers as to who (or what) made the change and when? > Sorry if this was raised at the mic today. I came to the room a bit late. > > Joe > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod
- [netmod] Thoughts on draft-clemm-netmod-nmda-diff Joe Clarke
- Re: [netmod] Thoughts on draft-clemm-netmod-nmda-… Qin Wu
- Re: [netmod] Thoughts on draft-clemm-netmod-nmda-… Alexander Clemm
- Re: [netmod] Thoughts on draft-clemm-netmod-nmda-… Alexander Clemm
- Re: [netmod] Thoughts on draft-clemm-netmod-nmda-… Qin Wu