Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8DF12F4E3 for ; Tue, 29 May 2018 23:16:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 Ayv1rTSnlgob for ; Tue, 29 May 2018 23:16:16 -0700 (PDT) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BD2D12FA97 for ; Tue, 29 May 2018 23:16:16 -0700 (PDT) Received: by mail-oi0-x232.google.com with SMTP id h79-v6so8819202oig.13 for ; Tue, 29 May 2018 23:16:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Xpnl6+DoUgCfRAA2HBbb3JKMZkidNTumWlMman54z+8=; b=ke2nqmL6a0t+Rx/x6L794iN6XuhJx38ZZm9XQmbML8lTL8i0RL8kllUcHXE/bC17Oz XjBLDxQsaQ05VLtuaCU+p3t+jcc1wqwJiyXNhNOje4x8e+w1r2Ho2GyTxE1LDpigL7HN FQhESPPX9gkAzNJzFe0d4bslEoPHwGyGmS5x3xjEX5VW+ZO0e65sKrNcrKNs1KXQXysM B4OVMAIyx5SySvRr1VN1Z+FLcWaOnmO4C6Gmwg7HhU1LtvXV1NK+IyWsvHNK8F2BwxJd Pwd36ckn3ZcB6xL0csrFGzifIJQMmgajDhsiBe2nmZe1M1i+3xunX6aOWJOmj6ATKarD ROuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Xpnl6+DoUgCfRAA2HBbb3JKMZkidNTumWlMman54z+8=; b=q3q5jcHFt3XJieEf5Z9Tp5o6HMo0fwcOw33htRfkQGtnsG0BlbF1iIX72XB1AoUYcH nzZTRFtllP+i/ObFEl0yNLbNteQdiq5O5giMNtA8SF+k4E9p7C8QGhwuIJY5sKCVvWNX b/UNmUarvk/YpbBzyfprixIWJdeRyWoqZ7o9HvxP+w+IF95Tf01HWLq8tfyLn0VoG9m4 /IkkqaGc+38AFjp3SOjVVu0FagUajjR7bWWrjGhMTxm/icCnED8y7XRgJsTnecXrKUSk mW8yA0cXr38rbgOWTTWb+2YH2m1MAkOsN6bzfNbWTZW56cXTzTb4+gUKaUqMlTaEoVJd Qtww== X-Gm-Message-State: APt69E0iBx1orDemOHTzxPIYJHJJ3D/KeJD1pTCoayHNEn6REk2a0G7+ g1teKIiq2OWy3YOuB44MOEjUYOC36+vlUtwzX08= X-Google-Smtp-Source: ADUXVKIykpErrC/mz0d/fmi20aEdFFgDk7jhpjSk7Tucnf/WxA3XQ+PZKmeW/X0vBegr+lZsVNykhLGRobmkCMiDp+o= X-Received: by 2002:aca:1218:: with SMTP id 24-v6mr742499ois.144.1527660975300; Tue, 29 May 2018 23:16:15 -0700 (PDT) MIME-Version: 1.0 From: Shiva Kumar Pathori Date: Wed, 30 May 2018 11:46:04 +0530 Message-ID: To: netconf@ietf.org Content-Type: multipart/alternative; boundary="000000000000c52750056d6649c7" Archived-At: Subject: Re: [Netconf] Clarification about subtree filter X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2018 06:16:19 -0000 --000000000000c52750056d6649c7 Content-Type: text/plain; charset="UTF-8" Hi, Sorry did not update subject line, It's updated now. On Wed 30 May, 2018, 2:53 AM , wrote: > Send Netconf mailing list submissions to > netconf@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/netconf > or, via email, send a message with subject or body 'help' to > netconf-request@ietf.org > > You can reach the person managing the list at > netconf-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Netconf digest..." > > > Today's Topics: > > 1. Re: Netconf Digest, Vol 123, Issue 43 (Shiva Kumar Pathori) > 2. How would RESTCONF access multiple datastores defined by NMDA > (Henry Yu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 May 2018 01:29:53 +0530 > From: Shiva Kumar Pathori > To: netconf@ietf.org > Subject: Re: [Netconf] Clarification about subtree filter > Message-ID: > < > CAJtYN8LBOrmZqSJug5n80UdSuOit2rZW8jQaUzsjNPyvs6Q3RQ@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > What could be the reason for not including the "" leaf in the > reply? > I see the example in section 6.4.5 in RFC 6241 include the above mentioned > leaf when a content match node present in the filter. > > BTW, the reply is same for the both xpath and subtree filter RPCs mentioned > in the mail? > > On 29 May 2018 at 00:30, wrote: > > > Send Netconf mailing list submissions to > > netconf@ietf.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://www.ietf.org/mailman/listinfo/netconf > > or, via email, send a message with subject or body 'help' to > > netconf-request@ietf.org > > > > You can reach the person managing the list at > > netconf-owner@ietf.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Netconf digest..." > > > > > > Today's Topics: > > > > 1. Re: Clarification about su tree filtering (Martin Bjorklund)Hi > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Mon, 28 May 2018 15:37:48 +0200 (CEST) > > From: Martin Bjorklund > > To: mjethanandani@gmail.com > > Cc: netconf@ietf.org > > Subject: Re: [Netconf] Clarification about su tree filtering > > Message-ID: <20180528.153748.2044064270808262081.mbj@tail-f.com> > > Content-Type: Text/Plain; charset=utf-8 > > > > Hi, > > > > See answers inline. > > > > > > Mahesh Jethanandani wrote: > > > Forwarding to NETCONF WG mailing list. > > > > > > Begin forwarded message: > > > > > > > From: Shiva Kumar Pathori > > > > Date: May 28, 2018 at 5:27:19 AM EDT > > > > To: Alex Campbell > > > > Cc: netmod@ietf.org > > > > Subject: Re: [netmod] Clarification about subtree filtering > > > > > > > > Thanks Alex for the clarification. Can somebody please clarify about > > subtree filter behaviour or provide some pointers in RFC so that I can > > refer to it. > > > > > > > >> On Thu 24 May, 2018, 5:56 AM Alex Campbell, < > > Alex.Campbell@aviatnet.com> wrote: > > > >> Hi, > > > >> > > > >> > > > >> Since nobody else has answered I'll have a go. > > > >> I'm not familiar with subtree filtering, but I am with XPath. > > Assuming your XPath translation is accurate, it will return no data > > (response A). > > > >> > > > >> From: netmod on behalf of Shiva Kumar > > Pathori > > > >> Sent: Tuesday, 22 May 2018 8:38 p.m. > > > >> To: netmod@ietf.org > > > >> Subject: [netmod] Clarification about subtree filtering > > > >> > > > >> > > > >>> Hi, > > > >>> Can somebody clarify what could be the response for the > > > operation provided below. > > > >>> > > > >>> Following is the user information in the datastore that is provided > > in the RFC 6241 as example. > > > >>>> > > >>>> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> root > > > >>>> superuser > > > >>>> Charlie Root > > > >>>> > > > >>>> 1 > > > >>>> 1 > > > >>>> > > > >>>> > > > >>>> > > > >>>> fred > > > >>>> admin > > > >>>> Fred Flintstone > > > >>>> > > > >>>> 2 > > > >>>> 2 > > > >>>> > > > >>>> > > > >>>> > > > >>>> barney > > > >>>> admin > > > >>>> Barney Rubble > > > >>>> > > > >>>> 2 > > > >>>> 3 > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>> > > > >>> > > > >>> The operation with content-match at parent and child > > nodes; > > > >>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> admin > > > >>>> > > > >>>> 1 > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>> > > > >>> The equivalent XPATH expression : > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > >>>> type="xpath" > > > >>>> select="/t:top/t:users/t:user[ > > t:type='admin']/t:company-info[t:dept=?1?]"/> > > > >>>> > > > >>>> > > > > This is not an equivalent expression, b/c a content-match node ("type") > > is not AND:ed with a selection node ("company-info"). > > > > > >>> For this what could be the response > > > >>> > > > >>> a) The response based on content-match nodes are AND-ed together > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>> OR > > > >>> > > > >>> b) The response based on content-match nodes treated separately > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> fred > > > >>>> admin > > > >>>> Fred Flintstone > > > >>>> > > > >>>> > > > >>>> barney > > > >>>> admin > > > >>>> Barney Rubble > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > > Sibling content-match nodes are AND:ed, but in this case "type" and > > "dept" are not siblings. > > > > The correct reply is: > > > > > > > > > > > > fred (*) > > admin > > > > > > barney (*) > > admin > > > > > > > > > > > > (*) note that if the name is the key, it MAY (or may not) be present > > in the output, see 6.2.5 of RFC 6241: > > > > o If any sibling nodes of the selection node are instance identifier > > components for a conceptual data structure (e.g., list key leaf), > > then they MAY also be included in the filter output. > > > > > > > > /martin > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Netconf mailing list > > Netconf@ietf.org > > https://www.ietf.org/mailman/listinfo/netconf > > > > > > ------------------------------ > > > > End of Netconf Digest, Vol 123, Issue 43 > > **************************************** > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://mailarchive.ietf.org/arch/browse/netconf/attachments/20180530/93583caa/attachment.html > > > > ------------------------------ > > Message: 2 > Date: Tue, 29 May 2018 17:23:07 -0400 > From: Henry Yu > To: netconf@ietf.org > Subject: [Netconf] How would RESTCONF access multiple datastores > defined by NMDA > Message-ID: > < > CAFsbzLkU5W5hL5Yb5YB3ft73idYoT1QPxXNWwMa_VBBvQ+c_GQ@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > According to my understanding of RFC 8040, there is only one datastore > (which is represented by "{+restconf}/data"). But NMDA introduces multiple > datastores. How does RESTCONF provide access to them? I think a RESTCONF > user would, at minimum, need the access to the and the > . > > Thanks, > Henry > P.S., I would not find an answer in the mailing list's archive. My > apologies if this question has already been asked/answered. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://mailarchive.ietf.org/arch/browse/netconf/attachments/20180529/81c594a0/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf > > > ------------------------------ > > End of Netconf Digest, Vol 123, Issue 44 > **************************************** > --000000000000c52750056d6649c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0 Sorry did not update subject line, It'= s updated now.

On Wed 30= May, 2018, 2:53 AM , <netco= nf-request@ietf.org> wrote:
= Send Netconf mailing list submissions to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 netconf@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf= .org/mailman/listinfo/netconf
or, via email, send a message with subject or body 'help' to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 netconf-request@ietf.org

You can reach the person managing the list at
=C2=A0 =C2=A0 =C2=A0 =C2=A0 netconf-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netconf digest..."


Today's Topics:

=C2=A0 =C2=A01. Re: Netconf Digest, Vol 123, Issue 43 (Shiva Kumar Pathori)=
=C2=A0 =C2=A02. How would RESTCONF access multiple datastores defined by NM= DA
=C2=A0 =C2=A0 =C2=A0 (Henry Yu)


----------------------------------------------------------------------

Message: 1
Date: Wed, 30 May 2018 01:29:53 +0530
From: Shiva Kumar Pathori <pathori@gmail.com>
To: netconf@ietf.org
Subject: Re: [Netconf] Clarification about subtree filter
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <CAJtYN8LBOrmZqSJug5n80UdSuOit2rZW8jQaUzsjNPyvs6Q3RQ@mail.gmail.com= >
Content-Type: text/plain; charset=3D"utf-8"

Hi,
What could be the reason for not including the "<full-name>"= ; leaf in the
reply?
I see the example in section 6.4.5 in RFC 6241 include the above mentioned<= br> leaf when a content match node present in the filter.

BTW, the reply is same for the both xpath and subtree filter RPCs mentioned=
in the mail?

On 29 May 2018 at 00:30, <netconf-request@ietf.org> wrote:<= br>
> Send Netconf mailing list submissions to
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0netconf@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https:= //www.ietf.org/mailman/listinfo/netconf
> or, via email, send a message with subject or body 'help' to >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0netconf-request@ietf.org >
> You can reach the person managing the list at
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0netconf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific > than "Re: Contents of Netconf digest..."
>
>
> Today's Topics:
>
>=C2=A0 =C2=A0 1. Re: Clarification about su tree filtering (Martin Bjor= klund)Hi
>
>
> ----------------------------------------------------------------------=
>
> Message: 1
> Date: Mon, 28 May 2018 15:37:48 +0200 (CEST)
> From: Martin Bjorklund <mbj@tail-f.com>
> To: mjethanandani@gmail.com
> Cc: netconf@ietf.org
> Subject: Re: [Netconf] Clarification about su tree filtering
> Message-ID: <20180528.153748.204406= 4270808262081.mbj@tail-f.com>
> Content-Type: Text/Plain; charset=3Dutf-8
>
> Hi,
>
> See answers inline.
>
>
> Mahesh Jethanandani <mjethanandani@gmail.com> wrote: > > Forwarding to NETCONF WG mailing list.
> >
> > Begin forwarded message:
> >
> > > From: Shiva Kumar Pathori <pathori@gmail.com>
> > > Date: May 28, 2018 at 5:27:19 AM EDT
> > > To: Alex Campbell <Alex.Campbell@aviatnet.com= >
> > > Cc: netmod@ietf.org
> > > Subject: Re: [netmod] Clarification about subtree filtering<= br> > > >
> > > Thanks Alex for the clarification. Can somebody please clari= fy about
> subtree filter behaviour or provide some pointers in RFC so that I can=
> refer to it.
> > >
> > >> On Thu 24 May, 2018, 5:56 AM Alex Campbell, <
> Alex.Campbell@aviatnet.com> wrote:
> > >> Hi,
> > >>
> > >>
> > >> Since nobody else has answered I'll have a go.
> > >> I'm not familiar with subtree filtering, but I am wi= th XPath.
> Assuming your XPath translation is accurate, it will return no data > (response A).
> > >>
> > >> From: netmod <netmod-bounces@ietf.org> on= behalf of Shiva Kumar
> Pathori <pathori@gmail.com>
> > >> Sent: Tuesday, 22 May 2018 8:38 p.m.
> > >> To: netmod@ietf.org
> > >> Subject: [netmod] Clarification about subtree filtering<= br> > > >>
> > >>
> > >>> Hi,
> > >>> Can somebody clarify what could be the response for = the <get-config>
> operation provided below.
> > >>>
> > >>> Following is the user information in the datastore t= hat is provided
> in the RFC 6241 as example.
> > >>>> <rpc message-id=3D"101"
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0xmlns=3D= "urn:ietf:params:xml:ns:netconf:base:1.0">
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <get-config> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <source>=
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <run= ning/>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 </source>= ;
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <filter typ= e=3D"subtree">
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <top= xmlns=3D"http://example.com/schema/1.2/config">
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = <users/>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 </to= p>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 </filter>= ;
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 </get-config> > > >>>>=C2=A0 =C2=A0 =C2=A0 </rpc>
> > >>>
> > >>>> <rpc-reply message-id=3D"101" xmlns= =3D"urn:ietf:params:xml:ns:
> netconf:base:1.0">
> > >>>>=C2=A0 =C2=A0<data>
> > >>>>=C2=A0 =C2=A0 =C2=A0<top xmlns=3D"http://example.com/schema/1.2/config">
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0<users>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<name= >root</name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<type= >superuser</type>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<full= -name>Charlie Root</full-name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<comp= any-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;dept>1</dept>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;id>1</id>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</com= pany-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<name= >fred</name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<type= >admin</type>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<full= -name>Fred Flintstone</full-name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<comp= any-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;dept>2</dept>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;id>2</id>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</com= pany-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<name= >barney</name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<type= >admin</type>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<full= -name>Barney Rubble</full-name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<comp= any-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;dept>2</dept>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;id>3</id>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</com= pany-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0</users>
> > >>>>=C2=A0 =C2=A0 =C2=A0</top>
> > >>>>=C2=A0 =C2=A0</data>
> > >>>> </rpc-reply>
> > >>>
> > >>>
> > >>> The <get-config> operation with content-match = at parent and child
> nodes;
> > >>>
> > >>>> <rpc message-id=3D"101" xmlns=3D&qu= ot;urn:ietf:params:xml:ns:
> netconf:base:1.0">
> > >>>>=C2=A0 =C2=A0<get-config>
> > >>>>=C2=A0 =C2=A0 =C2=A0<source>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0<running/>
> > >>>>=C2=A0 =C2=A0 =C2=A0</source>
> > >>>>=C2=A0 =C2=A0 =C2=A0<filter type=3D"subtr= ee">
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0<top xmlns=3D"= http://example.com/schema/1.2/config"> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<users> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<user= >
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;type>admin</name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;company-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0<dept>1</dept>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&= lt;/company-info>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</use= r>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</users><= br> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0</top>
> > >>>>=C2=A0 =C2=A0 =C2=A0</filter>
> > >>>>=C2=A0 =C2=A0</get-config>
> > >>>> </rpc>
> > >>>
> > >>> The equivalent XPATH expression :
> > >>>> <rpc message-id=3D"101" xmlns=3D&qu= ot;urn:ietf:params:xml:ns:
> netconf:base:1.0">
> > >>>>=C2=A0 =C2=A0<get-config>
> > >>>>=C2=A0 =C2=A0 =C2=A0<source>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0<running/>
> > >>>>=C2=A0 =C2=A0 =C2=A0</source>
> > >>>>=C2=A0 =C2=A0 =C2=A0<filter xmlns:t=3D"http://example.com/schema/1.2/config"
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 type=3D"xpath"
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 select=3D"/t:top/t:users/t:user[
> t:type=3D'admin']/t:company-info[t:dept=3D?1?]"/>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</get-config= >
> > >>>>=C2=A0 =C2=A0 =C2=A0 </rpc>
>
> This is not an equivalent expression, b/c a content-match node ("= type")
> is not AND:ed with a selection node ("company-info").
>
> > >>> For this what could be the response
> > >>>
> > >>> a) The response based on content-match nodes are AND= -ed together
> > >>>> <rpc-reply message-id=3D"101" xmlns= =3D"urn:ietf:params:xml:ns:
> netconf:base:1.0">
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <data>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0</data>
> > >>>>=C2=A0 =C2=A0 =C2=A0 </rpc-reply>
> > >>> OR
> > >>>
> > >>> b)=C2=A0 The response based on content-match nodes t= reated separately
> > >>>> <rpc-reply message-id=3D"101" xmlns= =3D"urn:ietf:params:xml:ns:
> netconf:base:1.0">
> > >>>>=C2=A0 =C2=A0<data>
> > >>>>=C2=A0 =C2=A0 =C2=A0<top xmlns=3D"http://example.com/schema/1.2/config">
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0<users>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<name= >fred</name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<type= >admin</type>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<full= -name>Fred Flintstone</full-name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<name= >barney</name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<type= >admin</type>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<full= -name>Barney Rubble</full-name>
> > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</user> > > >>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0</users>
> > >>>>=C2=A0 =C2=A0 =C2=A0</top>
> > >>>>=C2=A0 =C2=A0</data>
> > >>>> </rpc-reply>
>
> Sibling content-match nodes are AND:ed, but in this case "type&qu= ot; and
> "dept" are not siblings.
>
> The correct reply is:
>
>=C2=A0 =C2=A0 <data>
>=C2=A0 =C2=A0 =C2=A0 <top xmlns=3D"http:/= /example.com/schema/1.2/config">
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <users>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <user>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <name>fred</name>= (*)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <type>admin</type>= ;
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 </user>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <user>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <name>barney</name&g= t; (*)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <type>admin</type>= ;
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 </user>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 </users>
>=C2=A0 =C2=A0 =C2=A0 </top>
>=C2=A0 =C2=A0 </data>
>
> (*) note that if the name is the key, it MAY (or may not) be present > in the output, see 6.2.5 of RFC 6241:
>
>=C2=A0 =C2=A0 o=C2=A0 If any sibling nodes of the selection node are in= stance identifier
>=C2=A0 =C2=A0 =C2=A0 =C2=A0components for a conceptual data structure (= e.g., list key leaf),
>=C2=A0 =C2=A0 =C2=A0 =C2=A0then they MAY also be included in the filter= output.
>
>
>
> /martin
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/n= etconf
>
>
> ------------------------------
>
> End of Netconf Digest, Vol 123, Issue 43
> ****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailarchive.ietf.org/arch/browse/netconf/attachments/= 20180530/93583caa/attachment.html>

