Re: [netmod] Issue with path statements in RPC
Martin Björklund <mbj+ietf@4668.se> Mon, 10 August 2020 09:24 UTC
Return-Path: <mbj+ietf@4668.se>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 964A83A0E5A; Mon, 10 Aug 2020 02:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LOTS_OF_MONEY=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=4668.se header.b=S5mk08N4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dYQBxh3P
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 CShbdraPR5t4; Mon, 10 Aug 2020 02:24:28 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FB9B3A0BA7; Mon, 10 Aug 2020 02:24:28 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 814AF5C0162; Mon, 10 Aug 2020 05:24:26 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 10 Aug 2020 05:24:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=4668.se; h=date :message-id:to:cc:subject:from:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm2; bh= 1+Z1g48zuK9cNrvqGV+bVBctL47ON31n0bpSwWOoXGY=; b=S5mk08N4aq2YDAqY 5z+tvQxO1vcLQTworQ1E8EQM4+A/0KVjAzYvN5o8lM8x78CbOUtQOgfxuHfOyauc BrA2Sa1RdXztJXNza/9dyMAI4KsiHPKNiYHbtZrKEzP3ejVPJeSIa5va4amKeHtg RkIep/Tead+lPJPGfJddRiSVj2Z5SO17WJywHi6Qb+CUsjUHXvRefByQI4x0sDeu xWtI+oLyf4PUjMT+/Xu71xRuQBp8ivoj+a7Z49PHYxEm/UIT2pXHXATcLfQ5WEKS ZsswTjVEryU9BJVShbmGec/l4FJ4PExrdrI2DMW92o5wcE18VCQ4pOvS7FIL/AtS syf9Rw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=1+Z1g48zuK9cNrvqGV+bVBctL47ON31n0bpSwWOoX GY=; b=dYQBxh3PuIy3Jn/hDE6ZxBTGKmgds9TMDPg6KKr7+rCy6FXnR8ZMWKEL8 uUne0Gjd6kc639ASdAfb2VUNiyYsmyEdHposCP4Wx/q1dIpIWSUAqhhaVvnfD26S JaTumE+qVzR+YFE+xiKiTs83qPHstKG4G2J8ypqtg2+6pmat43XniEsNttTPKDza S5dxhyTWoeh/XCww90N2LM1x9X39M1yM8tJY2m46P7KSzaiNQIbXQ2DpiVQUdTiN o0ALqFgFzh0OGEkO2buP/p45dfPMTxtoGaG9QUT6CM/xp78PZ81Y6njcWGBG3sDv Z6BGYsS7+EpvuCxLORpwDGQQhNwHA==
X-ME-Sender: <xms:SRIxX29TAcTJJwc9_7n9In30OJEYXxe9OsKDR1Va7gpU552t3HjbSQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrkeekgdduiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffkvffuhfgjfhfogggtgfesthhqre dtredtleenucfhrhhomhepofgrrhhtihhnuceujhpnrhhklhhunhguuceomhgsjhdoihgv thhfseegieeikedrshgvqeenucggtffrrghtthgvrhhnpeehgfelheffgedtfeffleffud egffduueeuveejjeduhfeltdevvdfgtdfffeejvdenucffohhmrghinhepihgvthhfrdho rhhgpdhgihhthhhusgdrtghomhdphhhurgifvghirdgtohhmnecukfhppeduheekrdduje egrdegrdeggeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehmsghjodhivghtfhesgeeiieekrdhsvg
X-ME-Proxy: <xmx:SRIxX2tc0Bnj7lZOKn4B2kMrkvGVgQ_qP4BaT4zQ8tEtoxWm7j-Vyw> <xmx:SRIxX8DTwyTyARTjtQhlJob9nvSjCYwQgOm531G2xEvhw2qlyatrVw> <xmx:SRIxX-cUg5EAAQsGiCRVt6WORKwazlXjiApjjFev9UHU1iOCBKcYzA> <xmx:ShIxX6aRff3DYYI5S7mbO4Mn9C2s51OJ84kFJGtMdkuszCTjaBv8eQ>
Received: from localhost (unknown [158.174.4.44]) by mail.messagingengine.com (Postfix) with ESMTPA id 1207B30600A3; Mon, 10 Aug 2020 05:24:24 -0400 (EDT)
Date: Mon, 10 Aug 2020 11:24:23 +0200
Message-Id: <20200810.112423.1011687310446809904.id@4668.se>
To: Italo.Busi@huawei.com
Cc: netmod@ietf.org, teas@ietf.org
From: Martin Björklund <mbj+ietf@4668.se>
In-Reply-To: <9c365f0d89ae4f9c9054eed5c4730d59@huawei.com>
References: <9c365f0d89ae4f9c9054eed5c4730d59@huawei.com>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/3vmzza2QQ2ZVxUOU_daRTZDt0P8>
Subject: Re: [netmod] Issue with path statements in RPC
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2020 09:24:31 -0000
Italo Busi <Italo.Busi@huawei.com> wrote: > We have found some issues with RPC XPaths when developing the YANG > code for > https://tools.ietf.org/html/draft-ietf-teas-yang-path-computation > > As discussed during the TEAS WG session in IETF 108, this issue has > been raised on pyang github: > https://github.com/mbj4668/pyang/issues/662 > > It was also suggested to check with Netmod WG what should be the > correct behavior according to RFC7950. > > The following code is accepted by pyang 1.75 but not by pyang 2.1: > > type leafref { > path "/te:tunnels-path-compute/te:input/" > + "te:path-compute-info/" > + "te-pc:tunnel-attributes/te-pc:tunnel-name"; > } > > The following code instead is accepted by pyang 2.1 but not by pyang > 1.7.5: > > type leafref { > path "/te:tunnels-path-compute/" > + "te:path-compute-info/" > + "te-pc:tunnel-attributes/te-pc:tunnel-name"; > } The leafref path is an XPath expression, which operates on the data tree (instance data). The "input" node is not present in the instance data / data tree. See section 6.4.1 of RFC 7950. So the latter path (as verfied by pyang 2.1) is correct. > Moreover the following when statement, which is quite useful to > constraint which information is provided by the RPC output based on > some attributes in the RPC input, is accepted by pyang 1.7.5 but not > accepted by pyang 2.1; > > augment "/te:tunnels-actions/te:output" { > description > "Augment Tunnels Action RPC input with path delete result"; > > container path-computed-delete-result { > when "derived-from-or-self(../../te:input/te:action-info/" > + "te:action, 'tunnel-action-path-compute-delete')"; > description "Path Delete RPC output"; > leaf-list path-compute-transaction-id { > type string; > description > "The list of the transaction-id values of the > transient states that have been successfully deleted"; > } > } // container path-computed-delete-result > } // path-delete rpc output > > > Could you please help us to understand what is the correct behavior? > > In case the correct behavior is the one of pyang 2.1, our > understanding is that it would not be possible to provide in YANG when > constraints for the data nodes in the RPC output depending on specific > values of the data nodes used in the RPC input. Therefore these > constraints should be specified as behavior and implemented in the > back-end. > > Is our understanding correct? Yes, this is correct. It is not possible to refer to the corresponding "input" instance data in the XPath expressions for the "output". /martin > > Thanks for your help > > Sergio and Italo (on behalf of co-authors/contributors) > > Italo Busi > Principal Optical Transport Network Research Engineer > > [cid:image001.jpg@01D5AC11.9575BB40] > ____________________________________________________________________ > > Huawei Technologies Italia S.r.l. > Address: Centro Direzionale Milano 2, Palazzo Verrocchio, 20090 > Segrate (MI) > Tel: +39 345 4721946 - Mobile: > Italo.busi@huawei.com<mailto:Italo.busi@huawei.com> > > __________________________________________________________________________________ > Huawei Technologies Italia S.r.l. is a company registered in Italy at > the Company Registration Office of Milan, with registered number > 04501190963 and equity capital €3,000,000 fully paid up, whose > registered office is in Milan, Via Lorenteggio 240, Tower A, 20147 > Milan, Italy. Huawei Technologies Italia S.r.l. is 100% owned by > Huawei Technologies Cooperatief U.A. > CONAI Reg. No. cc 12639454 - A.E.E. Registry No. IT10010000006521 - > Batteries and Accumulators Registry No. IT12050P00002839. > ________________________________________________________________________________________________________________________ > This e-mail and its attachments contain confidential information from > HUAWEI, which is intended only for the person or entity whose address > is listed above. Any use of the information contained herein in any > way (including, but not limited to, total or partial disclosure, > reproduction, or dissemination) by persons other than the intended > recipient(s) is prohibited. If you receive this e-mail in error, > please notify the sender by phone or email immediately and delete it! > Thank you. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > PRIVACY NOTICE: Pursuant to Art. 13 of the General Data Protection > Regulation 2016/679 (GDPR), Huawei Technologies Italia S.r.l. informs > you that the personal data contained in this email will be collected > and treated for the acquisition of information preliminary to the > conclusion of contracts, for the definition of the contractual > relationship, as well as for the fulfillment of legal requirements > related to civil, tax and accounting law or any other legal obligation > to which Huawei may be subject. Personal data will not be subject to > disclosure and spread unless otherwise required by law. Huawei will > take appropriate security measures to protect personal data against > loss, misuse disclosure or destruction of the information. Personal > Data held may be transferred to countries outside the European Union, > however Huawei Italia has put in place appropriate safeguards for the > transfer of personal data to third countries by adopting the standard > data protection clauses of the EU Commission. Personal Data are kept > for a period necessary for the fulfillment of contract obligations > unless otherwise required by law. You can exercise your rights under > Art. 15 and following of the GDPR (i.e. right of access, > rectification, erasure, restriction, portability, object) by > contacting Huawei at this email address: > dataprotection@huawei.com<mailto:dataprotection@huawei.com> or through > the following channel: > www.huawei.com/en/personal-data-request<http://www.huawei.com/en/personal-data-request>. You > have also the right to lodge a complaint with the competent > supervisory authorities. If you need any further information or have > any queries on how Huawei process your personal data, please send an > email to our Data Protection Officer at > dpo@huawei.com<mailto:dpo@huawei.com>.The Data Controller is Huawei > Technologies Italia S.r.l. with registered office in Milan, Via > Lorenteggio 240 Tower A, 20147. > >
- [netmod] Issue with path statements in RPC Italo Busi
- Re: [netmod] Issue with path statements in RPC tom petch
- Re: [netmod] Issue with path statements in RPC Martin Björklund
- Re: [netmod] Issue with path statements in RPC tom petch
- Re: [netmod] Issue with path statements in RPC Martin Björklund