Hi Rob,
This helps a lot. What you wrote will work.
The only difference is that if we would have the "joimt with" clause as we
proposed, the server would be able to tailor the te-tunnel presentation to the
client's requirements, e.g. substituting the connection pointers with
connection
"t.petch" wrote:
> - Original Message -
> From: "Ladislav Lhotka"
> Sent: Thursday, October 05, 2017 1:52 PM
> > Martin Bjorklund writes:
> >
> > > This version fixes the XPath context for parent-reference.
> > >
> > > However, there
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
Robert Wilton wrote:
>
>
> On 09/10/2017 22:06, Benoit Claise wrote:
> > On 10/6/2017 6:01 PM, Robert Wilton wrote:
> >>
> >>
> >> On 06/10/2017 16:32, Martin Bjorklund wrote:
> >>> Benoit Claise wrote:
> Dear all,
>
> [including the routing
On 09/10/2017 22:06, Benoit Claise wrote:
On 10/6/2017 6:01 PM, Robert Wilton wrote:
On 06/10/2017 16:32, Martin Bjorklund wrote:
Benoit Claise wrote:
Dear all,
[including the routing and multicast YANG design teams]
Can we please finalize the discussion regarding
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