Return-Path: 
 <01000197cb8d182c-9ef3ffe2-d204-434a-84c1-a5c0a8af83cc-000000@amazonses.watsen.net>
X-Original-To: netmod@mail2.ietf.org
Delivered-To: netmod@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1])
	by mail2.ietf.org (Postfix) with ESMTP id 687713CDD291
	for <netmod@mail2.ietf.org>; Wed,  2 Jul 2025 07:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.665
X-Spam-Level: 
X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5
	tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
	RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001,
	RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.232,
	RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001,
	SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key)
	header.d=amazonses.com
Received: from mail2.ietf.org ([166.84.6.31])
	by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id B37g9oaJpkJO for <netmod@mail2.ietf.org>;
	Wed,  2 Jul 2025 07:35:11 -0700 (PDT)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com
 [54.240.8.96])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256)
	(No client certificate requested)
	by mail2.ietf.org (Postfix) with ESMTPS id 956E13CDB05C
	for <netmod@ietf.org>; Wed,  2 Jul 2025 07:31:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1751466711;
	h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID;
	bh=l9k9TmqaGf78ajdwEG5lUDPhalHk4zwa8QHpnMwgo0o=;
	b=iOGLbuu4hxPd4UTtL0O7CfVcnhEh9FMFn9fFMUra9mjX45E05U515ikxoHf+CWDS
	caqhwO3Aymx1Z2/NDur7C5VAyNMVhLXbK/CFu1CAJk0EtWatCz9So670Sc6ey3Lq61i
	uTmVxAVphLTco/rUyyMAyHISXip8B2jFJDVGbRU4=
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: 
 <010001975fa8de84-cc828a4b-b30b-422c-b1b5-bb507135826d-000000@email.amazonses.com>
Date: Wed, 2 Jul 2025 14:31:51 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: 
 <01000197cb8d182c-9ef3ffe2-d204-434a-84c1-a5c0a8af83cc-000000@email.amazonses.com>
References: 
 <174729479008.2148929.4497624645916698398@dt-datatracker-58d4498dbd-6gzjf>
 <701e0394bb364174a1ac6cf457f17bef@huawei.com>
 <010001975fa8de84-cc828a4b-b30b-422c-b1b5-bb507135826d-000000@email.amazonses.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>,
	"Jason Sterne (Nokia)" <jason.sterne@nokia.com>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
Feedback-ID: 
 ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2025.07.02-54.240.8.96
Message-ID-Hash: DOOBWIVZTNPNGJQFTVASUQ6PHNX3YPJD
X-Message-ID-Hash: DOOBWIVZTNPNGJQFTVASUQ6PHNX3YPJD
X-MailFrom: 
 01000197cb8d182c-9ef3ffe2-d204-434a-84c1-a5c0a8af83cc-000000@amazonses.watsen.net
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: "netmod@ietf.org" <netmod@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: =?utf-8?q?=5Bnetmod=5D_Re=3A_I-D_Action=3A_draft-ietf-netmod-immutable-flag-?=
	=?utf-8?q?04=2Etxt?=
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/netmod/in4T0YoLUA8gU16KXHfv8TqV7HQ>
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>

Rob/Jason,

Can you confirm the updates are good?

I wish to successfully-close the WGLC now.

Thanks,
Kent


> On Jun 11, 2025, at 11:43=E2=80=AFAM, Kent Watsen <kent@watsen.net> =
wrote:
>=20
> Hi Qiufang, I have looked through the diffs and all seems good now =
(sans the nit below).
>=20
> Nit:  one example shows an unencrypted password, i.e., beginning with =
"$0$.  The "ianach:crypt-hash" type should always return a hashed =
password.=20
>=20
> Rob/Jason - are the updates okay with you as well?
>=20
> Kent
>=20
>=20
>=20
>=20
>=20
>=20
>> On May 15, 2025, at 3:49=E2=80=AFAM, maqiufang (A) =
<maqiufang1=3D40huawei.com@dmarc.ietf.org> wrote:
>>=20
>> Hi, all,
>>=20
>> -04 is available now, which addresses the 2nd WGLC comments from =
Kent, Jason, and Rob (thanks a lot for your valuable comments!).
>>=20
>> The primary revisions are concentrated in section 5 (i.e., Use of =
Immutable Flag for Different Statements), alongside the incorporation of =
examples of  immutability of list/leaf-list as shown in Appendix B. Both =
parts might benefit from further review from the WG to ensure agreement =
is clearly documented. There are also some other updates as suggested by =
reviewers. Would appreciate any other comments and suggestions from the =
WG. Thanks a lot!
>>=20
>> Best Regards,
>> Qiufang
>>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
>> Sent: Thursday, May 15, 2025 3:40 PM
>> To: i-d-announce@ietf.org
>> Cc: netmod@ietf.org
>> Subject: [netmod] I-D Action: draft-ietf-netmod-immutable-flag-04.txt
>>=20
>> Internet-Draft draft-ietf-netmod-immutable-flag-04.txt is now =
available. It is a work item of the Network Modeling (NETMOD) WG of the =
IETF.
>>=20
>>  Title:   YANG Metadata Annotation for Immutable Flag
>>  Authors: Qiufang Ma
>>           Qin Wu
>>           Balazs Lengyel
>>           Hongwei Li
>>  Name:    draft-ietf-netmod-immutable-flag-04.txt
>>  Pages:   24
>>  Dates:   2025-05-15
>>=20
>> Abstract:
>>=20
>>  This document defines a way to formally document an existing
>>  behavior, implemented by servers in production, on the immutability
>>  of some system-provided nodes, using a YANG metadata annotation
>>  called "immutable" to flag which nodes are immutable.
>>=20
>>  Clients may use "immutable" annotations provided by the server, to
>>  know beforehand why certain otherwise valid configuration requests
>>  will cause the server to return an error.
>>=20
>>  The immutable flag is descriptive, documenting an existing behavior,
>>  not proscriptive, dictating server behaviors.
>>=20
>>  This document updates RFC 8040 and RFC 8526.
>>=20
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-immutable-flag/
>>=20
>> There is also an HTML version available at:
>> =
https://www.ietf.org/archive/id/draft-ietf-netmod-immutable-flag-04.html
>>=20
>> A diff from the previous version is available at:
>> =
https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-netmod-immutable-fl=
ag-04
>>=20
>> Internet-Drafts are also available by rsync at:
>> rsync.ietf.org::internet-drafts
>>=20
>>=20
>> _______________________________________________
>> netmod mailing list -- netmod@ietf.org
>> To unsubscribe send an email to netmod-leave@ietf.org
>> _______________________________________________
>> netmod mailing list -- netmod@ietf.org
>> To unsubscribe send an email to netmod-leave@ietf.org
>=20
> _______________________________________________
> netmod mailing list -- netmod@ietf.org
> To unsubscribe send an email to netmod-leave@ietf.org

