portant thing is
that the client will get all the data in one piece.
Thanks a lot,
Igor
c
From:Robert Wilton
To:Igor Bryskin,
Cc:Per Hedeland,netmod@ietf.org,netc...@ietf.org
<mailto:netmod@ietf.org,netc...@ietf.org>,
Date:2017-10-10 06:41:04
Sub
netc...@ietf.org
<mailto:netmod@ietf.org,netc...@ietf.org> ,
Date:2017-10-10 06:41:04
Subject:Re: [netmod] [Netconf] Retrieving Information Pointed by leafref
Hi Igor,
On 09/10/2017 23:11, Igor Bryskin wrote:
Hi Per,
This is a good news, but, please, help us out.
Consider, we have a node
ot,
Igor
c
From:Robert Wilton
To:Igor Bryskin,
Cc:Per Hedeland,netmod@ietf.org,netc...@ietf.org,
Date:2017-10-10 06:41:04
Subject:Re: [netmod] [Netconf] Retrieving Information Pointed by leafref
Hi Igor,
On 09/10/2017 23:11, Igor Bryskin wrote:
Hi Per,
This is a good news, but, please, help us
t:Re: [netmod] [Netconf] Retrieving Information Pointed by leafref
Hi Igor,
On 09/10/2017 23:11, Igor Bryskin wrote:
> Hi Per,
>
> This is a good news, but, please, help us out.
> Consider, we have a node - "te-tunnel" - which among other attributes
has two key leafref lists:
t, the important thing is that the client will
get all the data in one piece.
Thanks a lot,
Igor
c
From:Robert Wilton
To:Igor Bryskin,
Cc:Per Hedeland,netmod@ietf.org,netc...@ietf.org,
Date:2017-10-10 06:41:04
Subject:Re: [netmod] [Netconf] Retrieving Information Pointed by leafref
Hi Igor,
Hi Igor,
On 09/10/2017 23:11, Igor Bryskin wrote:
Hi Per,
This is a good news, but, please, help us out.
Consider, we have a node - "te-tunnel" - which among other attributes has two
key leafref lists:
1) each member of the 1st list points to a "connection" supporting the
te-tunnel. All conne
I already showed you an XPath filter expression that will do what you
originally asked for, i.e. retrieve the data for a tunnel and the
associated 'explicit-path's in a single request, based on the
(simplified) data model that you provided. What you are describing now
seems like just variations on
Hi Per,
This is a good news, but, please, help us out.
Consider, we have a node - "te-tunnel" - which among other attributes has two
key leafref lists:
1) each member of the 1st list points to a "connection" supporting the
te-tunnel. All connections supporting all te-tunnels are stored in a sin
Just to be clear: what we're suggesting is that you can use the
already-existing standard NETCONF XPath capability to achieve the desired
result - see https://tools.ietf.org/html/rfc6241#section-8.9
--Per
On 2017-10-09 21:52, Igor Bryskin wrote:
I agree. For example, a leafref may point not to
I agree. For example, a leafref may point not to a singls entity, but to a list
of entities, and the client might want to expand all of them into the joint get
response.
Igor
From:Per Hedeland
To:Martin Bjorklund,
Cc:Igor Bryskin,xufeng.liu.i...@gmail.com,netc...@ietf.org,netmod@ietf.org,
Date:
On 2017-10-09 19:13, Martin Bjorklund wrote:
Igor Bryskin wrote:
Hi Per,
Basically, what we need is a way for a client to request something
like this:
get joint with
... which is what Per's expression does! Note that "|" in XPath means
"union".
But as Per explained, it only works in so
> But as Per explained, it only works in some cases (when the leafref
acts a "single pointer").
We think this is good enough. In all other cases leafref is simply not
qualified for the expansion.
I am not an expert , but I believe there is a similar capability in SQL, no?
Igor
-Original Mes
Igor Bryskin wrote:
>
> Hi Per,
>
> Basically, what we need is a way for a client to request something
> like this:
>
> get joint with
... which is what Per's expression does! Note that "|" in XPath means
"union".
But as Per explained, it only works in some cases (when the leafref
acts a "
Hi Per,
Basically, what we need is a way for a client to request something like this:
get joint with
with a server interpreting the request as follows:
if a node pointed by XPath contains a pointer (e.g. key leafref) matching one
of the XPath from the "joint with" list, then the server must
I understand your use case, but a leaf of type leafref does not in
general identify a single node in the data tree - the leafref path could
be for a non-key leaf, and/or the path could traverse list nodes, and/or
the "target" list could have multiple keys and thus multiple
leafref-leafs be required
I'm not sure that my XPath foo is good enough, but would NETCONF's XPath
filter solve this problem?
Thanks,
Rob
On 09/10/2017 14:42, Xufeng Liu wrote:
Hi Per,
*From:* Igor Bryskin [mailto:igor.brys...@huawei.com]
*Sent:* Sunday, October 8, 2017 7:04 PM
*To:* Igor Bryskin ; p...@tail-f.com;
Hi Per,
From: Igor Bryskin [mailto:igor.brys...@huawei.com]
Sent: Sunday, October 8, 2017 7:04 PM
To: Igor Bryskin ; p...@tail-f.com;
xufeng.liu.i...@gmail.com
Cc: netc...@ietf.org; netmod@ietf.org
Subject: Re: [Netconf] [netmod] Retrieving Information Pointed by leafref
Hi Joel,
Thanks,
Hi Joel,
Thanks, I think I didnt explain our problem correctly.
In our case we have a leafref pointing to a te tunnel name, which happens to be
a key to lookup the (axilary) tunnel. We need a way to include the entire
tunnel body (not just a name) into the get response. This is to optimize t
Hi Per,
In a nutshell we would lika for a netconf client to have a way to instruct the
server on whether in response to the get request the server needs to provide
the entire body of a datastore node pointed to by a leafref or just a pointer
to said node, so that the node's body could be retri
19 matches
Mail list logo
