[netconf] [Errata Rejected] RFC6243 (7427)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 02 October 2023 13:13 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, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231002131306.0441FE7276@rfcpa.amsl.com>
Date: Mon, 02 Oct 2023 06:13:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ZJNu5Kh9UOmzjGMrELEInRXC9_4>
Subject: [netconf] [Errata Rejected] RFC6243 (7427)
Precedence: list

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

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

--------------------------------------
Status: Rejected
Type: Technical

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

Section: 3.3

Original Text
-------------
When data is retrieved with a <with-defaults> parameter equal to 'explicit', a data node that was set by a client to its schema default value MUST be reported. 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.

Corrected Text
--------------
When data is retrieved with a <with-defaults> parameter equal to 'explicit', a data node that was set by a client to its schema default value MUST be reported. A conceptual data node that would be set by the server to the schema default value MUST NOT be reported. A conceptual data node that would be set by the server to a value other than its schema default value MUST be reported. Non-configuration data nodes containing the schema default value MUST be reported.

Notes
-----
The RFC defines "Explicitly set data" for the sole purpose of defining the explicit retrieval mode. This definition is clear about when data set by the server should be considered "explicitly set" i.e. when not set to the schema default value. However, the 2.3.1 and 3.3 sections are ambiguous and prone to misunderstanding, as they only emphasise the "set by the client" case, which leads to think that data set by the server to a value different from its schema default value should not be reported.
This erratum is for the 3.3 section.
--VERIFIER NOTES--
After discussion with the WG, it was agreed that several server implementations would likely behave as your errata suggests. However, the consensus was that this behavior is beyond what can be clarified as part of an errata without specifying a new RFC. In particular, it is noted that the current RFC predominantly defines expected behavior for data nodes modified via the external API between the client and server and defining "conceptual data nodes being set by a server" is beyond the scope of behavior specified by the RFC.

Please also see errata 7426 that helps clarify the behavior for section 2.3.1.

--------------------------------------
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 Rejected] RFC6243 (7427) RFC Errata System