------------------------------

Message: 2
Date: Tue, 29 May 2018 17:23:07 -0400
From: Henry Yu <hyu2010b@gmail.com>
To: netconf@ietf.org
Subject: [Netconf] How would RESTCONF access multiple datastores
=C2=A0 =C2=A0 =C2=A0 =C2=A0 defined by NMDA
Message-ID:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <CAFsbzLkU5W5hL5Yb5YB3ft73idYoT1QPxXNWwMa_VBBvQ+c_GQ@mail.gmail.com>
Content-Type: text/plain; charset=3D"utf-8"

Hi,

According to my understanding of RFC 8040, there is only one datastore
(which is represented by "{+restconf}/data"). But NMDA introduces= multiple
datastores. How does RESTCONF provide access to them? I think a RESTCONF user would, at minimum, need the access to the <running> and the
<operational>.

Thanks,
Henry
P.S., I would not find an answer in the mailing list's archive. My
apologies if this question has already been asked/answered.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailarchive.ietf.org/arch/browse/netconf/attachments/= 20180529/81c594a0/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Netconf mailing list
Ne= tconf@ietf.org
https://www.ietf.org/mailman/listinfo/netcon= f


------------------------------

End of Netconf Digest, Vol 123, Issue 44
****************************************
--000000000000c52750056d6649c7--