[Netconf] [Technical Errata Reported] RFC6241 (5388)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 11 June 2018 15:37 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 71468129C6B for <netconf@ietfa.amsl.com>; Mon, 11 Jun 2018 08:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KjbbkUPYKFDF for <netconf@ietfa.amsl.com>; Mon, 11 Jun 2018 08:37:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A82A41277BB for <netconf@ietf.org>; Mon, 11 Jun 2018 08:37:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D1B5DB80E72; Mon, 11 Jun 2018 08:37:45 -0700 (PDT)
To: rob.enns@gmail.com, mbj@tail-f.com, j.schoenwaelder@jacobs-university.de, andy@yumaworks.com, ibagdona@gmail.com, warren@kumari.net, kwatsen@juniper.net, mjethanandani@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jonathan@hansfords.net, netconf@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180611153745.D1B5DB80E72@rfc-editor.org>
Date: Mon, 11 Jun 2018 08:37:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/-PD6MNtmdg3ioFSENP9ubAJVw5Y>
Subject: [Netconf] [Technical Errata Reported] RFC6241 (5388)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing 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: Mon, 11 Jun 2018 15:37:49 -0000
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/eid5388 -------------------------------------- Type: Technical Reported by: Jonathan Hansford <jonathan@hansfords.net> Section: 8.3.4.2 Original Text ------------- 8.3.4.2. <discard-changes> If the client decides that the candidate configuration is not to be committed, the <discard-changes> operation can be used to revert the candidate configuration to the current running configuration. <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <discard-changes/> </rpc> This operation discards any uncommitted changes by resetting the candidate configuration with the content of the running configuration. Corrected Text -------------- 8.3.4.2. <discard-changes> Description: If the client decides that the candidate configuration is not to be committed, the <discard-changes> operation can be used to revert the candidate configuration to the current running configuration. This operation discards any uncommitted changes by resetting the candidate configuration with the content of the running configuration. Positive Response: If the device was able to satisfy the request, an <rpc-reply> is sent that contains an <ok> element. Negative Response: An <rpc-error> element is included in the <rpc-reply> if the request cannot be completed for any reason. Example: <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <discard-changes/> </rpc> <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ok/> </rpc-reply> Notes ----- RFC 6241 section 1.1 includes the following two definitions: o protocol operation: A specific remote procedure call, as used within the NETCONF protocol. o remote procedure call (RPC): Realized by exchanging <rpc> and <rpc-reply> messages. Positive and negative responses are detailed for all instances of an operation within the RFC with the exception of <discard-changes>. Section 8.3.4.2 identifies <discard-changes> as an operation, and appendices A and C identify "rollback-failed" as an error-tag to be used when the "Request to roll back some configuration change (via rollback-on-error or <discard-changes> operations) was not completed for some reason." This change clarifies that <discard-changes> requires an <rpc-reply>. 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
- Re: [Netconf] [Technical Errata Reported] RFC6241… Kent Watsen
- Re: [Netconf] [Technical Errata Reported] RFC6241… Mahesh Jethanandani
- Re: [Netconf] [Technical Errata Reported] RFC6241… Kent Watsen
- [Netconf] [Technical Errata Reported] RFC6241 (53… RFC Errata System
- Re: [Netconf] [Technical Errata Reported] RFC6241… Andy Bierman