Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Alanna Paloma <apaloma@staff.rfc-editor.org>
In-Reply-To: <4EDA71D9-49B5-46D0-8677-DFFA4EDB2B5C@staff.rfc-editor.org>
Date: Wed, 15 Jul 2026 14:04:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C68B0429-ADC9-47E8-A5D2-7310BED5FE12@staff.rfc-editor.org>
References: <178338089143.13.8535512300281727431@rfc-editor.org>
 <F22BAB29-BFD7-48A4-BF03-31D19C1C35E9@gmail.com>
 <4EDA71D9-49B5-46D0-8677-DFFA4EDB2B5C@staff.rfc-editor.org>
To: iana@iana.org
Message-ID-Hash: CUTUWS5JB64FC52XQAM4RGXQVXYF6PBY
CC: Mahesh Jethanandani <mjethanandani@gmail.com>,
 Qin Wu <bill.wu@huawei.com>, fengchonglly@gmail.com,
 RFC Editor <rfc-editor@rfc-editor.org>,
 "maqiufang (A)" <maqiufang1@huawei.com>,
 auth48archive <auth48archive@rfc-editor.org>, ops-ads@ietf.org,
 Kent Watsen <kent+ietf@watsen.net>, netmod-chairs@ietf.org,
 "mohamed.boucadair" <mohamed.boucadair@orange.com>
Precedence: list
Subject: =?utf-8?q?=5Bauth48=5D_=5BIANA=5D_Re=3A_Final_Review=3A_RFC-to-be_10016_=28d?=
 =?utf-8?q?raft-ietf-netmod-system-config=29_in_XML?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/auth48archive/BvhTLudaHfxosXJDm_sPHzasFA4>

IANA,

Please make this minor punctuation update in the Registrant Contact =
field for this XML namespace URI in the =E2=80=9Cns=E2=80=9D registry at =
<https://www.iana.org/assignments/xml-registry/ns/yang/ietf-system-datasto=
re.txt>.

Old:=20
   URI: urn:ietf:params:xml:ns:yang:ietf-system-datastore
   Registrant Contact: The IESG.

New:=20
   URI: urn:ietf:params:xml:ns:yang:ietf-system-datastore
   Registrant Contact: The IESG

Best regards,
Alanna Paloma
RFC Production Center

