[netconf] [Errata Verified] RFC6243 (7426)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 02 October 2023 12:55 UTC

To: dylan.sadoun@orange.com, andy@yumaworks.com, balazs.lengyel@ericsson.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rwilton@cisco.com, iesg@ietf.org, netconf@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231002125534.41FA6E7276@rfcpa.amsl.com>
Date: Mon, 02 Oct 2023 05:55:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/-3sO87KUQTwv-_-wd0E6YMnLTXo>
Subject: [netconf] [Errata Verified] RFC6243 (7426)
Precedence: list

The following errata report has been verified for RFC6243,
"With-defaults Capability for NETCONF". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7426

--------------------------------------
Status: Verified
Type: Technical

Reported by: Dylan Sadoun <dylan.sadoun@orange.com>
Date Reported: 2023-04-18
Verified by: Rob Wilton (IESG)

Section: 2.3.1

Original Text
-------------
   When data is retrieved from a server using the 'explicit' basic mode,
   and the <with-defaults> parameter is not present, data nodes MUST be
   reported if explicitly set by the client, even if they contain the
   schema default value.  Non-configuration data nodes containing the
   schema default value MUST be reported.

Corrected Text
--------------
   When data is retrieved from a server using the 'explicit' basic mode,
   and the <with-defaults> parameter is not present, data nodes MUST be
   reported if explicitly set by the client, even if they contain the
   schema default value.  A conceptual data node that would be set by
   the server to the schema default value MUST NOT be reported.
   Non-configuration data nodes containing the schema default value MUST
   be reported.

Notes
-----
This change brings the text and behavior more in alignment between ‘explicit’ Basic Mode (2.3.1) and ‘explicit’ Retrieval Mode (3.3).

The original errata also proposed that the text be clarified to define the behaviour for configuration explicitly set by a server, but after discussion with members of the WG, the general consensus is that this behaviour is outside the scope of the YANG and related management protocol RFCs that generally define changes to the server datastore contents in terms of explicit client requests to changes to the server’s configuration data.  The terminology definition of “Explicitly set data” in the RFC does give some guidance of the expectations of how server set data should be treated.

Further clarification on server behavior absent of explicit client operations should be specified in new RFCs.

--------------------------------------
RFC6243 (draft-ietf-netconf-with-defaults-14)
--------------------------------------
Title               : With-defaults Capability for NETCONF
Publication Date    : June 2011
Author(s)           : A. Bierman, B. Lengyel
Category            : PROPOSED STANDARD
Source              : Network Configuration
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

[netconf] [Errata Verified] RFC6243 (7426) RFC Errata System