[netmod] FW: New Version Notification for draft-ma-netmod-immutable-flag-03.txt

"maqiufang (A)" <maqiufang1@huawei.com> Thu, 11 August 2022 09:52 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 D9B65C14CF05 for <netmod@ietfa.amsl.com>; Thu, 11 Aug 2022 02:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 1Lyb-_7VgLQB for <netmod@ietfa.amsl.com>; Thu, 11 Aug 2022 02:52:31 -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 6EA45C14CF12 for <netmod@ietf.org>; Thu, 11 Aug 2022 02:52:31 -0700 (PDT)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4M3MRv0Vzwz67xV0 for <netmod@ietf.org>; Thu, 11 Aug 2022 17:47:55 +0800 (CST)
Received: from kwepemm600018.china.huawei.com (7.193.23.140) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 11 Aug 2022 11:52:29 +0200
Received: from kwepemm600017.china.huawei.com (7.193.23.234) by kwepemm600018.china.huawei.com (7.193.23.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 11 Aug 2022 17:52:27 +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; Thu, 11 Aug 2022 17:52:27 +0800
From: "maqiufang (A)" <maqiufang1@huawei.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] FW: New Version Notification for draft-ma-netmod-immutable-flag-03.txt
Thread-Index: AditZz4DlmEC8ybxR1+C/e7VZDdayQ==
Date: Thu, 11 Aug 2022 09:52:27 +0000
Message-ID: <4d946900965c4438b63cf93923396365@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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/jDnewyF3S59lN0kfAcPSkw_ADtM>
Subject: [netmod] FW: New Version Notification for draft-ma-netmod-immutable-flag-03.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: Thu, 11 Aug 2022 09:52:35 -0000

Hi, all
This version has made the following changes:

   *  Avoid using and rephrase "server MUST reject" statement, and try
      to clarify that this documents aims to provide visibility into
      existing immutable behavior;

   *  Add a new section to discuss the inheritance of immutability;

   *  Clarify that deletion to an immutable node in <running> which is
      instantiated in <system> and copied into <running> should always
      be allowed;

   *  Clarify that write access restriction due to general YANG rules
      has no need to be marked as immutable.

More details are provided in the I-D, any comments and suggestions are much appreciated.

Best Regards,
Qiufang

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, August 11, 2022 5:45 PM
To: Balazs Lengyel <balazs.lengyel@ericsson.com>; Hongwei Li <flycoolman@gmail.com>; 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-immutable-flag-03.txt


A new version of I-D, draft-ma-netmod-immutable-flag-03.txt
has been successfully submitted by Qiufang Ma and posted to the IETF repository.

Name:		draft-ma-netmod-immutable-flag
Revision:	03
Title:		YANG Extension and Metadata Annotation for Immutable Flag
Document date:	2022-08-11
Group:		Individual Submission
Pages:		20
URL:            https://www.ietf.org/archive/id/draft-ma-netmod-immutable-flag-03.txt
Status:         https://datatracker.ietf.org/doc/draft-ma-netmod-immutable-flag/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ma-netmod-immutable-flag
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ma-netmod-immutable-flag-03

Abstract:
   This document defines a YANG extension named "immutable" to indicate
   that specific "config true" data nodes are not allowed to be
   created/deleted/updated.  To indicate that specific entries of a
   list/leaf-list node or instances inside list entries cannot be
   updated/deleted after initialization, a metadata annotation with the
   same name is also defined.  Any data node or instance marked as
   immutable is read-only to the clients of YANG-driven management
   protocols, such as NETCONF, RESTCONF and other management operations
   (e.g., SNMP and CLI requests).

   This document aims to provide more visibility into immutability
   characteristic of particular schema or instance nodes by defining a
   standard mechanism to allow the server to document the existing
   immutable configuration data, while this doesn't mean attaching such
   restrictions is encouraged.

                                                                                  


The IETF Secretariat