Re: [Netconf] [Editorial Errata Reported] RFC6241 (5443)

Andy Bierman <andy@yumaworks.com> Fri, 27 July 2018 15:45 UTC

MIME-Version: 1.0
In-Reply-To: <20180727153628.86BB2B81052@rfc-editor.org>
References: <20180727153628.86BB2B81052@rfc-editor.org>
From: Andy Bierman <andy@yumaworks.com>
Date: Fri, 27 Jul 2018 08:45:28 -0700
Message-ID: <CABCOCHTBYDVmp4+VXmB5RHTAXudLLDF8AxcYX+7vPS_AhJ2hYw@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: Rob Enns <rob.enns@gmail.com>, Martin Bjorklund <mbj@tail-f.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Ignas Bagdonas <ibagdona@gmail.com>, Warren Kumari <warren@kumari.net>, Kent Watsen <kwatsen@juniper.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, jnatale@juniper.net, Netconf <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004c996f0571fd00ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/nQYVm8sm5pZamtRAIhbcB9cOuos>
Subject: Re: [Netconf] [Editorial Errata Reported] RFC6241 (5443)
Precedence: list

Hi,

The addition of the words "and only if" do not seem to change the semantics.
The XSD (page 83) makes it clear that <ok/> and (<rpc-error>, data) cannot
both be present.


Andy


On Fri, Jul 27, 2018 at 8:36 AM, RFC Errata System <
rfc-editor@rfc-editor.org> wrote:

> The following errata report has been submitted for RFC6241,
> "Network Configuration Protocol (NETCONF)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5443
>
> --------------------------------------
> Type: Editorial
> Reported by: Jonathan Natale <jnatale@juniper.net>
>
> Section: 4.4
>
> Original Text
> -------------
> The <ok> element is sent in <rpc-reply> messages if no errors or
> warnings occurred during the processing of an <rpc> request, and no
> data was returned from the operation.
>
> Corrected Text
> --------------
> The <ok> element is sent in <rpc-reply> messages if
> and only if
> no errors or
> warnings occurred during the processing of an <rpc> request, and no
> data was returned from the operation.
>
> Notes
> -----
> I have been informed that an <ok> element should not include any errors or
> warnings, even in the event of the associated operation completing because
> the error's severity was only at warning level).
>
> 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.
>
> --------------------------------------
> RFC6241 (draft-ietf-netconf-4741bis-10)
> --------------------------------------
> Title               : Network Configuration Protocol (NETCONF)
> Publication Date    : June 2011
> Author(s)           : R. Enns, Ed., M. Bjorklund, Ed., J. Schoenwaelder,
> Ed., A. Bierman, Ed.
> Category            : PROPOSED STANDARD
> Source              : Network Configuration
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>

[Netconf] [Editorial Errata Reported] RFC6241 (54… RFC Errata System
Re: [Netconf] [Editorial Errata Reported] RFC6241… Andy Bierman