[netmod] Re: comments on system-config-08 draft

"maqiufang (A)" <maqiufang1@huawei.com> Fri, 23 August 2024 03:09 UTC

Return-Path: <maqiufang1@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 18A84C151068 for <netmod@ietfa.amsl.com>; Thu, 22 Aug 2024 20:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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] 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 bleZcx7MPnKF for <netmod@ietfa.amsl.com>; Thu, 22 Aug 2024 20:09:35 -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 C781CC151061 for <netmod@ietf.org>; Thu, 22 Aug 2024 20:09:34 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4WqlMm4cKpz6K5bq for <netmod@ietf.org>; Fri, 23 Aug 2024 11:06:28 +0800 (CST)
Received: from lhrpeml100004.china.huawei.com (unknown [7.191.162.219]) by mail.maildlp.com (Postfix) with ESMTPS id 0D6D0140447 for <netmod@ietf.org>; Fri, 23 Aug 2024 11:09:32 +0800 (CST)
Received: from kwepemm600020.china.huawei.com (7.193.23.147) by lhrpeml100004.china.huawei.com (7.191.162.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 23 Aug 2024 04:09:31 +0100
Received: from kwepemm600017.china.huawei.com (7.193.23.234) by kwepemm600020.china.huawei.com (7.193.23.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 23 Aug 2024 11:09:29 +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.2507.039; Fri, 23 Aug 2024 11:09:29 +0800
From: "maqiufang (A)" <maqiufang1@huawei.com>
To: Andy Bierman <andy@yumaworks.com>
Thread-Topic: [netmod] Re: comments on system-config-08 draft
Thread-Index: AQHa9KW5yk9AAtxM1UC4y+up9Oswr7Iy8rYAgAEjdgA=
Date: Fri, 23 Aug 2024 03:09:29 +0000
Message-ID: <bd836cb888554e539bf9b39e948dc550@huawei.com>
References: <CABCOCHScHJENof+1obOgXUDZZMhhPhs9rvKHw4W0RRfF0R1_Hw@mail.gmail.com> <bf769710572f4b3884d58d128cf58305@huawei.com> <CABCOCHRWgBpt1Cx4FJqec=-80_PLvRKK1gz7oWJ06C=+_zjNRA@mail.gmail.com> <0100019175c50c8e-f22d8526-dfbf-49a2-badb-6ad10afd0186-000000@email.amazonses.com> <CABCOCHQihWy92AzWzgQSVFuWFuHEkN-_yK5T-r=jL0r5eOPkTQ@mail.gmail.com> <010001917aa52f3b-02340517-a63d-42ee-8c27-590f00b4b451-000000@email.amazonses.com> <CABCOCHTq-i3utR5_EUrYfdUfnx56gr5FxVNLubVEmc+LLXsUag@mail.gmail.com>
In-Reply-To: <CABCOCHTq-i3utR5_EUrYfdUfnx56gr5FxVNLubVEmc+LLXsUag@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.118.147]
Content-Type: multipart/alternative; boundary="_000_bd836cb888554e539bf9b39e948dc550huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: VGLI2G7QVTZ42CXTND4SZJPKXYQZHVMV
X-Message-ID-Hash: VGLI2G7QVTZ42CXTND4SZJPKXYQZHVMV
X-MailFrom: maqiufang1@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netmod.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Kent Watsen <kent@watsen.net>, "netmod@ietf.org" <netmod@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netmod] Re: comments on system-config-08 draft
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/VEqmhggkjkHNGp1J4CDXVnGBSO0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Owner: <mailto:netmod-owner@ietf.org>
List-Post: <mailto:netmod@ietf.org>
List-Subscribe: <mailto:netmod-join@ietf.org>
List-Unsubscribe: <mailto:netmod-leave@ietf.org>

Hi, Andy,


Changing the running config so it is split into 2 datastores makes operations more complicated.
It doesn't actually work since YANG is hierarchical and has cross-references.

IMO the only improvement needed is to add metadata to <running> so a client can
better understand the system config and make edit requests that will not fail.

Most deployment (90%?) is non-NMDA and it will probably stay that way.
The developer focus is on data model deployment, not redoing the foundation. IMO people want YANG to
be simpler and faster. I don't see how splitting config up into 2 datastores helps.

I am not sure I agree this draft is “changing the running config so it is split into 2 datastores”.

I think it is already the case that NMDA never puts system configuration into <running>, it’s only in <operational>. So has NMDA already made NBC changes to the behavior of non-NMDA servers? If you know any existing standards that say system configuration is defined in <running>, I would appreciate that if you could help navigate, as I’ve always thought putting system configuration into <running> is just one of the existing various proprietary implementations, our implementation used to be this way, but not now, after some customers complained that they don’t want to see some system config magically appeared when they write some config into <running> and then read back, and there are other reasons like performance.


Best Regards,
Qiufang