Re: [netconf] Private Candidates
"Fengchong (frank)" <frank.fengchong@huawei.com> Tue, 01 November 2022 02:00 UTC
Return-Path: <frank.fengchong@huawei.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF63C1524D7 for <netconf@ietfa.amsl.com>; Mon, 31 Oct 2022 19:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PqTwnSvUC4Y8 for <netconf@ietfa.amsl.com>; Mon, 31 Oct 2022 19:00:11 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605FDC14CF04 for <netconf@ietf.org>; Mon, 31 Oct 2022 19:00:11 -0700 (PDT)
Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4N1Y5t2PSRz67wsC; Tue, 1 Nov 2022 09:56:18 +0800 (CST)
Received: from kwepemm000020.china.huawei.com (7.193.23.93) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Tue, 1 Nov 2022 03:00:08 +0100
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by kwepemm000020.china.huawei.com (7.193.23.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Tue, 1 Nov 2022 10:00:06 +0800
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2375.031; Tue, 1 Nov 2022 10:00:06 +0800
From: "Fengchong (frank)" <frank.fengchong@huawei.com>
To: "Cumming, James (Nokia - US)" <james.cumming@nokia.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: Private Candidates
Thread-Index: AdjtlXAI9OJZY3gWTz+nQ6GaZN2pZQ==
Date: Tue, 01 Nov 2022 02:00:06 +0000
Message-ID: <d7a070a5bd444597a01adb23b43ed05b@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.97.178]
Content-Type: multipart/alternative; boundary="_000_d7a070a5bd444597a01adb23b43ed05bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/IdNIThLe1OlDGxJa_nQJuY-eQsk>
Subject: Re: [netconf] Private Candidates
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2022 02:00:13 -0000
Hi James, Thanks for your effort on private candidate, it’s a very important feature, and provide a way to detect and solve conflicts. I have a suggestion on conflict detection. The current solution will check the conflict per node, it’s a good way, but more efforts will be payed if we try to implement this solution. For example, we MUST check all descendent nodes of a specified interface to determine whether the conflict occurs when this interface is deleted in running datastore. We may add a simple solution to detect conflicts, that is checking the conflicts globally. For example, we can use commit-id to determine whether the conflict occurs. The commit-id will be changed if the configuration of running datastore. When a private candidate datastore is created, the commit-id (e.g. 100) of current running datastore will be recorded, And if another session commits it’s configuration ,the commit-id of running datastore will be changed (from 100 to 101). And then this session want to commit its configuration, the conflict will be Detected (for commit-id of private candidate is different with the one of current running datastore). We can provide two ways (global and per node), the implementation can choose one way. 发件人: netconf [mailto:netconf-bounces@ietf.org] 代表 Cumming, James (Nokia - US) 发送时间: 2022年10月21日 22:17 收件人: netconf@ietf.org 主题: [netconf] Private Candidates Good morning/afternoon/evening, On behalf of the authors I would like to draw your attention to this draft. It deals with the use of Private Candidates over NETCONF. https://datatracker.ietf.org/doc/draft-jgc-netconf-privcand/ We hope to present this for the first time in London. Kind regards.
- [netconf] Private Candidates Cumming, James (Nokia - US)
- Re: [netconf] Private Candidates Andy Bierman
- Re: [netconf] Private Candidates Ladislav Lhotka
- Re: [netconf] Private Candidates Fengchong (frank)
- Re: [netconf] Private Candidates Andy Bierman