[Netconf] [Technical Errata Reported] RFC6241 (3821)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 06 December 2013 10:07 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 726EF1AE315 for <netconf@ietfa.amsl.com>; Fri, 6 Dec 2013 02:07:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 FBJz4iHHY-Ar for <netconf@ietfa.amsl.com>; Fri, 6 Dec 2013 02:07:41 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 8AEE51ADBE5 for <netconf@ietf.org>; Fri, 6 Dec 2013 02:07:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B33EB7FC383; Fri, 6 Dec 2013 02:07:37 -0800 (PST)
To: rob.enns@gmail.com, mbj@tail-f.com, j.schoenwaelder@jacobs-university.de, andy.bierman@brocade.com, bclaise@cisco.com, joelja@bogus.com, bertietf@bwijnen.net, mehmet.ersue@nsn.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20131206100737.B33EB7FC383@rfc-editor.org>
Date: Fri, 06 Dec 2013 02:07:37 -0800
X-Mailman-Approved-At: Fri, 06 Dec 2013 02:23:12 -0800
Cc: netconf@ietf.org, rfc-editor@rfc-editor.org
Subject: [Netconf] [Technical Errata Reported] RFC6241 (3821)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Dec 2013 10:07:44 -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_search.php?rfc=6241&eid=3821 -------------------------------------- Type: Technical Reported by: Jonathan Hansford <jonathan@hansfords.net> Section: 8.4.1 Original Text ------------- 8.4.1. Description The :confirmed-commit:1.1 capability indicates that the server will support the <cancel-commit> operation and the <confirmed>, <confirm-timeout>, <persist>, and <persist-id> parameters for the <commit> operation. See Section 8.3 for further details on the <commit> operation. A confirmed <commit> operation MUST be reverted if a confirming commit is not issued within the timeout period (by default 600 seconds = 10 minutes). The confirming commit is a <commit> operation without the <confirmed> parameter. The timeout period can be adjusted with the <confirm-timeout> parameter. If a follow-up confirmed <commit> operation is issued before the timer expires, the timer is reset to the new value (600 seconds by default). Both the confirming commit and a follow-up confirmed <commit> operation MAY introduce additional changes to the configuration. If the <persist> element is not given in the confirmed commit operation, any follow-up commit and the confirming commit MUST be issued on the same session that issued the confirmed commit. If the <persist> element is given in the confirmed <commit> operation, a follow-up commit and the confirming commit can be given on any session, and they MUST include a <persist-id> element with a value equal to the given value of the <persist> element. If the server also advertises the :startup capability, a <copy-config> from running to startup is also necessary to save the changes to startup. If the session issuing the confirmed commit is terminated for any reason before the confirm timeout expires, the server MUST restore the configuration to its state before the confirmed commit was issued, unless the confirmed commit also included a <persist> element. If the device reboots for any reason before the confirm timeout expires, the server MUST restore the configuration to its state before the confirmed commit was issued. If a confirming commit is not issued, the device will revert its configuration to the state prior to the issuance of the confirmed commit. To cancel a confirmed commit and revert changes without waiting for the confirm timeout to expire, the client can explicitly restore the configuration to its state before the confirmed commit was issued, by using the <cancel-commit> operation. Corrected Text -------------- 8.4.1. Description The :confirmed-commit:1.1 capability indicates that the server will support the <cancel-commit> operation, the <confirmed>, <confirm- timeout>, <persist>, and <persist-id> parameters for the <commit> operation, and differentiate between a to be confirmed <commit> operation (a confirmed commit) and a confirming <commit> operation. See Section 8.3 for further details on the <commit> operation. A confirmed <commit> operation MUST be reverted if a confirming commit is not issued within the timeout period (by default 600 seconds = 10 minutes). The confirming commit is a <commit> operation without the <confirmed> parameter and, if successful, cannot be reverted. The timeout period can be adjusted with the <confirm- timeout> parameter. If a follow-up confirmed <commit> operation is issued before the timer expires, the timer is reset to the new value (600 seconds by default). Both the confirming commit and a follow-up confirmed <commit> operation MAY introduce additional changes to the configuration. If the <persist> element is not given in the confirmed commit operation, any follow-up commit and the confirming commit MUST be issued on the same session that issued the confirmed commit. If the <persist> element is given in the confirmed <commit> operation, a follow-up commit and the confirming commit can be given on any session, and they MUST include a <persist-id> element with a value equal to the given value of the <persist> element. If the server also advertises the :startup capability, a <copy- config> from running to startup is also necessary to save the changes to startup. If the session issuing a sequence of one or more confirmed commits is terminated for any reason before the confirm timeout expires, the server MUST restore the configuration to its state before the sequence of confirmed commits was issued, unless the last confirmed commit also included a <persist> element. If the device reboots for any reason before the confirm timeout expires, the server MUST restore the configuration to its state before the sequence of confirmed commits was issued. If a confirming commit is not issued, the device will revert its configuration to the state prior to the issuance of the first in the current sequence of confirmed commits. To cancel the current sequence of confirmed commits and revert changes without waiting for the confirm timeout to expire, the client can explicitly restore the configuration to its state before the sequence of confirmed commits was issued, by using the <cancel-commit> operation. Notes ----- Instructions: ------------- This errata 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 (IESG) 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] [Technical Errata Reported] RFC6241 (38… RFC Errata System
- Re: [Netconf] [Technical Errata Reported] RFC6241… Bert Wijnen (IETF)
- Re: [Netconf] [Technical Errata Reported] RFC6241… Juergen Schoenwaelder
- Re: [Netconf] [Technical Errata Reported] RFC6241… Jonathan Hansford
- Re: [Netconf] [Technical Errata Reported] RFC6241… Jonathan Hansford
- Re: [Netconf] [Technical Errata Reported] RFC6241… Martin Bjorklund
- Re: [Netconf] [Technical Errata Reported] RFC6241… Ladislav Lhotka
- Re: [Netconf] [Technical Errata Reported] RFC6241… Bert Wijnen (IETF)
- Re: [Netconf] [Technical Errata Reported] RFC6241… Jonathan Hansford
- Re: [Netconf] [Technical Errata Reported] RFC6241… Bert Wijnen (IETF)
- Re: [Netconf] [Technical Errata Reported] RFC6241… Martin Bjorklund
- Re: [Netconf] [Technical Errata Reported] RFC6241… Juergen Schoenwaelder
- Re: [Netconf] [Technical Errata Reported] RFC6241… joel jaeggli
- Re: [Netconf] [Technical Errata Reported] RFC6241… Andy Bierman
- Re: [Netconf] [Technical Errata Reported] RFC6241… Andy Bierman
- Re: [Netconf] [Technical Errata Reported] RFC6241… Jonathan Hansford
- Re: [Netconf] [Technical Errata Reported] RFC6241… Andy Bierman
- Re: [Netconf] [Technical Errata Reported] RFC6241… Andy Bierman
- Re: [Netconf] [Technical Errata Reported] RFC6241… Jonathan Hansford
- Re: [Netconf] [Technical Errata Reported] RFC6241… Jonathan Hansford
- Re: [Netconf] [Technical Errata Reported] RFC6241… Andy Bierman
- Re: [Netconf] [Technical Errata Reported] RFC6241… ietfdbh
- Re: [Netconf] [Technical Errata Reported] RFC6241… Andy Bierman
- Re: [Netconf] [Technical Errata Reported] RFC6241… Martin Bjorklund
- Re: [Netconf] [Technical Errata Reported] RFC6241… Juergen Schoenwaelder
- Re: [Netconf] [Technical Errata Reported] RFC6241… Bert Wijnen (IETF)
- Re: [Netconf] [Technical Errata Reported] RFC6241… Benoit Claise
- [Netconf] [Errata Held for Document Update] RFC62… RFC Errata System
- [Netconf] Fwd: [Errata Held for Document Update] … Benoit Claise
- Re: [netconf] [Errata Held for Document Update] R… Megan Ferguson
- Re: [netconf] [Errata Held for Document Update] R… Benoit Claise
- Re: [netconf] [Errata Held for Document Update] R… Martin Bjorklund
- Re: [netconf] [Errata Held for Document Update] R… Per Hedeland
- Re: [netconf] [Errata Held for Document Update] R… Per Hedeland
- Re: [netconf] [Errata Held for Document Update] R… jonathan
- Re: [netconf] [Errata Held for Document Update] R… Jonathan