> On Jul 15, 2026, at 12:51=E2=80=AFPM, Alanna Paloma =
<apaloma@staff.rfc-editor.org> wrote:
>=20
> Hi Chong, Qin, and Mahesh*,
>=20
> Thank you for your approvals. They=E2=80=99ve been noted here:
> https://queue.rfc-editor.org/final-review/rfc10016/
>=20
> *Mahesh - We have updated the text per your suggestion. As you noted =
that more changes to the template are actively being discussed, we will =
hold publication of this document until we hear further from you.
>=20
> The files have been posted here (please refresh):
> https://www.rfc-editor.org/authors/rfc10016.xml
> https://www.rfc-editor.org/authors/rfc10016.txt
> https://www.rfc-editor.org/authors/rfc10016.html
> https://www.rfc-editor.org/authors/rfc10016.pdf
>=20
> The relevant diff files have been posted here:
> https://www.rfc-editor.org/authors/rfc10016-diff.html (comprehensive =
diff)
> https://www.rfc-editor.org/authors/rfc10016-auth48diff.html (Final =
Review changes)
> https://www.rfc-editor.org/authors/rfc10016-auth48rfcdiff.html (Final =
Review changes side by side)=20
> https://www.rfc-editor.org/authors/rfc10016-lastdiff.html (last =
version to this one)
> https://www.rfc-editor.org/authors/rfc10016-lastrfcdiff.html (rfcdiff =
between last version and this)
>=20
> Best regards,
> Alanna Paloma
> RFC Production Center
>=20
>> On Jul 15, 2026, at 10:42=E2=80=AFAM, Mahesh Jethanandani =
<mjethanandani@gmail.com> wrote:
>>=20
>> Hi Alanna,
>>=20
>> I have looked at the changes you have made for question #5. Most of =
the changes look good to me. However, there is more change that we have =
to make (and something that I need to update the wiki also with) is the =
following:
>>=20
>> In the second paragraph, the template text is getting updated to say =
the following. Note, this is still being debated, and we can expect some =
more changes to the text.
>>=20
>>=20
>> OLD:
>> (1) have to use a secure transport layer (e.g., Secure Shell (SSH)
>> [RFC4252], TLS [RFC8446], and QUIC [RFC9000]) and (2) have to use
>> mutual authentication.
>>=20
>> NEW:
>>=20
>> (1) have to use a secure transport layer and (2) have to use
>> mutual authentication (e.g., Secure Shell (SSH) [RFC4252],
>> TLS [RFC8446], and QUIC [RFC9000]).
>>=20
>>> On Jul 6, 2026, at 4:34=E2=80=AFPM, rfc-editor@rfc-editor.org wrote:
>>>=20
>>> Authors and *AD,
>>>=20
>>> While reviewing this document during Final Review, please resolve =
(as necessary) the following questions, which are also in the source =
file.
>>>=20
>>> *AD, please review question #5 below.
>>>=20
>>>=20
>>> 1) <!--[rfced] We note that most of the recently published RFCs
>>> containing YANG modules format their titles as "A YANG Data Model
>>> for...", for example:
>>>=20
>>> RFC 9094 - A YANG Data Model for Wavelength Switched Optical =
Networks (WSONs)
>>> RFC 9093 - A YANG Data Model for Layer 0 Types
>>> RFC 9067 - A YANG Data Model for Routing Policy
>>>=20
>>> Please consider whether the title of this document should be =
updated.
>>>=20
>>> Current:
>>>  System-Defined Configuration
>>>=20
>>> Perhaps:
>>>  A YANG Data Model for System-Defined Configuration   =20
>>> -->
>>>=20
>>>=20
>>> 2) <!--[rfced] Per guidance from Section 2 of RFC 8340, we moved the
>>> lines in the YANG tree diagram (in Section 7.1) over two spaces
>>> to the left. Please review and let us know of any objections.
>>> -->
>>>=20
>>>=20
>>> 3) <!--[rfced] Because XML examples are present in this document, we
>>> added a citation to W3C in Section 7.3 and a corresponding entry
>>> under the Informative References section.  Please let us know if
>>> this is agreeable or if you prefer otherwise.
>>>=20
>>> Original:
>>>  The following example shows how the configuration in <system> could
>>>  be retrieved in a NETCONF <get-data> RPC operation.  The example =
uses
>>>  the "example-application" fictional data model defined in
>>>  Appendix A.1.
>>>=20
>>> Current:=20
>>>  The following example shows how the configuration in <system> could
>>>  be retrieved in a NETCONF <get-data> RPC operation.  The example
>>>  uses XML [W3C.XML1.0] and the "example-application" fictional data
>>>  model defined in Appendix A.1.
>>> -->
>>>=20
>>>=20
>>> 4) <!--[rfced] FYI - In Section 7.3, note that we moved the example =
over
>>> three spaces to the left because
>>> "xmlns:sysds=3D"urn:ietf:params:xml:ns:yang:ietf-system-datastore">"
>>> was 3 characters over the limit.
>>> -->
>>>=20
>>>=20
>>> 5) <!--[rfced] *[AD] We have altered some text in the Security
>>> Considerations section to match the boilerplate text at
>>> <https://wiki.ietf.org/group/ops/yang-security-guidelines>. Also
>>> note that paragraph 4 varies from the template (we attempted to
>>> make it match more closely). Please review and let us know if any
>>> further updates are needed or if the text is agreeable as is.
>>> -->       =20
>>>=20
>>>=20
>>> 6) <!--[rfced] Note that the YANG module examples have been updated =
per
>>> the formatting option of pyang.  Please let us know any concerns.
>>>=20
>>> a) example-application has been updated as follows:
>>>=20
>>> prefix "ex-app" -> prefix ex-app
>>> prefix "inet"   -> prefix inet
>>>=20
>>> b) example-acl has been updated as follows:
>>>=20
>>> prefix "ex-acl" -> prefix ex-acl
>>> prefix "ex-app" -> prefix ex-app
>>> prefix "inet"   -> prefix inet
>>>=20
>>> c) example-interface has been updated as follows:
>>>=20
>>> prefix "ex-if" -> prefix ex-if
>>> prefix "inet"  -> prefix inet
>>> key name       -> key "name"
>>>=20
>>> d) example-interface-management has been updated as follows:
>>>=20
>>> prefix "ex-ifm" -> prefix ex-ifm
>>> prefix "inet"   -> prefix inet
>>> -->
>>>=20
>>>=20
>>> 7) <!--[rfced] We note that the following system configuration terms =
are
>>> hyphenated. Are these specific terms that should always appear
>>> hyphenated? We are confirming because adverbs ending in "ly" are
>>> not typically hyphenated in the RFC Series, and we could not find
>>> the hyphenated forms of these terms in past RFCs.
>>>=20
>>> If the hyphens are not essential, we would remove them from
>>> "immediately-present" and "conditionally-present", and we would
>>> hyphenate "always present" only when in attributive position=20
>>> (i.e., when followed by a noun). Please let us know your preference.
>>>=20
>>> always-present
>>> conditionally-present
>>> immediately-present
>>> -->
>>>=20
>>>=20
>>> 8) <!-- [rfced] FYI - We have added expansions for the following
>>> abbreviations per Section 3.6 of RFC 7322 ("RFC Style
>>> Guide"). Please review each expansion in the document carefully
>>> to ensure correctness.
>>>=20
>>> Access Control List (ACL)
>>> Network Configuration Protocol (NETCONF)
>>> -->
>>>=20
>>>=20
>>> 9) <!-- [rfced] Please review the "Inclusive Language" portion of =
the online
>>> Style Guide =
<https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
>>> and let us know if any changes are needed.  Updates of this nature =
typically
>>> result in more precise language, which is helpful for readers.=20
>>>=20
>>> Note that our script did not flag any words in particular, but this =
should=20
>>> still be reviewed as a best practice.
>>> -->
>>>=20
>>>=20
>>> Thank you.
>>>=20
>>> Alanna Paloma and Karen Moore
>>> RFC Production Center
>>>=20
>>>=20
>>> On Jul 6, 2026, at 4:24=E2=80=AFPM, rfc-editor@rfc-editor.org wrote:
>>>=20
>>> *****IMPORTANT*****
>>>=20
>>> RFC Author(s):
>>> --------------
>>>=20
>>> Final Review for RFC-to-be 10016 <draft-ietf-netmod-system-config>
>>>=20
>>> Your document is now available for Final Review (previously AUTH48). =
Once it has been
>>> reviewed and approved by you and all coauthors, it will be published =
as an RFC.
>>> If an author is no longer available, there are several remedies;
>>> see the Unavailable Authors section
>>> =
(https://authors.ietf.org/rfc-publication-process#unavailable-authors).
>>>=20
>>> You and you coauthors are responsible for engaging other parties
>>> (e.g., Contributors or Working Group) as necessary before providing
>>> your approval.
>>>=20
>>> Planning your review
>>> ---------------------
>>>=20
>>> Please review the following aspects of your document:
>>>=20
>>> *  RFC Editor questions
>>>=20
>>> Please review and resolve any questions raised by the RFC Editor
>>> that have been included in the XML file as comments marked as
>>> follows:
>>>=20
>>> <!-- [rfced] ... -->
>>>=20
>>> These questions will also be sent in a subsequent email.
>>>=20
>>> *  Changes submitted by coauthors
>>>=20
>>> Please ensure that you review any changes submitted by your
>>> coauthors.  We assume that if you do not speak up that you
>>> agree to changes submitted by your coauthors.
>>>=20
>>> *  Content
>>>=20
>>> Please review the full content of the document, as this cannot
>>> change once the RFC is published.  Please pay particular attention =
to:
>>> - IANA considerations updates (if applicable)
>>> - contact information
>>> - references
>>>=20
>>> *  Copyright notices and legends
>>>=20
>>> Please review the copyright notice and legends as defined in
>>> RFC 5378 and the Trust Legal Provisions
>>> (TLP =E2=80=93 https://trustee.ietf.org/license-info).
>>>=20
>>> *  Semantic markup
>>>=20
>>> Please review the markup in the XML file to ensure that elements of
>>> content are correctly tagged.  For example, ensure that <sourcecode>
>>> and <artwork> are set correctly.  See details at
>>> <https://authors.ietf.org/rfcxml-vocabulary>.
>>>=20
>>> *  Formatted output
>>>=20
>>> Please review the PDF, HTML, and TXT files to ensure that the
>>> formatted output, as generated from the markup in the XML file, is
>>> reasonable.  Please note that the TXT will have formatting
>>> limitations compared to the PDF and HTML.
>>>=20
>>>=20
>>> Submitting changes
>>> ------------------
>>>=20
>>> To submit changes, please reply to this email using 'REPLY ALL' as =
all
>>> the parties CCed on this message need to see your changes. The =
parties
>>> include:
>>>=20
>>> *  your coauthors
>>>=20
>>> *  rfc-editor@rfc-editor.org (the RPC team)
>>>=20
>>> *  other document participants, depending on the stream (e.g.,
>>>    IETF Stream participants are your working group chairs, the
>>>    responsible ADs, and the document shepherd).
>>>=20
>>> *  auth48archive@rfc-editor.org, which is an archival mailing list
>>>    to preserve discussion about the document while in the RPC =
editorial
>>>    queue; it is not an active discussion list:
>>>=20
>>>   *  More info:
>>>      =
https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P=
8O4Zc
>>>=20
>>>   *  The archive itself:
>>>      https://mailarchive.ietf.org/arch/browse/auth48archive/
>>>=20
>>>   *  Note: If only absolutely necessary, you may temporarily opt out
>>>      of the archiving of messages (e.g., to discuss a sensitive =
matter).
>>>      If needed, please add a note at the top of the message that you
>>>      have dropped the address. When the discussion is concluded,
>>>      auth48archive@rfc-editor.org will be re-added to the CC list =
and
>>>      its addition will be noted at the top of the message.
>>>=20
>>> You may submit your changes in one of two ways:
>>>=20
>>> An update to the provided XML file
>>> =E2=80=94 OR =E2=80=94
>>> An explicit list of changes in this format
>>>=20
>>> Section # (or indicate Global)
>>>=20
>>> OLD:
>>> old text
>>>=20
>>> NEW:
>>> new text
>>>=20
>>> You do not need to reply with both an updated XML file and an =
explicit
>>> list of changes, as either form is sufficient.
>>>=20
>>> We will ask a stream manager to review and approve any changes that =
seem
>>> beyond editorial in nature, e.g., addition of new text, deletion of =
text,
>>> and technical changes.  Information about stream managers can be =
found in
>>> the FAQ.  Editorial changes do not require approval from a stream =
manager.
>>>=20
>>>=20
>>> Approving for publication
>>> --------------------------
>>>=20
>>> To approve your RFC for publication, please reply to this email =
stating
>>> that you approve this RFC for publication.  Please use 'REPLY ALL',
>>> as all the parties CCed on this message need to see your approval.
>>>=20
>>>=20
>>> Files
>>> -----
>>>=20
>>> The files are available here:
>>> https://www.rfc-editor.org/authors/rfc10016.xml
>>> https://www.rfc-editor.org/authors/rfc10016.html
>>> https://www.rfc-editor.org/authors/rfc10016.pdf
>>> https://www.rfc-editor.org/authors/rfc10016.txt
>>>=20
>>> Diff file of the text:
>>> https://www.rfc-editor.org/authors/rfc10016-diff.html
>>> https://www.rfc-editor.org/authors/rfc10016-rfcdiff.html (side by =
side)
>>>=20
>>> Diff of the XML:
>>> https://www.rfc-editor.org/authors/rfc10016-xmldiff1.html
>>>=20
>>>=20
>>> Tracking progress
>>> -----------------
>>>=20
>>> Details on the status of your Final Review are here:
>>> https://queue.rfc-editor.org/final-review/rfc10016/
>>>=20
>>> Please let us know if you have any questions.
>>>=20
>>> Thank you for your cooperation,
>>>=20
>>> RFC Editor
>>>=20
>>> --------------------------------------
>>> RFC 10016 (draft-ietf-netmod-system-config)
>>>=20
>>> Title            : System-defined Configuration
>>> Author(s)        : Q. Ma, Ed.,
>>>                 Q. Wu,
>>>                 C. Feng
>>> WG Chair(s)      : Kent Watsen, Lou Berger
>>> Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani
>>=20
>>=20
>> Mahesh Jethanandani
>> mjethanandani@gmail.com
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20