[netmod] FW: New Version Notification for draft-ma-netmod-with-system-04.txt

"maqiufang (A)" <maqiufang1@huawei.com> Tue, 09 August 2022 11:39 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 03AE6C159486; Tue, 9 Aug 2022 04:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 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, 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 8FHgU2R7hOhj; Tue, 9 Aug 2022 04:39:53 -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 0324CC14F727; Tue, 9 Aug 2022 04:39:53 -0700 (PDT)
Received: from fraeml704-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4M2B1v5S2cz6889m; Tue, 9 Aug 2022 19:39:47 +0800 (CST)
Received: from kwepemm600019.china.huawei.com (7.193.23.64) by fraeml704-chm.china.huawei.com (10.206.15.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Tue, 9 Aug 2022 13:39:49 +0200
Received: from kwepemm600017.china.huawei.com (7.193.23.234) by kwepemm600019.china.huawei.com (7.193.23.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 9 Aug 2022 19:39:47 +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; Tue, 9 Aug 2022 19:39:47 +0800
From: "maqiufang (A)" <maqiufang1@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
CC: "draft-ma-netconf-with-system@ietf.org" <draft-ma-netconf-with-system@ietf.org>
Thread-Topic: [netmod] FW: New Version Notification for draft-ma-netmod-with-system-04.txt
Thread-Index: Adir5JIsm+5FW0sAT0iOy0x8j0t8aQ==
Date: Tue, 09 Aug 2022 11:39:47 +0000
Message-ID: <372afa20063a445e98319e568a7a8d53@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.100.87]
Content-Type: multipart/alternative; boundary="_000_372afa20063a445e98319e568a7a8d53huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/PTSHyGXWb2NxJmvxYPbXIXu2K_o>
Subject: [netmod] FW: New Version Notification for draft-ma-netmod-with-system-04.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 09 Aug 2022 11:39:55 -0000

Hi, all

v-04 is available at:

URL:            https://www.ietf.org/archive/id/draft-ma-netmod-with-system-04.txt

Status:         https://datatracker.ietf.org/doc/draft-ma-netmod-with-system/

Htmlized:       https://datatracker.ietf.org/doc/html/draft-ma-netmod-with-system

Diff:           https://www.ietf.org/rfcdiff?url2=draft-ma-netmod-with-system-04



Based on the WG discussion in IETF 114, the major update is following:

instead of simply saying

"If the 'resolve-system' parameter is not given by the client, the

server should not modify <running> in any way otherwise not specified

by the client",



v-04 has clarified that

"  If the 'resolve-system' parameter is not given by the client, the

   server should not modify <running> in any way otherwise not specified

   by the client.  Not using capitalized 'SHOULD NOT' in the previous

   sentence is intentional.  The intention is bring awareness to the

   general need to not surprise clients with unexpected changes.  It is

   desirable for clients to always opt into using mechanisms having

   server-side changes.  This document enables a client to opt into this

   behavior using the "resolve-system" parameter.  RFC 7317 enables a

   client to opt into its behavior using a "$0$" prefix."



Comments and suggestions are appreciated.



Best Regards,

Qiufang



-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
Sent: Tuesday, August 9, 2022 7:25 PM
To: Fengchong (frank) <frank.fengchong@huawei.com>; Fengchong (frank) <frank.fengchong@huawei.com>; Jan Lindblad <jlindbla@cisco.com>; Kent Watsen <kent+ietf@watsen.net>; Qin Wu <bill.wu@huawei.com>; Qin Wu <bill.wu@huawei.com>; maqiufang (A) <maqiufang1@huawei.com>
Subject: New Version Notification for draft-ma-netmod-with-system-04.txt





A new version of I-D, draft-ma-netmod-with-system-04.txt

has been successfully submitted by Qiufang Ma and posted to the IETF repository.



Name:                  draft-ma-netmod-with-system

Revision:              04

Title:                      System-defined Configuration

Document date:               2022-08-09

Group:                  Individual Submission

Pages:                   43

URL:            https://www.ietf.org/archive/id/draft-ma-netmod-with-system-04.txt

Status:         https://datatracker.ietf.org/doc/draft-ma-netmod-with-system/

Htmlized:       https://datatracker.ietf.org/doc/html/draft-ma-netmod-with-system

Diff:           https://www.ietf.org/rfcdiff?url2=draft-ma-netmod-with-system-04



Abstract:

   This document updates NMDA to define a read-only conventional

   configuration datastore called "system" to hold system-defined

   configurations.  To avoid clients' explicit copy/paste of referenced

   system-defined configuration into the target configuration datastore

   (e.g., <running>), a "resolve-system" parameter has been defined to

   allow the server acting as a "system client" to copy referenced

   system-defined nodes automatically.  The solution enables clients

   manipulating the target configuration datastore (e.g., <running>) to

   overlay and reference nodes defined in <system>, override values of

   configurations defined in <system>, and configure descendant nodes of

   system-defined nodes.









The IETF Secretariat