[Netconf] "depth" parameter: nest-level semantics

"Alberto Gonzalez Prieto (albertgo)" <albertgo@cisco.com> Tue, 03 December 2013 21:37 UTC

Return-Path: <albertgo@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED171ADED6 for <netconf@ietfa.amsl.com>; Tue, 3 Dec 2013 13:37:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 5S6QPOvCgUxE for <netconf@ietfa.amsl.com>; Tue, 3 Dec 2013 13:37:14 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 097F21AD942 for <netconf@ietf.org>; Tue, 3 Dec 2013 13:37:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3526; q=dns/txt; s=iport; t=1386106631; x=1387316231; h=from:to:subject:date:message-id:mime-version; bh=6Btzn6/GoGVkvo8RjawWFGt3HuJyKQrsjQHqdIdgeQ0=; b=WcLZ0DPDpw9arFheWDZAdFA1LVFBAx0ltwdisvost9uKfrxgMykkRzNZ iHg7vm1XWs7npblOEnX7ZXkFhRnCTvgcfJIq1sswPwTIrxi2LYOgZXcOB 4omgi50bYNbAsWYgRjISgsXxhjMnb3w/QklODW3qY/jJLQJUVVXkTftn5 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAMlOnlKtJV2Z/2dsb2JhbABagkNEgQu6AxZ0giyBCwEMdCcEiBSiNJ88kzgDmBSSE4Mpgio
X-IronPort-AV: E=Sophos; i="4.93,819,1378857600"; d="scan'208,217"; a="288974064"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-1.cisco.com with ESMTP; 03 Dec 2013 21:36:57 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rB3LauIE030671 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <netconf@ietf.org>; Tue, 3 Dec 2013 21:36:56 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.50]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Tue, 3 Dec 2013 15:36:55 -0600
From: "Alberto Gonzalez Prieto (albertgo)" <albertgo@cisco.com>
To: Netconf <netconf@ietf.org>
Thread-Topic: "depth" parameter: nest-level semantics
Thread-Index: AQHO8G/JHFyrNhD7hUyEToIqJC/K0g==
Date: Tue, 03 Dec 2013 21:36:55 +0000
Message-ID: <CEC38EF4.3AC41%albertgo@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.154.204.28]
Content-Type: multipart/alternative; boundary="_000_CEC38EF43AC41albertgociscocom_"
MIME-Version: 1.0
Subject: [Netconf] "depth" parameter: nest-level semantics
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 03 Dec 2013 21:37:16 -0000

Hello,

I wanted to confirm my understanding of the semantics of a nest-level.

I understand that a nest-level is composed of a resource + its children.
Data resources are: containers and lists.
Children of a data resource are: leaves, leaf-lists, anyxml. How about presence containers?


1) In the example of 3.8.1, for a depth of 2, the response includes  2 containers (I.e., jukebox and library) and 1 list (I.e., artist). Would that make it 3 resources, and therefore 3 nest-levels?

2) I am assuming that choice and case nodes are "transparent"  wrt nest-levels. Is this the case?
That is, for the following resource


Container alpha {

     choice interface-type {
         case a {
             leaf foo { ... }
         }
         case b {
             container bar { ...}
         }
     }


}


For a get for "alpha" and depth = 1, the leaf "foo" should be returned if it existed. "Bar" would not be returned if it existed.

Thanks,

Alberto