IETF Logo Mail Archive

Re: [netconf] [Editorial Errata Reported] RFC6243 (7428)

Andy Bierman <andy@yumaworks.com> Tue, 18 April 2023 17:52 UTC

Return-Path: <andy@yumaworks.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 3CD14C151556 for <netconf@ietfa.amsl.com>; Tue, 18 Apr 2023 10:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks.com
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 zBN12Ley3Hr3 for <netconf@ietfa.amsl.com>; Tue, 18 Apr 2023 10:52:19 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 B6FF0C151B30 for <netconf@ietf.org>; Tue, 18 Apr 2023 10:52:18 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id z38so15216494ljq.12 for <netconf@ietf.org>; Tue, 18 Apr 2023 10:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks.com; s=google; t=1681840336; x=1684432336; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0tJsLfTq3ufUesHj/nFwK8PrcCJxnfydLgsaLjxQalM=; b=O5NyeTKAu5Qmm/IEUSxZkBqRVThmvXsWT5RGJ+0c8g7Zj3pIaa7jrXcHxs6oKSMxKa mSYB2OhWdsMh2+omzo8WJsOlGezHvOFanbNuT4ZLqNvFzh1ZqM3NusMjE0cQKHh3eGX1 lsH5X0OHUxGtXiUHUwFFNfKixxgXsHBMb1vUD6DpbdTVXn3ZjjMcxMxGi5e73isQ3bpb Yq5Xij6zoZ0A41A/yn0PfcemQ2kPBW0uEf/e+TnHxKD1A8Ab1pXcHqkUtg5vX2VrCehA NQLbln0X1TV3QqYeiLvnfNHMj/o/mKKZW2tabzvLiwVXmRPc9L2tGrRRoGwvly4nM2wQ xhtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681840336; x=1684432336; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0tJsLfTq3ufUesHj/nFwK8PrcCJxnfydLgsaLjxQalM=; b=NRSZRWQ62UVbHw2wpO9c/wJXwt2ks4EOoLNrcpxF6pm3eZzJBOPWVgKH7Yo8Qs2Tc9 wdgkrK0QlzQH/wxPbbzmXMYmhTXoLoNNHWAqAhiVJfjjUS+pKDF1crFGH3Jcu/Yis0Sz Acy3TCKqd76KzsR2zlqEVlY6WHVxJmnB3dgSVL6DCc46DdjxErt1e/m11d3vXNCRnRSA ADU4Pz7acalvoP02abT085lIaW5Caol8rVDgvcXdTcrOgm6NFMqEQxCmZTKoSlXVwNxc dw2k36w1KqiRItWhsYdRQOzD5i3b3zllK+ps4v/Wq9TDY0oiar5jbbcJ//dOaorScKBe 8e+Q==
X-Gm-Message-State: AAQBX9fsPaoUjDhRs37aBaDLT5rV1EThUORW17KfwPPYChDiD5KdPB0C 47ZNWqhoEVsOlz6NARzNDjxgkjeIJqdsA9qmDeDnwg==
X-Google-Smtp-Source: AKy350YfdztMO5m7uV8VgFFVfM3GFdpKM2ayWG9z5EW3ExLceFCxhrPgAqkIHlIMlYBNFNPt5prR7Cyg5W8kGPEfFrQ=
X-Received: by 2002:a2e:9dc7:0:b0:2a8:c7e4:9259 with SMTP id x7-20020a2e9dc7000000b002a8c7e49259mr919627ljj.34.1681840336071; Tue, 18 Apr 2023 10:52:16 -0700 (PDT)
MIME-Version: 1.0
References: <20230418123830.87C2B55E92@rfcpa.amsl.com>
In-Reply-To: <20230418123830.87C2B55E92@rfcpa.amsl.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 18 Apr 2023 10:52:04 -0700
Message-ID: <CABCOCHQ8m=A37p=iTWzx1D23sH7tTtCM2qtvt15OJxxtUmonvw@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: dylan.sadoun@orange.com, balazs.lengyel@ericsson.com, netconf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000cd054805f99ff7fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/kZctwkjW3JH0VAuD023V37CikwA>
Subject: Re: [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 17:52:23 -0000

Hi,

This Errata should be rejected.
There is no need to add an additional "eth4" interface entry to the
examples in Appendix A.


Andy


On Tue, Apr 18, 2023 at 5:38 AM RFC Errata System <rfc-editor@rfc-editor.org>
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/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
>

v2.23.0 | Report a Bug | By Email