Re: [netconf] [Technical Errata Reported] RFC6243 (7427)

[Andy Bierman <[e-mail]>]

Hi,

This Errata should be rejected.
The additional sentence is not needed and was not left out of the original
text by error.

This sentence refers to a node without an instance so the YANG default is
used instead.

     A conceptual data node that would be set by the server to the schema
default value MUST NOT be reported.

The key text is "would be set". A better clarification is "would be used"
The intent is that the node is not explicitly set.

It is not possible for a node to have a value other than the YANG default
and not be explicitly set.

Andy

On Tue, Apr 18, 2023 at 5:37 AM RFC Errata System <[e-mail]>
wrote:

> The following errata report has been submitted for RFC6243,
> "With-defaults Capability for NETCONF".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7427
>
> --------------------------------------
> Type: Technical
> Reported by: Dylan Sadoun <[e-mail]>
>
> 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.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> 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
>