[netconf] [Editorial Errata Reported] RFC6243 (7428)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 18 April 2023 12:38 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39FE3C17A743 for <netconf@ietfa.amsl.com>; Tue, 18 Apr 2023 05:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fW1GqajbA0v3 for <netconf@ietfa.amsl.com>; Tue, 18 Apr 2023 05:38:37 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29C5C17B324 for <netconf@ietf.org>; Tue, 18 Apr 2023 05:38:30 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 87C2B55E92; Tue, 18 Apr 2023 05:38:30 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: dylan.sadoun@orange.com, andy@yumaworks.com, balazs.lengyel@ericsson.com, netconf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230418123830.87C2B55E92@rfcpa.amsl.com>
Date: Tue, 18 Apr 2023 05:38:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/6pTOdeVonqsk-kWlHYmvPZ81sUk>
Subject: [netconf] [Editorial Errata Reported] RFC6243 (7428)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2023 12:38:41 -0000
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/eid7428 -------------------------------------- Type: Editorial Reported by: Dylan Sadoun <dylan.sadoun@orange.com> Section: Appendix A Original Text ------------- A.2. Example Data Set [...] <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status>up</status> </interface> <interface> <name>eth1</name> <mtu>1500</mtu> <status>up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu>1500</mtu> <status>waking up</status> </interface> </interfaces> </data> In this example, the 'mtu' field for each interface entry is set in the following manner: +--------------+--------------+--------------+ | name | set by | mtu | +--------------+--------------+--------------+ | eth0 | client | 8192 | | eth1 | server | 1500 | | eth2 | client | 9000 | | eth3 | client | 1500 | +--------------+--------------+--------------+ [...] A.3.1. <with-defaults> = 'report-all' The behavior of the <with-defaults> parameter handling for the value 'report-all' is demonstrated in this example. <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> report-all </with-defaults> </get> </rpc> <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status>up</status> </interface> <interface> <name>eth1</name> <mtu>1500</mtu> <status>up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu>1500</mtu> <status>waking up</status> </interface> </interfaces> </data> </rpc-reply> A.3.2. <with-defaults> = 'report-all-tagged' [...] <rpc message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> report-all-tagged </with-defaults> </get> </rpc> <rpc-reply message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:wd="urn:ietf:params:xml:ns:netconf:default:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status wd:default="true">up</status> </interface> <interface> <name>eth1</name> <mtu wd:default="true">1500</mtu> <status wd:default="true">up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu wd:default="true">1500</mtu> <status>waking up</status> </interface> </interfaces> </data> </rpc-reply> A.3.3. <with-defaults> = 'trim' The behavior of the <with-defaults> parameter handling for the value 'trim' is demonstrated in this example. <rpc message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> trim </with-defaults> </get> </rpc> <rpc-reply message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> </interface> <interface> <name>eth1</name> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <status>waking up</status> </interface> </interfaces> </data> </rpc-reply> A.3.4. <with-defaults> = 'explicit' The behavior of the <with-defaults> parameter handling for the value 'explicit' is demonstrated in this example. <rpc message-id="104" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> explicit </with-defaults> </get> </rpc> <rpc-reply message-id="104" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status>up</status> </interface> <interface> <name>eth1</name> <status>up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu>1500</mtu> <status>waking up</status> </interface> </interfaces> </data> </rpc-reply> Corrected Text -------------- A.2. Example Data Set [...] <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status>up</status> </interface> <interface> <name>eth1</name> <mtu>1500</mtu> <status>up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu>1500</mtu> <status>waking up</status> </interface> <interface> <name>eth4</name> <mtu>9112</mtu> <status>better call for help</status> </interface> </interfaces> </data> In this example, the 'mtu' field for each interface entry is set in the following manner: +--------------+--------------+--------------+ | name | set by | mtu | +--------------+--------------+--------------+ | eth0 | client | 8192 | | eth1 | server | 1500 | | eth2 | client | 9000 | | eth3 | client | 1500 | | eth4 | server | 9112 | +--------------+--------------+--------------+ [...] A.3.1. <with-defaults> = 'report-all' The behavior of the <with-defaults> parameter handling for the value 'report-all' is demonstrated in this example. <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> report-all </with-defaults> </get> </rpc> <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status>up</status> </interface> <interface> <name>eth1</name> <mtu>1500</mtu> <status>up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu>1500</mtu> <status>waking up</status> </interface> <interface> <name>eth4</name> <mtu>9112</mtu> <status>better call for help</status> </interface> </interfaces> </data> </rpc-reply> A.3.2. <with-defaults> = 'report-all-tagged' [...] <rpc message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> report-all-tagged </with-defaults> </get> </rpc> <rpc-reply message-id="102" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:wd="urn:ietf:params:xml:ns:netconf:default:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status wd:default="true">up</status> </interface> <interface> <name>eth1</name> <mtu wd:default="true">1500</mtu> <status wd:default="true">up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu wd:default="true">1500</mtu> <status>waking up</status> </interface> <interface> <name>eth4</name> <mtu>9112</mtu> <status>better call for help</status> </interface> </interfaces> </data> </rpc-reply> A.3.3. <with-defaults> = 'trim' The behavior of the <with-defaults> parameter handling for the value 'trim' is demonstrated in this example. <rpc message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> trim </with-defaults> </get> </rpc> <rpc-reply message-id="103" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> </interface> <interface> <name>eth1</name> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <status>waking up</status> </interface> <interface> <name>eth4</name> <mtu>9112</mtu> <status>better call for help</status> </interface> </interfaces> </data> </rpc-reply> A.3.4. <with-defaults> = 'explicit' The behavior of the <with-defaults> parameter handling for the value 'explicit' is demonstrated in this example. <rpc message-id="104" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter type="subtree"> <interfaces xmlns="http://example.com/ns/interfaces"/> </filter> <with-defaults xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults"> explicit </with-defaults> </get> </rpc> <rpc-reply message-id="104" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <interfaces xmlns="http://example.com/ns/interfaces"> <interface> <name>eth0</name> <mtu>8192</mtu> <status>up</status> </interface> <interface> <name>eth1</name> <status>up</status> </interface> <interface> <name>eth2</name> <mtu>9000</mtu> <status>not feeling so good</status> </interface> <interface> <name>eth3</name> <mtu>1500</mtu> <status>waking up</status> </interface> <interface> <name>eth4</name> <mtu>9112</mtu> <status>better call for help</status> </interface> </interfaces> </data> </rpc-reply> Notes ----- This erratum expands existing examples to include the case of a server setting data nodes to values other than their default schema values. This echoes the other errata about sections 2.3.1 and 3.3 and the explicit retrieval mode. 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
- [netconf] [Editorial Errata Reported] RFC6243 (74… RFC Errata System
- Re: [netconf] [Editorial Errata Reported] RFC6243… Andy Bierman