IETF Logo Mail Archive

Re: [netconf] Adoption call for draft-lindblad-netconf-transaction-id-02

"maqiufang (A)" <maqiufang1@huawei.com> Wed, 17 August 2022 06:50 UTC

Return-Path: <maqiufang1@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 A1D87C152700 for <netconf@ietfa.amsl.com>; Tue, 16 Aug 2022 23:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 NfnE8rcJcqeO for <netconf@ietfa.amsl.com>; Tue, 16 Aug 2022 23:49:59 -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 DC7A2C14CF08 for <netconf@ietf.org>; Tue, 16 Aug 2022 23:49:58 -0700 (PDT)
Received: from fraeml734-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4M6z8C4LMYz67Lmq for <netconf@ietf.org>; Wed, 17 Aug 2022 14:46:51 +0800 (CST)
Received: from kwepemm000020.china.huawei.com (7.193.23.93) by fraeml734-chm.china.huawei.com (10.206.15.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 17 Aug 2022 08:49:55 +0200
Received: from kwepemm600017.china.huawei.com (7.193.23.234) 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.24; Wed, 17 Aug 2022 14:49:53 +0800
Received: from kwepemm600017.china.huawei.com ([7.193.23.234]) by kwepemm600017.china.huawei.com ([7.193.23.234]) with mapi id 15.01.2375.024; Wed, 17 Aug 2022 14:49:53 +0800
From: "maqiufang (A)" <maqiufang1@huawei.com>
To: Kent Watsen <kent+ietf@watsen.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] Adoption call for draft-lindblad-netconf-transaction-id-02
Thread-Index: AQHYrL5kWXdciv0QWkuX/abal+q5wK2vvLrg
Date: Wed, 17 Aug 2022 06:49:53 +0000
Message-ID: <a8e3f0b785d9423ca154b33c1316ec24@huawei.com>
References: <0100018287f8dfb8-753b6dc6-6329-44e0-90f4-63b55956f1ad-000000@email.amazonses.com>
In-Reply-To: <0100018287f8dfb8-753b6dc6-6329-44e0-90f4-63b55956f1ad-000000@email.amazonses.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.87]
Content-Type: multipart/alternative; boundary="_000_a8e3f0b785d9423ca154b33c1316ec24huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/EMc38YLrbyf97gAkG6jV-JSxV_U>
Subject: Re: [netconf] Adoption call for draft-lindblad-netconf-transaction-id-02
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: Wed, 17 Aug 2022 06:50:01 -0000

Hi, all

I've read the latest version of the draft and support the adoption of this work.

After reading the draft, I have some comments which hopefully could help improve this work:

*         Sec.3.1 use cases; there are several use cases that are given, but I am quite confused with "configuration update with txid return" and "configuration update with txid specification" cases, I did not find any details in the following sections describing these two cases. Does "configuration update with txid return" mean a client issues a transaction without txid specified (like a normal <edit-config> operation)? But what's the difference between "configuration update with txid specifiction" and "conditional configuration change"?

*         Sec.5.3. Configuration Change; for a rpc ok reply to an <edit-config> operation, it's not clear which versioned node the txid value is attached to. In the example, is the txid value "nc7688" applied to acls list node?  And in sec.5.5, what does the etag value "nc8008" mean? Is the etag value for <running> or <candidate>? And what does the rpc reply look like if a server both supports both etag and last-modified mechanisms?

*         Sec.6 YANG modules; should other operations like <discard-changes>, <copy-config> and <delete-config> also be augmented in the YANG module?



Best Regards,

Qiufang



-----Original Message-----
From: netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Kent Watsen
Sent: Wednesday, August 10, 2022 9:37 PM
To: netconf@ietf.org<mailto:netconf@ietf.org>
Subject: [netconf] Adoption call for draft-lindblad-netconf-transaction-id-02



NETCONF WG,



This message starts a two week poll ending on Aug 24, to decide if the document in the Subject line should be made a WG document or not. Please reply-all to this email as to whether or not you support adoption of this draft by the WG. Indications that the draft has been read are also appreciated.  From the IPR-poll, there is no known IPR associated with this draft.



                https://datatracker.ietf.org/doc/draft-lindblad-netconf-transaction-id



Thanks,

Kent (and Mahesh)





_______________________________________________

netconf mailing list

netconf@ietf.org<mailto:netconf@ietf.org>

https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email