Re: [Netconf] [Technical Errata Reported] RFC5717 (2657)

Martin Bjorklund <mbj@tail-f.com> Fri, 03 December 2010 09:40 UTC

Return-Path: <mbj@tail-f.com>
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 69A283A6AB8 for <netconf@core3.amsl.com>; Fri, 3 Dec 2010 01:40:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level:
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553]
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 fTz51Gn+H+bL for <netconf@core3.amsl.com>; Fri, 3 Dec 2010 01:40:15 -0800 (PST)
Received: from mail.tail-f.com (de-0316.d.ipeer.se [213.180.79.212]) by core3.amsl.com (Postfix) with ESMTP id 276E63A68C6 for <netconf@ietf.org>; Fri, 3 Dec 2010 01:40:15 -0800 (PST)
Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id D9323616001; Fri, 3 Dec 2010 10:41:30 +0100 (CET)
Date: Fri, 03 Dec 2010 10:41:28 +0100
Message-Id: <20101203.104128.123611252.mbj@tail-f.com>
To: rfc-editor@rfc-editor.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20101203053002.0FBC1E06E0@rfc-editor.org>
References: <20101203053002.0FBC1E06E0@rfc-editor.org>
X-Mailer: Mew version 7.0.50 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: rbonica@juniper.net, viswanath@huawei.com, netconf@ietf.org
Subject: Re: [Netconf] [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:40:16 -0000

Hi,

The report is correct - the prefix "usr:" is missing in these two
cases.

However, there is actually another error in these two expressions -
there is a trailing " character after each expression.  So:

OLD:

        /usr:top/usr:users/user[usr:name="Joe"]"

NEW:

        /usr:top/usr:users/usr:user[usr:name="Joe"]


/martin


RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> 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
>