[Netconf] Fwd: [Technical Errata Reported] RFC5717 (2657)
"Bert (IETF) Wijnen" <bertietf@bwijnen.net> Fri, 03 December 2010 09:25 UTC
Return-Path: <bertietf@bwijnen.net>
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EABE28C180 for <netconf@core3.amsl.com>; Fri, 3 Dec 2010 01:25:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.461
X-Spam-Level:
X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXYuE-oBnlDy for <netconf@core3.amsl.com>; Fri, 3 Dec 2010 01:25:52 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id F0C073A68C6 for <netconf@ietf.org>; Fri, 3 Dec 2010 01:25:51 -0800 (PST)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <bertietf@bwijnen.net>) id 1PORv1-0006Ve-4D for netconf@ietf.org; Fri, 03 Dec 2010 10:27:08 +0100
Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.63) (envelope-from <bertietf@bwijnen.net>) id 1PORv0-0008J5-TQ for netconf@ietf.org; Fri, 03 Dec 2010 10:27:07 +0100
Message-ID: <4CF8B7EA.7050708@bwijnen.net>
Date: Fri, 03 Dec 2010 10:27:06 +0100
From: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Netconf <netconf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4a40c92f6efe55790d64b44015b53c13e
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4a40c92f6efe55790d64b44015b53c13e
Subject: [Netconf] Fwd: [Technical Errata Reported] RFC5717 (2657)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 03 Dec 2010 09:25:53 -0000
FYI, I did not see this reflected on our WG mailing list. Martin, can you have a first look at this, since Balazs is not following thiss as closely anymore as he used to do. Bert -------- Original Message -------- Subject: [Technical Errata Reported] RFC5717 (2657) Date: Thu, 2 Dec 2010 21:30:01 -0800 (PST) From: RFC Errata System <rfc-editor@rfc-editor.org> To: balazs.lengyel@ericsson.com, mbj@tail-f.com, dromasca@avaya.com, rbonica@juniper.net, bertietf@bwijnen.net, mehmet.ersue@nsn.com CC: viswanath@huawei.com, netconf@ietf.org, rfc-editor@rfc-editor.org The following errata report has been submitted for RFC5717, "Partial Lock Remote Procedure Call (RPC) for NETCONF". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5717&eid=2657 -------------------------------------- Type: Technical Reported by: B Viswanath Reddy<viswanath@huawei.com> Section: Appendix C Original Text ------------- Step 6 - Lock user Joe <nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" message-id="104"> <partial-lock> <select xmlns:usr="http://example.com/users"> | /usr:top/usr:users/user[usr:name="Joe"]" </select> </partial-lock> </nc:rpc> The NETCONF server grants the partial lock. The scope of this second lock includes only the<user> node with name Joe. The lock protects all data below this particular<user> node. Step 7 - Receive lock <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" message-id="104"> <lock-id>2</lock-id> <locked-node xmlns:usr="http://example.com/users"> | /usr:top/usr:users/user[usr:name="Joe"]" </locked-node> </nc:rpc-reply> Corrected Text -------------- Step 6 - Lock user Joe <nc:rpc xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" message-id="104"> <partial-lock> <select xmlns:usr="http://example.com/users"> | /usr:top/usr:users/usr:user[usr:name="Joe"]" </select> </partial-lock> </nc:rpc> The NETCONF server grants the partial lock. The scope of this second lock includes only the<user> node with name Joe. The lock protects all data below this particular<user> node. Step 7 - Receive lock <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:ietf:params:xml:ns:netconf:partial-lock:1.0" message-id="104"> <lock-id>2</lock-id> <locked-node xmlns:usr="http://example.com/users"> | /usr:top/usr:users/usr:user[usr:name="Joe"]" </locked-node> </nc:rpc-reply> Notes ----- The instance identifier /usr:top/usr:users/user[usr:name="Joe"]" must be replaced with /usr:top/usr:users/usr:user[usr:name="Joe"]" 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. -------------------------------------- RFC5717 (draft-ietf-netconf-partial-lock-11) -------------------------------------- Title : Partial Lock Remote Procedure Call (RPC) for NETCONF Publication Date : December 2009 Author(s) : B. Lengyel, M. Bjorklund Category : PROPOSED STANDARD Source : Network Configuration Area : Operations and Management Stream : IETF Verifying Party : IESG
- [Netconf] [Technical Errata Reported] RFC5717 (26… RFC Errata System
- [Netconf] Fwd: [Technical Errata Reported] RFC571… Bert (IETF) Wijnen
- Re: [Netconf] [Technical Errata Reported] RFC5717… Martin Bjorklund